Scott Long wrote:
Glen Van Lehn wrote:
Scott Long <[EMAIL PROTECTED]> 10/25/06 7:36 PM >>>
Glen Van Lehn wrote:
Hi, I'm new to the FreeBSD lists, and still uncertain on protocol.
I posted this today on the freebsd-hardware list, but from the
discussion I'm seeing today, it may better apply to 5-stable than
hardware.
-----
I'm installing 5-STABLE from the 5.4 CDset onto a new HP DL140 G2
with an Adaptec 2120S RAID controller that someone else had already
installed with a Linux OS. Two HDD are config'd as RAID1 set. After
the probes for VGA & mouse, the boot stuck on a repeated series of
messages:
aac0: COMMAND 0xc39ef000 TIMEOUT AFTER xxx SECONDS
# 16 diff hex offsets per set .. each set repeating every 20 seconds
aac0: COMMAND 0xc39ef708 TIMEOUT AFTER xxx SECONDS
A different boot has a different hex prefix, 0xc3a16, but the same
sequence of 16 trailing digits, 000 to 708.
Searching this list, I found a similar post from Chris Knight in
January, but he was on 6 and that was apparently right at a change
to the aac driver. Searching FreeBSD.org turned up a similar
problem back in March 2004 [5.2.1]. Scott Long responded to that
one as a known issue being resolved.
The BIOS firmware was 'Build 7244' from May 2004, but I updated that
to Build 8205 [latest for that chipset] and still had the same problem.
Would the pre-existing different OS install mess up the aac0
driver? like format the array first?
I broke the array, re-inited the disks and recreated RAID 1.. but
didn't format drives .. still had problem.
something else? I was able to install Fedora4 after failing on
5.4, but I'd like to use FreeBSD for this project.
comments appreciated,
glen van lehn
Does the 'Safe mode' boot option work? This is likely an interrupt
routing problem.
Scott
----
Yes! it did, thank you.
glen
Ok, you'll probably want to put the following line into
/boot/loader.conf:
hint.apic.0.disabled=1
However, if this is an SMP machine, this option will only allow 1 CPU
to be used. If this option doesn't work, then the next one to try is
hint.acpi.0.disabled=1
Scott
---
I actually already had acpi disabled and added the apci to loader.conf.
Still have the problem if I don't manually boot to Safe mode. One
difference is that right before the aacd0 errors in the default boot, I
also get errors about ata0-master and others that may relate no floppy
drive in the system . Following is the tail of dmesg output from Safe
boot annotated where the default mode errors occur:
vga0: <Generic ISA VGA> at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0
unknown: <PNP0303> can't assign resources (port)
unknown: <PNP0c02> can't assign resources (memory)
unknown: <PNP0f13> can't assign resources (irq)
unknown: <PNP0501> can't assign resources (port)
fdc1: cannot allocate I/O port (6 ports)
Timecounter "TSC" frequency 2800112140 Hz quality 800
Timecounters tick every 10.000 msec
acd0: DVDROM <DV-28E-N/C.6B> at ata0-master PIO4
<deflt: has 4 lines "ata0-master: Failure - ATAPI_IDENTIFY Timeout >
aacd0: <RAID 1 (Mirror)> on aac0
aacd0: 34730MB (71127808 sectors)
<deflt: after wait of 20sec the aacd0: command timeouts start >
pass0 at aacp0 bus 0 target 0 lun 0
pass0: <COMPAQ BF03699BC6 HPB1> Fixed unknown SCSI-3 device
pass0: 160.000MB/s transfers (80.000MHz, offset 127, 16bit)
pass1 at aacp0 bus 0 target 1 lun 0
pass1: <COMPAQ BF03699BC6 HPB1> Fixed unknown SCSI-3 device
pass1: 160.000MB/s transfers (80.000MHz, offset 127, 16bit)
Mounting root from ufs:/dev/aacd0s1a
stray irq7 ## is this stray significant?
--glen
_______________________________________________
[email protected] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
