On 06/21/11 19:58, Matt wrote:
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-unsubscr...@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
_______________________________________________
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to
"freebsd-current-unsubscr...@freebsd.org"
Same here,
ASUS board, Intel ICH10R, SATA 3GB. Custom kernel:
# S-ATA/AHCI Interface
device ahci # Serial ATA Advanced Host Controller
Interface driver
device ata # Legacy Core ATA functionality
options ATA_CAM # ATA CAM
#
device mvs # Marvell Serial ATA Host Controller driver
device siis # Marvell Serial ATA Host Controller driver
and the SCSI stuff.
Seems to be a very verbose thing inside the CAM system.
Oliver
_______________________________________________
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
