From: Patrick Mansfield <patmans@us.ibm.com>
To: Nicolas Mailhot <Nicolas.Mailhot@laPoste.net>
Cc: linux-scsi@vger.kernel.org, dbrownell@users.sourceforge.net
Subject: Re: Usb storage mounting was broken somewhere between 2.6.0-test5-bk10 and 2.6.0-test6-bk1
Date: Tue, 21 Oct 2003 17:55:56 -0700 [thread overview]
Message-ID: <20031021175556.A8670@beaverton.ibm.com> (raw)
In-Reply-To: <1066775616.3458.8.camel@m70.net81-64-235.noos.fr>; from Nicolas.Mailhot@laPoste.net on Wed, Oct 22, 2003 at 12:33:36AM +0200
On Wed, Oct 22, 2003 at 12:33:36AM +0200, Nicolas Mailhot wrote:
> 2. the usb storage maintainer says nothing changed at the usb level, so
> it's probably the scsi layer that broke somehow
In the bug, Matthew says:
looks like someone may have broken usb_reset_configuration or some
other code path outside of usb-storage.
> I've just retested with 2.6.0-test8-bk1 and the bug is still there.
>
> More patch tests, logs, etc available on demand (though the bugzilla
> entry is already pretty complete)
Since the device functioned in an earlier 2.6 release, I doubt the MODE
SENSE page is causing a problem.
It is a multi slot card reader, and SCSI sees these as multiple LUNs
(multiple sd's), though you say you can only use one at a time. So we see
INQUIRY's to LUN 0 and LUN 1, and LUN 1 shows up and is then mounted via
/dev/smartmedia, correct?
David - as replied to you by Nicolas in the bug, the dmesg you commented
on is the one that was working (the "2.6.0-test5-bk5 scenario"). SCSI is
not confused in that case (though I am somewhat confused by the various
dmesg and log files).
Where are the SCSI INQUIRY messages? The ones with Vendor and Model. And
sd attach messages?
If the SCSI INQUIRY messages are not output, SCSI is not seeing the device
at all and it is more likely a usb issue.
AFAICT the bad dmesg ends without a reset, where the good one shows an
INQUIRY being sent and returned back OK, followed by logs of the mount
command.
i.e. bad demsg/log has:
Oct 2 23:55:35 rousalka kernel: usb-storage: USB Mass Storage device detected
Oct 2 23:55:35 rousalka kernel: usb-storage: act_altsetting is 0, id_index is 16
Oct 2 23:55:35 rousalka kernel: usb-storage: -- associate_dev
Oct 2 23:55:35 rousalka kernel: usb-storage: Vendor: SCM Microsystems
Oct 2 23:55:35 rousalka kernel: usb-storage: Product: eUSB SmartMedia /
CompactFlash Adapter
And then nothing at all???
-- Patrick Mansfield
next prev parent reply other threads:[~2003-10-22 1:01 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-21 22:33 Usb storage mounting was broken somewhere between 2.6.0-test5-bk10 and 2.6.0-test6-bk1 Nicolas Mailhot
2003-10-22 0:55 ` Patrick Mansfield [this message]
2003-10-22 2:25 ` David Brownell
2003-10-22 7:49 ` Nicolas Mailhot
2003-10-22 15:11 ` David Brownell
2003-10-22 15:45 ` Nicolas Mailhot
2003-10-22 16:20 ` David Brownell
2003-10-22 18:03 ` Nicolas Mailhot
2003-10-22 18:44 ` Usb storage mounting was broken David Brownell
2003-10-22 20:33 ` Nicolas Mailhot
2003-10-22 22:53 ` David Brownell
2003-10-23 19:59 ` Nicolas Mailhot
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=20031021175556.A8670@beaverton.ibm.com \
--to=patmans@us.ibm.com \
--cc=Nicolas.Mailhot@laPoste.net \
--cc=dbrownell@users.sourceforge.net \
--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 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.