From: Jeff Garzik <jgarzik@mandrakesoft.com>
To: Jerrad Pierce <belg4mit@dirty-bastard.pthbb.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Tulip bug?
Date: Tue, 05 Mar 2002 12:35:20 -0500 [thread overview]
Message-ID: <3C8501D8.A20D4A09@mandrakesoft.com> (raw)
In-Reply-To: <200203060425.g264PaO00901@dirty-bastard.pthbb.org>
Jerrad Pierce wrote:
>
> Well I managed to switch the console to the 8x9 font which gave 42 lines of
> spew... No mention of tulip this time, at least not in what was visible.
> Also none of these ever get logged to messages so ksymoops wouldn't help?
> Most of it is Call Trace and Stack, which I am guessing is useless without
> knowing the exact state of the machine before hand (I do have Call Trace and
> Stack available if useful)?
>
> Other than that I got:
>
> reference at virtual address 00000070 printing eip: c0120095
> *pde=00000000
> Oops: 0
> CPI=0
> EIP: 0010:[<c0120095>] Not tainted
> ...
>
> AND
>
> <1> Unable to hande kernel NULL pointer dereference at virtual address
> 00000000 printing eip: c010ee96
> *pde=00000000
> Oops=0000
> CPU=0
> EIP: 0010:[<c010ee96>] Not tainted
> ...
You need to run this stuff through "ksymoops"... See REPORTING-BUGS...
--
Jeff Garzik |
Building 1024 |
MandrakeSoft | Choose life.
next prev parent reply other threads:[~2002-03-05 17:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-06 4:25 Tulip bug? Jerrad Pierce
2002-03-05 17:35 ` Jeff Garzik [this message]
2002-03-06 17:10 ` Jerrad Pierce
2002-03-06 4:06 ` Keith Owens
-- strict thread matches above, loose matches on Subject: below --
2002-03-13 7:28 Tulip Bug ? Adam Schrotenboer
2002-03-02 13:29 Tulip bug? Jerrad Pierce
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=3C8501D8.A20D4A09@mandrakesoft.com \
--to=jgarzik@mandrakesoft.com \
--cc=belg4mit@dirty-bastard.pthbb.org \
--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