From: Pat LaVarre <p.lavarre@ieee.org>
To: linux-scsi@vger.kernel.org
Subject: Re: sg MiB writes scheduling while atomic
Date: 10 Sep 2003 13:30:16 -0600 [thread overview]
Message-ID: <1063222216.3669.87.camel@patehci2> (raw)
In-Reply-To: <1063219776.3669.72.camel@patehci2>
By the way, I notice I can quickly repeat the first couple of lines of
Call Trace if I interrupt the default 0.25 MiB writes of sg_dd with
Ctrl+C:
> http://www.tldp.org/HOWTO/SCSI-Generic-HOWTO/sg3_utils.html
> Appendix A. Sg3_utils package
> variants of the Unix dd command:
> sg_dd, sgp_dd, sgq_dd and sgm_dd, ...
> ...
> http://www.torque.net/sg/
> http://www.torque.net/sg/p/sg3_utils-1.05.tgz
> $ tar -zx ...
> $ cd sg3_utils-1.05
> $ make
> $ sudo ./sg_scan -i
> $ sudo ./sg_dd of=/dev/sg1 if=/dev/zero bs=2k
> ^C
Where I quote ^C I mean I use Ctrl+C to interrupt sg i/o. I see I
provoke such dmsg as:
...
usb-storage: Command WRITE_10 (10 bytes)
usb-storage: 2a 00 00 00 0f 80 00 00 80 00
usb-storage: Bulk Command S 0x43425355 T 0x1dfbf L 262144 F 0 Trg 0 LUN 0 CL 10
usb-storage: usb_stor_bulk_transfer_buf: xfer 31 bytes
usb-storage: Status code 0; transferred 31/31
usb-storage: -- transfer complete
usb-storage: Bulk command transfer result=0
usb-storage: usb_stor_bulk_transfer_sglist: xfer 262144 bytes, 8 entries
usb-storage: Status code 0; transferred 262144/262144
usb-storage: -- transfer complete
usb-storage: Bulk data transfer result 0x0
usb-storage: Attempting to get CSW...
usb-storage: usb_stor_bulk_transfer_buf: xfer 13 bytes
usb-storage: Status code 0; transferred 13/13
usb-storage: -- transfer complete
usb-storage: Bulk status result = 0
usb-storage: Bulk Status S 0x53425355 T 0x1dfbf R 0 Stat 0x0
usb-storage: scsi cmd done, result=0x0
usb-storage: *** thread sleeping.
usb-storage: queuecommand called
usb-storage: *** thread awakened.
usb-storage: Command WRITE_10 (10 bytes)
usb-storage: 2a 00 00 00 10 00 00 00 80 00
usb-storage: Bulk Command S 0x43425355 T 0x1dfc0 L 262144 F 0 Trg 0 LUN 0 CL 10
usb-storage: usb_stor_bulk_transfer_buf: xfer 31 bytes
usb-storage: Status code 0; transferred 31/31
usb-storage: -- transfer complete
usb-storage: Bulk command transfer result=0
usb-storage: usb_stor_bulk_transfer_sglist: xfer 262144 bytes, 8 entries
usb-storage: Status code 0; transferred 262144/262144
usb-storage: -- transfer complete
usb-storage: Bulk data transfer result 0x0
usb-storage: Attempting to get CSW...
usb-storage: usb_stor_bulk_transfer_buf: xfer 13 bytes
usb-storage: Status code 0; transferred 13/13
usb-storage: -- transfer complete
usb-storage: Bulk status result = 0
usb-storage: Bulk Status S 0x53425355 T 0x1dfc0 R 0 Stat 0x0
usb-storage: scsi cmd done, result=0x0
usb-storage: *** thread sleeping.
Debug: sleeping function called from invalid context at include/linux/rwsem.h:66
Call Trace:
[<c0121f16>] __might_sleep+0x5f/0x72
[<c0280ec0>] scsi_device_put+0x3c/0xfe
[<df9263e3>] sg_cmd_done+0x19e/0x266 [sg]
[<c0280ba6>] scsi_finish_command+0x78/0xb0
[<c0280ad2>] scsi_softirq+0xb4/0xd9
[<c0128c0b>] do_softirq+0xd3/0xd5
[<c012912f>] ksoftirqd+0xbf/0xf8
[<c0129070>] ksoftirqd+0x0/0xf8
[<c0109245>] kernel_thread_helper+0x5/0xb
Another time:
Debug: sleeping function called from invalid context at include/linux/rwsem.h:66
Call Trace:
[<c0121f16>] __might_sleep+0x5f/0x72
[<c0280ec0>] scsi_device_put+0x3c/0xfe
[<df9263e3>] sg_cmd_done+0x19e/0x266 [sg]
[<c021fa59>] read_chan+0x0/0x98c
[<c0280ba6>] scsi_finish_command+0x78/0xb0
[<c0280ad2>] scsi_softirq+0xb4/0xd9
[<c0128c0b>] do_softirq+0xd3/0xd5
[<c011b4a0>] smp_apic_timer_interrupt+0xd8/0x140
[<c010beae>] apic_timer_interrupt+0x1a/0x20
next prev parent reply other threads:[~2003-09-10 19:29 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3F5E434D.6080801@unixsol.org>
2003-09-10 16:23 ` [linux-usb-devel] [2.6-test] Bug in usb-storage or scsi? Alan Stern
2003-09-10 18:16 ` [usb-storage] " Pat LaVarre
2003-09-10 18:49 ` sg MiB writes scheduling while atomic Pat LaVarre
2003-09-10 19:30 ` Pat LaVarre [this message]
2003-09-16 6:35 ` Douglas Gilbert
2003-09-16 11:42 ` Matthew Wilcox
2003-09-16 12:58 ` Christoph Hellwig
2003-10-14 23:36 ` Pat LaVarre
2003-09-10 20:08 ` [PATCH] mount -w of dvd+rw etc. in vanilla 2.6 Pat LaVarre
2003-09-10 22:49 ` Patrick Mansfield
2003-09-22 14:52 ` max GiB written per boot Pat LaVarre
2003-09-10 20:51 ` unsolicited sense in 2.6.0-test5 usb-storage.ko Pat LaVarre
2003-09-10 21:03 ` [usb-storage] " Alan Stern
2003-09-10 21:24 ` Pat LaVarre
2003-09-10 21:52 ` Matthew Dharm
2003-09-10 22:08 ` Pat LaVarre
2003-09-12 0:21 ` Pat LaVarre
2003-09-12 0:29 ` Pat LaVarre
2003-09-16 11:28 ` Douglas Gilbert
2003-09-11 0:02 ` [linux-usb-devel] [2.6-test] Bug in usb-storage or scsi? Patrick Mansfield
2003-09-11 20:04 ` [usb-storage] " Pat LaVarre
2003-09-11 20:05 ` Alan Stern
2003-09-11 20:19 ` James Bottomley
2003-09-12 21:17 ` Alan Stern
2003-09-11 20:42 ` Pat LaVarre
2003-09-12 19:59 ` Alan Stern
2003-09-12 19:18 ` Pat LaVarre
2003-09-12 18:43 ` Pat LaVarre
2003-09-12 20:56 ` Patrick Mansfield
2003-09-12 21:53 ` Pat LaVarre
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=1063222216.3669.87.camel@patehci2 \
--to=p.lavarre@ieee.org \
--cc=linux-scsi@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