On Tuesday 02 December 2008 07:41:17 Ji wrote: > Hi all, > > I ran into a weird problem when enabling serial console on the FreeBSD > 7.0. Your help is really appreciated. > I installed FreeBSD 7.0 amd64 (from the CD) on a Dell R200, and then > enabled the serial console by adding the following to > /boot/loader.conf > > hint.sio.0.flags="0x30" > console="comconsole vidconsole" > comconsole_speed="9600" > boot_multicons="yes" > > And also replaced the following line on /etc/ttys > > ttyd0 "/usr/libexec/getty std.9600" dialup off secure > > with > > ttyd0 "/usr/libexec/getty std.9600" vt220 on secure. > > During rebooting, I found that the system hangs with the following > messages and interrupt looks totally messed up > > " > ... > Trying to mount root from ufs:/dev/ad4s1a > > 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> > > ..." > > And to my surprise, if I keep rebooting again and again without doing > any fixing, the problem comes and goes, which confused me. > When the problem is not present, the serial console looks working > normally. Can anyone help me with that? Thanks a lot. > > Jim
> atapci0: <Intel ICH9 SATA300 controller> port > 0xbc30-0xbc37,0xbc28-0xbc2b,0xbc38-0xbc3f,0xbc2c-0xbc2f,0xbc40-0xbc4f,0xbc5 >0-0xbc5f irq 6 at device 31.2 on pci0 > atapci0: unable to map interrupt > device_attach: atapci0 attach returned 6 There's your problem. Atapci0 can't get an interrupt, which is the ata controller that controls your disk. -- Mel Problem with today's modular software: they start with the modules and never get to the software part. _______________________________________________ firstname.lastname@example.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"