Bug 9191 - Unable to handle kernel NULL pointer dereference at virtual address 00000000
Summary: Unable to handle kernel NULL pointer dereference at virtual address 00000000
Status: REJECTED INVALID
Alias: None
Product: Other
Classification: Unclassified
Component: Other (show other bugs)
Hardware: All Linux
: P1 normal
Assignee: other_other
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-10-19 06:45 UTC by Arseny Solokha
Modified: 2008-09-05 05:56 UTC (History)
2 users (show)

See Also:
Kernel Version: 2.6.22-gentoo-r6 #1 PREEMPT
Subsystem:
Regression: ---
Bisected commit-id:

Attachments
Kernel output (927 bytes, application/octet-stream)
2007-10-19 06:46 UTC, Arseny Solokha 		Details
Add an attachment (proposed patch, testcase, etc.)

Description Arseny Solokha 2007-10-19 06:45:36 UTC 
Most recent kernel where this bug did not occur: don't know
Distribution: Gentoo 2007.0
Hardware Environment: AMD Athlon 2600+, 512 Mb RAM; chipset - nVidia nForce2
Software Environment:
Problem Description: The attached message occured when I've just powered on machine. This was not happened before.
Steps to reproduce: Don't know
Comment 1 Arseny Solokha 2007-10-19 06:46:16 UTC 
Created attachment 13213 [details]
Kernel output
Comment 2 Natalie Protasevich 2007-11-12 23:13:40 UTC 
Arseny,
Can you explain a bit how you get an error. Did you system work earlier with different kernel? Is this problem intermittent or happens often?
Thanks.
Comment 3 Arseny Solokha 2007-11-13 01:20:30 UTC 
> Did you system work earlier with different kernel?
Sure, but I've built this kernel September, 3rd, and got a bug only October, 19th.

> Is this problem intermittent or happens often?
This happened twice: first time that day and second time after about 2 weeks.
It seems to happens randomly: I've just turned on my machine and saw this. I can reboot here and machine boots with no trouble.

I really suppose to have broken motherboard. I had some troubles with memory handling about a year ago. But now it works fine.
Comment 4 Natalie Protasevich 2007-11-19 23:50:46 UTC 
The pattern in panic suggests that this maybe something to do with vsyscall DSO.
Comment 5 Arseny Solokha 2007-11-20 06:45:48 UTC 
(In reply to comment #4)
> The pattern in panic suggests that this maybe something to do with vsyscall
> DSO.
>
This bug appears irregularly. You say that bug probably regards to DSO. So it can be really troubles with my hardware. Unfortunately I don't have time to work about it now.
Comment 6 Arseny Solokha 2008-09-05 05:47:25 UTC 
It is quite difficult to provide additional info. Described kernel panic did not occured from that time. Once I got panic related to FSB frequency changing but I consider that all these troubles caused by damaged motherboard.

This trouble appears irregulary and anybody except me have it, that is a reason to mark this bug invalid.
Comment 7 Thomas Gleixner 2008-09-05 05:56:20 UTC 
Thanks, for the update. Closing it
Note You need to log in before you can comment on or make changes to this bug.