SD Card not accessible until reboot
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Expired
|
Medium
|
Unassigned |
Bug Description
I put a SD Card into the card reader of my notebook. It won't be detected, dmesg says "Timeout, waiting for hardware interrupt".
If i reboot the machine, the SD Card can be mounted one or two times, after that the same problem described above appears. If i remove the SD Card and put it in again, it is the same problem.
Tested multiple SD Cards from 2 GB SD, 4 GB SDHC, 64 GB SDXC and many MicroSD Cards with Adapter, it is all the same.
ProblemType: Bug
DistroRelease: Ubuntu 13.04
Package: linux-image-
ProcVersionSign
Uname: Linux 3.8.0-1-generic x86_64
ApportVersion: 2.8-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/
/dev/snd/seq: timidity 2056 F.... timidity
CRDA:
country DE:
(2400 - 2494 @ 40), (N/A, 35)
(4910 - 5835 @ 40), (N/A, 35)
Date: Tue Jan 22 22:54:12 2013
GvfsMonitorLog: Monitoring events. Press Ctrl+C to quit.
HibernationDevice: RESUME=
HotplugNewDevices:
HotplugNewMounts:
InstallationDate: Installed on 2012-10-07 (107 days ago)
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Beta amd64 (20120926)
MachineType: Acer V5-171
MarkForUpload: True
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon.
RelatedPackageV
linux-
linux-
linux-firmware 1.99
SourcePackage: linux
Symptom: storage
UdevMonitorLog:
monitor will print the received events for:
UDEV - the event which udev sends out after rule processing
UdisksMonitorLog:
Monitoring the udisks daemon. Press Ctrl+C to exit.
22:54:35.157: The udisks-daemon is running (name-owner :1.47).
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/26/2012
dmi.bios.vendor: Acer
dmi.bios.version: V1.02
dmi.board.
dmi.board.name: Mimic
dmi.board.vendor: Acer
dmi.board.version: Type2 - Board Version
dmi.chassis.type: 10
dmi.chassis.vendor: Acer
dmi.chassis.
dmi.modalias: dmi:bvnAcer:
dmi.product.name: V5-171
dmi.product.
dmi.sys.vendor: Acer
Did this issue start happening after an update/upgrade? Was there a kernel version where you were not having this particular problem? This will help determine if the problem you are seeing is the result of the introduction of a regression, and when this regression was introduced.