[Junk released by Allow List] [ale] Stack dump

[Louis Zamora]

I didn't see where anyone replied to this.

There was no mention of whether you are using the same memory as before?
1. May be bad due to hit
2. May not be compatible with "like" mobo
3. Less likely but I have seen, bad memory slot on new mobo (rule out by
moving memory modules around and looking for different boot up behavior
pattern)


Try memtest and rule out memory first. Also does the address always say
2361 or does this change around?

Offline email me your mobo, cpu and memory modules and I'll see if I can
make heads or tail of it.

 
Louis Zamora 
Senior Sales Engineer 
louisz at senecadata.com 

1280 Old Alpharetta Rd.
Alpharetta, GA 30005
Toll Free: 888-843-6916 
Fax: 315-579-1300
www.senecadata.com
www.nexlink.com
 
 
 
-----Original Message-----
From: ale-bounces at ale.org [mailto:ale-bounces at ale.org] On Behalf Of
PairOfTwins
Sent: Thursday, September 06, 2007 7:14 PM
To: Atlanta Linux Enthusiasts
Subject: [Junk released by Allow List] [ale] Stack dump

Anyone:

Replaced the motherboard in a working Ubuntu 7.04 installation, after 
lightning struck, with a NEARLY identical motherboard (same brand and 
same ViA chipset), expecting to have a working system.

Nearly every boot, I get a stack trace, etc, but can't pin down the 
problem, unless it's SATA hard drive stuff.  Running e2fsck didn't turn 
up any errors.  Booting Xubuntu from CD works fine.

"BUG: unable to handle kernel paging request at virtual address 00002361
Printing EIP"

Once, with several SATA features disabled in BIOS, it booted, but next 
boot the old errors came back.

My googling turned up some kernel parameters to try -- none of which 
helped:
   all-generic-ide, pci=nomsi, acpi=off

Any suggestions, short of reinstalling?

Thanks,
Tom

_______________________________________________
Ale mailing list
Ale at ale.org
http://www.ale.org/mailman/listinfo/ale