All of lore.kernel.org
 help / color / mirror / Atom feed
* Re: [Bugme-new] [Bug 8885] New: Unable to access memory card reader anymore
       [not found] <bug-8885-10286@http.bugzilla.kernel.org/>
@ 2007-08-14  3:13 ` Andrew Morton
  2007-08-14  4:19   ` James Bottomley
  2007-08-14  4:45   ` Pierre Ossman
  2007-08-14  4:53   ` Andrew Morton
  1 sibling, 2 replies; 5+ messages in thread
From: Andrew Morton @ 2007-08-14  3:13 UTC (permalink / raw)
  To: linux-kernel-announce, linux-scsi, linux-usb-devel, Pierre Ossman,
	Michal Piotrowski
  Cc: bugme-daemon, casteyde.christian

On Mon, 13 Aug 2007 09:07:36 -0700 (PDT) bugme-daemon@bugzilla.kernel.org 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: io_scsi@kernel-bugs.osdl.org
>         ReportedBy: casteyde.christian@free.fr
> 
> 
> 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).
> 
> 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.

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: [Bugme-new] [Bug 8885] New: Unable to access memory card reader anymore
  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
  2007-08-14  4:45   ` Pierre Ossman
  1 sibling, 0 replies; 5+ messages in thread
From: James Bottomley @ 2007-08-14  4:19 UTC (permalink / raw)
  To: Andrew Morton
  Cc: Michal Piotrowski, linux-scsi, casteyde.christian,
	linux-kernel-announce, Pierre Ossman, bugme-daemon,
	linux-usb-devel

> 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

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: [Bugme-new] [Bug 8885] New: Unable to access memory card reader anymore
  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
@ 2007-08-14  4:45   ` Pierre Ossman
  1 sibling, 0 replies; 5+ messages in thread
From: Pierre Ossman @ 2007-08-14  4:45 UTC (permalink / raw)
  To: Andrew Morton
  Cc: linux-usb-devel, linux-scsi, casteyde.christian,
	linux-kernel-announce, bugme-daemon, Michal Piotrowski


[-- Attachment #1.1: Type: text/plain, Size: 400 bytes --]

On Mon, 13 Aug 2007 20:13:54 -0700
Andrew Morton <akpm@linux-foundation.org> wrote:

> 
> 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

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

[-- Attachment #2: Type: text/plain, Size: 315 bytes --]

-------------------------------------------------------------------------
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/

[-- Attachment #3: Type: text/plain, Size: 191 bytes --]

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

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: [Bugme-new] [Bug 8885] New: Unable to access memory card reader anymore
       [not found] <bug-8885-10286@http.bugzilla.kernel.org/>
@ 2007-08-14  4:53   ` Andrew Morton
  2007-08-14  4:53   ` Andrew Morton
  1 sibling, 0 replies; 5+ messages in thread
From: Andrew Morton @ 2007-08-14  4:53 UTC (permalink / raw)
  To: linux-kernel, linux-scsi, linux-usb-devel, Pierre Ossman,
	Michal Piotrowski
  Cc: bugme-daemon, casteyde.christian


(resend, fixed mailing list address)

On Mon, 13 Aug 2007 09:07:36 -0700 (PDT) bugme-daemon@bugzilla.kernel.org 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: io_scsi@kernel-bugs.osdl.org
>         ReportedBy: casteyde.christian@free.fr
> 
> 
> 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).
> 
> 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.

-------------------------------------------------------------------------
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

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: [Bugme-new] [Bug 8885] New: Unable to access memory card reader anymore
@ 2007-08-14  4:53   ` Andrew Morton
  0 siblings, 0 replies; 5+ messages in thread
From: Andrew Morton @ 2007-08-14  4:53 UTC (permalink / raw)
  To: linux-kernel, linux-scsi, linux-usb-devel, Pierre Ossman,
	Michal Piotrowski
  Cc: bugme-daemon, casteyde.christian


(resend, fixed mailing list address)

On Mon, 13 Aug 2007 09:07:36 -0700 (PDT) bugme-daemon@bugzilla.kernel.org 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: io_scsi@kernel-bugs.osdl.org
>         ReportedBy: casteyde.christian@free.fr
> 
> 
> 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).
> 
> 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.

^ permalink raw reply	[flat|nested] 5+ messages in thread

end of thread, other threads:[~2007-08-14  4:55 UTC | newest]

Thread overview: 5+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
     [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
2007-08-14  4:45   ` Pierre Ossman
2007-08-14  4:53 ` Andrew Morton
2007-08-14  4:53   ` Andrew Morton

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.