From: James Bottomley <James.Bottomley@SteelEye.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Michal Piotrowski <michal.k.k.piotrowski@gmail.com>,
linux-scsi@vger.kernel.org, casteyde.christian@free.fr,
linux-kernel-announce@vger.kernel.org,
Pierre Ossman <drzeus@drzeus.cx>,
bugme-daemon@bugzilla.kernel.org,
linux-usb-devel@lists.sourceforge.net
Subject: Re: [Bugme-new] [Bug 8885] New: Unable to access memory card reader anymore
Date: Mon, 13 Aug 2007 23:19:26 -0500 [thread overview]
Message-ID: <1187065166.3331.27.camel@localhost.localdomain> (raw)
In-Reply-To: <20070813201354.baffcaba.akpm@linux-foundation.org>
> I'm struggling a bit to work out if this is a scsi bug, a USB bug, an MMC bug
> or whatever. But it's a bug.
>
> Michal, can you please track this as a post-2.6.22 regression?
>
> Others: can you please take a look at the dmesg output, see if we can work
> out which subsystem is (newly) failing?
There's not enough info in the dmesg. We really need the dmesg when
it's failing, not when it's booting up, so after the
blockdev --rereadpt /dev/sda
and the
fdisk /dev/sda
If no messages at all, that's also significant (and I'd guess problems
with media change propagation).
James
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
linux-usb-devel@lists.sourceforge.net
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
next prev parent reply other threads:[~2007-08-14 4:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-8885-10286@http.bugzilla.kernel.org/>
2007-08-14 3:13 ` [Bugme-new] [Bug 8885] New: Unable to access memory card reader anymore Andrew Morton
2007-08-14 4:19 ` James Bottomley [this message]
2007-08-14 4:45 ` Pierre Ossman
2007-08-14 4:53 ` Andrew Morton
2007-08-14 4:53 ` Andrew Morton
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=1187065166.3331.27.camel@localhost.localdomain \
--to=james.bottomley@steeleye.com \
--cc=akpm@linux-foundation.org \
--cc=bugme-daemon@bugzilla.kernel.org \
--cc=casteyde.christian@free.fr \
--cc=drzeus@drzeus.cx \
--cc=linux-kernel-announce@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=linux-usb-devel@lists.sourceforge.net \
--cc=michal.k.k.piotrowski@gmail.com \
/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.