On Wed, May 25, 2016 at 14:36:59 +0200, Gary Jennejohn wrote: > On Wed, 25 May 2016 08:15:11 +0200 > Gary Jennejohn <gljennj...@gmail.com> wrote: > > > On Tue, 24 May 2016 15:10:41 -0400 > > "Kenneth D. Merry" <k...@freebsd.org> wrote: > > > > > Can you send full dmesg output from the working kernel? > > > > > > > I'll give it a try and hope that the mail server doesn't strip it ==> > > dmesg.boot.gz. > > > > > It looks like you have some ATAPI devcies on your machine (signature > > > eb14). > > > They would likely be attaching to the da(4) driver if they are disks, and > > > that is a different code path. > > > > > > > The one and only ATAPI device is cd0. > > > > OK, it appears that one of the ATA fixes ken@ recently committed > fixed my problem also.
Great! I'm glad it's working! > I'm now at r300677 and booting succeeds. > > I guess the ATAPI DVD drive was the culprite. It was most likely the Samsung hard drive. This drive is the exact same model that Alex Petrov also had problems with: ada1 at ahcich2 bus 0 scbus2 target 0 lun 0 ada1: <SAMSUNG HD501LJ CR100-10> ATA8-ACS SATA 2.x device ada1: Serial Number S0MUJ1KP317818 ada1: 300.000MB/s transfers (SATA 2.x, UDMA6, PIO 8192bytes) ada1: Command Queueing enabled ada1: 476938MB (976771055 512 byte sectors) It claims to support Read Log, but actually doesn't. The change I checked in in revision 300640 will only send a Read Log (and additional SMR probe steps) to drives that claim they're SMR drives. Any non-SMR drives should get the same probe as before. Ken -- Kenneth Merry k...@freebsd.org _______________________________________________ firstname.lastname@example.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"