From: "Dr. Ernst Molitor" <molitor@uni-bonn.de>
To: James Bottomley <James.Bottomley@steeleye.com>
Cc: Andrew Morton <akpm@osdl.org>,
SCSI Mailing List <linux-scsi@vger.kernel.org>,
molitor@uni-bonn.de
Subject: Re: Fw: PROBLEM: Linux V. 2.6.3 panics with "Buffers at physical address >16Mb used for aha1542" at boot time
Date: Fri, 20 Feb 2004 09:30:37 +0100 [thread overview]
Message-ID: <1077265837.1297.9.camel@felicia> (raw)
In-Reply-To: <1077243517.2164.61.camel@mulgrave>
Dear James Bottomley,
thank you very much for looking into the problem I have seen.
Following to your kind suggestion, I have commented out the two "panic
(... Buffers and physical address > 16Mb ...)" lines in the aha1542.c
source and added "BUG();"-lines in their places. Booting the kernel
built afterwards resulted in a bunch of messages; I haven't been able to
read the first lines; this is what I could copy:
[<c02ee972>] scsi_request_fn+0x1c2/0x310
[<c02aa35d>] __elv_add_request+0x2d/0x50
[<c02aca14>] blk_insert_request+0x84/0xc0
[<c02ed679>] scsi_insert_special_req+0x39/0x40
[<c02ed8a9>] scsi_wait_req+0x69/0xb0
[<c02ed7c0>] scsi_wait_done+0x0/0x80
[<c0319980>] sr_do_ioctl+0x90/0x290
[<c0319735>] sr_packet+0x25/0x40
[<c0320262>] cdrom_is_mrw+0x52/0x80
[<c03194b0>] get_capabilities+0x1d0/0x430
[<c023d87f>] sprintf+0x1f/0x30
[<c0318fd1>] sr_probe+0x1f/0x30
[<c02a736d>] bus_match+0x3d/0x70
[<c02a74ac>] driver_attach+0x5c/0xa0
[<c02a77c6>] bus_add_driver+0xa6/0xc0
[<c05422ff>] init_sr+0x2f/0x40
[<c05289db>] do_initcalls+0x2b/0xa0
[<c01317d2>] init_workqueues+0x12/0x29
[<c01050ec>] init+0x4c/0x150
[<c01050a0>] init+0x0/0x150
[<c010719d>] kernel_thread_helper+0x5/0x18
Code: 0f 0b 3e 00 c2 5a 43 c0 89 ec 5d c3 8d 76 00 8d bc 28 00 00
<0>Kernel panic: Attempted to kill init!
Please don't hesitate to contact me if I can be of any further help in
this matter.
Best wishes and regards,
Ernst
On Thu, 2004-02-19 at 21:18 -0500, James Bottomley wrote:
> On Wed, 2004-02-18 at 20:12, Andrew Morton wrote:
> > thank you very much for your work on Linux. Today, I came across a
> > problem; sorry, I have failed in trying to spot the cause...
> >
> > [1.] Linux V. 2.6.3 panics with "Buffers at physical address >16Mb used
> > for aha1542" at boot time on my box.
>
> Could you replace the panic with a BUG() statement and make sure you
> have CONFIG_KALLSYMS set, that should give us a backtrace showing where
> the bad kernel allocation is.
>
> Thanks,
>
> James
>
>
>
> ______________________________________
> Inflex - installed on mailserver for domain @mibi03.meb.uni-bonn.de
> Queries to: postmaster@mibi03.meb.uni-bonn.de
next prev parent reply other threads:[~2004-02-20 8:30 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 [this message]
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
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=1077265837.1297.9.camel@felicia \
--to=molitor@uni-bonn.de \
--cc=James.Bottomley@steeleye.com \
--cc=akpm@osdl.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 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.