Date: Wed, 10 Dec 2003 10:41:26 +0200 From: Ian Freislich <ianf@za.uu.net> To: xtc@pocketheaven.com Cc: freebsd-current@freebsd.org Subject: Re: -CURRENT kernel fails to boot Message-ID: <50325.1071045686@za.uu.net> In-Reply-To: Your message of "Fri, 28 Nov 2003 14:57:21 PST." <1070060241.3fc7d2d17a13f@pocketheaven.com> References: <1070060241.3fc7d2d17a13f@pocketheaven.com>
next in thread | previous in thread | raw e-mail | index | archive | help
wrote:
> I just updated my src and the GENERIC kernel I build from -CURRENT locks up
> with my hdd light on solid. Does anyone else have this issue?
Yes, but no one who can do anything about it appears to have read
my error report. It appears to be related to the new interrupt
code John Baldwin introduced loosing interrupts from the HDD
controler. The most recent kernel I can boot is from source dated
midnight 2003-10-21 GMT. Perhaps a couple of days later but compiling
kernel after kernel on a P-133 is a little tedious. Here's the
last bit of my boot message:
GEOM: create disk ad0 dp=0xc1538170
ad0: <FUJITSU MHD2032AT/1812> ATA-3 disk at ata0-master
ad0: 3102MB (6354432 sectors), 6304 C, 16 H, 63 S, 512 B
ad0: 16 secs/int, 1 depth queue, UDMA33
GEOM: new disk ad0
ad0: WARNING - READ_DMA recovered from missing interrupt <<<<<<<<<
ad0: WARNING - READ_DMA recovered from missing interrupt <<<<<<<<<
ad0: WARNING - READ_DMA recovered from missing interrupt <<<<<<<<<
Mounting root from ufs:/dev/ad0s1a
setrootbyname failed
ffs_mountroot: can't find rootvp
Root mount failed: 6
Manual root filesystem specification:
<fstype>:<device> Mount <device> using filesystem <fstype>
eg. ufs:da0s1a
? List valid disk boot devices
<empty line> Abort manual input
mountroot>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?50325.1071045686>