On Tue, 1 Jul 2003, Adam Kessel wrote: > One more data point--I recently got the following error message. The > fact that it says kernel BUG suggests something wrong--should I forward > this report to the kernel list, or is it a USB problem? > --- > kernel BUG at fs/buffer.c:1161! > invalid operand: 0000 [#2] > CPU: 0 > EIP: 0060:[<c015208e>] Not tainted > EFLAGS: 00010206 > eax: 0000178f ebx: 00000200 ecx: 00001790 edx: 00001790 > esi: 00000200 edi: d7cdd540 ebp: 00000060 esp: c838bca4 > ds: 007b es: 007b ss: 0068 > Process ls (pid: 2065, threadinfo=c838a000 task=d29fa1c0) > Stack: d7cdd540 00000060 00000200 00000200 00000200 00000060 d7cdd540 00000000 > c015250f d7cdd540 00000060 00000200 d76fd000 00000000 00000000 c015253f > d7cdd540 00000060 00000200 d886c272 d7cdd540 00000060 00000200 c0161c1e > Call Trace: [<c015250f>] [<c015253f>] [<d886c272>] [<c0161c1e>] [<d886837b>] > [<d88769a0>] [<d88769a0>] [<c0134bec>] [<c0135cf7>] [<c0142025>] [<c0134bec>] > [<c0135cf7>] [<c0142025>] [<c01423b0>] [<c0116f2c>] [<d88684a9>] [<c0161b20>] > [<c01617fc>] [<c0161b20>] [<c0161cb1>] [<c0161b20>] [<c010932b>] > Code: 0f 0b 89 04 86 c7 2f c0 8d 86 00 fe ff ff 3d 00 0e 00 00 76
This isn't a USB problem, it's a problem with the filesystem code. That code doesn't expect devices to just vanish into thin air -- it's not yet ready to handle hot-unplugging. The fact that the message says BUG is just a result of the way the code that detects the error was written; don't worry about it. Also, the message itself is nearly meaningless, because the numerical values refer to addresses that are unique to _your_ particular kernel. You need to translate the numbers into symbolic values that will be meaningful to kernel developers; do this by running the text of the BUG report through the 'ksymoops' program. You can post the result on the kernel mailing list if you want, provided you explain the circumstances under which it occurred (filesystem failure when unplugging a mounted USB storage device). The response will probably be something like: "Don't unplug a device until you've unmounted it!" Of course, that's not much help when the device is failing. There's no reason to run a memory test on your machine, contrary to what Joshua Wise suggested. Alan Stern ------------------------------------------------------- This SF.Net email sponsored by: Free pre-built ASP.NET sites including Data Reports, E-commerce, Portals, and Forums are available now. Download today and enter to win an XBOX or Visual Studio .NET. http://aspnet.click-url.com/go/psa00100006ave/direct;at.asp_061203_01/01 _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
