linux-scsi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jens Axboe <jens.axboe@oracle.com>
To: James Bottomley <James.Bottomley@SteelEye.com>
Cc: Bob Tracy <rct@gherkin.frus.com>,
	linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org,
	hch@infradead.org
Subject: Re: BAD_SG_DMA panic in aha1542
Date: Mon, 30 Apr 2007 19:32:45 +0200	[thread overview]
Message-ID: <20070430173243.GP21015@kernel.dk> (raw)
In-Reply-To: <1177712499.3688.25.camel@mulgrave.il.steeleye.com>

On Fri, Apr 27 2007, James Bottomley wrote:
> > sgpnt[0:1] page c1ee5af0/0x1ee5af0 length 32
> > Kernel panic - not syncing: Buffer at physical address > 16 Mb used for aha1542
> > 
> > As before, no problems using the sda hard disk (which is the boot drive):
> > everything works reliably until I touch the cdrom drive.
> > 
> > I'll be happy to assist with the debugging, but the system with the
> > aha1542 has no development facilities, i.e., I'll have to build test
> > kernels on a different system, and turnaround is going to be slow :-(.
> 
> 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.

It's due to the crappy ->generic_packet() ioctl stuff, it bypasses the
block layer. So that needs to be converted to use block pc requests and
the block layer interface, then things will just work.

Christoph had a sort-of ready patch for that some time ago. Christoph,
did that ever materialize into a full blown patch?

-- 
Jens Axboe


  parent reply	other threads:[~2007-04-30 17:37 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-27 21:47 BAD_SG_DMA panic in aha1542 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
2007-04-30 14:33   ` Bob Tracy
2007-04-30 17:32   ` Jens Axboe [this message]
2007-04-30 17:39     ` Christoph Hellwig
2007-04-30 17:52       ` Jens Axboe
  -- strict thread matches above, loose matches on Subject: below --
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=20070430173243.GP21015@kernel.dk \
    --to=jens.axboe@oracle.com \
    --cc=James.Bottomley@SteelEye.com \
    --cc=hch@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=rct@gherkin.frus.com \
    /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;
as well as URLs for NNTP newsgroup(s).