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 driver > bug (based on reports of similar panics with different NICs, notably nge) > and one is a filesystem corruption problem. > > Here's the process that I go through to reliably reproduce both problems. > 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=1" in the boot > 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"
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. -- 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 limited subset of filesystem errors. -- Matt Emmerton _______________________________________________ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"