[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Different sized SODIMM causes kernel panic in laptop?
- To: misc_(_at_)_openbsd_(_dot_)_org
- Subject: Different sized SODIMM causes kernel panic in laptop?
- From: "Scott C. Kennedy" <sck_(_at_)_nogas_(_dot_)_org>
- Date: Fri, 16 Apr 2004 01:59:59 -0000
I've googled around and can't find an answer, so it's now to the mailing-lists....
On a Dell Latitude D600 running OpenBSD 3.4-current (updated 4/15 5:05 PST) with a GENERIC conf build, I am getting the following problem.
1) With a 1 GB SODIMM and a 512 MB SO DIMM in the two slots of the laptop, Open BSD dies with a "DDB> " error (ps and dump Details attached below)
2) With either RAM removed, OpenBSD boots cleanly, thus it's not likely the RAM itself. Plus, both Fedora Core #1 and Windows XP both boot fine with both SODIMMs in the laptop. Plus, it doesn't matter which SODIMM is in which slot, OpenBSD doesn't like both at the same time.
3) With the OpenBSD 3.4 CD or booting from the bsd.rd kernel, I can successfully boot to a shell and mount the filesystem.
So, any ideas?
DDB debugging details below.
dkcsum: wd0 matched BIOS disk 80
root on wd0a
rootdev=0x0 rrootdev=0x300 rawdev=0x302
panic:pmap_remove_pte: managed page without PG_PVLIST for 0xe9586000
Stopped at Debugger+0x04: leave
RUN AT LEAST 'trace' and 'ps' AND INCLUDE OUTPUT WHEN REPORTING THIS PANIC!
DO NOT EVEN BOTHER REPORTING THIS WITHOUT INCLUDING THAT INFORMATION!
Debugger(24a5,3db5b,e9584a30,0,e9586000) at Debugger +0x4
panic(d04b58e0,e9586000,e9584a34,d02c9ae2,0) at panic+0x87
pmap_copy_page(d05c2420,0,cffa5618,e9586000) at pmap_copy_page+0x59d
[....] ahhh screw it...
Screen shots available at...
Visit your host, monkey.org