From: Alan Cox <alan@redhat.com>
To: murrayr@brain.org (Murray J. Root)
Cc: linux-kernel@vger.kernel.org, alan@redhat.com
Subject: Re: 2.4.20-rc4-ac1 SiS IDE driver troubles
Date: Wed, 27 Nov 2002 06:52:32 -0500 (EST) [thread overview]
Message-ID: <200211271152.gARBqXI09379@devserv.devel.redhat.com> (raw)
In-Reply-To: <20021127030633.GA1642@Master.Wizards> from "Murray J. Root" at Nov 26, 2002 10:06:33 PM
> After booting and initscripts I get some kind of error like a BUG() but
> I can't see what it is because it scrolls off with repeated "unable to
> handle kernel paging request" messages. The first error shows a stack trace
> (briefly) but all the rest just show the offsets without the text.
Stick a while(1); at the end of the stack dump code and you should get
jus tthe first oops you can read
next prev parent reply other threads:[~2002-11-27 11:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-27 3:06 2.4.20-rc4-ac1 SiS IDE driver troubles Murray J. Root
2002-11-27 11:52 ` Alan Cox [this message]
[not found] <r1_200211271152.gARBqXI09379@devserv.devel.redhat.com>
2002-11-28 13:26 ` Bill Davidsen
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=200211271152.gARBqXI09379@devserv.devel.redhat.com \
--to=alan@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=murrayr@brain.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.