From: Keith Owens <kaos@ocs.com.au>
To: Jerrad Pierce <belg4mit@dirty-bastard.pthbb.org>
Cc: linux-kernel@vger.kernel.org (Linux Kernel Mailing List)
Subject: Re: Tulip bug?
Date: Wed, 06 Mar 2002 15:06:55 +1100 [thread overview]
Message-ID: <13857.1015387615@kao2.melbourne.sgi.com> (raw)
In-Reply-To: Your message of "Tue, 05 Mar 2002 23:25:36 CDT." <200203060425.g264PaO00901@dirty-bastard.pthbb.org>
On Tue, 05 Mar 2002 23:25:36 -0500,
Jerrad Pierce <belg4mit@dirty-bastard.pthbb.org> 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?
Use a serial console (Documentation/serial-console.txt) and capture the
oops output on the second machine.
next prev parent reply other threads:[~2002-03-06 4:07 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
2002-03-06 17:10 ` Jerrad Pierce
2002-03-06 4:06 ` Keith Owens [this message]
-- 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=13857.1015387615@kao2.melbourne.sgi.com \
--to=kaos@ocs.com.au \
--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