All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Joseph Mathewson" <joe@mathewson.co.uk>
To: linux-kernel@vger.kernel.org
Subject: Logging kernel oops
Date: Wed, 02 May 2001 20:57:16 +0100	[thread overview]
Message-ID: <200105021957.f42JvH511805@localhost.localdomain> (raw)

I get a kernel oops every few days (even weeks if I'm lucky) with kernel
2.4.2 that I suspect are related to my Speedtouch USB ADSL modem.  The box
in question is monitor and keyboardless unless strictly necessary, and
routes the ADSL internet connection to a local network.

What is the preferred what of getting debugging information from a kernel
oops?  Is my only way connecting a monitor and getting a pencil and paper?
Is there any conceivable way I can get some useful debugging information
(on reset) without plugging in a keyboard/monitor?

+=================================================+
| Joseph Mathewson <joe@mathewson.co.uk>          |
+=================================================+

             reply	other threads:[~2001-05-02 20:57 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-05-02 19:57 Joseph Mathewson [this message]
2001-05-02 21:09 ` Logging kernel oops Alan Cox
2001-05-02 23:23 ` Keith Owens

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=200105021957.f42JvH511805@localhost.localdomain \
    --to=joe@mathewson.co.uk \
    --cc=joe.mathewson@btinternet.com \
    --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 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.