Bug 43191 - Syslog fills with messages about assuming drive cache when SD card not present
Syslog fills with messages about assuming drive cache when SD card not present
Status: ASSIGNED
Product: IO/Storage
Classification: Unclassified
Component: Serial ATA
i386 Linux
: P1 normal
Assigned To: Alan
:
: 43190 (view as bug list)
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2012-05-01 22:21 UTC by Sree Harsha Totakura
Modified: 2016-03-19 16:56 UTC (History)
13 users (show)

See Also:
Kernel Version: 3.4.0
Tree: Mainline
Regression: No


Attachments
list of currently loaded modules (2.39 KB, text/plain)
2012-05-01 22:21 UTC, Sree Harsha Totakura
Details
lspci (2.08 KB, text/plain)
2012-05-01 22:22 UTC, Sree Harsha Totakura
Details
scsi (495 bytes, text/plain)
2012-05-01 22:22 UTC, Sree Harsha Totakura
Details
dmesg; lspci; lspci -v; lspci -vvv; cat /proc/scsi/scsi; lsmod (99.69 KB, text/plain)
2012-05-03 07:10 UTC, Christian Kujau
Details
dmesg output (55.73 KB, text/x-log)
2012-05-07 14:33 UTC, Daniel Mehrmann
Details

Description Sree Harsha Totakura 2012-05-01 22:21:48 UTC
Created attachment 73153 [details]
list of currently loaded modules

I'm observing the issue discussed in this bug report: https://bugzilla.kernel.org/show_bug.cgi?id=43190
I'm reporting it here since the original reporter didn't seem to have reported here:


I get this output repeatedly after every minute or so:

[  465.435298] sd 6:0:0:0: [sdb] Test WP failed, assume Write Enabled
[  465.438295] sd 6:0:0:0: [sdb] Asking for cache data failed
[  465.438303] sd 6:0:0:0: [sdb] Assuming drive cache: write through
[  517.147818] sd 6:0:0:0: [sdb] Test WP failed, assume Write Enabled
[  517.150811] sd 6:0:0:0: [sdb] Asking for cache data failed
[  517.150822] sd 6:0:0:0: [sdb] Assuming drive cache: write through
[  568.859459] sd 6:0:0:0: [sdb] Test WP failed, assume Write Enabled
[  568.862330] sd 6:0:0:0: [sdb] Asking for cache data failed
[  568.862339] sd 6:0:0:0: [sdb] Assuming drive cache: write through
[  620.571790] sd 6:0:0:0: [sdb] Test WP failed, assume Write Enabled
[  620.574659] sd 6:0:0:0: [sdb] Asking for cache data failed

However, when I put in a memory card it stops after outputting this:

[ 1543.770351] sd 6:0:0:0: [sdb] 3970048 512-byte logical blocks: (2.03 GB/1.89 GiB)
[ 1543.775577] sd 6:0:0:0: [sdb] No Caching mode page present
[ 1543.775586] sd 6:0:0:0: [sdb] Assuming drive cache: write through
[ 1543.780604] sd 6:0:0:0: [sdb] No Caching mode page present
[ 1543.780611] sd 6:0:0:0: [sdb] Assuming drive cache: write through
[ 1543.807961]  sdb: sdb1

and once I eject the memory card it continues:

[ 4980.766490] sd 6:0:0:0: [sdb] Assuming drive cache: write through
[ 5032.474959] sd 6:0:0:0: [sdb] Test WP failed, assume Write Enabled
[ 5032.477961] sd 6:0:0:0: [sdb] Asking for cache data failed
[ 5032.477970] sd 6:0:0:0: [sdb] Assuming drive cache: write through
[ 5084.187541] sd 6:0:0:0: [sdb] Test WP failed, assume Write Enabled
[ 5084.190546] sd 6:0:0:0: [sdb] Asking for cache data failed
[ 5084.190554] sd 6:0:0:0: [sdb] Assuming drive cache: write through
[ 5135.899244] sd 6:0:0:0: [sdb] Test WP failed, assume Write Enabled
[ 5135.902369] sd 6:0:0:0: [sdb] Asking for cache data failed
[ 5135.902378] sd 6:0:0:0: [sdb] Assuming drive cache: write through
Comment 1 Sree Harsha Totakura 2012-05-01 22:22:23 UTC
Created attachment 73154 [details]
lspci
Comment 2 Sree Harsha Totakura 2012-05-01 22:22:51 UTC
Created attachment 73155 [details]
scsi
Comment 3 Chris Fahlman 2012-05-02 04:07:43 UTC
*** Bug 43190 has been marked as a duplicate of this bug. ***
Comment 4 Christian Kujau 2012-05-03 06:55:27 UTC
Noticed this on a "Lenovo Ideapad S10" as well. Ubuntu #925760 has a workaround for this:

