Hyper Threading

eyagos

- Using Foobar2000 the system hangs when changing song: This player has 4 options for output: "Direct Sound", "Direct Sound v2.0", "Wave Out" and "Kernel Streaming". And ONLY with the "WaveOut" method the system hangs when playing/changing track. Probably here is the problem.

For example when using DirectSound v2.0, there is no hang, but I have some error messages in "monitor". Here is a sequence:

- The hangs are not pressent if I disable Hyper Threading in the BIOS. And when HT is diabled, a new option called "APIC" is abaliable and activated. Don't know if this can help.


----Hardware / Software configuration---------------
Driver Name:kX Audio Driver (Debug)
Driver Date: Nov 9 2003 23:06:09
Driver Version: 5.10.00.3536 - debug
DB Name:non
SB0240 10k2 [b400]
PCI Information:
Device: 41102 Subsys: 10021102 ChipRev: 4
Card is '10k2'
Card has MPU device
Card model is '5.1'
Card is Audigy2-compatible
Card HAS AC97 codec
Codec name: SigmaTel STAC9721/23
3D Extension: SigmaTel 3D Enhancement
Codec is 2.0 compliant
Capabilities[6940] :
DAC resolutions : -16-bit- -18-bit-
ADC resolutions : -16-bit- -18-bit-
Ext Capabilities [200]: -slot/DAC mappings-
Port: b400 Irq: 0xa(10)
Playback buffer: 20a0
Record buffer: 4000
Number of AC3 buffers: 4
Tank memory: 256 kb
GSIF buffer: 256 samples
OS version: [2 5 1 Service Pack 1; 2 5 1 Service Pack 1; 156 148]
----------------------------------------------------

Eugene Gavrilov

ok... strange...

I'll include some -additional- debugging information in the 3536d release -- please re-post monitor's logs when 3536d is out

/E

eyagos

Well, lots of problems still with rc1

- When reset settings allways hangs.

- When reinitializing DSP:
- When playing sound in Direct Sound no lines sowed in Analizer. When with wave out, the analizer seems ok, but there are still hangs. And with the Analizer window opened the hang is "sure" in a 30 seconds:

This is what I have get. If I can do anymore...

My pc is a PIV2.6GH, 1GB RAM DDR in dual mode, chipset Intel 865PE, HT enabled. The other specs are in the above post.

Eugene Gavrilov

hmm.. bad news...

I will try to add a 'legacy' way of synchronization in the next dev. release (3534-compatible)

/E

Eugene Gavrilov

here's a new version of kx.sys available:

http://kx.maincore.nl/beta/kx.rar
download, unrar, replace, reboot

after that, open the monitor, run "kxctrl -shw 19 2"
watch its output & test the driver functionality...

[3536rc1 or 3536rc1.1 is assumed to be installed]

/Eugene

eyagos

Yep, seems more stable, but still produces errors and hangs...

- When playing music or cahnging track: No aparent HANGS
- When decoding AC3: Now I can decode AC3 with kx drivers without syncoization problems, not in other versions. (rc1.1 + new version of kx)

- But when resetting settings or when Analizer is opened, the PC hangs inmediatilly.


Thanks, and take it easy.

danespen

No hangs here with the new drivers, tried the following which before would cause bluescreen&hang:
1. Playing mp3 with winamp
2. Playing Hidden & Dangerous 2
3. KX menu --> Reset settings

Thank you, Eugene

Eugene Gavrilov

>> danespen

you mean the '3536rc1.1' + updated kx.sys + kxctrl -shw 19 2 ?

/E

eyagos

Ops, I have tested angain and:

1.- With instruction 'kxctrl -shw 19 2' aplyed, reseting settings doesn't hangs my computer.
2.- But with instruction 'kxctrl -shw 19 2' aplyed, and foobar2000 playing, reseting settings HANGS my computer.

But this could be logical if the reset settings function turns back the synchronization mode until the other things that hangs the computer. So I conclude that the '-shw 19 2' could solve the problem.

