Date: Tue, 21 Jun 2011 10:58:58 -0700 From: Matt <sendtomatt@gmail.com> To: George Kontostanos <gkontos.mail@gmail.com> Cc: FreeBSD-Current <freebsd-current@freebsd.org> Subject: Re: xpt_action_default: CCB type 0xe not supported Message-ID: <4E00DBE2.3080003@gmail.com> In-Reply-To: <BANLkTi=W=yr5-8Q58rzh%2BbMfd2DFTuJnZw@mail.gmail.com> References: <BANLkTi=W=yr5-8Q58rzh%2BbMfd2DFTuJnZw@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 06/21/11 10:51, George Kontostanos wrote: > Fresh installation and after world&& kernel update I get these messages > during boot: > > xpt_action_default: CCB type 0xe not supported > xpt_action_default: CCB type 0xe not supported > > The system is running GENERIC with debugging for use in current off options. > > > Full dmesg attached. > > Regards, > > > > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" SImilar issues on Tyan board with SATA 3gbs, atapicam custom kernel. I assumed it was the ugly CF adapter I have, as I've had shoddy USB devices confuse CAM in the past. Not as annoying as virtualbox being borked "currently", I assume it's simply a printf that is a little too verbose? Or is scsi borked too? Matt
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4E00DBE2.3080003>