Bug 1025479

Summary:	JMicron card reader works only if card is insert before power on computer
Product:	[Fedora] Fedora	Reporter:	Peque <msdeleonpeque>
Component:	kernel	Assignee:	Kernel Maintainer List <kernel-maint>
Status:	CLOSED INSUFFICIENT_DATA	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	19	CC:	bnrj.rudra, gansalmon, itamar, jonathan, kernel-maint, madhu.chinakonda, msdeleonpeque
Target Milestone:	---	Flags:	jforbes: needinfo?
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:	986488
Clones:	1076656 (view as bug list)		Environment:
Last Closed:	2014-03-10 14:45:53 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Peque 2013-10-31 19:08:44 UTC

+++ This bug was initially created as a clone of Bug #986488 +++

Description of problem:
JMicron Standard SD Host Controller does not detect  Memory card (eg SD) if the card is inserted when fedora is running. I need to restart computer with memory card inserted to get it into.

Version-Release number of selected component (if applicable):
JMicron Technology Corp. Standard SD Host Controller (rev 30)


How reproducible:
Every time

Steps to Reproduce:
1. boot fedora
2. insert memory card
3.

Actual results:

Memory card not detected

Expected results:
Memory card should be detected

Additional info:

lspci|grep SD
05:00.0 System peripheral: JMicron Technology Corp. SD/MMC Host Controller (rev 30)
05:00.2 SD Host controller: JMicron Technology Corp. Standard SD Host Controller (rev 30)

$ uname -r
3.9.9-302.fc19.x86_64


This is a duplicate of https://bugzilla.redhat.com/show_bug.cgi?id=855515, I reopend it as a endoflife is there for f17 against which the bug is reported.

--- Additional comment from Peque on 2013-08-17 22:09:47 EDT ---

Same problem here. It has always been this way for me since I bought the computer. Kernel version 3.10.6-200.fc19.x86_64.

--- Additional comment from Josh Boyer on 2013-09-18 16:54:05 EDT ---

*********** MASS BUG UPDATE **************

We apologize for the inconvenience.  There is a large number of bugs to go through and several of them have gone stale.  Due to this, we are doing a mass bug update across all of the Fedora 19 kernel bugs.

Fedora 19 has now been rebased to 3.11.1-200.fc19.  Please test this kernel update and let us know if you issue has been resolved or if it is still present with the newer kernel.

If you experience different issues, please open a new bug report for those.

--- Additional comment from Josh Boyer on 2013-10-08 12:51:19 EDT ---

This bug is being closed with INSUFFICIENT_DATA as there has not been a response in 2 weeks. If you are still experiencing this issue, please reopen and attach the relevant data from the latest kernel you are running and any data that might have been requested previously.

Comment 1 Peque 2013-10-31 19:15:44 UTC

Same bug reported for Fedora 17 (#781812, #855515), but was never solved.

Problem still exist in Fedora 19. Using kernel version 3.11.6-200.fc19.x86_64.

Comment 2 Justin M. Forbes 2014-01-03 22:12:22 UTC

*********** MASS BUG UPDATE **************

We apologize for the inconvenience.  There is a large number of bugs to go through and several of them have gone stale.  Due to this, we are doing a mass bug update across all of the Fedora 19 kernel bugs.

Fedora 19 has now been rebased to 3.12.6-200.fc19.  Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel.

If you have moved on to Fedora 20, and are still experiencing this issue, please change the version to Fedora 20.

If you experience different issues, please open a new bug report for those.

Comment 3 Justin M. Forbes 2014-03-10 14:45:53 UTC

*********** MASS BUG UPDATE **************

This bug has been in a needinfo state for more than 1 month and is being closed with insufficient data due to inactivity. If this is still an issue with Fedora 19, please feel free to reopen the bug and provide the additional information requested.