Lockup with ALSA CVS on 2.4.19 SMP, 1 GB
Hi,
I tried reporting this a few days ago, but it seems as if the list is currently being moderated by a tame black hole. I have now subscribed ...
My machine run Linux 2.4.19 SMP, 1 GB memory (Highmem), has a SB Live! card and recently locked up completely after updating my ALSA kernel modules from CVS. All I had done to trigger it was to try and play a WAV file using aplay, but aplay did not even return before the keyboard, mouse and network connection all froze. After rebooting and fscking, I restored memory.c to version 1.19 and wrappers.c to version 1.5, recompiled, and everything was fine again. I have since stopped updating my CVS sources, of course.
Does anyone have hardware similar to mine (SMP + HIGHMEM) for comparison? I haven't noticed any other screams of pain recently, apart from ones relating to snd_pcm_hw_params_get_format().
Chris
__________________________________________________
Do You Yahoo!?
Everything you'll ever need on one web page from News and Sport to Email and Music Charts
http://uk.my.yahoo.com
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven.
http://thinkgeek.com/sf
At Mon, 16 Sep 2002 22:58:34 +0100 (BST),
Quoted 7 lines · Chris Rankin
Hi,
I tried reporting this a few days ago, but it seems as if the list is currently being moderated by a tame black hole. I have now subscribed ...
Quoted 10 lines
My machine run Linux 2.4.19 SMP, 1 GB memory (Highmem), has a SB Live! card and recently locked up completely after updating my ALSA kernel modules from CVS. All I had done to trigger it was to try and play a WAV file using aplay, but aplay did not even return before the keyboard, mouse and network connection all froze. After rebooting and fscking, I restored
memory.cto version 1.19 andwrappers.cto version 1.5, recompiled, and everything was fine again. I have since stopped updating my CVS sources, of course.
is yours the vanilla kernel?
i still don't figure out which part of the last change of pci_alloc_consistent hack affects it.
it's nothing bug calling pci_alloc_consistent() with a proper dma_mask.
anyway, could you try the attached patch?
ciao,
Takashi
Quoted 2 lines · --- Takashi Iwai
At Mon, 16 Sep 2002 22:58:34 +0100 (BST), is yours the vanilla kernel?
Yes, I compiled it myself using vanilla source. (2.4.19, SMP, HighMem, SB Live!)
Quoted 4 lines
i still don't figure out which part of the last change of
pci_alloc_consistenthack affects it. it's nothing bug callingpci_alloc_consistent()with a properdma_mask.
I have since rebooted the machine and reinstalled the very latest ALSA CVS drivers *without* applying your patch, and everything is currently working. However, I have currently got only about 30% of my 1GB RAM in use:
$ free -t
total used free shared
buffers cached
Mem: 1033544 311820 721724 0
16340 156860
-/+ buffers/cache: 138620 894924
Swap: 498004 0 498004
Total: 1531548 311820 1219728It is possible that the lock-up only occurs when the RAM is so heavily used that Linux has difficulty finding a DMA-able buffer. I know that the old snd_pci_hack_alloc_consistent() function failed gracefully in this case because I witnessed just such a failure (and posted it to this list). So maybe my box is doomed to lock-up again in a few days? I will be extra vigilant!
Chris
__________________________________________________
Do You Yahoo!?
Everything you'll ever need on one web page from News and Sport to Email and Music Charts
http://uk.my.yahoo.com
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven.
http://thinkgeek.com/sf