On Tuesday 02 December 2008 08:52:58 Ji wrote: > On Mon, Dec 1, 2008 at 11:26 PM, Mel > > <[EMAIL PROTECTED]> wrote: > > On Tuesday 02 December 2008 07:41:17 Ji wrote: > >> Hi all, > > ... > > >> atapci0: <Intel ICH9 SATA300 controller> port > >> 0xbc30-0xbc37,0xbc28-0xbc2b,0xbc38-0xbc3f,0xbc2c-0xbc2f,0xbc40-0xbc4f,0x > >>bc5 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. > > > Thank you for your reply, Mel. > > There must be something wrong. What confused me is why the booting > problem does not appear every time I reboot the computer and the > serial console does work fine if it can boot. > And I will really appreciate if you can specify my problem. Thanks a lot.
I'm not sure. Your controller doesn't always get an interrupt, so could be the serial console and atapci bridge fight for it and who ever is first gets it. I would scoot this over to freebsd-hardware list and post a verbose boot without the serial console enabled and with. Also mention if your BIOS has an "Enhanced" or "AHCI" setting for the disk controllers and whether MSI interrupts are supported and enabled. -- 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]"