All of lore.kernel.org
 help / color / mirror / Atom feed
From: James Bottomley <James.Bottomley@steeleye.com>
To: "Dr. Ernst Molitor" <molitor@uni-bonn.de>
Cc: Andrew Morton <akpm@osdl.org>,
	SCSI Mailing List <linux-scsi@vger.kernel.org>
Subject: Re: Fw: PROBLEM: Linux V. 2.6.3 panics with "Buffers at physical address >16Mb used for aha1542" at boot time
Date: 20 Feb 2004 08:49:24 -0800	[thread overview]
Message-ID: <1077295765.1937.0.camel@mulgrave> (raw)
In-Reply-To: <1077265837.1297.9.camel@felicia>

On Fri, 2004-02-20 at 00:30, Dr. Ernst Molitor wrote:
> Please don't hesitate to contact me if I can be of any further help in
> this matter.

The problem seems to be a non-GFP_DMA allocation in sr.c.  Could you try
this patch?

Thanks,

James

===== drivers/scsi/sr.c 1.98 vs edited =====
--- 1.98/drivers/scsi/sr.c	Mon Feb  9 12:59:10 2004
+++ edited/drivers/scsi/sr.c	Fri Feb 20 08:47:55 2004
@@ -716,7 +716,7 @@
 	set_disk_ro(cd->disk, 1);
 
 	/* allocate a request for the TEST_UNIT_READY */
-	SRpnt = scsi_allocate_request(cd->device, GFP_KERNEL);
+	SRpnt = scsi_allocate_request(cd->device, GFP_KERNEL | GFP_DMA);
 	if (!SRpnt) {
 		printk(KERN_WARNING "(get_capabilities:) Request allocation "
 		       "failure.\n");


  parent reply	other threads:[~2004-02-20 16:49 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-19  1:12 Fw: PROBLEM: Linux V. 2.6.3 panics with "Buffers at physical address >16Mb used for aha1542" at boot time Andrew Morton
2004-02-20  2:18 ` James Bottomley
2004-02-20  8:30   ` Dr. Ernst Molitor
2004-02-20  8:38     ` Jens Axboe
2004-02-20 18:10       ` James Bottomley
2004-02-20 18:49         ` Jens Axboe
2004-02-20 19:37         ` Jens Axboe
2004-02-23 16:48         ` Jens Axboe
2004-02-23 17:34           ` James Bottomley
2004-02-23 19:04             ` Jens Axboe
2004-02-20 16:49     ` James Bottomley [this message]
2004-02-20 17:52       ` Mike Anderson
2004-02-20 18:06         ` James Bottomley
2004-02-20 20:17       ` Dr. Ernst Molitor

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=1077295765.1937.0.camel@mulgrave \
    --to=james.bottomley@steeleye.com \
    --cc=akpm@osdl.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=molitor@uni-bonn.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.