Messages in this thread | | | Date | Fri, 23 Aug 2002 08:57:34 -0400 | From | Adam Kropelin <> | Subject | Re: page_alloc bug |
| |
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
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |