https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=208365
--- Comment #35 from Graham Perrin <[email protected]> --- I reused the PersonaCrypt device with PC-BSD 11.0-CURRENTMAY2016 on two notebooks with 4 GB memory: an Ergo Vista 621 (circa 2007) and a MacBookPro8,2 (15-inch, early 2011). I see occasional 'CAM status: CCB request completed with an error' (examples below) but happily, with this month's CURRENT, neither machine grinds to a halt. More specifically, with reference to bug report 208668: * I no longer see 'Error 5, Retries exhausted' $ date ; uptime ; freebsd-version ; uname -a 18 May 2016 at 19:20:43 UTC 7:20p.m. up 1:39, 1 users, load averages: 1.52, 1.88, 1.77 11.0-CURRENTMAY2016 FreeBSD cces3-gjp4-pcbsd-macbookpro82 11.0-CURRENTMAY2016 FreeBSD 11.0-CURRENTMAY2016 #19 5bab0d2(master): Fri May 6 17:56:25 UTC 2016 root@devastator:/usr/obj/usr/src/sys/GENERIC amd64 $ sudo dmesg | grep umass umass0: <JetFlash TS256MJF2A, class 0/0, rev 1.10/1.00, addr 6> on usbus3 umass0: SCSI over Bulk-Only; quirks = 0xc100 umass0:2:0: Attached to scbus2 da0 at umass-sim0 bus 0 scbus2 target 0 lun 0 umass0: at uhub7, port 2, addr 6 (disconnected) da0 at umass-sim0 bus 0 scbus2 target 0 lun 0 (da0:umass-sim0:0:0:0): Periph destroyed umass0: <Kingston DataTraveler 3.0, class 0/0, rev 2.10/1.00, addr 4> on usbus1 umass0: SCSI over Bulk-Only; quirks = 0x8100 umass0:2:0: Attached to scbus2 da0 at umass-sim0 bus 0 scbus2 target 0 lun 0 umass0: <Kingston DataTraveler 3.0, class 0/0, rev 2.10/1.00, addr 7> on usbus1 umass0: SCSI over Bulk-Only; quirks = 0x8100 umass0:2:0: Attached to scbus2 da0 at umass-sim0 bus 0 scbus2 target 0 lun 0 (da0:umass-sim0:0:0:0): READ(10). CDB: 28 00 02 f4 97 c2 00 00 07 00 (da0:umass-sim0:0:0:0): CAM status: CCB request completed with an error (da0:umass-sim0:0:0:0): Retrying command (da0:umass-sim0:0:0:0): READ(10). CDB: 28 00 02 f4 97 c2 00 00 07 00 (da0:umass-sim0:0:0:0): CAM status: CCB request completed with an error (da0:umass-sim0:0:0:0): Retrying command $ (In reply to Graham Perrin from comment #29) > … in my case the trouble began with an > earlier FreeBSD-based PC-BSD, 11.0-CURRENTDEC2015 > http://lists.pcbsd.org/pipermail/testing/2015-December/010270.html That remains a puzzle but in my opinion, not enough of a puzzle for this bug report 208365 to remain open. Thanks -- You are receiving this mail because: You are on the CC list for the bug. _______________________________________________ [email protected] mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-amd64 To unsubscribe, send any mail to "[email protected]"
