Ejecting a firewire iPod causes kernel panic

Bug #20876 reported by Chris Halse Rogers
6
Affects Status Importance Assigned to Milestone
linux-source-2.6.15 (Ubuntu)
Fix Released
Medium
Ben Collins

Bug Description

Trying to eject the ipod results in a kernel panic.

I have a 3G iPod, connected via firewire.
Up-to-date Breezy install, kernel version 2.6.12-8-amd64-k8

Running the command "eject -v ipod" from a terminal results in:
eject -v ipod
...
unmounting /media/ipod
/dev/sdb2 is multipartition device.
Trying to eject /dev/sdb2 using CD-ROM eject command
Kernel Panic - not synching: PCI-DMA: High address but no IOMMU

Running "sudo umount /media/ipod" succeeds, but the ipod still reports "Do not
disconnect"

Ejecting when the ipod is connected via USB works:
eject -v ipod
...
unmounting /media/ipod
/dev/sdb2 is multipartition device.
Trying to eject /dev/sdb2 using CD-ROM eject command
CD-ROM eject command succeeded

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

Not sure if this is an ieee1394 bug, or an amd64 bug. Do you have an i386 system
to test this on?

Revision history for this message
Chris Halse Rogers (raof) wrote :

Created an attachment (id=3624)
Output of sudo lspci -vvv

Revision history for this message
Chris Halse Rogers (raof) wrote :

(In reply to comment #1)
> Not sure if this is an ieee1394 bug, or an amd64 bug. Do you have an i386 system
> to test this on?

Tested on the same computer using the latest Breezy i386 live cd - Ejecting
works fine there, so it seems to be something amd64 specific.
Anything else I can do to help?

Revision history for this message
Stephan Fabel (sfabel) wrote :

I can confirm this bug. Kernel panics giving out this message:

"Kernel panic - not syncing: PCI-DMA: high address but no IOMMU"

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

This bug has been fixed in an upcoming release kernel. Please keep an eye out
for linux-image-2.6.15-8.10, or higher in your next upgrade. If this upgrade
does not fix your problem, please reopen this bug report, and refresh any
information that was requested before.

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

Fixed in 2.6.15-8.10

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.