mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@osdl.org>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: Soeren Sonnenburg <kernel@nn7.de>,
	Linux Kernel <linux-kernel@vger.kernel.org>,
	linux-usb-devel <linux-usb-devel@lists.sourceforge.net>
Subject: Re: [linux-usb-devel] 2.6.20-rc6 SCSI error: I/O error - trouble with mass storage devices ?!
Date: Thu, 1 Feb 2007 13:37:44 -0800	[thread overview]
Message-ID: <20070201133744.1a548ad5.akpm@osdl.org> (raw)
In-Reply-To: <Pine.LNX.4.44L0.0701301300050.7522-100000@iolanthe.rowland.org>

On Tue, 30 Jan 2007 13:08:19 -0500 (EST)
Alan Stern <stern@rowland.harvard.edu> wrote:

> On Sat, 27 Jan 2007, Soeren Sonnenburg wrote:
> 
> > Dear all,
> > 
> > I am trying to use a P990 phone in via mass storage under linux. I was
> > able to copy data to/from the phone without trouble under winxp but
> > receive millions of I/O errors (see below (*), basically on any sector).
> > As this was also happening on a casio camera (and working on winxp) I
> > tried a couple of things to nail this down:
> 
> ...
> 
> > 4) I enabled usb mass storage verbose debug output and collected 2 runs
> > of I/O once with the sandisk and one with the P990 (attached as sandisk
> > and p990)
> 
> ...
> 
> > Now I am clueless what could have gone wrong (as I *think* this was all
> > working at some point at least before firmware updates) and what the
> > difference between these mass storage devices is.
> 
> The log revealed that the phone's firmware returns garbage values in the 
> Residue field for some WRITEs.  This patch should take care of it.
> 
> Alan Stern
> 
> 
> 
> Index: usb-2.6/drivers/usb/storage/unusual_devs.h
> ===================================================================
> --- usb-2.6.orig/drivers/usb/storage/unusual_devs.h
> +++ usb-2.6/drivers/usb/storage/unusual_devs.h
> @@ -1318,12 +1318,13 @@ UNUSUAL_DEV(  0x0fce, 0xe031, 0x0000, 0x
>  		US_SC_DEVICE, US_PR_DEVICE, NULL,
>  		US_FL_FIX_CAPACITY ),
>  
> -/* Reported by Jan Mate <mate@fiit.stuba.sk> */
> +/* Reported by Jan Mate <mate@fiit.stuba.sk>
> + * and by Soeren Sonnenburg <kernel@nn7.de> */
>  UNUSUAL_DEV(  0x0fce, 0xe030, 0x0000, 0x0000,
>  		"Sony Ericsson",
>  		"P990i",
>  		US_SC_DEVICE, US_PR_DEVICE, NULL,
> -		US_FL_FIX_CAPACITY ),
> +		US_FL_FIX_CAPACITY | US_FL_IGNORE_RESIDUE ),
>  
>  /* Reported by Kevin Cernekee <kpc-usbdev@gelato.uiuc.edu>
>   * Tested on hardware version 1.10.

This fixes the phone, but what's the situation with that Casio camera?

  parent reply	other threads:[~2007-02-01 21:38 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1169909796.2462.56.camel@localhost>
2007-01-30 18:08 ` Alan Stern
2007-01-31  9:12   ` Soeren Sonnenburg
2007-02-01 21:37   ` Andrew Morton [this message]
     [not found] <fa.PeThxrKzzfWoGYao97lEVEZgJlc@ifi.uio.no>
     [not found] ` <fa.SlST1aKbNgZSghdvI9esD81kVnI@ifi.uio.no>
2007-01-30 23:12   ` Robert Hancock
2007-01-31  1:03     ` Greg KH
2007-01-31  1:06       ` Robert Hancock
2007-01-31 15:20     ` Alan Stern

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=20070201133744.1a548ad5.akpm@osdl.org \
    --to=akpm@osdl.org \
    --cc=kernel@nn7.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

Powered by JetHome