[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#594845: Acknowledgement (linux-image-2.6.32-5-amd64: kernel BUG at /build/buildd-linux-2.6_2.6.32-20-amd64-lNUT1p/..../fs/sysfs/file.c:539)



On Mon, 2010-08-30 at 14:48 +0100, Ben Hutchings wrote: 
> On Mon, 2010-08-30 at 17:34 +1000, Russell Stuart wrote:
> > The problem disappears in
> > linux-image-2.6.35-trunk-amd64_2.6.35-1~experimental.2.
> 
> Yes, as I expected.
> 
> Can you please test the attached patch against the version in unstable?
> Directions for rebuilding an official kernel package are at
> <http://kernel-handbook.alioth.debian.org/ch-common-tasks.html#s-common-official>.

Applied that.  It changed the problem.

Before I got a nice repeatable BUG.  Now the openvpn instance
unconditionally segfaults and normally nothing appears on the console or
in kern.log.  Once I got "lucky" and this appeared on the console:

        Message from syslogd@toby at Sep  4 09:11:57 ...
         kernel:[52062.327222] ------------[ cut here ]------------
        
        Message from syslogd@toby at Sep  4 09:11:57 ...
         kernel:[52062.329577] invalid opcode: 0000 [#1] SMP 
        
        Message from syslogd@toby at Sep  4 09:11:57 ...
         kernel:[52062.330671] last sysfs
        file: /sys/devices/virtual/misc/tun/uevent
        
        Message from syslogd@toby at Sep  4 09:11:57 ...
         kernel:[52062.330671] Stack:
        
        Message from syslogd@toby at Sep  4 09:11:57 ...
         kernel:[52062.330671] Call Trace:
        
        Message from syslogd@toby at Sep  4 09:11:57 ...
         kernel:[52062.330671] Code: 74 0f 48 89 ef e8 24 07 00 00 eb 05
        bb fe ff ff ff 89 d8 5b 5d 41 5c c3 48 85 ff 74 0e 48 8b 7f 30
        48 85 ff 74 05 48 85 f6 75 04 <0f> 0b eb fe ba 02 00 00 00 e9 5d
        ff ff ff 55 53 48 89 fb 48 c7 

The machine appears to freeze in various ways - eg you can't get a login
prompt to have a sniff around and the first command you type at an
existing shell prompt that requires disk IO freezes, and a "sleep 300;
sudo reboot -f" doesn't do anything.  On the other hand a "for f in
$(seq 1000); do echo $f; sleep 1; done" continues on as though nothing
has happened.  Disk IO is probably borked.




Reply to: