From: Ralf Baechle <ralf@oss.sgi.com>
To: Predrag Malicevic <pmalic@blic.net>
Cc: <linux-mips@oss.sgi.com>
Subject: Re: O200 problem...
Date: Tue, 16 Jan 2001 04:10:29 -0200 [thread overview]
Message-ID: <20010116041028.B2068@bacchus.dhis.org> (raw)
In-Reply-To: <Pine.LNX.4.30.0101121507090.13361-100000@quake.blic.net>; from pmalic@blic.net on Fri, Jan 12, 2001 at 03:20:25PM +0100
On Fri, Jan 12, 2001 at 03:20:25PM +0100, Predrag Malicevic wrote:
> > Thanks for sending the oops message; however without additional data
> > provided I can't use it. Can you please point please put the kernel image
> > that resulted in the oops online?
>
> http://lothar.penguinpowered.com/o200.tar.gz
>
> You'll find everything in the archive: vmlinux, System.map, kernel
> configuration file and a new session log with 'oops messages'.
I just examined your crash data; it's not obvious why what is causing the
DBE exception that is making your kernel die. It seems to happen in
the SCSI code; I wonder if any of the devices you have on the SCSI bus
especially on the second hostadapter is making the Qlogic driver go nuts.
Can you retry your kernel with devices from this bus removed?
Thanks,
Ralf
WARNING: multiple messages have this Message-ID (diff)
From: Ralf Baechle <ralf@oss.sgi.com>
To: Predrag Malicevic <pmalic@blic.net>
Cc: linux-mips@oss.sgi.com
Subject: Re: O200 problem...
Date: Tue, 16 Jan 2001 04:10:29 -0200 [thread overview]
Message-ID: <20010116041028.B2068@bacchus.dhis.org> (raw)
Message-ID: <20010116061029.x0gdu3oPYlnZ6y6I2P8J8-b1RGPr11yePdGgkZBAqqU@z> (raw)
In-Reply-To: <Pine.LNX.4.30.0101121507090.13361-100000@quake.blic.net>; from pmalic@blic.net on Fri, Jan 12, 2001 at 03:20:25PM +0100
On Fri, Jan 12, 2001 at 03:20:25PM +0100, Predrag Malicevic wrote:
> > Thanks for sending the oops message; however without additional data
> > provided I can't use it. Can you please point please put the kernel image
> > that resulted in the oops online?
>
> http://lothar.penguinpowered.com/o200.tar.gz
>
> You'll find everything in the archive: vmlinux, System.map, kernel
> configuration file and a new session log with 'oops messages'.
I just examined your crash data; it's not obvious why what is causing the
DBE exception that is making your kernel die. It seems to happen in
the SCSI code; I wonder if any of the devices you have on the SCSI bus
especially on the second hostadapter is making the Qlogic driver go nuts.
Can you retry your kernel with devices from this bus removed?
Thanks,
Ralf
next prev parent reply other threads:[~2001-01-16 6:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-09 2:16 O200 problem Predrag Malicevic
2001-01-09 2:16 ` Predrag Malicevic
2001-01-09 2:41 ` Ralf Baechle
2001-01-09 2:41 ` Ralf Baechle
2001-01-09 10:23 ` Predrag Malicevic
2001-01-09 10:23 ` Predrag Malicevic
2001-01-12 14:20 ` Predrag Malicevic
2001-01-12 14:20 ` Predrag Malicevic
2001-01-16 6:10 ` Ralf Baechle [this message]
2001-01-16 6:10 ` Ralf Baechle
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=20010116041028.B2068@bacchus.dhis.org \
--to=ralf@oss.sgi.com \
--cc=linux-mips@oss.sgi.com \
--cc=pmalic@blic.net \
/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