All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nicolas Mailhot <Nicolas.Mailhot@laPoste.net>
To: Jens Axboe <axboe@suse.de>
Cc: Alan Stern <stern@rowland.harvard.edu>,
	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: Fri, 07 Nov 2003 09:50:39 +0100	[thread overview]
Message-ID: <1068195038.21576.1.camel@ulysse.olympe.o2t> (raw)
In-Reply-To: <20031107082439.GB504@suse.de>

[-- Attachment #1: Type: text/plain, Size: 906 bytes --]

Le ven 07/11/2003 à 09:24, Jens Axboe a écrit :
> On Wed, Nov 05 2003, Alan Stern wrote:

> > In any case, it quite likely _does_ point to a driver bug.  But since
> > sddr09_read_data() was handed this sg entry and didn't change it, if there
> > is such a bug it must lie in a higher-level driver.  Maybe the scsi layer, 
> > maybe the block layer, maybe the memory-management system, maybe the file 
> > system.  That was my original point.
> 
> Well, the sg entry looks perfectly valid. And that was my original
> point :-). And that is why I said it looks like a driver bug, not in
> upper layers. How much memory did the system that crashed have? If the
> system has highmem, try testing with scsi_calculate_bounce_limit()
> unconditionally returning BLK_BOUNCE_HIGH.

The system has 1 GiB of memory, ie just enough to make stuff like
radeonfb fail

Cheers,

-- 
Nicolas Mailhot

[-- Attachment #2: Ceci est une partie de message numériquement signée. --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2003-11-08  0:33 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 ` [Bug 1412] Copy from USB1 CF/SM reader stalls, no actual content is read (only directory structure) Alan Stern
2003-11-04  7:49   ` 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 [this message]
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=1068195038.21576.1.camel@ulysse.olympe.o2t \
    --to=nicolas.mailhot@laposte.net \
    --cc=axboe@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb-devel@lists.sourceforge.net \
    --cc=stern@rowland.harvard.edu \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.