[bug?] Multimedia card reader outputs weird messages

[Jonathan Nieder]

Hi,

Camaleón reports[1]:

> cards are recognized when insterted into the 
> embedded reader but still seeing the weird message when booting.
[...]
> root at stt300:~# uname -a
> Linux stt300 3.2.0-rc3 #1 SMP Sat Nov 26 12:29:30 CET 2011 i686 GNU/Linux
>
> 01:00.1 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. Device 5288 (rev 01)
> 	Subsystem: Hewlett-Packard Company Device 148a
[...]
>
> [    7.094189] rts_pstor: module is from the staging directory, the quality is unknown, you have been warned.
> [    7.096974] Initializing Realtek PCIE storage driver...
> [    7.097056] rts_pstor 0000:01:00.1: PCI INT B -> GSI 17 (level, low) -> IRQ 17
> [    7.097216] Resource length: 0x10000
> [    7.097283] Original address: 0x93000000, remapped address: 0xf8600000
> [    7.097296] pci->irq = 17
> [    7.097302] rtsx_acquire_irq: chip->msi_en = 0, pci->irq = 17
> [    7.097350] rts_pstor 0000:01:00.1: setting latency timer to 64
[...]
> [    8.296174] rts_pstor: device scan complete
> [    8.296397] scsi 4:0:0:0: Direct-Access     Generic- xD/SD/M.S.   1.00 PQ: 0 ANSI: 0 CCS
> [    8.296491] Bad LUN (0:1)
> [    8.296649] Bad target number (1:0)
> [    8.296786] Bad target number (2:0)
> [    8.296922] Bad target number (3:0)
> [    8.297056] Bad target number (4:0)
> [    8.297191] Bad target number (5:0)
> [    8.297319] Bad target number (6:0)
> [    8.297448] Bad target number (7:0)
> [    8.298401] sd 4:0:0:0: [sdb] Attached SCSI removable disk
> [    8.314139] Linux media interface: v0.10
> [    8.318091] sd 0:0:0:0: Attached scsi generic sg0 type 0
> [    8.318635] sd 4:0:0:0: Attached scsi generic sg1 type 0
[...]
> [  355.088042] rts_pstor 0000:01:00.1: vpd r/w failed.  This is likely a firmware bug on this device.  Contact the card vendor for a firmware update.
> [  370.892028] rts_pstor 0000:01:00.1: vpd r/w failed.  This is likely a firmware bug on this device.  Contact the card vendor for a firmware update.

Known problem?  Any ideas for tracking it down?

More details at [1].  Thanks, it's great to see the progress of this
driver.

Regards,
Jonathan

[1] http://bugs.debian.org/637813