From: rct@gherkin.frus.com (Bob Tracy)
To: James Bottomley <James.Bottomley@SteelEye.com>
Cc: linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org
Subject: Re: BAD_SG_DMA panic in aha1542
Date: Fri, 27 Apr 2007 18:53:17 -0500 (CDT) [thread overview]
Message-ID: <20070427235317.71B9DDBA2@gherkin.frus.com> (raw)
In-Reply-To: <1177712499.3688.25.camel@mulgrave.il.steeleye.com> "from James Bottomley at Apr 27, 2007 05:21:39 pm"
James Bottomley wrote:
> On Fri, 2007-04-27 at 16:47 -0500, Bob Tracy wrote:
> > I previously reported an ISA DMA issue for the 2.6.12 kernel. The issue
> > persists through at least 2.6.18. SCSI controller is an Adaptec
> > AHA-1542B (ISA).
> >
> > The action "mount -t iso9660 /dev/scd0 /mnt/cdrom -r"
> >
> > produces
> >
> > (cdrom detection messages as various modules autoload, then...)
>
> Knowing what these messages are is would be helpful; it tells me what
> point in the initialisation it got to.
Sorry about that... I'm running the DSL-N distribution (based on
Knoppix), and having to transcribe the log messages by hand from the
console, i.e., there's no logfile to cut-and-paste from :-(. I don't
have access to the machine except on weekdays, but I'll repeat the
crash first thing Monday morning and copy everything that's there...
> I'm interested.
>
> This is clearly a use_sg==1 path that has failed to bounce the buffer
> for some reason ... and I was contemplating eliminating the GFP_DMA from
> our sr driver because I thought the block bouncing had it covered.
>
> It might also be helpful to apply this patch. It should give a stack
> trace of the problem command and not immediately panic the box.
I'll throw together a 2.6.21 kernel with this patch and give it a try.
Again, it will be at least Monday before you hear back from me on this.
Thanks!
--
-----------------------------------------------------------------------
Bob Tracy WTO + WIPO = DMCA? http://www.anti-dmca.org
rct@frus.com
-----------------------------------------------------------------------
next prev parent reply other threads:[~2007-04-27 23:53 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-27 21:47 Bob Tracy
2007-04-27 22:13 ` Alan Cox
2007-04-27 23:56 ` Bob Tracy
2007-04-27 22:21 ` James Bottomley
2007-04-27 23:53 ` Bob Tracy [this message]
2007-04-30 14:33 ` Bob Tracy
2007-04-30 17:32 ` Jens Axboe
2007-04-30 17:39 ` Christoph Hellwig
2007-04-30 17:52 ` Jens Axboe
2007-05-01 2:10 Bob Tracy
2007-05-01 13:33 ` Jens Axboe
2007-05-01 13:42 ` Bob Tracy
2007-05-01 13:46 ` Alan Cox
2007-05-01 18:32 ` Bob Tracy
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=20070427235317.71B9DDBA2@gherkin.frus.com \
--to=rct@gherkin.frus.com \
--cc=James.Bottomley@SteelEye.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
/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
Powered by JetHome