From: Nick Piggin <nickpiggin@yahoo.com.au>
To: Pedro Larroy <piotr@larroy.com>
Cc: linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org,
linux-usb-devel@lists.sourceforge.net
Subject: Re: [BUG] 2.6.9-rc2 scsi and elevator oops when I/O error
Date: Mon, 11 Oct 2004 18:10:26 +1000 [thread overview]
Message-ID: <416A3FF2.3000206@yahoo.com.au> (raw)
In-Reply-To: <20041011050320.GA28703@larroy.com>
Pedro Larroy wrote:
> I've been observing this bug in other kernel versions and other hardware
> configurations, so I think it's easily reproductible.
>
> Happens when I/O error on external ide <-> usb drives. Can be reproduced
> by unplugging the usb cable while accessing the drive, or with a faulty
> drive.
>
> I don't think my real u2w scsi controllers would like the real scsi disks
> being hot swapped, so I haven't tried there.
>
> Regards.
>
Thanks. It looks like it may possibly not be an elevator specific
oops. Can you try booting with elevator=deadline and see if you can
reproduce the oops please?
[snip]
> SCSI error : <0 0 0 0> return code = 0x70000
> end_request: I/O error, dev sda, sector 10889005
> usb 4-1: USB disconnect, address 2
> SCSI error : <0 0 0 0> return code = 0x70000
> end_request: I/O error, dev sda, sector 10889006
> scsi: Device offlined - not ready after error recovery: host 0 channel 0 id 0 lun 0
> sd 0:0:0:0: Illegal state transition cancel->offline
> Badness in scsi_device_set_state at drivers/scsi/scsi_lib.c:1688
> [<c023a230>] scsi_device_set_state+0xbc/0x10a
> [<c0238605>] scsi_eh_offline_sdevs+0x5a/0x73
> [<c02389f4>] scsi_unjam_host+0xa7/0xa9
> [<c0238a8e>] scsi_error_handler+0x98/0xb7
> [<c02389f6>] scsi_error_handler+0x0/0xb7
> [<c0104249>] kernel_thread_helper+0x5/0xb
> SCSI error : <0 0 0 0> return code = 0x70000
> end_request: I/O error, dev sda, sector 10889007
> printk: 157 messages suppressed.
> Buffer I/O error on device sda1, logical block 10888944
> lost page write due to I/O error on sda1
> ------------[ cut here ]------------
> kernel BUG at drivers/block/as-iosched.c:1853!
> invalid operand: 0000 [#1]
> Modules linked in: hostap usbnet nfs nls_iso8859_1 nls_cp437 vfat fat nfsd exportfs lockd sunrpc parport_pc lp parport cls_fw sch_sfq sch_htb ipt_REJECT ipt_state iptable_filter iptable_nat ipt_helper ip_conntrack ipt_tos ipt_MARK iptable_mangle ip_tables ide_cd cdrom
> CPU: 0
> EIP: 0060:[<c02176f0>] Not tainted VLI
> EFLAGS: 00010283 (2.6.9-rc2)
> EIP is at as_exit+0x44/0x58
> eax: dedab58c ebx: dedab580 ecx: db995aa0 edx: db963ebc
> esi: ded301b4 edi: 00000286 ebp: dec174b4 esp: db963ef4
> ds: 007b es: 007b ss: 0068
> Process scsi_eh_0 (pid: 1550, threadinfo=db962000 task=db995aa0)
> Stack: ded30128 c020fc40 c021179b db911824 db911800 c023ba5b db9119a8 c03963a8
> c03963c0 dec174d8 c020c371 c0116abe 00000000 c0380a80 c1627d00 c019af91
> db9119c0 c019af93 00000000 db911800 c019b263 00000000 c030eabc 00000000
> Call Trace:
> [<c020fc40>] elevator_exit+0xd/0xf
> [<c021179b>] blk_cleanup_queue+0x31/0x78
> [<c023ba5b>] scsi_device_dev_release+0xc6/0xd5
> [<c020c371>] device_release+0x53/0x57
> [<c0116abe>] recalc_task_prio+0x8f/0x183
> [<c019af91>] kobject_cleanup+0x8c/0x8e
> [<c019af93>] kobject_release+0x0/0x8
> [<c019b263>] kref_put+0x34/0x8d
> [<c030eabc>] __up_wakeup+0x8/0xc
> [<c0235a3e>] scsi_done+0x0/0x16
> [<c0235e63>] __scsi_iterate_devices+0x47/0x51
> [<c023821f>] scsi_eh_stu+0x80/0xd8
> [<c023887c>] scsi_eh_ready_devs+0x19/0x6e
> [<c02389f4>] scsi_unjam_host+0xa7/0xa9
> [<c0238a8e>] scsi_error_handler+0x98/0xb7
> [<c02389f6>] scsi_error_handler+0x0/0xb7
> [<c0104249>] kernel_thread_helper+0x5/0xb
> Code: 8d 43 0c 39 43 0c 75 23 8b 43 70 e8 fa ab f1 ff 8b 83 cc 00 00 00 e8 ae ba ff ff 8b 43 30 e8 51 f9 f1 ff 89 d8 5b e9 49 f9 f1 ff <0f> 0b 3d 07 f8 9b 33 c0 eb d3 0f 0b 3c 07 f8 9b 33 c0 eb c1 55
>
next prev parent reply other threads:[~2004-10-11 8:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-11 5:03 [BUG] 2.6.9-rc2 scsi and elevator oops when I/O error Pedro Larroy
2004-10-11 8:10 ` Nick Piggin [this message]
2004-10-11 9:50 ` Jens Axboe
2004-10-11 14:03 ` James Bottomley
2004-10-11 19:07 ` [linux-usb-devel] " Alan Stern
2004-10-11 15:12 ` Pedro Larroy
2004-10-11 15:24 ` Pedro Larroy
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=416A3FF2.3000206@yahoo.com.au \
--to=nickpiggin@yahoo.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=linux-usb-devel@lists.sourceforge.net \
--cc=piotr@larroy.com \
/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).