From: Adam Kropelin <akropel1@rochester.rr.com>
To: Tom <tom@lemuria.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: page_alloc bug
Date: Fri, 23 Aug 2002 08:57:34 -0400 [thread overview]
Message-ID: <20020823125734.GA8854@www.kroptech.com> (raw)
In-Reply-To: <20020823090527.A7715@lemuria.org>
On Fri, Aug 23, 2002 at 09:05:27AM +0200, Tom wrote:
> first time reporting a kernel bug, so please tell me if you need any
> other details. I'm following the instructions on kernel.org as closely
> as I can.
Actually, you need to follow them a little closer if you want anyone to
help you. Perhaps you missed this paragraph in REPORTING-BUGS:
If the failure includes an "OOPS:" type message in your log or on screen
please read "Documentation/oops-tracing.txt" before posting your bug
report. This explains what you should do with the "Oops" information to
make it useful to the recipient.
> (5) Output of oops:
> not sure if this is it, but here is what is displayed on the console:
> kernel BUG at page_alloc.c:91!
> invalid operand: 0000
> CPU: 0
> EIP: 0010:[<c012b96d>] Tainted: P
^
What proprietary modules did you have loaded when this BUG() was hit? nVidia,
perhaps? Reproduce the problem from a cold boot without ever having loaded the
closed-source module(s). If you can't, go talk to whomever made the module; the
community cannot help you solve a problem when we can't see the code.
--Adam
next prev parent reply other threads:[~2002-08-23 12:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-23 7:05 page_alloc bug Tom
2002-08-23 12:57 ` Adam Kropelin [this message]
2002-08-23 13:13 ` Tom
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=20020823125734.GA8854@www.kroptech.com \
--to=akropel1@rochester.rr.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tom@lemuria.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox