public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Stefan Richter <stefanr@s5r6.in-berlin.de>
To: Andrew de Quincey <adq_dvb@lidskialf.net>
Cc: linux1394-devel@lists.sourceforge.net, linux-scsi@vger.kernel.org
Subject: Re: linux kernel panic when ejecting ieee1394 ipod
Date: Thu, 08 Dec 2005 02:17:35 +0100	[thread overview]
Message-ID: <439789AF.4070500@s5r6.in-berlin.de> (raw)
In-Reply-To: <200512072358.15398.adq_dvb@lidskialf.net>

Andrew de Quincey wrote to linux1394-devel:
> Reposting to the -devel list since there was no response on -user.

I would have responded eventually... :-)

> Hi, I'm using linux kernel 2.6.14 with an generation 1 ipod connected via 
> ieee1394/sbp2.
> 
> I can mount/unmount it and use it fine. It even works with HAL now.
> 
> The problem comes when I want to remove it. If I do:
> 
> eject /dev/sdb
> 
> The kernel panics with the following error:
> Kernel panic - not syncing: PCI-DMA: high address but no IOMMU

I think there was another report about "eject" of a FireWire iPod 
crashing the kernel but I cannot find it in any archive anymore and do 
not remember which kernel version and machine architecture was affected.

The eject command does work for me with a few different SBP-2 devices, 
but I do not have an iPod. But more importantly, I have currently only 
i386 with 512 MB RAM to test. The "high address but no IOMMU" panic 
message is specific to x86_64.

I had only a superficial look at it so far and did not spot anything 
obvious. (That's because I do not know anything about Linux' memory 
management.) My only idea at the moment is to Cc this to linux-scsi 
since sd_mod does work for you but the one thing you do via the sg 
driver does not.

> I'm using an nforce 4 motherboard (Asus A8N-SLI Deluxe). The ipod is attached 
> to the ieee1394 port on a creative labs Audigy2 sound card (uses OHCI-1394).
> 
> I do _not_ have "Enable Phys DMA support for SBP2 (Debug)" enabled if thats 
> any help.

-- 
Stefan Richter
-=====-=-=-= ==-- -=---
http://arcgraph.de/sr/

       reply	other threads:[~2005-12-08  1:19 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200512072358.15398.adq_dvb@lidskialf.net>
2005-12-08  1:17 ` Stefan Richter [this message]
2005-12-08  1:57 ` linux kernel panic when ejecting ieee1394 ipod Andrew de Quincey
     [not found] ` <200512080119.48740.adq@lidskialf.net>
2005-12-08  1:59   ` Andrew de Quincey
2005-12-08  2:09     ` Andrew de Quincey
2005-12-08  2:44       ` Stefan Richter
2005-12-08  3:19         ` Andrew de Quincey
2005-12-08  7:52           ` Stefan Richter
2005-12-08 19:27             ` Stefan Richter
2005-12-08 17:34         ` Patrick Mansfield
2005-12-08 19:25           ` Stefan Richter
2005-12-09 13:37           ` Jens Axboe
2005-12-09 13:42             ` Jens Axboe
2005-12-09 18:39               ` Stefan Richter
2005-12-09 19:35                 ` Stefan Richter
2005-12-09 22:45                   ` James Bottomley
2005-12-10 18:20                     ` Christoph Hellwig
2005-12-13 20:44                     ` Stefan Richter
2005-12-13 20:54                       ` Jens Axboe
2005-12-10  8:48                   ` Jens Axboe
2005-12-10  9:28                     ` Christoph Hellwig
2005-12-10 10:55                       ` Stefan Richter

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=439789AF.4070500@s5r6.in-berlin.de \
    --to=stefanr@s5r6.in-berlin.de \
    --cc=adq_dvb@lidskialf.net \
    --cc=linux-scsi@vger.kernel.org \
    --cc=linux1394-devel@lists.sourceforge.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox