linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alan Stern <stern@rowland.harvard.edu>
To: Nicolas Mailhot <Nicolas.Mailhot@laPoste.net>
Cc: USB development list <linux-usb-devel@lists.sourceforge.net>,
	<linux-kernel@vger.kernel.org>
Subject: Re: [Bug 1412] Copy from USB1 CF/SM reader stalls, no actual content is read (only directory structure)
Date: Sat, 1 Nov 2003 10:47:47 -0500 (EST)	[thread overview]
Message-ID: <Pine.LNX.4.44L0.0311011039330.18079-100000@netrider.rowland.org> (raw)
In-Reply-To: <1067633171.3886.1.camel@m70.net81-64-235.noos.fr>

On Fri, 31 Oct 2003, Nicolas Mailhot wrote:

> Le ven 31/10/2003 à 19:33, bugme-daemon@osdl.org a écrit :
> > ------- Additional Comments From stern@rowland.harvard.edu  2003-10-31 10:33 -------
> > Created an attachment (id=1303)
> >  --> (http://bugme.osdl.org/attachment.cgi?id=1303&action=view)
> > New diagnostic patch
> > 
> > Try using this diagnostic patch instead of the one sent earlier by Matt Dharm
> > in attachment #14.  It may reveal that the source of the problem is not in the
> > USB system but higher up.
> 
> Done. Do you want to be CCed on this bug ?

There's no need.  The output from that diagnostic is definitive -- this 
isn't a USB problem.  It's got to be a problem higher up, maybe in the 
SCSI layer but more likely in the block layer or the file system code.

Oct 31 21:12:09 rousalka kernel: usb-storage: READ_10: read page 160 pagect 8
Oct 31 21:12:09 rousalka kernel: usb-storage: sddr09_read_data: use_sg = 1, sg[0].page = c18c5b40, .offset = 0, sg_address = 00000000
Oct 31 21:12:09 rousalka kernel: usb-storage: Read 8 pages, from PBA 11 (LBA 5) page 0
Oct 31 21:12:09 rousalka kernel: usb-storage: usb_stor_ctrl_transfer: rq=00 rqtype=41 value=0000 index=00 len=12
Oct 31 21:12:09 rousalka kernel: usb-storage: Status code 0; transferred 12/12
Oct 31 21:12:09 rousalka kernel: usb-storage: -- transfer complete
Oct 31 21:12:09 rousalka kernel: usb-storage: usb_stor_bulk_transfer_buf: xfer 4096 bytes
Oct 31 21:12:09 rousalka kernel: usb-storage: Status code 0; transferred 4096/4096
Oct 31 21:12:09 rousalka kernel: usb-storage: -- transfer complete
Oct 31 21:12:09 rousalka kernel: usb-storage: us_copy_to_sgbuf: buffer = f38e6000, len = 4096, content = f7e01e40, *index = 0, *offset = 0, use_sg = 1
Oct 31 21:12:09 rousalka kernel: usb-storage: in loop, ptr = 00000000

The line where it says sg_address = 00000000 indicates that something has
asked us to read data from the device and store it at a virtual address
that isn't mapped to memory!  You can see the same thing in the last line,
where ptr = 00000000.  No wonder you get an oops.

This bug should be reassigned, but I don't know to whom.  Maybe someone on 
the linux-kernel mailing list can help.

Alan Stern


       reply	other threads:[~2003-11-01 15:47 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1067633171.3886.1.camel@m70.net81-64-235.noos.fr>
2003-11-01 15:47 ` Alan Stern [this message]
2003-11-04  7:49   ` [Bug 1412] Copy from USB1 CF/SM reader stalls, no actual content is read (only directory structure) Jens Axboe
2003-11-04 17:33     ` Alan Stern
2003-11-05  8:40       ` Jens Axboe
2003-11-05 15:47         ` Alan Stern
2003-11-07  8:24           ` Jens Axboe
2003-11-07  8:50             ` Nicolas Mailhot
2003-11-07  9:09               ` Jens Axboe
2003-11-07  9:25                 ` Nicolas Mailhot
2003-11-07 21:02                   ` Nicolas Mailhot
2003-11-07 21:03                     ` Nicolas Mailhot
2003-11-07 21:22                     ` Jens Axboe
2003-11-07 15:48             ` Alan Stern
2003-11-07 21:22               ` Jens Axboe
2003-11-07 18:56             ` [linux-usb-devel] " David Brownell

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=Pine.LNX.4.44L0.0311011039330.18079-100000@netrider.rowland.org \
    --to=stern@rowland.harvard.edu \
    --cc=Nicolas.Mailhot@laPoste.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb-devel@lists.sourceforge.net \
    /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).