And other thing, when the analyzer window is opened and something is playing, the computer hangs too (allways).


PD: The last errors I have posted are true, with 'kxctrl -shw 19 2' aplyed.

danespen

>> you mean the '3536rc1.1' + updated kx.sys + kxctrl -shw 19 2 ?
Yes... sorry, thought I stated...

but... I can't do this:
>> after that, open the monitor, run "kxctrl -shw 19 2"

----------------------------
C:\Documents and Settings\Dan>kxctrl -shw 19 2
kX Driver Control Program
Copyright ® Eugene Gavrilov, 2001-2003. All rights reserved.
Error setting HW parameter

C:\Documents and Settings\Dan>
----------------------------

As you can see, kxctrl exits immediately
I also get no output in Monitor.

>> And other thing, when the analyzer window is opened and something is playing, the computer hangs too (allways).
Yes, same here... my first crash since installing the new drivers:
************************************************** *****************
1. Started Monitor:
Monitor Reader thread started
Monitor Remote reader thread started
Monitor -- end --
Closed monitor

2. Focused Winamp, pressed play, opened monitor:
Monitor Reader thread started
Monitor Remote reader thread started
-2.472442 Win32 core chain: pos 0: WA3 MP3 to PCM converter
-2.431539 Default kx_wdm: waveout open[82dc65f0;826cf000]: open(freq=48000; n_channels=2[2]; bps=16; type: Normal)
-2.472402 Win32 core chain: pos 1: Winamp 2x DSP Wrapper
-2.429419 Default kx_wdm: waveout open[82dc65f0;826a3000]: open(freq=44100; n_channels=2[2]; bps=16; type: Normal)
-2.472366 Win32 core chain: pos 2: WA3 crossfader
-2.472329 Win32 core chain: pos 3: DirectSound Output
Monitor -- end --
Closed monitor

3. Opened the analyzer "tab" in kxmixer

4. 3-4 seconds waiting time

5. 1 second of analyzer showing lots of colors (I can give you a cam capture if you want...)

6. Bluescreen

7. Reboot, opened Monitor:
Monitor Reader thread started
Monitor Remote reader thread started
-178.110068 Win32 [WMDM PMSP Service](1684): Calling StartServiceCtrlDispatcher()
-178.169255 Default tcaicchg.sys - GpdCreateDevice
-178.101817 Win32 [WMDM PMSP Service](1708): Entering CNTService::ServiceMain()
-178.101771 Win32 [WMDM PMSP Service](1708): Entering CNTService::Initialize()
-128.704539 Default kx_wdm: [CMiniportCtrl::NewStream]
-178.101734 Win32 [WMDM PMSP Service](1708): CNTService::SetStatus(1331632, 2)
-178.037657 Win32 [WMDM PMSP Service](1708): CNTService::SetStatus(1331632, 4)
-101.581219 Default NVCap: ADAPTERCLOSESTREAM --- StreamNumber=4 -#openStrms=(0)
-178.037432 Win32 [WMDM PMSP Service](1708): Leaving CNTService::Initialize()
-101.581214 Default NVCap: *********Last one out turns off the lights******************
-177.876749 Win32 [WMDM PMSP Service](1708): My service is runnig (0)...
-154.787156 Win32 DT3: TDIOpenSession
-154.786417 Win32 TCATDI: TCATDI service already started
-101.580873 Default NVTVSND: 9850 or unknown: PAL_B: Mute
-154.784037 Win32 DT3: TDIOpenGlobal
-154.784018 Win32 5555 hw-WaitBindEvent: Bind Event. get ownership of mutex
-154.783960 Win32 DT3: TDIOpenCard - QueryDosDevice for name = DTA_TCAITDI_{3D4A88D1-D62F-48CF-8D90-713D550736F7}
-154.783917 Win32 DT3: TDIOpenCard - Device not found
-154.783771 Win32 5555 hw-WaitBindEvent: Bind Event. release ownership of mutex
-154.783749 Win32 555511 hw-WaitBindEvent: Bind Event. get ownership of mutex
-154.783694 Win32 555511 hw-WaitBindEvent: Bind Event. release ownership of mutex
-152.797659 Win32 !!!!!!!Mutex_Index1 = 0
-152.797639 Win32 !!!!!!!Mutex_Index2 = 0
-152.797621 Win32 2222 hw-WaitBindEvent: Bind Event. get ownership of mutex
-152.797598 Win32 DT3: TDICloseCard
-152.797451 Win32 2222 hw-WaitBindEvent: Bind Event. release ownership of mutex
-152.797431 Win32 DT3: TDICloseSession
-152.797413 Win32 DT3: TDICloseAllAdapters
Monitor -- end --
************************************************** *****************

