-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Thursday 12 February 2004 07:44, Andrew Morton wrote:
> Florian Schanda <ma1flfs@bath.ac.uk> wrote:
> > Sometimes (not allways, thats the problem, otherwise I could just avoid
> > the offending command) during paralel builds (for instance kde-libs or
> > kde-base) the build just stops, and I get a 99% system load.
> >
> Make sure that you have enabled CONFIG_KALLSYMS, and that
> /proc/sys/kernel/sysrq is set to one.  Then, when it hangs, do
>
> 	echo t > /proc/sysrq-trigger
>
> or type alt-sysrq-t
>
> Then, run
>
> 	dmesg -s 1000000 > /tmp/foo
>
> and make `foo' available.

Finally it happened again. I attached the output of that dmesg.

> It would help if you could make a note of the PIDs of the hung processes,
> so they can be correlated with the sysrq output.

The PIDs hanging are 3303, 3305, 3306, 3307.

An advance warning: I had the nvidia driver (yes, I know, closed source makes 
debugging impossible) loaded, and before the trace begins, there are some 
messages of that module:

1: NVRM: AGPGART: unable to retrieve symbol table
atkbd.c: Unknown key released (translated set 2, code 0x7a on isa0060/serio0).
atkbd.c: This is an XFree86 bug. It shouldn't access hardware directly.
atkbd.c: Unknown key released (translated set 2, code 0x7a on isa0060/serio0).
atkbd.c: This is an XFree86 bug. It shouldn't access hardware directly.
request_module: failed /sbin/modprobe -- block-major-3-0. error = 256
3: nvidia: trying to map 0xef9f1000 to kernel space, but we're in an interrupt 
or holding a spinlock
2: nvidia: trying to map 0xef9f1000 to kernel space, but we're in an interrupt 
or holding a spinlock
3: nvidia: trying to map 0xef9f1000 to kernel space, but we're in an interrupt 
or holding a spinlock
1: nvidia: trying to map 0xef9f1000 to kernel space, but we're in an interrupt 
or holding a spinlock
2: nvidia: trying to map 0xef9f1000 to kernel space, but we're in an interrupt 
or holding a spinlock
2: nvidia: trying to map 0xef9f1000 to kernel space, but we're in an interrupt 
or holding a spinlock

- From what I understand is I get some kind of deadlock, right?

Thanks in advance,

	Florian
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFAMoSbfCf8muQVS4cRAuvPAJ4upsbqfGCuP6NgrR1wtgH99S8R7ACdG9yh
GHbC6dZIwX65HDp7sFPg3sQ=
=sy7G
-----END PGP SIGNATURE-----