From: Greg KH <greg@kroah.com>
To: Roger Leblanc <r_leblanc@videotron.ca>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Deadlock in kernel on USB shutdown
Date: Thu, 3 Jan 2002 10:57:30 -0800 [thread overview]
Message-ID: <20020103185730.GA11356@kroah.com> (raw)
In-Reply-To: <3C33A22F.40906@videotron.ca> <20020103001816.GB4162@kroah.com> <3C33A4EC.1040300@videotron.ca> <20020103002827.GA4462@kroah.com> <3C33AF4F.7000703@videotron.ca> <20020103013231.GA4952@kroah.com> <3C33BD88.3010903@videotron.ca> <20020103030356.GA5313@kroah.com> <3C33CF71.4060202@videotron.ca>
In-Reply-To: <3C33CF71.4060202@videotron.ca>
On Wed, Jan 02, 2002 at 10:26:41PM -0500, Roger Leblanc wrote:
> Oops? I know about cores but I don't know about oopses. I'm only a C++,
> hight level, OO developer. Sorry ;-). Can you explain please?
When the seg-fault happens, I am guessing that an oops message is sent
to the kernel log. Look at 'dmesg'. Run that oops through ksymoops.
See Documentation/oops-tracing.txt for more info on oopses and how to
get info from them.
thanks,
greg k-h
next prev parent reply other threads:[~2002-01-03 18:59 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-03 0:13 Deadlock in kernel on USB shutdown Roger Leblanc
2002-01-03 0:18 ` Greg KH
2002-01-03 0:25 ` Roger Leblanc
2002-01-03 0:28 ` Greg KH
2002-01-03 1:09 ` Roger Leblanc
2002-01-03 1:32 ` Greg KH
2002-01-03 2:10 ` Roger Leblanc
2002-01-03 3:03 ` Greg KH
2002-01-03 3:26 ` Roger Leblanc
2002-01-03 18:57 ` Greg KH [this message]
2002-01-04 21:46 ` Roger Leblanc
[not found] <000701c193f6$4ca368a0$6800000a@brownell.org>
2002-01-03 2:25 ` Roger Leblanc
-- strict thread matches above, loose matches on Subject: below --
2002-01-01 21:48 Roger Leblanc
2002-01-02 14:40 ` Greg KH
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=20020103185730.GA11356@kroah.com \
--to=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=r_leblanc@videotron.ca \
/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