On Sun, 27 Jan 2013, Ben Hutchings wrote:

tracking the bug. The bad thing is, that I don't have direct access to the
console of the system, a 48-core machine with 512 GB main memory.

How about netconsole or an IPMI serial console?

The IPMI console is unreliable (connections are closed after a while; if the computer is stalled, it is just black). I just did not know the netconsole and started this now and will provide more information, if (when) the next Bug appears.

After rebooting, the following error is found in kern.log:

Jan 26 15:19:19 prost kernel: [798028.655254] ------------[ cut here 
]------------
Jan 26 15:19:19 prost kernel: [798028.659193] kernel BUG at 
/build/buildd-linux_3.2.35-2-amd64-v9djlH/linux-3.2.35/fs/locks.c:2104!
Jan 26 15:19:19 prost kernel: [798028.659193] invalid opcode: 0000 [#1] SMP
Jan 26 15:19:19 prost kernel: [798028.659193] CPU 0
[...]

That's all it says?  Nothing more before the next boot messages?

nothing.

Thank you,
Erik


--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/alpine.DEB.2.02.1301271623050.24948@kule.heimat

Reply via email to