From: "Sebastian Piecha" <spi@gmxpro.de>
To: "Randy.Dunlap" <rddunlap@osdl.org>, linux-kernel@vger.kernel.org
Subject: Re: How to understand an oops?
Date: Wed, 24 Sep 2003 01:10:18 +0200 [thread overview]
Message-ID: <3F70EEFA.14060.1665A54C@localhost> (raw)
In-Reply-To: <20030923111621.5b583d62.rddunlap@osdl.org>
...
> | > Are there a few informative lines missing before the Oops: line below?
>
> I was expecting more like (cut from source code):
>
> ("Unable to handle kernel NULL pointer dereference");
> or
> ("Unable to handle kernel paging request");
> and
> (" at virtual address %08lx\n",address);
> (" printing eip:\n");
> ("%08lx\n", regs->eip);
> ("*pde = %08lx\n", page);
> ("*pte = %08lx\n", page);
>
No output of that kind. Only the Oops posted.
> ...
>
> In the meantime, you haven't tried the other mailing lists that
> I suggested....
>
In the meantime I did.
>...
Mit freundlichen Gruessen/Best regards,
Sebastian Piecha
EMail: spi@gmxpro.de
next prev parent reply other threads:[~2003-09-23 23:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-23 10:42 How to understand an oops? Sebastian Piecha
2003-09-23 16:36 ` Randy.Dunlap
2003-09-23 17:31 ` Sebastian Piecha
2003-09-23 18:16 ` Randy.Dunlap
2003-09-23 23:10 ` Sebastian Piecha [this message]
2003-09-27 10:23 ` Sebastian Piecha
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=3F70EEFA.14060.1665A54C@localhost \
--to=spi@gmxpro.de \
--cc=linux-kernel@vger.kernel.org \
--cc=rddunlap@osdl.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.