Re: PROBLEM: kernel BUG at lib/kernel_lock.c:199!

["Fabio d'Alessi" <cars@bio.unipd.it>]

Jesper,
okay I will see if I can resolve this issue by removing the
module (and, obviously, making it so that it does not get
loaded at all). One more thing I noticed way up in the message
log (hadn't noticed them at first):

Feb  2 15:32:53 telethon ainit: Memory: Failed to release semaphore
Feb  2 15:32:53 telethon ainit: Error: No such file or directory
Feb  2 15:32:53 telethon ainit: Memory: Failed to release SHM segment
Feb  2 15:32:53 telethon ainit: Error: No such file or directory
Feb  2 15:32:53 telethon ainit: Memory: Failed to release SHM segment
Feb  2 15:32:53 telethon ainit: Error: No such file or directory
Feb  2 15:32:53 telethon ainit: No such file or directory
Feb  2 15:32:53 telethon ainit: Memory: Failed to release semaphore
Feb  2 15:32:53 telethon ainit: Error: No such file or directory
Feb  2 15:32:53 telethon ainit: Memory: Failed to release SHM segment
Feb  2 15:32:53 telethon ainit: Error: No such file or directory
Feb  2 15:32:53 telethon ainit: Memory: Failed to release SHM segment
Feb  2 15:32:53 telethon ainit: Error: No such file or directory
Feb  2 15:32:53 telethon ainit: No such file or directory

looked it up on google and it seems to be related to a bug
that causes the kernel to lock under various circumstances,
see http://lkml.org/lkml/2006/1/12/282

I wonder if it's related to the hardlock I'm having here.

Thanks again for the kind feedback.

fda




Jesper Juhl wrote:
> On 2/2/06, Fabio d'Alessi <cars@bio.unipd.it> wrote:
>> Dear sirs,
>> I have a problem with a dual athlon xp running fedora/4
>> with the 2.6.14-1 kernel. Hard locks. Please if anyone
> [...]
>> [7.1] standard fedora 4 install - nothing new added, just the
>> drivers for the nv graphic board.
>>
> Adding the binary only nvidia module is not a little thing.
> That driver is a closed source binary blob that noone here has a
> chance to debug.
> 
> You can switch to the 'nv' driver and see if you still have the
> problem. The nv driver won't give you accelerated 3D, but for 2D it
> should work just fine.
> 
> [...]
>> nvidia 4095984 12 - Live 0xf8f31000
> [...]
> Please try to reproduce without the nvidia driver ever being loaded -
> just unloading it is *not* good enough, it needs to have never been
> loaded at all.
> As long as that (or any other binary-only module for that matter) has
> been loaded into the kernel for just a second it's impossible to say
> if that module or some other part of the kernel is the cause of the
> problem.
> 
> 
> --
> Jesper Juhl <jesper.juhl@gmail.com>
> Don't top-post  http://www.catb.org/~esr/jargon/html/T/top-post.html
> Plain text mails only, please      http://www.expita.com/nomime.html
>