Question

9

Errors in dmesg - Test WP failed, assume Write Enabled

rated 0 times [ 9] [ 0] / answers: 1 / hits: 30724 / 3 Years ago, mon, august 9, 2021, 10:15:23

I'm experiencing some problems with drive cache and I don't know what's causing these problems.
This is my dmesg:

[11690.011238] sd 6:0:0:0: [sdb] Asking for cache data failed

[11690.011248] sd 6:0:0:0: [sdb] Assuming drive cache: write through

[11741.720851] sd 6:0:0:0: [sdb] Test WP failed, assume Write Enabled

[11741.722965] sd 6:0:0:0: [sdb] Asking for cache data failed

[11741.722975] sd 6:0:0:0: [sdb] Assuming drive cache: write through

[11793.433011] sd 6:0:0:0: [sdb] Test WP failed, assume Write Enabled

[11793.435347] sd 6:0:0:0: [sdb] Asking for cache data failed

[11793.435356] sd 6:0:0:0: [sdb] Assuming drive cache: write through

[11845.140846] sd 6:0:0:0: [sdb] Test WP failed, assume Write Enabled

[11845.143098] sd 6:0:0:0: [sdb] Asking for cache data failed

[11845.143102] sd 6:0:0:0: [sdb] Assuming drive cache: write through

[11896.856723] sd 6:0:0:0: [sdb] Test WP failed, assume Write Enabled

There are hundreds of these lines. It is happening since I've installed Ubuntu 12.04 64bit beta2 from my pendrive.
Now I don't have anything at /dev/sdb. I don't know if these errors are making my system less responsive, but I think that dmesg shouldn't look like this.

My kernel version: 3.2.0-24-generic.

Do you have any idea how to solve it?

Thank you in advance.

Answers

Only authorized users can answer the question. Please sign in first, or register a free account.

etzelmortg

Add To Favorites

Follow

Total Points: 430

Total Questions: 105

Total Answers: 106

Location: Suriname

Member since Sun, Jun 13, 2021

3 Years ago

answered 3 Years ago scusaper · Accepted Answer

I'm having the same issue on the official 12.04 LTS relase i also believe it is causing the system to be less responsive. According to some sources it's harmless. (i can apparently only post 2 links)

The following thinks this is error output from an onboard card reader:

https://bbs.archlinux.org/viewtopic.php?pid=1059099

It's confirmed to be an upstream issue in

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/987993

Run lsusb and find the offending device



nathan@Ham-Bone:~$ lsusb 



Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub

Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub

Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub

Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub

Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub

Bus 008 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub

Bus 001 Device 002: ID 0bda:0158 Realtek Semiconductor Corp. USB 2.0 multicard reader

In my case it's the Realtek multicard reader which a quick check of



$ dmesg | grep realtek

[    4.716068] usbcore: registered new interface driver ums-realtek

$ lsmod | grep realtek

ums_realtek            17920  0

reveals a module ums-realtek



$sudo rmmod ums_realtek

Fixes the problem in a reversible way for me. That is



$sudo modprobe ums_realtek

enables the card reader again. I haven't tested if it works since I never use it.

If this doesn't work there are some other ways to disable usb devices by unbinding them in the /sys/ directory.