* kernel BUG at drivers/usb/storage/usb.c:848
@ 2004-07-01 10:18 Markus Schaber
2004-07-02 22:49 ` Greg KH
0 siblings, 1 reply; 3+ messages in thread
From: Markus Schaber @ 2004-07-01 10:18 UTC (permalink / raw)
To: Linux Kernel Mailing List
Hello,
Running Kernel 2.6.4-mm2 (We use an mm2 kernel because of problems with
highmem and cryto-loop playing together which seemed to be solved in
mm2) and dd'ing from a IDE disk in an external USB case, the following
just happened (from /var/log/syslog):
Jul 1 12:05:36 kingfisher kernel: usb 1-5: USB disconnect, address 3
Jul 1 12:05:36 kingfisher kernel: SCSI error : <5 0 0 0> return code = 0x50000
Jul 1 12:05:36 kingfisher kernel: end_request: I/O error, dev sda, sector 156301440
Jul 1 12:05:36 kingfisher kernel: Buffer I/O error on device sda, logical block 156301440
Jul 1 12:05:36 kingfisher kernel: SCSI error : <5 0 0 0> return code = 0x10000
Jul 1 12:05:36 kingfisher kernel: end_request: I/O error, dev sda, sector 156301441
Jul 1 12:05:36 kingfisher kernel: Buffer I/O error on device sda, logical block 156301441
Jul 1 12:05:36 kingfisher kernel: scsi5 (0:0): rejecting I/O to dead device
Jul 1 12:05:36 kingfisher kernel: Buffer I/O error on device sda, logical block 156301442
Jul 1 12:05:36 kingfisher kernel: Buffer I/O error on device sda, logical block 156301443
Jul 1 12:05:36 kingfisher kernel: Buffer I/O error on device sda, logical block 156301444
Jul 1 12:05:36 kingfisher kernel: Buffer I/O error on device sda, logical block 156301445
Jul 1 12:05:36 kingfisher kernel: Buffer I/O error on device sda, logical block 156301446
Jul 1 12:05:36 kingfisher kernel: Buffer I/O error on device sda, logical block 156301447
Jul 1 12:05:36 kingfisher kernel: Buffer I/O error on device sda, logical block 156301448
Jul 1 12:05:36 kingfisher kernel: Buffer I/O error on device sda, logical block 156301449
Jul 1 12:05:36 kingfisher kernel: Buffer I/O error on device sda, logical block 156301450
Jul 1 12:05:36 kingfisher kernel: Buffer I/O error on device sda, logical block 156301451
Jul 1 12:05:36 kingfisher kernel: Buffer I/O error on device sda, logical block 156301452
Jul 1 12:05:36 kingfisher kernel: Buffer I/O error on device sda, logical block 156301453
Jul 1 12:05:36 kingfisher kernel: Buffer I/O error on device sda, logical block 156301454
Jul 1 12:05:36 kingfisher kernel: Buffer I/O error on device sda, logical block 156301455
Jul 1 12:05:36 kingfisher kernel: Buffer I/O error on device sda, logical block 156301456
Jul 1 12:05:36 kingfisher kernel: Buffer I/O error on device sda, logical block 156301457
Jul 1 12:05:36 kingfisher kernel: Buffer I/O error on device sda, logical block 156301458
Jul 1 12:05:36 kingfisher kernel: Buffer I/O error on device sda, logical block 156301459
Jul 1 12:05:36 kingfisher kernel: Buffer I/O error on device sda, logical block 156301460
Jul 1 12:05:36 kingfisher kernel: Buffer I/O error on device sda, logical block 156301461
Jul 1 12:05:36 kingfisher kernel: Buffer I/O error on device sda, logical block 156301462
Jul 1 12:05:36 kingfisher kernel: Buffer I/O error on device sda, logical block 156301463
Jul 1 12:05:36 kingfisher kernel: Buffer I/O error on device sda, logical block 156301464
Jul 1 12:05:36 kingfisher kernel: Buffer I/O error on device sda, logical block 156301465
Jul 1 12:05:36 kingfisher kernel: Buffer I/O error on device sda, logical block 156301466
Jul 1 12:05:36 kingfisher kernel: Buffer I/O error on device sda, logical block 156301467
Jul 1 12:05:36 kingfisher kernel: Buffer I/O error on device sda, logical block 156301468
Jul 1 12:05:36 kingfisher kernel: Buffer I/O error on device sda, logical block 156301469
Jul 1 12:05:36 kingfisher kernel: Buffer I/O error on device sda, logical block 156301470
Jul 1 12:05:36 kingfisher kernel: Buffer I/O error on device sda, logical block 156301471
Jul 1 12:05:36 kingfisher kernel: Buffer I/O error on device sda, logical block 156301472
Jul 1 12:05:36 kingfisher kernel: Buffer I/O error on device sda, logical block 156301473
Jul 1 12:05:36 kingfisher kernel: Buffer I/O error on device sda, logical block 156301474
Jul 1 12:05:36 kingfisher kernel: Buffer I/O error on device sda, logical block 156301475
Jul 1 12:05:36 kingfisher kernel: Buffer I/O error on device sda, logical block 156301476
Jul 1 12:05:36 kingfisher kernel: Buffer I/O error on device sda, logical block 156301477
Jul 1 12:05:36 kingfisher kernel: Buffer I/O error on device sda, logical block 156301478
Jul 1 12:05:36 kingfisher kernel: Buffer I/O error on device sda, logical block 156301479
Jul 1 12:05:36 kingfisher kernel: Buffer I/O error on device sda, logical block 156301480
Jul 1 12:05:36 kingfisher kernel: Buffer I/O error on device sda, logical block 156301481
Jul 1 12:05:36 kingfisher kernel: Buffer I/O error on device sda, logical block 156301482
Jul 1 12:05:36 kingfisher kernel: Buffer I/O error on device sda, logical block 156301483
Jul 1 12:05:36 kingfisher kernel: Buffer I/O error on device sda, logical block 156301484
Jul 1 12:05:36 kingfisher kernel: Buffer I/O error on device sda, logical block 156301485
Jul 1 12:05:36 kingfisher kernel: Buffer I/O error on device sda, logical block 156301486
Jul 1 12:05:36 kingfisher kernel: Buffer I/O error on device sda, logical block 156301487
Jul 1 12:05:36 kingfisher kernel: Buffer I/O error on device sda, logical block 156301488
Jul 1 12:05:37 kingfisher kernel: ------------[ cut here ]------------
Jul 1 12:05:37 kingfisher kernel: kernel BUG at drivers/usb/storage/usb.c:848!
Jul 1 12:05:37 kingfisher kernel: invalid operand: 0000 [#1]
Jul 1 12:05:37 kingfisher kernel: PREEMPT
Jul 1 12:05:37 kingfisher kernel: CPU: 0
Jul 1 12:05:37 kingfisher kernel: EIP: 0060:[<c02d0b77>] Not tainted VLI
Jul 1 12:05:37 kingfisher kernel: EFLAGS: 00010202 (2.6.4-mm2-uli)
Jul 1 12:05:37 kingfisher kernel: EIP is at usb_stor_release_resources+0xa2/0xc9
Jul 1 12:05:37 kingfisher kernel: eax: 000062fe ebx: e5487c00 ecx: c0432ea8 edx: ef533ad8
Jul 1 12:05:37 kingfisher kernel: esi: c0439100 edi: f7e81f0c ebp: f7e81f08 esp: f7e81e88
Jul 1 12:05:37 kingfisher kernel: ds: 007b es: 007b ss: 0068
Jul 1 12:05:37 kingfisher kernel: Process khubd (pid: 5, threadinfo=f7e80000 task=f7f98030)
Jul 1 12:05:37 kingfisher kernel: Stack: ef533ad8 f5c39280 c02ba53b e5487c00 f5c39280 ee0a6780 f5c39294 c0439120
Jul 1 12:05:37 kingfisher kernel: c0263e35 f5c39294 f5c392bc f5c39294 d838b8cc c0263f59 f5c39294 f5c392ec
Jul 1 12:05:37 kingfisher kernel: f5c39294 d838b8cc c0263026 f5c39294 f5c39294 d838b800 c0263077 f5c39294
Jul 1 12:05:37 kingfisher kernel: Call Trace:
Jul 1 12:05:37 kingfisher kernel: [<c02ba53b>] usb_unbind_interface+0x7b/0x7d
Jul 1 12:05:37 kingfisher kernel: [<c0263e35>] device_release_driver+0x64/0x66
Jul 1 12:05:37 kingfisher kernel: [<c0263f59>] bus_remove_device+0x55/0x96
Jul 1 12:05:37 kingfisher kernel: [<c0263026>] device_del+0x5d/0x9b
Jul 1 12:05:37 kingfisher kernel: [<c0263077>] device_unregister+0x13/0x23
Jul 1 12:05:37 kingfisher kernel: [<c02bffff>] usb_disable_device+0x76/0xd7
Jul 1 12:05:37 kingfisher kernel: [<c011eeb6>] printk+0x134/0x184
Jul 1 12:05:37 kingfisher kernel: [<c02bb005>] usb_disconnect+0x9b/0xe8
Jul 1 12:05:37 kingfisher kernel: [<c02bcdcb>] hub_port_connect_change+0x272/0x277
Jul 1 12:05:37 kingfisher kernel: [<c02bc7b9>] hub_port_status+0x45/0xb0
Jul 1 12:05:37 kingfisher kernel: [<c02bd0a3>] hub_events+0x2d3/0x346
Jul 1 12:05:37 kingfisher kernel: [<c02bd143>] hub_thread+0x2d/0xe4
Jul 1 12:05:37 kingfisher kernel: [<c037996a>] ret_from_fork+0x6/0x14
Jul 1 12:05:37 kingfisher kernel: [<c011b024>] default_wake_function+0x0/0x12
Jul 1 12:05:37 kingfisher kernel: [<c02bd116>] hub_thread+0x0/0xe4
Jul 1 12:05:37 kingfisher kernel: [<c010725d>] kernel_thread_helper+0x5/0xb
Jul 1 12:05:37 kingfisher kernel:
Jul 1 12:05:37 kingfisher kernel: Code: 24 04 83 c4 08 e9 cc d9 e6 ff 89 04 24 e8 0b e4 fe ff eb e6 89 04 24 e8 ba d9 e6 ff eb d2 8b 83 20 01 00 00 89 04 24 ff d2 eb bb <0f> 0b 50 03 2b 96 3b c0 eb 80 c7 80 d0 01 00 00 00 00 00 00 8b
The symptoms are that "ps aux" shows all processes trying to access the
disk (including the dd command) in D+ state, and the kernel does not
recognize that I removed and re-plugged USB devices in this slot. (I did
not test unplugging the other of the two USB slots I have because that's
my mouse :-)
Is this a known issue that is solved in later kernels?
Thanks,
Markus
--
markus schaber | dipl. informatiker
logi-track ag | rennweg 14-16 | ch 8001 zürich
phone +41-43-888 62 52 | fax +41-43-888 62 53
mailto:schabios@logi-track.com | www.logi-track.com
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: kernel BUG at drivers/usb/storage/usb.c:848
2004-07-01 10:18 kernel BUG at drivers/usb/storage/usb.c:848 Markus Schaber
@ 2004-07-02 22:49 ` Greg KH
2004-07-05 15:12 ` Markus Schaber
0 siblings, 1 reply; 3+ messages in thread
From: Greg KH @ 2004-07-02 22:49 UTC (permalink / raw)
To: Markus Schaber; +Cc: Linux Kernel Mailing List
On Thu, Jul 01, 2004 at 12:18:36PM +0200, Markus Schaber wrote:
> Hello,
>
> Running Kernel 2.6.4-mm2 (We use an mm2 kernel because of problems with
> highmem and cryto-loop playing together which seemed to be solved in
> mm2) and dd'ing from a IDE disk in an external USB case, the following
> just happened (from /var/log/syslog):
2.6.4-mm2 is quite an old kernel. Care to get a newer one to see if
this is still an issue or not?
thanks,
greg k-h
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: kernel BUG at drivers/usb/storage/usb.c:848
2004-07-02 22:49 ` Greg KH
@ 2004-07-05 15:12 ` Markus Schaber
0 siblings, 0 replies; 3+ messages in thread
From: Markus Schaber @ 2004-07-05 15:12 UTC (permalink / raw)
Cc: Linux Kernel Mailing List
Hi, Greg,
On Fri, 2 Jul 2004 15:49:27 -0700
Greg KH <greg@kroah.com> wrote:
> > Running Kernel 2.6.4-mm2 (We use an mm2 kernel because of problems
> > with highmem and cryto-loop playing together which seemed to be
> > solved in mm2) and dd'ing from a IDE disk in an external USB case,
> > the following just happened (from /var/log/syslog):
>
> 2.6.4-mm2 is quite an old kernel. Care to get a newer one to see if
> this is still an issue or not?
It's quite some effort to update those specific machines, but we planned
to update to 2.6.7 until we heared that there are some problems with
this version (especially, a co-worker of mine trying 2.6.7-mm1 on a
similar hardware and using both crypto-loop and highmem has had random
crashes, and some apps (including sun jdk 1.4) segfaulting on startup.).
Now we plan to update to some 2.6.6 version. Is dm-crypt considered
stable enough to give it a test shot? This way, we could get rid of
crypto-loop and thus avoid having to try the mm patches.
Thanks,
Markus
--
markus schaber | dipl. informatiker
logi-track ag | rennweg 14-16 | ch 8001 zürich
phone +41-43-888 62 52 | fax +41-43-888 62 53
mailto:schabios@logi-track.com | www.logi-track.com
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2004-07-05 15:12 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2004-07-01 10:18 kernel BUG at drivers/usb/storage/usb.c:848 Markus Schaber
2004-07-02 22:49 ` Greg KH
2004-07-05 15:12 ` Markus Schaber
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®