| Summary: | When a SDCARD is in the PCI SDCARD Reader at boot time, SDCARD fails to initialize the device. | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | gcarter |
| Component: | kernel | Assignee: | Kernel Maintainer List <kernel-maint> |
| Status: | CLOSED INSUFFICIENT_DATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | low | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 16 | CC: | gansalmon, itamar, jonathan, kernel-maint, madhu.chinakonda |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2012-09-04 15:49:55 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
[mass update] kernel-3.3.0-4.fc16 has been pushed to the Fedora 16 stable repository. Please retest with this update. [mass update] kernel-3.3.0-4.fc16 has been pushed to the Fedora 16 stable repository. Please retest with this update. [mass update] kernel-3.3.0-4.fc16 has been pushed to the Fedora 16 stable repository. Please retest with this update. |
Description of problem: When a SDCARD is place in the following device at startup time, errors occur: 0e:07.1 SD Host controller: Ricoh Co Ltd R5C822 SD/SDIO/MMC/MS/MSPro Host Adapter (rev 22) Subsystem: Rioworks Device 207a Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- Latency: 32, Cache Line Size: 64 bytes Interrupt: pin B routed to IRQ 17 Region 0: Memory at f8500800 (32-bit, non-prefetchable) [size=256] Capabilities: <access denied> Kernel driver in use: sdhci-pci Kernel modules: sdhci-pci 0e:07.2 System peripheral: Ricoh Co Ltd R5C592 Memory Stick Bus Host Adapter (rev 12) Subsystem: Rioworks Device 207a Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- Latency: 32, Cache Line Size: 64 bytes Interrupt: pin B routed to IRQ 17 Region 0: Memory at f8501000 (32-bit, non-prefetchable) [size=256] Capabilities: <access denied> Kernel driver in use: r592 Kernel modules: r592 Here is the DMESG output: [ 5.543080] mmcblk0: error -110 sending status command, retrying [ 5.543110] mmcblk0: error -110 sending status command, retrying [ 5.543169] mmcblk0: error -110 sending status command, aborting [ 5.543176] end_request: I/O error, dev mmcblk0, sector 64 [ 5.543179] Buffer I/O error on device mmcblk0, logical block 8 [ 5.543277] mmcblk0: error -110 sending status command, retrying [ 5.543307] mmcblk0: error -110 sending status command, retrying [ 5.543362] mmcblk0: error -110 sending status command, aborting [ 5.543366] end_request: I/O error, dev mmcblk0, sector 64 [ 5.543369] Buffer I/O error on device mmcblk0, logical block 8 [ 5.543470] mmcblk0: error -110 sending status command, retrying [ 5.543495] mmcblk0: error -110 sending status command, retrying [ 5.543549] mmcblk0: error -110 sending status command, aborting [ 5.543552] end_request: I/O error, dev mmcblk0, sector 64 [ 5.543554] Buffer I/O error on device mmcblk0, logical block 8 [ 5.543650] mmcblk0: error -110 sending status command, retrying [ 5.543678] mmcblk0: error -110 sending status command, retrying [ 5.543732] mmcblk0: error -110 sending status command, aborting [ 5.543735] end_request: I/O error, dev mmcblk0, sector 64 [ 5.543737] Buffer I/O error on device mmcblk0, logical block 8 [ 5.543830] mmcblk0: error -110 sending status command, retrying [ 5.543860] mmcblk0: error -110 sending status command, retrying [ 5.543913] mmcblk0: error -110 sending status command, aborting [ 5.543916] end_request: I/O error, dev mmcblk0, sector 64 [ 5.543918] Buffer I/O error on device mmcblk0, logical block 8 [ 5.544033] mmcblk0: error -110 sending status command, retrying [ 5.544058] mmcblk0: error -110 sending status command, retrying [ 5.544111] mmcblk0: error -110 sending status command, aborting [ 5.544114] end_request: I/O error, dev mmcblk0, sector 64 [ 5.544116] Buffer I/O error on device mmcblk0, logical block 8 [ 5.544211] mmcblk0: error -110 sending status command, retrying [ 5.544240] mmcblk0: error -110 sending status command, retrying [ 5.544293] mmcblk0: error -110 sending status command, aborting [ 5.544296] end_request: I/O error, dev mmcblk0, sector 64 [ 5.544298] Buffer I/O error on device mmcblk0, logical block 8 [ 5.544395] mmcblk0: error -110 sending status command, retrying [ 5.544419] mmcblk0: error -110 sending status command, retrying [ 5.544472] mmcblk0: error -110 sending status command, aborting [ 5.544475] end_request: I/O error, dev mmcblk0, sector 64 [ 5.544477] Buffer I/O error on device mmcblk0, logical block 8 [ 5.544570] mmcblk0: error -110 sending status command, retrying [ 5.544593] mmcblk0: error -110 sending status command, retrying [ 5.544622] mmcblk0: error -110 sending status command, aborting [ 5.544625] end_request: I/O error, dev mmcblk0, sector 64 [ 5.544719] mmcblk0: error -110 sending status command, retrying [ 5.544743] mmcblk0: error -110 sending status command, retrying [ 5.544772] mmcblk0: error -110 sending status command, aborting [ 5.544775] end_request: I/O error, dev mmcblk0, sector 64 [ 5.544868] mmcblk0: error -110 sending status command, retrying [ 5.544893] mmcblk0: error -110 sending status command, retrying [ 5.544922] mmcblk0: error -110 sending status command, aborting [ 5.544925] end_request: I/O error, dev mmcblk0, sector 64 [ 5.545031] mmcblk0: error -110 sending status command, retrying [ 5.545054] mmcblk0: error -110 sending status command, retrying [ 5.545084] mmcblk0: error -110 sending status command, aborting [ 5.545087] end_request: I/O error, dev mmcblk0, sector 256 [ 5.545184] mmcblk0: error -110 sending status command, retrying [ 5.545209] mmcblk0: error -110 sending status command, retrying [ 5.545238] mmcblk0: error -110 sending status command, aborting [ 5.545242] end_request: I/O error, dev mmcblk0, sector 512 [ 5.545335] mmcblk0: error -110 sending status command, retrying [ 5.545359] mmcblk0: error -110 sending status command, retrying [ 5.545389] mmcblk0: error -110 sending status command, aborting [ 5.545392] end_request: I/O error, dev mmcblk0, sector 32 [ 5.545488] mmcblk0: error -110 sending status command, retrying [ 5.545512] mmcblk0: error -110 sending status command, retrying [ 5.545541] mmcblk0: error -110 sending status command, aborting [ 5.545545] end_request: I/O error, dev mmcblk0, sector 4096 Version-Release number of selected component (if applicable): Fedora 16 latest update as of posted date. How reproducible: Place a SDCARD in the machine, in this case a W840 (i.e.) 00:00.0 Host bridge: Intel Corporation Mobile 4 Series Chipset Memory Controller Hub (rev 07) 00:01.0 PCI bridge: Intel Corporation Mobile 4 Series Chipset PCI Express Graphics Port (rev 07) 00:1a.0 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #4 (rev 03) 00:1a.1 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #5 (rev 03) 00:1a.2 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #6 (rev 03) 00:1a.7 USB Controller: Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #2 (rev 03) 00:1b.0 Audio device: Intel Corporation 82801I (ICH9 Family) HD Audio Controller (rev 03) 00:1c.0 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 1 (rev 03) 00:1c.2 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 3 (rev 03) 00:1c.3 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 4 (rev 03) 00:1c.4 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 5 (rev 03) 00:1d.0 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #1 (rev 03) 00:1d.1 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #2 (rev 03) 00:1d.2 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #3 (rev 03) 00:1d.7 USB Controller: Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #1 (rev 03) 00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev 93) 00:1f.0 ISA bridge: Intel Corporation ICH9M-E LPC Interface Controller (rev 03) 00:1f.2 IDE interface: Intel Corporation ICH9M/M-E 2 port SATA IDE Controller (rev 03) 00:1f.3 SMBus: Intel Corporation 82801I (ICH9 Family) SMBus Controller (rev 03) 00:1f.5 IDE interface: Intel Corporation ICH9M/M-E 2 port SATA IDE Controller (rev 03) 01:00.0 PCI bridge: PLX Technology, Inc. PEX 8624 24-lane, 6-Port PCI Express Gen 2 (5.0 GT/s) Switch [ExpressLane] (rev ab) 02:00.0 PCI bridge: PLX Technology, Inc. PEX 8624 24-lane, 6-Port PCI Express Gen 2 (5.0 GT/s) Switch [ExpressLane] (rev ab) 02:04.0 PCI bridge: PLX Technology, Inc. PEX 8624 24-lane, 6-Port PCI Express Gen 2 (5.0 GT/s) Switch [ExpressLane] (rev ab) 02:05.0 PCI bridge: PLX Technology, Inc. PEX 8624 24-lane, 6-Port PCI Express Gen 2 (5.0 GT/s) Switch [ExpressLane] (rev ab) 03:00.0 VGA compatible controller: ATI Technologies Inc Device 9509 06:00.0 VGA compatible controller: ATI Technologies Inc Device 9509 06:00.1 Audio device: ATI Technologies Inc Radeon HD 3870 Audio device 08:00.0 Ethernet controller: Marvell Technology Group Ltd. 88E8055 PCI-E Gigabit Ethernet Controller (rev 12) 0b:00.0 Network controller: Atheros Communications Inc. AR928X Wireless Network Adapter (PCI-Express) (rev 01) 0c:00.0 SATA controller: JMicron Technology Corp. JMB360 AHCI Controller (rev 02) 0e:07.0 FireWire (IEEE 1394): Ricoh Co Ltd R5C832 IEEE 1394 Controller (rev 05) 0e:07.1 SD Host controller: Ricoh Co Ltd R5C822 SD/SDIO/MMC/MS/MSPro Host Adapter (rev 22) 0e:07.2 System peripheral: Ricoh Co Ltd R5C592 Memory Stick Bus Host Adapter (rev 12) Steps to Reproduce: 1. Shutdown machine. Insert SDCARD. 2. Turn on machine. 3. Boot Fedora 16, all kernels I have, are affected by this issue. 3.2, 3.2.1, 3.1.9, 3.1.8, 3.1.7 Use to work OK I think in Fedora 14. Unfortunately I don't have a spare drive to test. No VT-d support on this machine so I can't debug with a guest as it is a PCI device. Actual results: Are random. Sometimes after boot you have to take the card out and reinsert it. Drives my plasma widgets a bit giddy that alert media insertions. Sometimes it works, rarely though. I think on ocassion, abrt fires up and thinks something is broken, and attempted to post the issue. It fails, with nothing in the posting box which is strange. I am not sure if this is the issue, but I am including it here because it might be related to bug: https://bugzilla.redhat.com/show_bug.cgi?id=782254 It might be causing that oops. Although I have never had issues before. Expected results: Should not require a reinsertion of the media at boot time. It should recognize the SDCARD and properly initialize the device with it during boot. This doesn't happen with no card inserted at startup time by the way. I have checked several different cards and they all cause the same problem at startup if they are inserted in the reader. Additional info: My Machine is a OCZ Whitebox W840. Pretty vanilla stuff with R600 adapters.