From: Jean-Christophe Le Lann <jc.lelann@wanadoo.fr>
To: linux-hotplug@vger.kernel.org
Subject: SCSI error, Buffer I/O error on device sda, wait_for_sysfs
Date: Sun, 12 Dec 2004 17:48:10 +0000 [thread overview]
Message-ID: <1102873691.3268.3.camel@localhost.localdomain> (raw)
Hi,
I have a serious bug in FC3, when connecting a USB key.
I am asked to send you this report.
Hope this helps !
JC
Here is the log :
Dec 8 23:04:42 localhost kernel: ohci_hcd 0000:00:07.4: wakeup
Dec 8 23:04:43 localhost kernel: usb 1-1: new full speed USB device
using address 2
Dec 8 23:04:45 localhost kernel: SCSI subsystem initialized
Dec 8 23:04:45 localhost kernel: Initializing USB Mass Storage
driver...
Dec 8 23:04:45 localhost kernel: scsi0 : SCSI emulation for USB Mass
Storage devices
Dec 8 23:04:45 localhost kernel: Vendor: LEXAR Model: JUMPDRIVE
PRO Rev: 0
Dec 8 23:04:45 localhost kernel: Type: Direct-Access
ANSI SCSI revision: 02
Dec 8 23:04:46 localhost kernel: usbcore: registered new driver usb-
storage
Dec 8 23:04:46 localhost kernel: USB Mass Storage support registered.
Dec 8 23:04:46 localhost scsi.agent[3866]: disk
at /devices/pci0000:00/0000:00:07.4/usb1/1-1/1-1:1.0/host0/0:0:0:0
Dec 8 23:04:46 localhost kernel: SCSI device sda: 503808 512-byte hdwr
sectors (258 MB)
Dec 8 23:04:46 localhost kernel: sda: Write Protect is off
Dec 8 23:04:46 localhost kernel: sda: assuming drive cache: write
through
Dec 8 23:04:46 localhost kernel: sda:<3>hub 1-0:1.0: port 1 disabled
by hub (EMI?), re-enabling...
Dec 8 23:04:46 localhost kernel: usb 1-1: USB disconnect, address 2
Dec 8 23:04:46 localhost kernel: SCSI error : <0 0 0 0> return code 0x70000
Dec 8 23:04:46 localhost kernel: end_request: I/O error, dev sda,
sector 0
Dec 8 23:04:46 localhost kernel: Buffer I/O error on device sda,
logical block 0
Dec 8 23:04:52 localhost wait_for_sysfs[3901]: either wait_for_sysfs
(udev 039) needs an update to handle the device '/block/sda' properly
(no bus device link) or the sysfs-support of your device's driver needs
to be fixed, please report to <linux-hotplug-
devel@lists.sourceforge.net>
Dec 8 23:05:16 localhost kernel: scsi: Device offlined - not ready
after error recovery: host 0 channel 0 id 0 lun 0
Dec 8 23:05:16 localhost kernel: sd 0:0:0:0: Illegal state transition
cancel->offline
Dec 8 23:05:16 localhost kernel: Badness in scsi_device_set_state at
drivers/scsi/scsi_lib.c:1688
Dec 8 23:05:16 localhost kernel: [<12a84645>] scsi_device_set_state
+0xc8/0xd3 [scsi_mod]
Dec 8 23:05:16 localhost kernel: [<12a81b8b>] scsi_eh_offline_sdevs
+0x49/0x5e [scsi_mod]
Dec 8 23:05:16 localhost kernel: [<12a82146>] scsi_unjam_host
+0x22d/0x23e [scsi_mod]
Dec 8 23:05:16 localhost kernel: [<12a82291>] scsi_error_handler
+0x13a/0x191 [scsi_mod]
Dec 8 23:05:16 localhost kernel: [<0211b3d9>] schedule_tail+0xc/0x37
Dec 8 23:05:16 localhost kernel: [<12a82157>] scsi_error_handler
+0x0/0x191 [scsi_mod]
Dec 8 23:05:16 localhost kernel: [<021041d9>] kernel_thread_helper
+0x5/0xb
Dec 8 23:05:46 localhost kernel: scsi: Device offlined - not ready
after error recovery: host 0 channel 0 id 0 lun 0
Dec 8 23:05:46 localhost kernel: sd 0:0:0:0: Illegal state transition
cancel->offline
Dec 8 23:05:46 localhost kernel: Badness in scsi_device_set_state at
drivers/scsi/scsi_lib.c:1688
Dec 8 23:05:46 localhost kernel: [<12a84645>] scsi_device_set_state
+0xc8/0xd3 [scsi_mod]
Dec 8 23:05:46 localhost kernel: [<12a81b8b>] scsi_eh_offline_sdevs
+0x49/0x5e [scsi_mod]
Dec 8 23:05:46 localhost kernel: [<12a82146>] scsi_unjam_host
+0x22d/0x23e [scsi_mod]
Dec 8 23:05:46 localhost kernel: [<12a7e5c5>] __scsi_iterate_devices
+0x123/0x12b [scsi_mod]
Dec 8 23:05:46 localhost kernel: [<12a82291>] scsi_error_handler
+0x13a/0x191 [scsi_mod]
Dec 8 23:05:46 localhost kernel: [<0211b3d9>] schedule_tail+0xc/0x37
Dec 8 23:05:46 localhost kernel: [<12a82157>] scsi_error_handler
+0x0/0x191 [scsi_mod]
Dec 8 23:05:46 localhost kernel: [<021041d9>] kernel_thread_helper
+0x5/0xb
Dec 8 23:05:46 localhost kernel: Unable to handle kernel NULL pointer
dereference at virtual address 00000008
Dec 8 23:05:46 localhost kernel: printing eip:
Dec 8 23:05:46 localhost kernel: 0224fb8f
Dec 8 23:05:46 localhost kernel: *pde = 00000000
Dec 8 23:05:46 localhost kernel: Oops: 0000 [#1]
Dec 8 23:05:46 localhost kernel: Modules linked in: sd_mod usb_storage
scsi_mod parport_pc lp parport autofs4 sunrpc ppp_synctty ppp_async
crc_ccitt ppp_generic slhc ipt_REJECT ipt_state ip_conntrack
iptable_filter ip_tables dm_mod md5 ipv6 ohci_hcd snd_ens1371
snd_rawmidi snd_seq_device snd_pcm_oss snd_mixer_oss snd_pcm snd_timer
snd_page_alloc snd_ac97_codec snd soundcore gameport via_rhine mii
floppy ext3 jbd
Dec 8 23:05:46 localhost kernel: CPU: 0
Dec 8 23:05:46 localhost kernel: EIP: 0060:[<0224fb8f>] Not
tainted VLI
Dec 8 23:05:46 localhost kernel: EFLAGS: 00010046 (2.6.9-1.667)
Dec 8 23:05:46 localhost kernel: EIP is at cfq_insert_request+0x45/0xdf
Dec 8 23:05:46 localhost kernel: eax: 11c344b8 ebx: 118bc2cc ecx:
00000001 edx: 118bc2cc
Dec 8 23:05:46 localhost kernel: esi: 00000001 edi: 00000000 ebp:
11c56808 esp: 03ffaefc
Dec 8 23:05:46 localhost kernel: ds: 007b es: 007b ss: 0068
Dec 8 23:05:46 localhost kernel: Process scsi_eh_0 (pid: 3844,
threadinfo\x03ffa000 task\x033f0bf0)
Dec 8 23:05:46 localhost kernel: Stack: 11c344b8 11c344b8 00000001
118bc2cc 00000206 02246367 11c344b8 00000001
Dec 8 23:05:46 localhost kernel: 118bc2cc 02246329 00000000
022484d8 0c937c40 10550800 0576c000 00001057
Dec 8 23:05:46 localhost kernel: 12a82576 0c937c40 00000001
0c937c40 03ffaf74 03ffaf74 03ffaf7c 12a81ec8
Dec 8 23:05:46 localhost kernel: Call Trace:
Dec 8 23:05:46 localhost kernel: [<02246367>] __elv_add_request
+0x3c/0x71
Dec 8 23:05:46 localhost kernel: [<02246329>] elv_requeue_request
+0x29/0x2b
Dec 8 23:05:46 localhost kernel: [<022484d8>] blk_insert_request
+0xba/0x18b
Dec 8 23:05:46 localhost kernel: [<12a82576>] scsi_queue_insert
+0x84/0x8d [scsi_mod]
Dec 8 23:05:46 localhost kernel: [<12a81ec8>] scsi_eh_flush_done_q
+0x7d/0xce [scsi_mod]
Dec 8 23:05:46 localhost kernel: [<12a8214f>] scsi_unjam_host
+0x236/0x23e [scsi_mod]
Dec 8 23:05:46 localhost kernel: [<12a7e5c5>] __scsi_iterate_devices
+0x123/0x12b [scsi_mod]
Dec 8 23:05:46 localhost kernel: [<12a82291>] scsi_error_handler
+0x13a/0x191 [scsi_mod]
Dec 8 23:05:46 localhost kernel: [<0211b3d9>] schedule_tail+0xc/0x37
Dec 8 23:05:46 localhost kernel: [<12a82157>] scsi_error_handler
+0x0/0x191 [scsi_mod]
Dec 8 23:05:46 localhost kernel: [<021041d9>] kernel_thread_helper
+0x5/0xb
Dec 8 23:05:46 localhost kernel: Code: 74 29 eb 51 83 f9 03 74 33 eb 4a
8b 04 24 89 fa e8 f8 fa ff ff 85 c0 75 f2 8b 47 08 8b 50 04 89 03 89 58
04 89 1a 89 53 04 eb 3f <8b> 47 08 8b 10 89 5a 04 89 13 89 43 04 89 18
eb 2e f6 42 08 10
Dec 8 23:06:34 localhost kernel: Badness in kref_get at lib/kref.c:32
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://productguide.itmanagersjournal.com/
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
next reply other threads:[~2004-12-12 17:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-12 17:48 Jean-Christophe Le Lann [this message]
2004-12-13 1:28 ` SCSI error, Buffer I/O error on device sda, wait_for_sysfs Kay Sievers
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1102873691.3268.3.camel@localhost.localdomain \
--to=jc.lelann@wanadoo.fr \
--cc=linux-hotplug@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).