From owner-freebsd-fs@FreeBSD.ORG Mon Jul 22 17:58:47 2013 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id C22C7AD1; Mon, 22 Jul 2013 17:58:47 +0000 (UTC) (envelope-from yaneurabeya@gmail.com) Received: from mail-ie0-x231.google.com (mail-ie0-x231.google.com [IPv6:2607:f8b0:4001:c03::231]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 4FF762BD8; Mon, 22 Jul 2013 17:58:47 +0000 (UTC) Received: by mail-ie0-f177.google.com with SMTP id w15so7682411iea.36 for ; Mon, 22 Jul 2013 10:58:46 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=references:mime-version:in-reply-to:content-type :content-transfer-encoding:message-id:cc:x-mailer:from:subject:date :to; bh=kWmkwYMeHRk5XVvakdsFTtiyQxa+DCus0uTLfKaOuXc=; b=mh1LD4g+Mz4K0oSCzTZNScpfCyExpfNG0H/2BRsDMPDiAYhxNlsUPxz6vSDOGQH4oJ QCWVuizbr36S9Ej/vpIvLBaoYAso/m2l58HyCM80TKfWBrAG5Iynmtyasaz2D0b+aq1z Pkb/Dw3h1E0tl0hCfKxbvvUEUlfJULcZOTfCxqWVXL6gpUYsxz4+TU47kR9n3zOsetvS +ZlR3r4is4RAOtXFIhoJ6DUbQFLrenh088E6C/lXv5pNr61WhUCdLYkSFSpI6k3h4V1w EEuLRmVojiYm2wc0uqrIhCsgWxgfhLF7bE6GUAfGb0yA7xoMpVpPgiLTNw/kdsAugxXz BGOw== X-Received: by 10.50.126.36 with SMTP id mv4mr19874670igb.45.1374515926742; Mon, 22 Jul 2013 10:58:46 -0700 (PDT) Received: from [10.176.148.89] (mobile-166-147-083-154.mycingular.net. [166.147.83.154]) by mx.google.com with ESMTPSA id t10sm434548igz.9.2013.07.22.10.58.42 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 22 Jul 2013 10:58:46 -0700 (PDT) References: <78424E5D-4EB2-4462-A190-D0AC97136790@gmail.com> <201307221208.22060.jhb@freebsd.org> Mime-Version: 1.0 (1.0) In-Reply-To: <201307221208.22060.jhb@freebsd.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Message-Id: X-Mailer: iPhone Mail (10B329) From: Garrett Cooper Subject: Re: [REGRESSION] Root zpool mounting broken between 06/30/2013 and 07/21/2013 when PS/2 support compiled into the kernel Date: Mon, 22 Jul 2013 10:58:36 -0700 To: John Baldwin Cc: "freebsd-fs@freebsd.org" , "freebsd-stable@freebsd.org" X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 Jul 2013 17:58:47 -0000 On Jul 22, 2013, at 9:08 AM, John Baldwin wrote: > On Monday, July 22, 2013 10:30:32 am Garrett Cooper wrote: >> I have a KERNCONF that previously had PS/2 support compiled into the kern= el. If I comment out the following lines like so: >>=20 >> # atkbdc0 controls both the keyboard and the PS/2 mouse >> #device atkbdc # AT keyboard controller >> #device atkbd # AT keyboard >>=20 >> then I'm able to mount root again (it was failing with ENOXDEV). >>=20 >> The working kernel was as follows: >>=20 >> $ strings /boot/kernel.WORKING/kernel | grep -B 2 -A 2 BAYONETTA >> @(#)FreeBSD 9.1-STABLE #7 r+0304216: Sun Jun 30 15:22:55 PDT 2013 >> FreeBSD 9.1-STABLE #7 r+0304216: Sun Jun 30 15:22:55 PDT 2013 >> gcooper@bayonetta.local:/usr/obj/scratch/git/github/yaneurabeya-freebs= d-stable-9/sys/BAYONETTA >> gcc version 4.2.1 20070831 patched [FreeBSD] >> FreeBSD >> 9.1-STABLE >> BAYONETTA >> $ cd /usr/src; git log 0304216 >> commit 03042167f73c213732b44218a24d8e1bbea00f8c >> Merge: 2edcad2 974abfb >> Author: Garrett Cooper >> Date: Mon Jun 24 19:00:45 2013 -0700 >>=20 >> Merge remote-tracking branch 'upstream/stable/9' into stable/9 >>=20 >> The working kernel [with atkbdc] was as follows: >>=20 >> FreeBSD bayonetta.local 9.2-BETA1 FreeBSD 9.2-BETA1 #12 r+c178034: Sun Ju= l 21 20:19:38 PDT 2013 =20 > root@bayonetta.local:/usr/obj/scratch/git/github/yaneurabeya-freebsd-stabl= e-9/sys/BAYONETTA amd64 >> $ git log c178034 >> commit c17803445f4ffb97e1a46a1be5f7ea04692793f0 >> Author: avg >> Date: Tue Jul 9 08:30:31 2013 +0000 >>=20 >> zfsboottest.sh: remove checks for things that are not strictly require= d >>=20 >> MFC after: 10 days >>=20 >> (Yes, I had to backport some things because they are busted on stable/9 d= ue to other incomplete/missing MFCs). >>=20 >> I can test out patches, but I don't have time to bisect the actual commit= that caused the failure. That being said my intuition says it's this > commit should be looked at first: >>=20 >> commit 28f961058b0667841d7e9d8639bfd02ed8689faa >> Author: jhb >> Date: Wed Jul 17 14:04:18 2013 +0000 >>=20 >> MFC 252576: >> Don't perform the acpi_DeviceIsPresent() check for PCI-PCI bridges. I= f >> we are probing a PCI-PCI bridge it is because we found one by enumerat= ing >> the devices on a PCI bus, so the bridge is definitely present. A few >> BIOSes report incorrect status (_STA) for some bridges that claimed th= ey >> were not present when in fact they were. >>=20 >> While here, move this check earlier for Host-PCI bridges so attach fai= ls >> before doing any work that needs to be torn down. >>=20 >> PR: kern/91594 >> Approved by: re (marius) >=20 > I strongly doubt that this is related. It would be most helpful if you co= uld > obtain a dmesg from the new kernel however (perhaps via a serial console) t= o > rule it out. All you would need to see is if the new kernel sees more "pc= ib" > devices than the old one to see if this change even has an effect on your > system. Unfortunately the USB keyboard is broken as well at the mount root prompt an= d the workstation doesn't have a uart on it that I can play with (it's my ho= me box), so I'm dead in the water when it panics at the mount root prompt ri= ght now. I guess I can revert this and a handful of other amd64/ata_cam/zfs commits t= o see if this goes away, but I won't be getting to that before next Sunday p= robably as this is my file server and DNS server now. Thanks!=