From owner-freebsd-current@freebsd.org Mon May 23 19:25:42 2016 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A0EB8B47E5F for ; Mon, 23 May 2016 19:25:42 +0000 (UTC) (envelope-from ken@kdm.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 8B81C1332 for ; Mon, 23 May 2016 19:25:42 +0000 (UTC) (envelope-from ken@kdm.org) Received: by mailman.ysv.freebsd.org (Postfix) id 86D1DB47E5E; Mon, 23 May 2016 19:25:42 +0000 (UTC) Delivered-To: current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 8671DB47E5D for ; Mon, 23 May 2016 19:25:42 +0000 (UTC) (envelope-from ken@kdm.org) Received: from mithlond.kdm.org (mithlond.kdm.org [96.89.93.250]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "A1-33714", Issuer "A1-33714" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 48C12132F for ; Mon, 23 May 2016 19:25:41 +0000 (UTC) (envelope-from ken@kdm.org) Received: from mithlond.kdm.org (localhost [127.0.0.1]) by mithlond.kdm.org (8.15.2/8.14.9) with ESMTPS id u4NJPdaA051423 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Mon, 23 May 2016 15:25:39 -0400 (EDT) (envelope-from ken@mithlond.kdm.org) Received: (from ken@localhost) by mithlond.kdm.org (8.15.2/8.14.9/Submit) id u4NJPd32051422; Mon, 23 May 2016 15:25:39 -0400 (EDT) (envelope-from ken) Date: Mon, 23 May 2016 15:25:39 -0400 From: "Kenneth D. Merry" To: "Oleg V. Nauman" Cc: current@freebsd.org Subject: Re: ATA? related trouble with r300299 Message-ID: <20160523192539.GB50102@mithlond.kdm.org> References: <16296020.R5v2TQkD2c@asus.theweb.org.ua> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <16296020.R5v2TQkD2c@asus.theweb.org.ua> User-Agent: Mutt/1.5.23 (2014-03-12) X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.4.3 (mithlond.kdm.org [127.0.0.1]); Mon, 23 May 2016 15:25:39 -0400 (EDT) X-Spam-Status: No, score=-2.9 required=5.0 tests=ALL_TRUSTED,BAYES_00, HEADER_FROM_DIFFERENT_DOMAINS autolearn=ham autolearn_force=no version=3.4.1 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on mithlond.kdm.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 May 2016 19:25:42 -0000 On Sat, May 21, 2016 at 09:30:35 +0300, Oleg V. Nauman wrote: > > I have faced the issue with fresh CURRENT stopped to boot on my old desktop > after update to r300299 > Verbose boot shows the endless cycle of > > ata2: SATA reset: ports status=0x05 > ata2: reset tp1 mask=03 ostat0=50 ostat1=50 > ata2: stat0=0x50 err=0x01 lsb=0x00 msb=0x00 > ata2: stat1=0x50 err=0x01 lsb=0x00 msb=0x00 > ata2: reset tp2 stat0=50 stat1=50 devices=0x3 > messages logged to console. > > Below is the relevant portion of ATA controller/devices probed/attached during > the boot: > > atapci0: port > 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xffa0-0xffaf at device 31.1 on pci0 > ata0: at channel 0 on atapci0 > atapci1: port 0xd080-0xd087, 0xd000-0xd003, > 0xcc00-0xcc07,0xc880-0xc883,0xc800-0xc80f irq 19 at device 31.2 on pci0 > ata2: at channel 0 on atapci1 > ata3: at channel 1 on atapci1 > ada0 at ata2 bus 0 scbus1 target 0 lun 0 > ada0: ATA-7 SATA 2.x device > ada1 at ata2 bus 0 scbus1 target 1 lun 0 > ada1: ATA8-ACS SATA 3.x device > cd0 at ata0 bus 0 scbus0 target 0 lun 0 > cd0: <_NEC DVD_RW ND-3570A 1.11> Removable CD-ROM SCSI device I'm not entirely sure what is causing the problem with your system, but hopefully we can narrow it down a bit. There is a bug that came in with my SMR changes in revision 300207 that broke the quirk functionality in the ada(4) driver. I don't think that is the problem you're seeing, though. Can you try out this patch: https://people.freebsd.org/~ken/cam_smr_ada_patch.20160523.1.txt In /boot/loader.conf, put the following: kern.cam.ada.0.quirks="0x04" kern.cam.ada.1.quirks="0x04" If you're able to boot with those quirk entries in the loader.conf, try taking one of them out, and reboot. If that works, try taking the other one out and reboot. What I'm trying to figure out here is where the problem lies: 1. The bug with the ada(4) driver (in where it loaded the quirks). 2. The extra probe steps in the ada(4) driver might be causing a problem with ada0 (Samsung drive). 3. The extra probe steps in the ada(4) driver might be causing a problem with ada1 (Seagate drive). 4. Something else. So, if you can try the patch and try to eliminate a few possibilities, we may be able to narrow it down. Thanks, Ken -- Kenneth Merry ken@FreeBSD.ORG