From: Jens Axboe <axboe@suse.de>
To: R.Oehler@GDImbH.com
Cc: Keith Owens <kaos@ocs.com.au>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
linux-kernel@vger.kernel.org
Subject: Re: kernel 2.4.17 crashes on SCSI-errors
Date: Fri, 4 Jan 2002 09:45:46 +0100 [thread overview]
Message-ID: <20020104094546.O8673@suse.de> (raw)
In-Reply-To: <19996.1010086392@ocs3.intra.ocs.com.au> <XFMail.20020104093136.R.Oehler@GDImbH.com>
In-Reply-To: <XFMail.20020104093136.R.Oehler@GDImbH.com>
On Fri, Jan 04 2002, R.Oehler@GDImbH.com wrote:
>
> On 03-Jan-2002 Keith Owens wrote:
> > On Thu, 03 Jan 2002 14:39:02 +0100 (MET),
> > R.Oehler@GDImbH.com wrote:
> >>Ksymoops was not possible, because after rebooting the
> >>memory/module-layout had changed. (Or is there a trick
> >>I don't know?)
> >
> > /var/log/ksymoops. man insmod, look for ksymoops assistance.
> >
>
> Thanks a lot, I'll try it for the next crash.
> But for now, I think, the output of the SGI debugger I sent
> to the list shows the same.
>
> kernel BUG at /usr/src/linux-2.4.17-Dbg/include/asm/pci.h:147!
> from [aic7xxx]ahc_linux_run_device_queue+0x39d
aic7xxx is calling pci_map_sg on either an unitialized scatterlist, or
maybe just specifying too many segments. try and add a printk to print
'i' before the BUG() at line 147 in include/asm-i386/pci.h
--
Jens Axboe
next prev parent reply other threads:[~2002-01-04 8:46 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-03 13:39 kernel 2.4.17 crashes on SCSI-errors R.Oehler
2002-01-03 19:33 ` Keith Owens
2002-01-04 8:31 ` R.Oehler
2002-01-04 8:45 ` Jens Axboe [this message]
2002-01-04 9:48 ` R.Oehler
-- strict thread matches above, loose matches on Subject: below --
2002-01-03 12:05 R.Oehler
2002-01-03 12:09 ` Jens Axboe
2002-01-03 12:34 ` Jens Axboe
2002-01-03 12:43 ` Alan Cox
2002-01-03 21:28 ` Andrew Morton
2002-01-04 9:43 ` Jens Axboe
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=20020104094546.O8673@suse.de \
--to=axboe@suse.de \
--cc=R.Oehler@GDImbH.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=kaos@ocs.com.au \
--cc=linux-kernel@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