No hot plug function SD card reader and firewire PCI Express card with kernel 2.6.28 kernel 2.6.29 and krnel 2.6.30.rc3

Bug #370159 reported by Giorgio
16
This bug affects 2 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Expired
Medium
Unassigned

Bug Description

After upgrading from Intrepid to Jaunty I noticed the new kernel 2.6.28 didn't perform any more the hot plug function for the SD card reader and the Express card (firewire) on my Acer Aspire 5930G (even with the suggested options for the modules pciehp and sdhci). I tried with the kernel 2.6.29 and 2.6.30.rc3 (from http://kernel.ubuntu.com/~kernel-ppa/mainline/) without success. I've attached the output, for 2.6.30, of dmesg and lsmod: the module sdhci is loaded, the pciehp one isn't (I don't know, but perhaps it's connected to the failure). With the kernel 2.6.27 the module pciehp is loaded and, after a hot plug of a SD Sandisk, this is the relevant part of the output of lspci:

05:00.0 System peripheral: JMicron Technologies, Inc. SD/MMC Host Controller
05:00.2 SD Host controller: JMicron Technologies, Inc. Standard SD Host Controller
05:00.3 System peripheral: JMicron Technologies, Inc. MS Host Controller
05:00.4 System peripheral: JMicron Technologies, Inc. xD Host Controller

WORKAROUND: Use kernel parameter:
pciehp.pciehp_force=1

Revision history for this message
Giorgio (valle-giorgio) wrote :
Revision history for this message
gmerrick (at903) wrote :

I have a firewire removable chassis that worked just fine up until 9.04. Afterwards it does not appear anywhere in the system. modules seem to be loaded but I can plug/unplug the drive in and out of the system and nothing appears. External USB drives work fine as do 32Gb USB memory sticks.

What information would you like from me in regards to this?

Revision history for this message
Giorgio (valle-giorgio) wrote :

I found out a solution in an italian blog: adding to /boot/grub/menu.lst the string
"pciehp.pciehp_force=1"
(and eventually also "pciehp.pciehp_poll_mode=1", but for me the first option was enough). I added it directly at the end of the kernel 2.6.28, in the line starting with "kernel":

kernel /boot/vmlinuz-2.6.28-8-generic root=UUID=978d9a41-90b5-43ba-a434-4d6ac3e44bea ro quiet splash pciehp.pciehp_force=1

In the blog I read it was written to add this string after the commented line # defoptions=quiet splash but I didn't because I'm usually running the kernel 2.6.27 (that should manage pciehp as a module)

Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

This seems related to the following upstream thread - http://lkml.org/lkml/2008/10/29/246

Changed in linux (Ubuntu):
importance: Undecided → Medium
status: New → Triaged
penalvch (penalvch)
description: updated
tags: added: jaunty kernel-media needs-kernel-logs needs-upstream-testing
tags: added: regression-release
Revision history for this message
penalvch (penalvch) wrote :

Giorgio, thank you for reporting this and helping make Ubuntu better. Jaunty reached EOL on October 23, 2010.

Please see this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases

We were wondering if this is still an issue in a supported release? If so, could you please test for this with the latest development release of Ubuntu? ISO CD images are available from http://cdimage.ubuntu.com/daily-live/current/ .

If it remains an issue, could you please run the following command in the development release from a Terminal (Applications->Accessories->Terminal), as it will automatically gather and attach updated debug information to this report:

apport-collect -p linux <replace-with-bug-number>

Also, could you please test the latest upstream kernel available following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Please do not test the kernel in the mainline kernels archive directory daily folder, but the one all the way at the bottom. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this bug is fixed in the mainline kernel, please add the following tags:
kernel-fixed-upstream
kernel-fixed-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested. For example:
kernel-fixed-upstream-v3.7-rc1-quantal

This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description. As well, please remove the tag:
needs-upstream-testing

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-VERSION-NUMBER

As well, please remove the tag:
needs-upstream-testing

If you are unable to test the mainline kernel, please comment as to why specifically you were unable to test it and add the following tags:
kernel-unable-to-test-upstream
kernel-unable-to-test-upstream-VERSION-NUMBER

Please let us know your results. Thank you for your understanding.

Helpful Bug Reporting Tips:
https://help.ubuntu.com/community/ReportingBugs

Changed in linux (Ubuntu):
status: Triaged → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]

Changed in linux (Ubuntu):
status: Incomplete → Expired
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.