From: Erik Mouw <erik@harddisk-recovery.com>
To: "Vladimir V. Saveliev" <vs@namesys.com>
Cc: msmulders@pronexus.nl, linux-kernel@vger.kernel.org
Subject: Re: help! kernel errors?
Date: Mon, 25 Jul 2005 18:20:33 +0200 [thread overview]
Message-ID: <20050725162033.GB23773@harddisk-recovery.com> (raw)
In-Reply-To: <42E4C6E7.4060806@namesys.com>
On Mon, Jul 25, 2005 at 03:03:03PM +0400, Vladimir V. Saveliev wrote:
> msmulders@pronexus.nl wrote:
> >Hello,
> >
> >I'm getting loads and loads of kernel errors in my syslog, but am unable to
> >decipher them into anything meaningful.
> You may want to take a look at linux/Documentation/oops-tracing.txt
And we're only interested in the *first* Oops, not in any later one.
The first Oops is most probably the cause of all other Oopses.
Erik
--
+-- Erik Mouw -- www.harddisk-recovery.com -- +31 70 370 12 90 --
| Lab address: Delftechpark 26, 2628 XH, Delft, The Netherlands
next prev parent reply other threads:[~2005-07-25 16:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-25 9:50 msmulders
2005-07-25 11:03 ` Vladimir V. Saveliev
2005-07-25 11:59 ` msmulders
2005-07-25 16:20 ` Erik Mouw [this message]
2005-07-25 18:28 ` msmulders
2005-07-25 10:28 msmulders
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=20050725162033.GB23773@harddisk-recovery.com \
--to=erik@harddisk-recovery.com \
--cc=linux-kernel@vger.kernel.org \
--cc=msmulders@pronexus.nl \
--cc=vs@namesys.com \
/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®