'Test WP failed, assume Write Enabled' messages on console
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Linux |
Confirmed
|
Medium
|
|||
linux (Ubuntu) |
Triaged
|
Medium
|
Unassigned |
Bug Description
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
ProcVersionSign
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/
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info: Error: [Errno 2] No such file or directory
Card0.Amixer.
Date: Tue Apr 24 20:43:07 2012
HibernationDevice: RESUME=
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=
RelatedPackageV
linux-
linux-
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.
dmi.product.name: Vostro 1220
dmi.sys.vendor: Dell Inc.
Changed in linux (Ubuntu): | |
status: | New → Confirmed |
Changed in linux: | |
importance: | Unknown → Medium |
status: | Unknown → Confirmed |
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/KernelMainl ineBuilds . 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/