From owner-freebsd-fs@FreeBSD.ORG Wed Jul 30 10:51:27 2014 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 350928F2; Wed, 30 Jul 2014 10:51:27 +0000 (UTC) Received: from mail-pa0-x234.google.com (mail-pa0-x234.google.com [IPv6:2607:f8b0:400e:c03::234]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id F00E62ACE; Wed, 30 Jul 2014 10:51:26 +0000 (UTC) Received: by mail-pa0-f52.google.com with SMTP id bj1so1311442pad.39 for ; Wed, 30 Jul 2014 03:51:26 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=1k69CfV87RE1BNtfzMghnIWBoXgJmb1tQuRSkAs0d0Y=; b=wTTtuEVQesWQRhs+kOv/h5RS1YMCmyz6yCoMtY7g0rW4QHltulJ8e6s74PN8IBx2zi ze95W5ngtz/3RuOuIB4kLJb6jQOSIQq5EzKsmjhYm9IAIw/GEM6pyq9IvPVDykXwxFnE J70iYFZj+nOeSlFY5e4+2cnRym/pcsoqsQh6bF5JcXZ0NlDCwzUhR2u5eBGY2OhVGfNM ompIOoWpeAGwbqU5KCiMTvompnP4Bam1aQCvtf7+UJEWCCfAsqAIO1jJ4si9YPOxTMco LQEE3oVt7YYhtL6kvi1a7nHxI0ptipIInr5Mal04APyvc17rQipY+W2Lu4OlsL9qesnB NqWw== X-Received: by 10.70.37.129 with SMTP id y1mr3714934pdj.12.1406717486174; Wed, 30 Jul 2014 03:51:26 -0700 (PDT) Received: from ?IPv6:2601:8:ab80:7d6:4de3:c604:bd4e:bab2? ([2601:8:ab80:7d6:4de3:c604:bd4e:bab2]) by mx.google.com with ESMTPSA id da14sm6775014pac.24.2014.07.30.03.51.25 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 30 Jul 2014 03:51:25 -0700 (PDT) Content-Type: text/plain; charset=windows-1252 Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) Subject: Re: [REGRESSION] Root zpool mounting broken between 06/30/2013 and 07/21/2013 when PS/2 support compiled into the kernel From: Garrett Cooper In-Reply-To: <10421077.Qp3biFQLVt@pippin.baldwin.cx> Date: Wed, 30 Jul 2014 03:51:24 -0700 Content-Transfer-Encoding: quoted-printable Message-Id: References: <78424E5D-4EB2-4462-A190-D0AC97136790@gmail.com> <95A4D9A9-9D69-4258-A1EC-CBC6DC2F49FF@FreeBSD.org> <10421077.Qp3biFQLVt@pippin.baldwin.cx> To: John Baldwin X-Mailer: Apple Mail (2.1878.6) Cc: "freebsd-fs@freebsd.org" , "freebsd-stable@freebsd.org" X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 30 Jul 2014 10:51:27 -0000 On Jul 28, 2014, at 6:32 PM, John Baldwin wrote: > On Monday 28 July 2014 09:57:08 Garrett Cooper wrote: >> On Mon, Jul 28, 2014 at 9:37 AM, John Baldwin = wrote: >>> On Jul 28, 2014, at 9:07 AM, Garrett Cooper = wrote: >>>> On Jul 22, 2013, at 10:58 AM, Garrett Cooper = =20 > wrote: >>>>> 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 >>>>>>> kernel. 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 >>>>>>>=20 >>>>>>> = gcooper@bayonetta.local:/usr/obj/scratch/git/github/yaneurabeya-freeb >>>>>>> sd-stable-9/sys/BAYONETTA>>>>>=20 >>>>>>> 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 >>>>>>> Jul 21 20:19:38 PDT 2013>>>>=20 >>>>>> = root@bayonetta.local:/usr/obj/scratch/git/github/yaneurabeya-freebsd-st >>>>>> able-9/sys/BAYONETTA amd64>>>>=20 >>>>>>> $ 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 >>>>>>> required >>>>>>>=20 >>>>>>> MFC after: 10 days >>>>>>>=20 >>>>>>> (Yes, I had to backport some things because they are busted on >>>>>>> stable/9 due 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>>>>=20 >>>>>> commit should be looked at first: >>>>>>> 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.=20 >>>>>>> If >>>>>>> we are probing a PCI-PCI bridge it is because we found one by >>>>>>> enumerating >>>>>>> the devices on a PCI bus, so the bridge is definitely present. = A few >>>>>>> BIOSes report incorrect status (_STA) for some bridges that = claimed >>>>>>> they >>>>>>> were not present when in fact they were. >>>>>>>=20 >>>>>>> While here, move this check earlier for Host-PCI bridges so = attach >>>>>>> fails >>>>>>> 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 >>>>>> could obtain a dmesg from the new kernel however (perhaps via a = serial >>>>>> console) to rule it out. All you would need to see is if the new >>>>>> kernel sees more "pcib" devices than the old one to see if this = change >>>>>> even has an effect on your system. >>>>>=20 >>>>> Unfortunately the USB keyboard is broken as well at the mount root >>>>> prompt and the workstation doesn't have a uart on it that I can = play >>>>> with (it's my home box), so I'm dead in the water when it panics = at the >>>>> mount root prompt right now. >>>>>=20 >>>>> I guess I can revert this and a handful of other amd64/ata_cam/zfs >>>>> commits to see if this goes away, but I won't be getting to that = before >>>>> next Sunday probably as this is my file server and DNS server = now.>>>=20 >>>> I ran into the issue going from vanilla 9.2-RELEASE-p10 to >>>> 9.3-RELEASE as well :(. I=92ve filed this bug to track the = issue: >>>> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D192183 . = I=92ll >>>> see if GENERIC can boot my system sometime this week (the = KERNCONF >>>> has been working for several releases, but it could be an = issue >>>> with that that=92s being overlooked by accident).>>=20 >>>> Thanks! >>=20 >> ... >>=20 >>> Also, you would need to get verbose dmesg's of old and new kernels = as a >>> first step in narrowing it down. >> I can't do trivial debugging because my USB keyboard doesn't work at >> the mountroot prompt ( >> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D133989 ), I don't >> have a PS/2 keyboard, and the system only has VGA access :(. I'll try >> working on disabling the PS/2 controller in the BIOS and a few other >> things to force the system to stop ignoring the USB keyboard to get >> scrollback, because that appeared to work for some folks with this >> issue according to the ukbd bug I referenced. >=20 > Do you have a serial port so you could use a serial console (or is = this a=20 > laptop)? I wish my motherboard had an RS232 port, but unfortunately it doesn=92t; = I don=92t have 2 USB RS-232 converters either (and I=92m not sure a USB = serial adapter would work for boot2sio, would it?) :/. If the legacy USB keyboard route doesn=92t work out, I have a USB to = PS/2 converter coming in the mail. It would be nice if bug 133989 was fixed. I=92ll talk to hps@ about it=85 Thanks! -Garrett=