From: "Randy.Dunlap" <rddunlap@osdl.org>
To: <mail@richardstevens.de>
Cc: <linux-kernel@vger.kernel.org>
Subject: Re: Newbie debugging question
Date: Wed, 6 Aug 2003 22:25:33 -0700 (PDT) [thread overview]
Message-ID: <32841.4.4.25.4.1060233933.squirrel@www.osdl.org> (raw)
In-Reply-To: <200308070230.49802.mail@richardstevens.de>
> Hi,
>
> I've been searching the net for quite some time now without success so I
> decided to ask the professionals. I'm looking for kernelhacker newbie
> friendly documentation on how to figure out a little more about a kernel
> lockup to be able to give the developer of a device driver some more info.
I suggest asking on the kernelnewbies mailing list (see kernelnewbies.org).
Also, some people started on this web page, but it's only a beginning:
http://lse.sourceforge.net/debugging/
> The problem is that after a while the machine locks up with Caps Lock and
> Scroll lock blinking. I don't see any logs and no messages on the console. I
> found some posts describing similar events and it was said that the kernel
> is not completely dead in this state. Is there a way to get some more
> information? Where should I start reading.
>
> Please CC me since I'm not subscribed.
What kernel version? That would have some effects on the answer.
Serial console is the usual option/route. If it boots completely,
you could also try netconsole (or, dare I say it, usb console).
Or LKCD (lkcd.sf.net), or kmsgdump (2.5.75/2.6.0 at
http://www.xenotime.net/linux/kmsgdump/2.5.75/).
~Randy
next prev parent reply other threads:[~2003-08-07 5:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-07 0:30 Richard Stevens
2003-08-07 5:25 ` Randy.Dunlap [this message]
2003-08-07 15:41 ` Richard Stevens
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=32841.4.4.25.4.1060233933.squirrel@www.osdl.org \
--to=rddunlap@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mail@richardstevens.de \
/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
all inboxes | Powered by JetHome®