FreeBSD 10.1-RELEASE regression

[stenio]

Hello,

for some reason my hardware (Fabiatech FX5621) doesn't work with FreeBSD 10.1 while it works perfectly with version 8.3. It tried to boot from a USB drive, disabling from BIOS all IDE drives and using all hints commands I found with no luck! This is what I tried:

set hint.atapci.1.msi=0
set hint.atapci.0.msi=0
set hint.ata.1.mode="PIO4"
set hint.ata.0.mode="PIO4"
set hint.acpi.0.disabled=1
set kern.cam.ada.write_cache=0

The boot loops with this error:

(aprobe0:ata1:0:1:0): ATA_IDENTIFY. ACB: ec 00 00 00 00 40 00 00 00 00 00 00
(aprobe0:ata1:0:1:0): CAM status: Command timeout
(aprobe0:ata1:0:1:0): Retrying command
run_interrupt_driven_hooks: still waiting after 60 seconds for xpt_config
(aprobe0:ata1:0:1:0): ATA_IDENTIFY. ACB: ec 00 00 00 00 40 00 00 00 00 00 00
(aprobe0:ata1:0:1:0): CAM status: Command timeout
(aprobe0:ata1:0:1:0): Error 5, Retries exhausted
(aprobe0:ata1:0:1:0): ATA_IDENTIFY. ACB: ec 00 00 00 00 40 00 00 00 00 00 00
(aprobe0:ata1:0:1:0): CAM status: Command timeout
(aprobe0:ata1:0:1:0): Retrying command
run_interrupt_driven_hooks: still waiting after 120 seconds for xpt_config
(aprobe0:ata1:0:1:0): ATA_IDENTIFY. ACB: ec 00 00 00 00 40 00 00 00 00 00 00
(aprobe0:ata1:0:1:0): CAM status: Command timeout
(aprobe0:ata1:0:1:0): Error 5, Retries exhausted

I found some FreeBSD users with similar errors:
http://freebsd.1045724.n5.nabble.com/no-subject-td5952628i20.html

Do you have any suggestions?

Edit: I've just tried with the latest PF 2.2.6 which has FreeBSD 10.1p25. The problem is still there :(

Thanks,
Stenio

[phil.davis]

It's a good question. I have run up against something similar (no exactly the same error messages from the disk driver) on a Jetway board:
https://149.20.54.209/threads/installing-freebsd-10-0-on-jetway-board-fails.44819
The system with this board is stuck on pfSense 2.1.5 I am not in a position to do mess about with trying to load FreeBSD 8.3, 9.0, 9.1, 9.2, 10.0, 10.1 on it to see when it goes wrong and to push the issue upstream. The post I referred to there is going nowhere. I guess nobody cares, and for me it is few hundred dollars loss to buy new hardware some time - have to think of something to do with the old hardware.
There seems to have been some underlying wholesale change in some disk drivers at some point and it is broken on some (presumably less used with FreeBSD) hardware. Bit disappointing when these sort of changes happen that "randomly" junk people's hardware.