[Bug 182765] Re: kernel BUG at /build/buildd/linux-2.6.24/fs/attr.c:138!

Adam J Richardson fatman at crackmonkey.us
Fri Jun 13 10:25:02 UTC 2008

I also have an Oops!ed dmesg. I do not believe this is to do with the
sshfs package, for the following reason.

A few nights ago (10th June 2008, I believe) I followed the instructions


I followed the instructions to the letter *except* that I opted for ext3
instead of ext2. (I don't see that making a difference. Or could I be
mistaken?) The USB stick is a 4GB SanDisk Cruzer Crossfire.

After installing I booted into the standard "ubuntu" user and started a
system upgrade. The upgrade hung the whole system while "preparing to
unpack sudo", leaving only the magic SysRq method to safely restart the

I booted into single user mode and started poking around. The command
"dpkg --install --force-all
/var/cache/apt/archives/sudo_1.6.9p10-1ubuntu3_i386.deb" produces the
attached debug report, accessed by the command "dmesg | grep 450".

The segfault occurs on several machines with good, memtest86-passed RAM
in them. They are all multicore systems.

(The upshot of all this is that now I have no sudo command on this
system. It's actually not too much of a problem, because I can always
reboot into single user mode if I need to do any root stuff.)

Still, be nice to fix this. Is there a way?

** Attachment added: "Oops! in single user mode"

kernel BUG at /build/buildd/linux-2.6.24/fs/attr.c:138!
You received this bug notification because you are a member of Kernel
Bugs, which is subscribed to linux-meta in ubuntu.

More information about the kernel-bugs mailing list