![]() |
Home
| Calendar
| Mail Lists
| List Archives
| Desktop SIG
| Hardware Hacking SIG
Wiki | Flickr | PicasaWeb | Video | Maps & Directions | Installfests | Keysignings Linux Cafe | Meeting Notes | Linux Links | Bling | About BLU |
I running the same combo, 2.2.11 and RH 6.0. And was having the same problems. What I found was that I had a bad memory module or at least one that was incompatible with the other 2. In the first slot was a SEC set of chips from Korea and the other two modules were NECs when I removed the first and replaved it with one of the NECs, viola, everything was fine. Before I did this uptime was measured in hours, minutes if I ran my memory stress program. I've been up for 5 days straight now. (the POST always said the memory was fine... ?-> Brad Noyes wrote: > Hi, > > I have a problem with my linux box. I'm using kernel 2.2.11 with RH 6. I'll > say it out right, I'm not sure what the cause was, and I don't know the > first step to fixing this (I did try the recuse image but not luck). The > Problem is; when i start my computer everything seems to be fine. After a > few minutes of running linux, it will either hang, or, if i'm in X, crash X. > If i'm still able to shutdown manually, i will shut down and reboot. When i > reboot i get a message similar to this one (this particular message came > from when i logged in as root after X crashed) > > Unable to handle kernel paging request at virtual address e02272cc > current->tss.cr3 = 020bf000, %cr3 = 020bf000 > *pde = 00000000 > Oops: 0000 > CPU: 0 > EIP: 0010:[<c01191b0>] > EFLAGS: 00010283 > eax: 0001356f ebx: 00000030 ecx: c3de3000 edx: c0319ba0 > esi: 00048000 edi: c20041b4 ebp: 00000022 esp: c1e07c3c > ds: 0018 es: 0018 ss: 0018 > Process bash (pid: 682, process nr: 43, stackpage=c1e07000) > Stack: c32201c0 00055000 c3de3000 00000000 0009d000 c20bf080 00000000 > 0809d000 > c20bf080 c011ad32 c32201c0 08048000 00055000 c1e06000 c1e06000 > c01f65d7 > c3e54800 c284a520 c0128d1e c32201c0 c1e06000 c1e07dc8 c01f65d7 > c3e54800 > Call Trace: [<c011ad32>] [<c01f65d7>] [<c0128d1e>] [<c01f65d7>] [<c0128e41>] > [<c > 01f65d7>] [<c0130d50>] > [<c01b6e55>] [<c01b6f2a>] [<c011bca0>] [<c011bb03>] [<c011bc94>] > [<c01f65 > d4>] [<c01293c3>] [<c01295a8>] > [<c0107ec7>] [<c0108ee8>] > Code: 8b 15 cc 52 22 c0 8d 44 c2 18 8b 00 85 c0 7c 19 8b 4c 24 10 > Aiee, killing interrupt handler > --------------------------------------------------------------- > > After I wait an hour or so I can boot my machine fine, and then the whole > process starts over. The first time that this happened, my X server crashed, > so i shutdown and rebooted. During the shutdown i remember seeing > "swap_duplicate" scroll down the screen, if that's any help. > > If anyone can help me solve this problem it would be greatly appreciated. > Thanks in advance, > > -Brad Noyes > > _______________________________________________________________ > Get Free Email and Do More On The Web. Visit http://www.msn.com > - > Subcription/unsubscription/info requests: send e-mail with > "subscribe", "unsubscribe", or "info" on the first line of the > message body to discuss-request at blu.org (Subject line is ignored). - Subcription/unsubscription/info requests: send e-mail with "subscribe", "unsubscribe", or "info" on the first line of the message body to discuss-request at blu.org (Subject line is ignored).
![]() |
|
BLU is a member of BostonUserGroups | |
We also thank MIT for the use of their facilities. |