New: Unable to access memory card reader anymore

Bugme-new Andrew Morton 3 participants 4 messages Aug 14, 2007 1 message not in the archive SCSI

lore

Share & tools

lore

A message that is not in the archive (sent off-list or not yet received): [email protected]/

Andrew Morton

author

2007-08-14 03:13 UTC #1 lore raw

Quoted 34 lines · On Mon, 13 Aug 2007 09:07:36 -0700 (PDT) [email protected] wrote:

http://bugzilla.kernel.org/show_bug.cgi?id=8885
           Summary: Unable to access memory card reader anymore
           Product: IO/Storage
           Version: 2.5
     KernelVersion: 2.6.23-rc3
          Platform: All
        OS/Version: Linux
              Tree: Mainline
            Status: NEW
          Severity: normal
          Priority: P1
         Component: SCSI
        AssignedTo: [email protected]
        ReportedBy: [email protected]
Most recent kernel where this bug did not occur: 2.6.22.1, maybe 2.6.23-rc2
Distribution: Slackware 12.0
Hardware Environment: Athlon64 3000, laptop Aspire 1511LMi, nForce3 150 Software Environment: Kernel 2.6.23-rc3, blockdev, udev, KDE 3.5.7 Problem Description:
With kernel 2.6.22.1, when I plug a memory card in the integrated card reader of my laptop, the card is detected and KDE(via udev) asks me for mounting the device.
With kernel 2.6.23-rc3, this does not happens anymore:
- first, at boot, there are some new lines in dmesg saying /dev/sda is seen but size cannot be get (normal: there is no memory card in the reader);
- second, plugging the card does nothing;
- third, issuing "blockdev --rereadpt /dev/sda" does not work;
- finally, fdisk /dev/sda fails (unable to open /dev/sda).
So the device seems to be completly unusable now (this is a Thomson card reader if I remember well).

Quoted 7 lines

dmesg output for 2.6.22.1-cfs19 and 2.6.23-rc3 appended to show the differences.
Steps to reproduce:
Maybe the problem is specific to my hardware. I presume: boot with an empty card reader connected, the plug the card and see it is inaccessible?

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?

Thanks.

James Bottomley

2007-08-14 04:19 UTC #2 lore raw

Quoted 7 lines

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/
_______________________________________________
[email protected]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel

Pierre Ossman

2007-08-14 04:45 UTC #3 lore raw

In reply to Andrew Morton

Quoted 4 lines · On Mon, 13 Aug 2007 20:13:54 -0700 Andrew Morton <[email protected]>…

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.

I can't see anything MMC related in his dmesg, only what seems to be a USB based reader:

scsi 0:0:0:0: Direct-Access Generic Flash R/W 2002 PQ: 0
ANSI: 2

Rgds
Pierre

_______________________________________________
[email protected]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel

Andrew Morton

author

2007-08-14 04:53 UTC #4 lore raw

In reply to a message not in the archive

(resend, fixed mailing list address)

Quoted 34 lines · On Mon, 13 Aug 2007 09:07:36 -0700 (PDT) [email protected] wrote:

http://bugzilla.kernel.org/show_bug.cgi?id=8885
           Summary: Unable to access memory card reader anymore
           Product: IO/Storage
           Version: 2.5
     KernelVersion: 2.6.23-rc3
          Platform: All
        OS/Version: Linux
              Tree: Mainline
            Status: NEW
          Severity: normal
          Priority: P1
         Component: SCSI
        AssignedTo: [email protected]
        ReportedBy: [email protected]
Most recent kernel where this bug did not occur: 2.6.22.1, maybe 2.6.23-rc2
Distribution: Slackware 12.0
Hardware Environment: Athlon64 3000, laptop Aspire 1511LMi, nForce3 150 Software Environment: Kernel 2.6.23-rc3, blockdev, udev, KDE 3.5.7 Problem Description:
With kernel 2.6.22.1, when I plug a memory card in the integrated card reader of my laptop, the card is detected and KDE(via udev) asks me for mounting the device.
With kernel 2.6.23-rc3, this does not happens anymore:
- first, at boot, there are some new lines in dmesg saying /dev/sda is seen but size cannot be get (normal: there is no memory card in the reader);
- second, plugging the card does nothing;
- third, issuing "blockdev --rereadpt /dev/sda" does not work;
- finally, fdisk /dev/sda fails (unable to open /dev/sda).
So the device seems to be completly unusable now (this is a Thomson card reader if I remember well).

Quoted 7 lines

dmesg output for 2.6.22.1-cfs19 and 2.6.23-rc3 appended to show the differences.
Steps to reproduce:
Maybe the problem is specific to my hardware. I presume: boot with an empty card reader connected, the plug the card and see it is inaccessible?

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?

Thanks.