Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 29 Nov 2014 18:26:44 -0800
From:      Neel Natu <neelnatu@gmail.com>
To:        =?UTF-8?Q?Ask_Bj=C3=B8rn_Hansen?= <ask@develooper.com>
Cc:        "freebsd-virtualization@freebsd.org" <freebsd-virtualization@freebsd.org>
Subject:   Re: Unsupported cmd:c4 (ada0:ahcich0:0:0:0): READ_MUL. ACB: c4 00 00 00 00 40 00 00 00 00 01 00
Message-ID:  <CAFgRE9F5bC4t6sDRtKVRLD0kLeLFWi%2B1kK5Jx5c8RZHYh5LyUA@mail.gmail.com>
In-Reply-To: <C47B8B4E-5127-4121-BC73-2B4E6129652B@develooper.com>
References:  <C47B8B4E-5127-4121-BC73-2B4E6129652B@develooper.com>

next in thread | previous in thread | raw e-mail | index | archive | help
Hi Bjorn,

On Fri, Nov 28, 2014 at 2:42 AM, Ask Bj=C3=B8rn Hansen <ask@develooper.com>=
 wrote:
> Hi everyone,
>
> I=E2=80=99ve spent some time off this week upgrading my build-my-personal=
-NanoBSD-image tool from a VMware virtual machine to a physical box running=
 a 32-bit build-box under bhyve.
>
> So far so good =E2=80=94 all that has been working really well.
>
> My nanobsd image is only used on Soekris and PC Engines boxes and my prod=
uction images are really small (some <100MB storage and ~32MB memory), so I=
 have a crufty kernel config that excluded a bunch of stuff I (thought I) d=
on=E2=80=99t need.
>
> Now I=E2=80=99d like to run my built image under bhyve for testing. It=E2=
=80=99s easier for me if the disk comes up as an ada device, so I=E2=80=99m=
 using ahci-hd instead of virtio-blk. With virtio-blk the system boots but =
the device has the =E2=80=9Cwrong" name.
>
> With ahci-hd it can=E2=80=99t read my partition for some reason.
>
> I=E2=80=99ve tried with both file and zvol backing store.
>
> This is the error I=E2=80=99m getting:
>
> ada0: <BHYVE SATA DISK 001> ATA-8 SATA 2.x device
> ada0: Serial Number 123456
> ada0: 300.000MB/s transfers (SATA 2.x, PIO4, PIO 8192bytes)
> ada0: Command Queueing enabled
> ada0: 260MB (532480 512 byte sectors: 16H 63S/T 528C)
> ada0: Previously was known as ad4
> Unsupported cmd:c4
>                   (ada0:ahcich0:0:0:0): READ_MUL. ACB: c4 00 c1 1f 08 40 =
00 00 00 00 04 00
> (ada0:ahcich0:0:0:0): CAM status: ATA Status Error
> (ada0:ahcich0:0:0:0): ATA status: 41 (DRDY ERR), error: 04 (ABRT )
> (ada0:ahcich0:0:0:0): RES: 41 04 00 00 00 40 00 00 00 00 00
> (ada0:ahcich0:0:0:0): Retrying command
> Unsupported cmd:c4
>
>
> Any suggestion for what I=E2=80=99m doing wrong? Did I compile my kernel =
with some idiotic set of not-working options?
>

Are you, by any chance, setting the tunable 'hw.ata.ata_dma' to 0 to
disable DMA?

I ask this because in the dmesg above you have:
ada0: 300.000MB/s transfers (SATA 2.x, PIO4, PIO 8192bytes)

In my setup, I get this instead:
ada0: 300.000MB/s transfers (SATA 2.x, UDMA6, PIO 8192bytes)

best
Neel

>
> Ask
>
> _______________________________________________
> freebsd-virtualization@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
> To unsubscribe, send any mail to "freebsd-virtualization-unsubscribe@free=
bsd.org"



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAFgRE9F5bC4t6sDRtKVRLD0kLeLFWi%2B1kK5Jx5c8RZHYh5LyUA>