Re: IXP700 AHCI fails to initialize

Hi,

ok, I do not know of a working solution. But something like this
happened to me too. I simply could not get newer FreeBSD versions
working on old hardware. I have had to stick then with 7 until a
lightning put an end to the affected machine.

You still have one other chance. Try 9.

My strategy in upgrading is also very simple. When I get a new machine,
I install CURRENT and stick with the branch it will become later until
this branch is not supported anymore. It saved me a lot of hassles as I
normally have to do just one big version jump if the machine gets
real old I have have to switch version.

Erich

 On Sat, 1 Mar 2014
22:00:52 +0400 Yuriy Taraday <yorik.sar_at_gmail.com> wrote:

> Hello.
> 
> I currently have FreeBSD 8.3 on my home server and it works fine but
> it's time to upgrade at last (new ath and new ipfw especially allure
> me). I've decided to go straight to 10.0 and reinstall system from
> scratch to purge all legacy unrelated configs and other stuff.
> 
> The problem I faced is as follows. I have a (rather old) motherboard
> with integrated SATA controller that presents in the OS as IXP700. In
> 8.3 it works fine. I have 2 disks attached to it: one with all my
> data and another one destined to be new system disk. I also have one
> IDE disk installed that is currently used as system disk.
> 
> When I booted from USB stick with 10.0, I couldn't see any SATA disks
> in the system. I dug into dmesg and found this:
> http://pastebin.com/wv2A0MUE As it seems AHCI controller or disks are
> not responding to commands and timeouts eventually.
> 
> A friend suggested to try CURRENT image. I went
> with FreeBSD-11.0-CURRENT-amd64-VT-20140222-r262336-mini-memstick.img
> and got almost the same error: http://pastebin.com/0iGaSWUD
> The error repeats and never stops (looks like CURRENT images have
> different config) but it is essentially the same.
> 
> I've googled the problem but found only notes about how IXP700 is
> really bad and pointers that cabling might be the problem. But I have
> absolutely no problems with 8.3, so it looks like some regression
> during further development (shift to CAM, maybe?).
> 
> Please help me to identify and fix the problem.
>