Date: Sun, 19 Mar 2006 16:45:42 -0500 From: Kris Kennaway <kris@obsecurity.org> To: Matt Emmerton <matt@compar.com> Cc: stable@freebsd.org, Kris Kennaway <kris@obsecurity.org> Subject: Re: 6.0-REL problems with ISA ed0, FFS corruption and ancient hardware Message-ID: <20060319214542.GA7164@xor.obsecurity.org> In-Reply-To: <001701c64b9d$94b44a70$1200a8c0@gsicomp.on.ca> References: <000c01c64b72$321d6520$1200a8c0@gsicomp.on.ca> <20060319174831.GA3270@xor.obsecurity.org> <001701c64b9d$94b44a70$1200a8c0@gsicomp.on.ca>
next in thread | previous in thread | raw e-mail | index | archive | help
--5vNYLRcllDrimb99 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Mar 19, 2006 at 04:39:19PM -0500, Matt Emmerton wrote: > On Sun, Mar 19, 2006 at 11:28:45AM -0500, Matt Emmerton wrote: > > [ Asked on -questions on Friday; re-asking now on -stable without > > cross-post] > > > > I recently upgraded a 4.11-REL machine to 6.0-REL and have run into some > > snags. While the installation from CD went fine, after configuring and > > enabling my ed0 NIC, bad things start to happen. > > > > FWIW, this machine is an ancient (hardware circa 1991, BIOS circa 1994) > > dual-Pentium 133 MHz machine, with EISA/PCI and onboard SCSI. > > > > So far I can reliably reproduce two panics, one appears to be a ed driv= er > > bug (based on reports of similar panics with different NICs, notably ng= e) > > and one is a filesystem corruption problem. > > > > Here's the process that I go through to reliably reproduce both problem= s. > > 1) Boot machine in multi-user mode > > 2) After ifconfig ed0, machine panics with a trap 12 in ithread_loop. > > 3) In debugger, reset (or panic to get vmcore) > > 4) Reboot in multi-user mode, but set "hint.ed.0.disabled=3D1" in the b= oot > > loader (to avoid ifconifg panic) > > 5) Root filesystem is fsckd; all other filesystems are scheduled for > > background fsck > > 6) Encounter panic "ffs_valloc: dup alloc" >=20 > I think this part is because you have filesystem corruption from your > previous panic. Force a fsck in foreground mode and it should clear > it up. >=20 > -- >=20 > That prevents the FFS panic from occurring. I had forgot about the fact > that fsck in multi-user mode runs as "fsck -p" which only catches a limit= ed > subset of filesystem errors. OK, now you can post about your other panic :-) Kris --5vNYLRcllDrimb99 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.2 (FreeBSD) iD8DBQFEHdEFWry0BWjoQKURAsvwAKCBpyTMuHtnrqp2wIkkskiIk5j4iACeOMZP F5v2my48Oa9hXreqATjpxbM= =wGVf -----END PGP SIGNATURE----- --5vNYLRcllDrimb99--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060319214542.GA7164>