Ejecting firewire HD (iPod) freezes kernel

Bug #52943 reported by edschofield
4
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

Binary package hint: linux-image-686

I can reliably reproduce a kernel freeze with the current (2.6.15.26) Dapper 686 kernel. The problem does NOT apply to the 386 kernel of the same version, which seems to work fine.

Typing
    sudo eject /dev/sda
or choosing 'eject' from Nautilus locks the machine up solid. The /dev/sda device is a 3rd generation iPod attached to a firewire PCI card (Agere Systems FW323 (rev 04) (prog-if 10 [OHCI])).

My machine is an Intel P4, 2.8 GHz. This lockup occurs whether or not hyperthreading is enabled in the BIOS.

This appears related to bug #28691 (https://launchpad.net/distros/ubuntu/+source/linux-source-2.6.12/+bug/28691), but applies more widely than that bug description indicates, and is still present in the Dapper kernel.

The machine locks up solid, doesn't reply to pings, to movements of the mouse cursor, or even the magic SysReq key. I can't see any relevant entries in /var/log/kern.log or /var/log/dmesg. If there's any other info I can post, please let me know.

Revision history for this message
edschofield (schofield) wrote :

I forgot to add: I do not have any binary-only modules loaded into the kernel.

Revision history for this message
Ben Collins (ben-collins) wrote :

Please try this from the console to see if there are any kernel oopses.

Changed in linux-meta:
status: Unconfirmed → Needs Info
Revision history for this message
edschofield (schofield) wrote :

Tried it -- no console messages at all. It just freezes.

Revision history for this message
edschofield (schofield) wrote :

The Numlock and Capslock keys also cease to change the state of the keyboard LEDs after the lockup.

edschofield (schofield)
Changed in linux-source-2.6.15:
status: Needs Info → Confirmed
Revision history for this message
Launchpad Janitor (janitor) wrote : This bug is now reported against the 'linux' package

Beginning with the Hardy Heron 8.04 development cycle, all open Ubuntu kernel bugs need to be reported against the "linux" kernel package. We are automatically migrating this linux-source-2.6.15 kernel bug to the new "linux" package. We appreciate your patience and understanding as we make this transition. Also, if you would be interested in testing the upcoming Intrepid Ibex 8.10 release, it is available at http://www.ubuntu.com/testing . Please let us know your results. Thanks!

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

The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would appreciate it if you could please test this newer 2.6.27 Ubuntu kernel. There are one of two ways you should be able to test:

1) If you are comfortable installing packages on your own, the linux-image-2.6.27-* package is currently available for you to install and test.

--or--

2) The upcoming Alpha5 for Intrepid Ibex 8.10 will contain this newer 2.6.27 Ubuntu kernel. Alpha5 is set to be released Thursday Sept 4. Please watch http://www.ubuntu.com/testing for Alpha5 to be announced. You should then be able to test via a LiveCD.

Please let us know immediately if this newer 2.6.27 kernel resolves the bug reported here or if the issue remains. More importantly, please open a new bug report for each new bug/regression introduced by the 2.6.27 kernel and tag the bug report with 'linux-2.6.27'. Also, please specifically note if the issue does or does not appear in the 2.6.26 kernel. Thanks again, we really appreicate your help and feedback.

Revision history for this message
edschofield (schofield) wrote :

I believe this issue has been resolved in upstream kernels for about two years. I no longer use Ubuntu, or that iPod, or any Firewire devices, so I'm afraid I can't easily check.

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

Thanks for the update. I'll go ahead and close this report. I'm tentatively setting it to "Fix Released" based on your comment that this should have been resolved upstream and since we've rebased recently with upstream this should be resolved for Ubuntu as well. Thanks.

Changed in linux:
status: Confirmed → Fix Released
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.