Anyway, I'm a bit confused concerning why I can't use kxctrl... should I use different parameters?

Eugene Gavrilov

>> reseting settings

yes, it resets the 'default' mode -- that is, right after 'reset_settings' you need to re-run kxctrl
do NOT run 'kxctrl' while any audio application is playing / recording
the best choice is to unload kxmixer, too

with this information in mind, does the 'analyzer' still causes the bug?..

>> danespen

turn HT off
download kxdrv 3536 rc1 -- install -- reboot
download kxdrv 3536 rc1.1 ''fix' -- install --reboot
download kx.rar (the link is above) -- install -- reboot

run 'kxctrl -shw'...

/Eugene

danespen

This took me half an hour with all those reboots... but still same result.
Are you sure it's me doing something wrong?
--------------------
C:\Documents and Settings\Dan>kxctrl -shw 19 2
kX Driver Control Program
Copyright ® Eugene Gavrilov, 2001-2003. All rights reserved.
Error setting HW parameter

C:\Documents and Settings\Dan>
--------------------

btw my soundcard is CT Live! 5.1 digital

eyagos

>yes, it resets the 'default' mode -- that is, right after 'reset_settings' you need to re-run kxctrl
>do NOT run 'kxctrl' while any audio application is playing / recording
>the best choice is to unload kxmixer, too

>with this information in mind, does the 'analyzer' still causes the bug?..


Yes, the anlyzer still causes the bug. The error report is some diferent now...

The bug appears when playing track with analyzer opened, and as you see it takes only two conssecutive erros, and five seconds to hang the computer.

And yesterday I experienced a hang after playing music for a while ( ~ 1 hour ), with the -shw 19 2 setting and with nothing more than player opened.

I don't know nothing about programing drivers, but it seems that the new driver stress too much to the little windows HAL. Could this problem be interpreted as an statistical problem? I mean, If you try the driver to be very precise, it could respond with 'lots' of instabilitys...

emmm... don't pay too many attention to this, but is evident that the new driver stress the system, and I'm asking myself if this would be neccesary since 3534 were 'more' stable.

By the way, I have installed the lastest dirvers for the 865PE chipset, but nothing.

Eugene Gavrilov

>> problem be interpreted as an statistical problem

no, I doubt
actually, the locking mechanism in 3534 was not HT/SMP-safe...
3535 & 3536 releases use a slightly different scheme which seems to cause deadlocks...

as for the 'analyzer': it uses the same hardware lock, as the rest of driver code
and this lock is not HT/SMP-safe

btw, you can try using 'kxctrl -shw 19 1" instead
(it uses a different scheme -- but this usually causes problems with UART devices )

btw, can you re-check if 3534 release outputs any debug messages, too?...
(as far as I remember, it should print 'BEWARE...' etc... on an SMP/HT machine)

>> danespen

your version of kx.sys is invalid
re-check everything

/E

eyagos

Ok, just a problem of strategy.


This log message is produced continuosly (many times per second) after a while playing music in 3534 version.

Eugene Gavrilov

after some [hard] time spent on imroving ht/smp compatibility, a completely new synchronization code was written
have a look at 3536rc2 -- should be compatible both with HT/SMP and non-SMP machines
no kxctrl tweak is necessary

(browse generic forum for the download link) -- here: http://www.hardwareheaven.com/showthre...threadid=31911

/Eugene