Help fixing a bug; HP MicroServer N40L; CAM status: Command timeout

Polytropon freebsd at
Sun Jun 28 14:23:51 UTC 2015

On Mon, 29 Jun 2015 00:05:31 +1000, Yudi V wrote:
> > Have you already verified that there are no hardware errors
> > (bad cabling of the cages)
> Given that v11 works without any errors, I assumed it has to be a software
> bug.

I just mentioned it because SATA sometimes shows the
"funniest" errors due to a minimally misaligned plug. :-)

> > > ==============================================
> > > I tried the suggestion from
> > >
> > >
> > > added hint.ahci.0.msi="1" to /boot/loader.conf  but did not fix the issue
> >
> > This is only effective after a reboot. Have you done that?
> > Have you verified that you applied the setting to the correct
> > ahci device? Check "dmesg | grep ahci" to see if there are
> > more than one controller in the system.
> >
> That's a good suggestion, based on the below output of "dmesg | grep ada"
> I added  "hint.atapci.0.msi="0" (also 1) but did not resolve the issue.

The output of dmesg indicates that the drives are of different
speed capabilities (2 x 300MB/s, 2 x 150MB/s). Are those the
four ones that occupy the 4 cages (and are probably connected
to the same controller)?

If you check "dmesg | grep ahci" you can see which controllers
are available. Using "camcontrol devlist" you can examine how
the drives are connected to the available buses.

> > In order to build a custom kernel, you need to know _which
> > difference_ it should implement compared to the GENERIC
> > kernel. "Just building one", as I mentioned, probably will
> > not be of great help.
> >
> I thought downloading the latest source files with the patch should be
> enough to include the patch, I am guessing that was incorrect thinking.

If you download the latest sources, you're trying to install
a v11 kernel on a v10 system (which might or might not work).
The patch, as far as I understand, applies to v11 (and might
or might not work with v10). Kernel and world need to be in
sync to work properly.

> so how to make sure I include the patch?

Download it and apply it using the "patch" command, for
example "patch < /tmp/the-patch-file".

>  I will reread the docs and try rebuilding the kernel again.

If you have confirmed that v11 works for you, why not use the
current snapshot? It already seems quite stable...

Magdeburg, Germany
Happy FreeBSD user since 4.0
Andra moi ennepe, Mousa, ...

More information about the freebsd-questions mailing list