$ rmmod ums_realtek

 usbcore: deregistering interface driver ums-realtek

And the messages stop. As soon as the module is loaded again, the messages resume and repeat every 52 seconds:

$ modprobe ums_realtek

May  2 23:50:46 scsi5 : usb-storage 1-5:1.0
May  2 23:50:46 usbcore: registered new interface driver ums-realtek
May  2 23:50:47 scsi 5:0:0:0: Direct-Access Generic- Multi-Card 1.00 PQ: 0 ANSI: 0 CCS
May  2 23:50:47 sd 5:0:0:0: Attached scsi generic sg1 type 0
May  2 23:50:47 sd 5:0:0:0: [sdb] Attached SCSI removable disk

May  2 23:51:38 sd 5:0:0:0: [sdb] Test WP failed, assume Write Enabled
May  2 23:51:38 sd 5:0:0:0: [sdb] Asking for cache data failed
May  2 23:51:38 sd 5:0:0:0: [sdb] Assuming drive cache: write through
May  2 23:52:30 sd 5:0:0:0: [sdb] Test WP failed, assume Write Enabled
May  2 23:52:30 sd 5:0:0:0: [sdb] Asking for cache data failed
May  2 23:52:30 sd 5:0:0:0: [sdb] Assuming drive cache: write through
Comment 5 Christian Kujau 2012-05-03 07:10:38 UTC
Created attachment 73164 [details]
dmesg; lspci; lspci -v; lspci -vvv; cat /proc/scsi/scsi; lsmod
Comment 6 Daniel Mehrmann 2012-05-07 14:32:14 UTC
I can confirm it happens with my Netbook LG x110 as well.
I attach a boot.log
Comment 7 Daniel Mehrmann 2012-05-07 14:33:29 UTC
Created attachment 73217 [details]
dmesg output

dmesg output of Netbook LG x110
Comment 8 Petr Pisar 2012-05-08 09:00:27 UTC
See <https://bugzilla.redhat.com/show_bug.cgi?id=769747> for other udev---kernel debugging.
Comment 9 TJ 2012-08-24 19:48:14 UTC
The issue is caused by ums_realtek module's 'selective suspend' operation. This option is enabled by default and - using its default delay timer of 50 seconds - triggers these events.

The driver seems to implement it's own sleep functionality and timer whilst also telling the kernel it supports auto-suspend callbacks.
Comment 10 Morgan Leijström 2013-05-12 23:39:15 UTC
I have an issue that may be the same

But i have much higher rate of errors, and it is continuously a couple hundred pair of message lines per second when i plug in a small video camera and do not have the microSD inserted in it.

And it also spews out the messages if i have the card inserted, if i power on the machine with it attached.

Do you think it is the same issue?
For details see: https://bugs.mageia.org/show_bug.cgi?id=10038
Comment 11 Ladislav Nesnera 2013-12-14 16:55:12 UTC
I can confirm - this problem causes Realtek card reader. This small work around works for me well - http://askubuntu.com/a/337802
Comment 12 Ladislav Nesnera 2013-12-14 16:59:17 UTC
Sorry I forgot:
modinfo ums_realtek
filename:       /lib/modules/3.11.10-200.fc19.x86_64/kernel/drivers/usb/storage/ums-realtek.ko
version:        1.03
license:        GPL
author:         wwang <wei_wang@realsil.com.cn>
description:    Driver for Realtek USB Card Reader
srcversion:     7211D16D16BECBF334341D5
alias:          usb:v0BDAp0159d*dc*dsc*dp*ic*isc*ip*in*
alias:          usb:v0BDAp0158d*dc*dsc*dp*ic*isc*ip*in*
alias:          usb:v0BDAp0138d*dc*dsc*dp*ic*isc*ip*in*
depends:        usb-storage
intree:         Y
vermagic:       3.11.10-200.fc19.x86_64 SMP mod_unload 
signer:         Fedora kernel signing key
sig_key:        73:A1:46:50:5C:77:01:B9:19:75:E6:40:A2:56:94:5B:70:16:C5:D0
sig_hashalgo:   sha256
parm:           auto_delink_en:enable auto delink (int)
parm:           ss_en:enable selective suspend (int)
parm:           ss_delay:seconds to delay before entering selective suspend (int

Note You need to log in before you can comment on or make changes to this bug.