From: bugme-daemon@bugzilla.kernel.org
To: linux-scsi@vger.kernel.org
Subject: [Bug 11302] I get a kernel OOPS! If I try to attach an usb card reader, SD, MMC, ecc.. to my Slamd64
Date: Mon, 1 Sep 2008 23:04:00 -0700 (PDT) [thread overview]
Message-ID: <20080902060400.93FDD108059@picon.linux-foundation.org> (raw)
In-Reply-To: <bug-11302-11613@http.bugzilla.kernel.org/>
http://bugzilla.kernel.org/show_bug.cgi?id=11302
------- Comment #9 from anonymous@kernel-bugs.osdl.org 2008-09-01 23:04 -------
Reply-To: drzeus@drzeus.cx
On Mon, 1 Sep 2008 23:30:56 +0000 (GMT)
pinco pallino <pinc_o@yahoo.it> wrote:
> Hi Andrew,
>
> with the new kernel 2.6.26.3 the SD are now read and wrote correctly, but SDHC are not read! The kernel repeat the error. Follow the error:
>
Have you checked that the reader does in fact support SDHC? They tend
to fail in all sorts of ways when they don't.
--
Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
next prev parent reply other threads:[~2008-09-02 6:04 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-10 20:45 [Bug 11302] New: I get a kernel OOPS! If I try to attach an usb card reader, SD, MMC, ecc.. to my Slamd64 bugme-daemon
2008-08-10 20:53 ` [Bug 11302] " bugme-daemon
2008-08-10 20:53 ` bugme-daemon
2008-08-11 5:46 ` bugme-daemon
2008-08-11 6:34 ` bugme-daemon
2008-08-11 13:33 ` bugme-daemon
2008-08-18 17:11 ` bugme-daemon
2008-09-01 23:31 ` bugme-daemon
2008-09-02 0:05 ` bugme-daemon
2008-09-02 2:21 ` bugme-daemon
2008-09-02 6:04 ` bugme-daemon [this message]
2008-09-03 13:13 ` bugme-daemon
[not found] <bug-11302-11613@https.bugzilla.kernel.org/>
2012-05-22 13:14 ` bugzilla-daemon
2012-05-22 13:14 ` bugzilla-daemon
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=20080902060400.93FDD108059@picon.linux-foundation.org \
--to=bugme-daemon@bugzilla.kernel.org \
--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 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).