On Sat, 2013-01-26 at 21:34 +0100, Erik Braun wrote: > Package: src:linux > Version: 3.2.35-2 > Severity: normal > > Dear Maintainer, > > I know, that the information I can give is most likely not enough for > 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? > >From time to time, about every two weeks, it happens, that the system > stalls. It is ping-able, but it's not possible to connect via ssh or > to use existing SSH-sessions. > 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? Ben. -- Ben Hutchings Experience is what causes a person to make new mistakes instead of old ones.
Attachment:
signature.asc
Description: This is a digitally signed message part