You are not logged in.
Hi,
this is my card reader:
Device: 13:00.0
Class: Unassigned class [ff00]
Vendor: Realtek Semiconductor Co., Ltd. [10ec]
Device: RTS5116 PCI Express Card Reader [5209]
SVendor: Hewlett-Packard Company [103c]
SDevice: Device [3581]
Rev: 01
Driver: rts_pstor
Module: rts_pstor
and errors are shown also during the boot,
Dec 11 21:23:28 localhost kernel: [ 3155.132435] ieee80211 phy0: brcms_ops_bss_info_changed: arp filtering: enabled true, count 0 (implement)
Dec 11 21:23:58 localhost kernel: [ 6.567303] Bad LUN (0:1)
Dec 11 21:23:58 localhost kernel: [ 6.567369] Bad target number (1:0)
Dec 11 21:23:58 localhost kernel: [ 6.567443] Bad target number (2:0)
Dec 11 21:23:58 localhost kernel: [ 6.567507] Bad target number (3:0)
Dec 11 21:23:58 localhost kernel: [ 6.567572] Bad target number (4:0)
Dec 11 21:23:58 localhost kernel: [ 6.567638] Bad target number (5:0)
Dec 11 21:23:58 localhost kernel: [ 6.567706] Bad target number (6:0)
Dec 11 21:23:58 localhost kernel: [ 6.567760] Bad target number (7:0)
Full dmesg log
[ 6.905826] scsi 6:0:0:0: Direct-Access Generic- xD/SD/M.S. 1.00 PQ: 0 ANSI: 0 CCS
[ 6.905999] Bad LUN (0:1)
[ 6.906036] scsi: killing requests for dead queue
[ 6.906082] Bad target number (1:0)
[ 6.906106] scsi: killing requests for dead queue
[ 6.906136] Bad target number (2:0)
[ 6.906160] scsi: killing requests for dead queue
[ 6.906187] Bad target number (3:0)
[ 6.906209] scsi: killing requests for dead queue
[ 6.906265] Bad target number (4:0)
[ 6.906297] scsi: killing requests for dead queue
[ 6.906319] sd 6:0:0:0: [sdb] Attached SCSI removable disk
[ 6.906335] Bad target number (5:0)
[ 6.906357] scsi: killing requests for dead queue
[ 6.906384] Bad target number (6:0)
[ 6.906406] scsi: killing requests for dead queue
[ 6.906432] Bad target number (7:0)
[ 6.906454] scsi: killing requests for dead queue
[ 6.906462] rts_pstor: device scan complete
Any help would be great.
Last edited by r0b0t (2012-07-05 16:16:26)
Offline
same with 3.1.5-1-ARCH ..
any advice?
should I open a bug for this?
I found that realtek supports up to 2.6.37
http://www.realtek.com/Downloads/downlo … Down=false
any help is welcome
Last edited by r0b0t (2011-12-14 13:25:48)
Offline
https://bbs.archlinux.org/viewtopic.php?id=124139 appears to be the same bug.
I filed a bug in Kernel Bugzilla: https://bugzilla.kernel.org/show_bug.cgi?id=42640
Offline
thank you, for now I blacklisted rts_pstor and finally got reed of the errors.
However would be good to have this working, let's hope for a fix.
Offline
I got in touch with the developer of the module. I think he's looking into it.
It is possible to get rid of the errors and still have a working rts_pstor module. For that, you need to download the source code from the realtek site, then edit the source code and comment out the lines that print the error messages, compile, gzip, and copy the rts_pstor.ko.gz file to the appropriate path.
Of course, that's still a workaround, since it doesn't take away the cause of the errors. That's why I don't really feel like getting into detail with the instructions above. :-)
Offline
From the developer:
"We will fix the issue to printing "bad lun" or "bad target number" during boot, in our next submission to the kernel staging tree. ".
Offline
Same issue with 3.3.3-1-ARCH, with which version will be fixed?
Offline
Same issue with 3.3.3-1-ARCH, with which version will be fixed?
I asked. according to the developer:
Because of the kernel merge window, the fix will be contained in kernel 3.4
Offline
yep, confirmed, actually it works
Offline