'Test WP failed, assume Write Enabled' messages on console

[James Page]

This appears not to cause any specific issue and the device (the internal CD-ROM drive) continues to function OK.

[ 362.518258] sd 6:0:0:0: [sdb] Test WP failed, assume Write Enabled
[ 362.521037] sd 6:0:0:0: [sdb] Asking for cache data failed
[ 362.521096] sd 6:0:0:0: [sdb] Assuming drive cache: write through
[ 414.230766] sd 6:0:0:0: [sdb] Test WP failed, assume Write Enabled
[ 414.233415] sd 6:0:0:0: [sdb] Asking for cache data failed
[ 414.233474] sd 6:0:0:0: [sdb] Assuming drive cache: write through
[ 465.942524] sd 6:0:0:0: [sdb] Test WP failed, assume Write Enabled
[ 465.945175] sd 6:0:0:0: [sdb] Asking for cache data failed
[ 465.945233] sd 6:0:0:0: [sdb] Assuming drive cache: write through
[ 517.654534] sd 6:0:0:0: [sdb] Test WP failed, assume Write Enabled
[ 517.657306] sd 6:0:0:0: [sdb] Asking for cache data failed
[ 517.657369] sd 6:0:0:0: [sdb] Assuming drive cache: write through
[ 569.366547] sd 6:0:0:0: [sdb] Test WP failed, assume Write Enabled
[ 569.369190] sd 6:0:0:0: [sdb] Asking for cache data failed
[ 569.370934] sd 6:0:0:0: [sdb] Assuming drive cache: write through
[ 621.078682] sd 6:0:0:0: [sdb] Test WP failed, assume Write Enabled
[ 621.081304] sd 6:0:0:0: [sdb] Asking for cache data failed
[ 621.083085] sd 6:0:0:0: [sdb] Assuming drive cache: write through
[ 672.790378] sd 6:0:0:0: [sdb] Test WP failed, assume Write Enabled
[ 672.793029] sd 6:0:0:0: [sdb] Asking for cache data failed
[ 672.794763] sd 6:0:0:0: [sdb] Assuming drive cache: write through
[ 724.502321] sd 6:0:0:0: [sdb] Test WP failed, assume Write Enabled
[ 724.504854] sd 6:0:0:0: [sdb] Asking for cache data failed
[ 724.506565] sd 6:0:0:0: [sdb] Assuming drive cache: write through
[ 776.214455] sd 6:0:0:0: [sdb] Test WP failed, assume Write Enabled
[ 776.216987] sd 6:0:0:0: [sdb] Asking for cache data failed
[ 776.218705] sd 6:0:0:0: [sdb] Assuming drive cache: write through
[ 827.926340] sd 6:0:0:0: [sdb] Test WP failed, assume Write Enabled
[ 827.928872] sd 6:0:0:0: [sdb] Asking for cache data failed
[ 827.930579] sd 6:0:0:0: [sdb] Assuming drive cache: write through

Hardware is a Dell Vostro 1220.

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: linux-image-server 3.2.0.23.25
ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14
Uname: Linux 3.2.0-23-generic x86_64
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
AplayDevices: Error: [Errno 2] No such file or directory
ApportVersion: 2.0.1-0ubuntu5
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info: Error: [Errno 2] No such file or directory
Card0.Amixer.values: Error: [Errno 2] No such file or directory
Date: Tue Apr 24 20:43:07 2012
HibernationDevice: RESUME=UUID=87fa8222-a909-4867-8f66-f8199071982a
InstallationMedia: Ubuntu-Server 12.04 LTS "Precise Pangolin" - Release amd64 (20120424.1)
IwConfig:
 lo no wireless extensions.

 eth0 no wireless extensions.
MachineType: Dell Inc. Vostro 1220
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.2.0-23-generic root=/dev/mapper/node--0026b9140967-root ro
RelatedPackageVersions:
 linux-restricted-modules-3.2.0-23-generic N/A
 linux-backports-modules-3.2.0-23-generic N/A
 linux-firmware 1.79
RfKill: Error: [Errno 2] No such file or directory
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/15/2009
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.3.0
dmi.board.name: 0Y743R
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.:bvr1.3.0:bd10/15/2009:svnDellInc.:pnVostro1220:pvr:rvnDellInc.:rn0Y743R:rvr:cvnDellInc.:ct8:cvr:
dmi.product.name: Vostro 1220
dmi.sys.vendor: Dell Inc.

[Joseph Salisbury (jsalisbury)]

Do you know if this issue happened in a previous version of Ubuntu, or is this a new issue?

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.4kernel[1] (Not a kernel in the daily directory). Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag(Only that one tag, please leave the other tags). This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text.

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'.
Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.4-rc4-precise/

[James Page (james-page)]

Hi Joseph

It did not happen on Ubuntu 11.10 - I double checked on the other vostro 1220 that I use and I see the same issue.

