lkml.org 
[lkml]   [2003]   [Dec]   [7]   [last100]   RSS Feed
Views: [more markup]  [less markup]  [headers]  [forward] 
 
Messages in this thread
/
DateSat, 6 Dec 2003 22:50:17 -0800 (PST)
FromAlex Davis <>
Subject2.4.23 hard lock, 100% reproducible.
I had the exact same thing happen to me about 
a year ago, with the same error message. It
started after I had upraded my kernel. It 
turned out one of my RAM sticks had gone
bad. Do you have another machine you can
test 2.4.23 with?


[...]
> 
> Not even sysrq?
> 

I did get msgs twice here in the past few hours, 
but only sometimes does it give anything.  Here's 
what it said: 

Unable to handle kernel NULL pointer
dereference at virtual address: 00000000
 printing eip:
c02363dd
*pde=00000000
Oops: 0000
CPU: 0
EIP: 0010:[<c02363d>]  Not tainted
EFLAGS: 00010217
eax: 00000006   ebx: 00000000  ecx: 7a01a8c0   ecx: c700b2a0
esi: c0299ce0   edi: 000001b7  ebp: c0299d94   esp: c0299c54
ds: 0018  es: 0018  ss: 0018
process: swapper (pid: 0, stackpage = c0299000)

Other than that, nothing.  Is there a patch out there 
that will simply make 2.4.22 secure?  Things run great
on that kernel. 

-- 
Mark

-

=====
I code, therefore I am
__________________________________
Do you Yahoo!?
New Yahoo! Photos - easier uploading and sharing.
http://photos.yahoo.com/
-
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/
\
 
 \ /
  Last update: 2005-03-22 12:59    [from the cache]
©2003-2008