Unable to handle kernel paging request

Apple products and Mac operating systems. Including discussions on Virtual PC for Mac, Parallels Desktop for Mac, all Apple hardware and everything relating to Mac!
(MacCentre701)

Moderator: Mandrake

Unable to handle kernel paging request

Postby Edward » Fri 25 Mar, 2005 8:32 pm

Upon upgrading the memory in an older PC, Linux would not boot up afterwards. During the initialization, it eventually displayed this error:

Unable to handle kernel paging request at virtual address 816cc448


then displayed what looked like a small core dump of the memory and it froze at that point. Removing the new memory and replacing it with the original memory, eliminated this problem and Linux booted up fine.

The new memory installed had been four 64 Mb EDO SIMM's (16x32). The original memory consists of two 32 Mb EDO SIMM's (8x32) and two 16 Mb EDO SIMM's (4x32).

Would the fact that the new memory being 16x32 (whatever it means) was not compatible with the motherboard?
UserAgent: Opera/8.0 (X11; Linux i586; U; en)
SillyDog701 Moderator
debian 6 - iceape - iceweasel - icedove - seamonkey
User avatar
Edward
Moderator
Moderator
 
Posts: 3569
Joined: Sun 01 Dec, 2002 7:15 pm

Postby Antony » Fri 01 Apr, 2005 8:17 am

If you take out the new RAM and put the old one back. Would it boot up?

Can the system see the RAM at all?
UserAgent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X; en) AppleWebKit/125.5.7 (KHTML, like Gecko) Safari/125.12
User avatar
Antony
diamond member
diamond member
 
Posts: 14343
Joined: Tue 18 Jun, 2002 11:36 pm
Location: Sydney, Australia

Postby Edward » Fri 01 Apr, 2005 5:12 pm

With the old memory back in, the PC boots up perfectly.

When the new memory was in, the initialization detected it and displayed the correct total amount.

There was something Linux didn't like about it..
UserAgent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.6) Gecko/20050317 Firefox/1.0.2
SillyDog701 Moderator
debian 6 - iceape - iceweasel - icedove - seamonkey
User avatar
Edward
Moderator
Moderator
 
Posts: 3569
Joined: Sun 01 Dec, 2002 7:15 pm

Postby Antony » Sun 03 Apr, 2005 2:46 am

It could be your new RAM is one of the newer format that's not fully supported by your mother board OR your new RAM is not 100% compatible with your mother board.
UserAgent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4) Gecko/20030624 Netscape/7.1 (ax) (CK-SillyDog)
User avatar
Antony
diamond member
diamond member
 
Posts: 14343
Joined: Tue 18 Jun, 2002 11:36 pm
Location: Sydney, Australia


Return to Mac OS and Apple

Who is online

Registered users: Google [Bot], Majestic-12 [Bot]