Date: Wed, 14 Apr 2004 20:18:47 -0700 From: Kris Kennaway <kris@obsecurity.org> To: Rick Updegrove <dislists@updegrove.net> Cc: freebsd-stable@freebsd.org Subject: Re: 4.9 SMP Stability? Message-ID: <20040415031847.GA60348@xor.obsecurity.org> In-Reply-To: <407DF735.7020705@updegrove.net> References: <407CA3D6.2090803@updegrove.net> <20040414083216.A45296@server.gisp.dk> <407D466E.9060900@updegrove.net> <407DBD39.6020405@updegrove.net> <20040414232312.GA56901@xor.obsecurity.org> <407DCB29.8010109@updegrove.net> <20040415000022.GA57253@xor.obsecurity.org> <407DE32B.8040304@updegrove.net> <20040415014851.GA58873@xor.obsecurity.org> <407DF735.7020705@updegrove.net>
next in thread | previous in thread | raw e-mail | index | archive | help
--Dxnq1zWXvFF0Q93v Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Apr 14, 2004 at 07:45:09PM -0700, Rick Updegrove wrote: > Ok BIOS is updated. > Sorry for the attachments, but the lines would wrap badly. >=20 >=20 > Kris Kennaway wrote: > >Run mptable. >=20 > See mptable.txt >=20 > >Look in /modules for stale files, and check kldstat to see what you're > >running. >=20 > See modules.txt >=20 > How do I know if they are stale? Use the -l option to ls and compare to the date you installed your kernel. > root@govmail /modules # kldstat > Id Refs Address Size Name > 1 1 0xc0100000 227ff4 kernel It doesn't like you're using them, though. > >This doesn't correspond to the recommended upgrade procedure (yes, in > >the handbook :-), e.g. you omit running mergemaster, and run the > >installworld target before rebooting, but that shouldn't cause panics. >=20 > Oh I am supposed to reboot first, then run make installworld? It's hard to back out an installworld if your new kernel is broken. > Well I admit that I don't use mergemaster because it has never actually > been useful. I prefer to keep my /etc configuration files in CVS and > refer to them if something breaks.. perhaps I should RTFM again and again? Might be worthwhile :-) > I will try to hook up a serial console can you point me to a HOWTO > maybe? I will also google... Again, it's well described in the handbook. > >man boot and see the 'v' option. >=20 > I hate man pages sometimes. After reading that several times, I took a > guess and I am trying: That would probably work, but the boot manpage talks about /boot.config or specifying -v with the keyboard at the boot propmpt. > Does that look OK? >=20 >=20 > >This indicates a problem - I don't know how serious - the BIOS update > >may help. >=20 > I am attaching the output from "dmesg -a" again after booting to the new > BIOS and making the above changes. Doesn't seem to have fixed the 'broken mptable' message. This may indicate broken (non-spec-compliant) hardware. > Ok but not until I make it crash with this BIOS right? Yep..one step at a time. > MPTable, version 2.0.15 Looks OK as far as stepping goes, I'm not an expert on SMP hardware to interpret any problems with the rest. Kris --Dxnq1zWXvFF0Q93v Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (FreeBSD) iD8DBQFAff8XWry0BWjoQKURAtoSAJ40BPmcnTwZ+9mpi7BaCmNrGcnIcQCgwqBy GwTnpUT+c7CadmvQdOifYOk= =9yqt -----END PGP SIGNATURE----- --Dxnq1zWXvFF0Q93v--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040415031847.GA60348>