A clarification: I did not think that the networking issue was caused by the oops; I thought that the networking issue might have been one of the things that triggered the oops. It might be completely unrelated, though.
After sending in the report I discovered that during a session of updating packages, fuse-utils had been updated. When I had a look at the terminal in which that was happening, this is what I saw: [...] Setting up fuse-utils (2.6.3-2) ... creating fuse device node... udev active, devices will be created in /dev/.static/dev/ creating fuse group... Starting filesystem in userspace: fuse/etc/init.d/fuse: line 30: 6332 Segmentation fault mount -t fusectl none $MOUNTPOINT >/dev/null 2>&1 Message from [EMAIL PROTECTED] at Wed Mar 28 17:24:50 2007 ... marmite kernel: ------------[ cut here ]------------ Message from [EMAIL PROTECTED] at Wed Mar 28 17:24:50 2007 ... marmite kernel: kernel BUG at fs/fuse/control.c:82! Message from [EMAIL PROTECTED] at Wed Mar 28 17:24:50 2007 ... marmite kernel: invalid opcode: 0000 [#1] Message from [EMAIL PROTECTED] at Wed Mar 28 17:24:50 2007 ... marmite kernel: SMP Message from [EMAIL PROTECTED] at Wed Mar 28 17:24:50 2007 ... marmite kernel: CPU: 0 Message from [EMAIL PROTECTED] at Wed Mar 28 17:24:50 2007 ... marmite kernel: EIP is at fuse_ctl_add_dentry+0x16/0xcb [fuse] failed! Message from [EMAIL PROTECTED] at Wed Mar 28 17:24:50 2007 ... marmite kernel: eax: c0621744 ebx: c0621744 ecx: ded63d80 edx: cd044d80 [...] -- Michael Wood <[EMAIL PROTECTED]> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