I'll test the mainline kernel to see if that makes a difference

[James Page (james-page)]

Tested with mainline kernel as requested:

Apr 25 15:04:56 node-0026b9140967 kernel: [ 17.393312] init: plymouth-upstart-bridge main process (803) killed by TERM signal
Apr 25 15:05:33 node-0026b9140967 kernel: [ 53.797041] sd 6:0:0:0: [sdb] Test WP failed, assume Write Enabled
Apr 25 15:05:33 node-0026b9140967 kernel: [ 53.799248] sd 6:0:0:0: [sdb] Asking for cache data failed
Apr 25 15:05:33 node-0026b9140967 kernel: [ 53.799316] sd 6:0:0:0: [sdb] Assuming drive cache: write through
Apr 25 15:06:24 node-0026b9140967 kernel: [ 105.494320] sd 6:0:0:0: [sdb] Test WP failed, assume Write Enabled
Apr 25 15:06:24 node-0026b9140967 kernel: [ 105.496851] sd 6:0:0:0: [sdb] Asking for cache data failed
Apr 25 15:06:24 node-0026b9140967 kernel: [ 105.496923] sd 6:0:0:0: [sdb] Assuming drive cache: write through
Apr 25 15:07:16 node-0026b9140967 kernel: [ 157.206555] sd 6:0:0:0: [sdb] Test WP failed, assume Write Enabled
Apr 25 15:07:16 node-0026b9140967 kernel: [ 157.209203] sd 6:0:0:0: [sdb] Asking for cache data failed
Apr 25 15:07:16 node-0026b9140967 kernel: [ 157.209274] sd 6:0:0:0: [sdb] Assuming drive cache: write through
Apr 25 15:08:08 node-0026b9140967 kernel: [ 208.918402] sd 6:0:0:0: [sdb] Test WP failed, assume Write Enabled
Apr 25 15:08:08 node-0026b9140967 kernel: [ 208.921058] sd 6:0:0:0: [sdb] Asking for cache data failed
Apr 25 15:08:08 node-0026b9140967 kernel: [ 208.921131] sd 6:0:0:0: [sdb] Assuming drive cache: write through
jamespage@node-0026b9140967:/var/log$ uname -a
Linux node-0026b9140967 3.4.0-030400rc4-generic-pae #201204230908 SMP Mon Apr 23 13:23:25 UTC 2012 i686 i686 i386 GNU/Linux
jamespage@node-0026b9140967:/var/log$

[Joseph Salisbury (jsalisbury)]

This issue appears to be an upstream bug, since you tested the latest upstream kernel. Would it be possible for you to open an upstream bug report at bugzilla.kernel.org [1]? That will allow the upstream Developers to examine the issue, and may provide a quicker resolution to the bug.

If you are comfortable with opening a bug upstream, It would be great if you can report back the upstream bug number in this bug report. That will allow us to link this bug to the upstream report.

[1] https://wiki.ubuntu.com/Bugs/Upstream/kernel

[Sree Harsha Totakura (sriharsha-totakura)]

I'm also experiencing this. In my case sdb happens to be the memory card reader. The output stops when I plug in a memory card. Here's an except from the dmesg output:

[ 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
[ 2849.045190] sdb: detected capacity change from 2032664576 to 0
[ 2893.403941] sd 6:0:0:0: [sdb] 3970048 512-byte logical blocks: (2.03 GB/1.89 GiB)
[ 2893.413063] sd 6:0:0:0: [sdb] No Caching mode page present
[ 2893.413074] sd 6:0:0:0: [sdb] Assuming drive cache: write through
[ 2893.418182] sd 6:0:0:0: [sdb] No Caching mode page present
[ 2893.418190] sd 6:0:0:0: [sdb] Assuming drive cache: write through
[ 2893.445548] sdb: sdb1

A similar bug has been raised at the kernel.org: https://bugzilla.kernel.org/show_bug.cgi?id=43190

[mike boatright (mike-boatright)]

I got the same problem. Happens with both32 and 64 bit on the CD Rom.

-Mike

[NuclearCat (denys-visp)]

Xubuntu 13.10
Device:
Bus 001 Device 006: ID 0bda:0158 Realtek Semiconductor Corp. USB 2.0 multicard reader
Device Descriptor:
  bLength 18
  bDescriptorType 1
  bcdUSB 2.00
  bDeviceClass 0 (Defined at Interface level)
  bDeviceSubClass 0
  bDeviceProtocol 0
  bMaxPacketSize0 64
  idVendor 0x0bda Realtek Semiconductor Corp.
  idProduct 0x0158 USB 2.0 multicard reader
  bcdDevice 58.87
  iManufacturer 1 Generic
  iProduct 2 USB2.0-CRW
  iSerial 3 20071114173400000
  bNumConfigurations 1

removing ums_realtek module helps, but hopefully ubuntu will propose solution for this problem (module options?)