syslog fills with messages due to empty SD card slot.

Bug #991395 reported by crf
18
This bug affects 4 people
Affects Status Importance Assigned to Milestone
Linux
Confirmed
Medium
linux (Ubuntu)
Triaged
Medium
Unassigned

Bug Description

Every 40 seconds or so, something like the following is printed in the syslog.

Apr 29 12:15:28 dellie-linux kernel: [12359.705257] sd 6:0:0:0: [sdb] Test WP failed, assume Write Enabled
Apr 29 12:15:28 dellie-linux kernel: [12359.707626] sd 6:0:0:0: [sdb] Asking for cache data failed
Apr 29 12:15:28 dellie-linux kernel: [12359.707634] sd 6:0:0:0: [sdb] Assuming drive cache: write through

I have a Dell laptop. sdb is probably my sd card reader slot. It's normally filled with a fake plastic protective card.

If I stick an actual sd card in the slot, the message logging goes away. Even after I pull the real card out, without unmounting it, the messaging doesn't come back. Once the system knows that the card's unmounted, the messages return.
---
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23.
ApportVersion: 2.0.1-0ubuntu7
Architecture: amd64
ArecordDevices:
 **** List of CAPTURE Hardware Devices ****
 card 0: Intel [HDA Intel], device 0: STAC92xx Analog [STAC92xx Analog]
   Subdevices: 2/2
   Subdevice #0: subdevice #0
   Subdevice #1: subdevice #1
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: chris 3153 F.... pulseaudio
Card0.Amixer.info:
 Card hw:0 'Intel'/'HDA Intel at 0xf6afc000 irq 47'
   Mixer name : 'IDT 92HD71B7X'
   Components : 'HDA:111d76b2,102802aa,00100302'
   Controls : 24
   Simple ctrls : 15
DistroRelease: Ubuntu 12.04
HibernationDevice: RESUME=UUID=656d1e1f-5a61-478c-b0f5-83de3100c497
MachineType: Dell Inc. Inspiron 1545
Package: linux (not installed)
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: root=UUID=9c0edb3e-d193-44ce-829f-858ced0747b2 ro acpi_sleep=old_ordering quiet splash resume=/dev/sda5
ProcVersionSignature: Ubuntu 2.6.38-13.56-generic 2.6.38.8
RelatedPackageVersions:
 linux-restricted-modules-2.6.38-13-generic N/A
 linux-backports-modules-2.6.38-13-generic N/A
 linux-firmware 1.79
SourcePackage: linux
Tags: precise precise
Uname: Linux 2.6.38-13-generic x86_64
UpgradeStatus: Upgraded to precise on 2012-04-28 (1 days ago)
UserGroups: adm admin cdrom dialout libvirtd lp lpadmin plugdev sambashare
WifiSyslog:
 Apr 30 08:05:05 dellie-linux wpa_supplicant[1492]: WPA: Group rekeying completed with 20:76:00:07:b0:d4 [GTK=CCMP]
 Apr 30 09:05:04 dellie-linux wpa_supplicant[1492]: WPA: Group rekeying completed with 20:76:00:07:b0:d4 [GTK=CCMP]
WpaSupplicantLog:

dmi.bios.date: 12/07/2009
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A14
dmi.board.name: 0G848F
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.:bvrA14:bd12/07/2009:svnDellInc.:pnInspiron1545:pvr:rvnDellInc.:rn0G848F:rvr:cvnDellInc.:ct8:cvr:
dmi.product.name: Inspiron 1545
dmi.sys.vendor: Dell Inc.

Revision history for this message
Brad Figg (brad-figg) wrote : Missing required logs.

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 991395

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

Changed in linux (Ubuntu):
status: New → Incomplete
Revision history for this message
crf (chrisfahlman) wrote : AcpiTables.txt

apport information

tags: added: apport-collected precise
description: updated
Revision history for this message
crf (chrisfahlman) wrote : AlsaDevices.txt

apport information

Revision history for this message
crf (chrisfahlman) wrote : AplayDevices.txt

apport information

Revision history for this message
crf (chrisfahlman) wrote : BootDmesg.txt

apport information

Revision history for this message
crf (chrisfahlman) wrote : CRDA.txt

apport information

Revision history for this message
crf (chrisfahlman) wrote : Card0.Amixer.values.txt

apport information

Revision history for this message
crf (chrisfahlman) wrote : Card0.Codecs.codec.0.txt

apport information

Revision history for this message
crf (chrisfahlman) wrote : CurrentDmesg.txt

apport information

Revision history for this message
crf (chrisfahlman) wrote : IwConfig.txt

apport information

Revision history for this message
crf (chrisfahlman) wrote : Lspci.txt

apport information

Revision history for this message
crf (chrisfahlman) wrote : Lsusb.txt

apport information

Revision history for this message
crf (chrisfahlman) wrote : PciMultimedia.txt

apport information

Revision history for this message
crf (chrisfahlman) wrote : ProcCpuinfo.txt

apport information

Revision history for this message
crf (chrisfahlman) wrote : ProcEnviron.txt

apport information

Revision history for this message
crf (chrisfahlman) wrote : ProcInterrupts.txt

apport information

Revision history for this message
crf (chrisfahlman) wrote : ProcModules.txt

apport information

Revision history for this message
crf (chrisfahlman) wrote : PulseList.txt

apport information

Revision history for this message
crf (chrisfahlman) wrote : RfKill.txt

apport information

Revision history for this message
crf (chrisfahlman) wrote : UdevDb.txt

apport information

Revision history for this message
crf (chrisfahlman) wrote : UdevLog.txt

apport information

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

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/

Changed in linux (Ubuntu):
importance: Undecided → Medium
tags: added: needs-upstream-testing
Changed in linux (Ubuntu):
status: Confirmed → Incomplete
crf (chrisfahlman)
tags: added: kernel-bug-exists-upstream
removed: needs-upstream-testing
Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

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

Changed in linux (Ubuntu):
status: Confirmed → Triaged
Revision history for this message
crf (chrisfahlman) wrote :

A new report on bugzilla.kernel.org:

https://bugzilla.kernel.org/show_bug.cgi?id=43190

Changed in linux:
importance: Unknown → Medium
status: Unknown → Invalid
Revision history for this message
crf (chrisfahlman) wrote :

the report on bugzilla.kernel.org was duped:

https://bugzilla.kernel.org/show_bug.cgi?id=43191

Changed in linux:
importance: Medium → Unknown
status: Invalid → Unknown
Changed in linux:
importance: Unknown → Medium
status: Unknown → Confirmed
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.