From owner-freebsd-current@freebsd.org Mon Oct 22 17:01:22 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 280D110390C7 for ; Mon, 22 Oct 2018 17:01:22 +0000 (UTC) (envelope-from marklmi@yahoo.com) Received: from sonic312-21.consmr.mail.bf2.yahoo.com (sonic312-21.consmr.mail.bf2.yahoo.com [74.6.128.83]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id BB84384F87 for ; Mon, 22 Oct 2018 17:01:21 +0000 (UTC) (envelope-from marklmi@yahoo.com) X-YMail-OSG: kseHqggVM1njVTk2ZdUDlI10knkwfLuPJgMRo55EloMZKp4eOhhc4iVdLa.PH8W 5UO1DO1U.iqyEnsjhXxslnqxtfXz4DbkbRtmyVLZU.E8c_FIAxZjTWC6RXvPW0nZYXkmG9Mvhsok jv5bPFC0pqBkI_0AJjPsnZUlfrUyYS33_pfgOoZgCF.DWYvT65_Fjd6AoiDYzbMpotww6O2Pfkpb kEIPfrBEC7hn4NffOCPQ6QYC.C_7KAzNzAf8jgJx6Vyr5suLVsF06ND36nQMDXxBB_pZAeRIUh5r C7BXUrMkCGqyPt9p0Hs3qvGK1vxa41SMZa7pUQVl4adyr4jj4J0e9PxkiO2JGFaP1G4bxWY6HH8I Vjyv5b1Kr4_K3ZG26hu33S4iR7Qzrc62CKbYBuBW9EXYSZ7bkEvxp.64RsPfeclxmy1t8EEp3krj 3S6DFfr57lfu0GGTTDNVbxFeMNAnFdeVb3dFdqXZH1LJlITmE2PqHrH6oqfep2iHiWrsfcQXLSTx RCbMLLQ9FzuARO49Q5Fwb..ILZjlG.jnuwhLPvHYl7JIr6_U4Wv6_uZTF4zSR8EBCijoIUsj3E.s _JWkPcqHW4pMU6wHXnPnWi6G086eTbWTF1ltR97MpjVPPzX4vMZLeAaMlku7j1JzOj4ajSFX.dkP IBVW0BPyfTL_SPujp2x3Jh_G2avHJnZjWXTovZBA0DhPmJ3tV2QR__cE8NYrmMX0QAI6dZW_lQef h.xOTyysv2GOeaddXugQmMa4dfmnuNjGTIxsvdghA20xGzg4YXxt_oz4RMOIANQLG2Fzof38zKMC f0GmiP22q1JZfecL8dlY54oLvtpU1b1HjGQM3hc7jcNwws1Bl97OlmzOjrd9WwaCRpc__oseZDQc l4iUfmc9EXXPJDQsCovqm3scliVMHnGxFPNryS.Cmmb.ByrDf_7dW6o684aytD.N48eygQrKetcT jgT6LUcMYGtNWpQ_eq2fR0_hH6TfUhB86ZsXQqIsLXweNbaaSvd0aMQWOv0Gfd0Z73SUImEujRKh TqIpcLIuZGphzU5IZizhk8xkvxQ9K9iI67u4LLruh69KuyPaKupKfTYemESXKCEt51gqTNT9XgtJ Y0sx0obFX Received: from sonic.gate.mail.ne1.yahoo.com by sonic312.consmr.mail.bf2.yahoo.com with HTTP; Mon, 22 Oct 2018 17:01:21 +0000 Received: from c-76-115-7-162.hsd1.or.comcast.net (EHLO [192.168.1.25]) ([76.115.7.162]) by smtp423.mail.bf1.yahoo.com (Oath Hermes SMTP Server) with ESMTPA ID 42bcd5d7160751ce49e2f3a1377a76b2; Mon, 22 Oct 2018 17:01:19 +0000 (UTC) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\)) Subject: Re: head -r338804 boots threadripper 1950X fine; head -r338810+ do not; -r338807 seems implicated From: Mark Millard In-Reply-To: Date: Mon, 22 Oct 2018 10:01:17 -0700 Cc: Toomas Soome , FreeBSD Current , FreeBSD-STABLE Mailing List Content-Transfer-Encoding: quoted-printable Message-Id: <16BF1504-AD3B-4B5F-A728-43C2A777A082@yahoo.com> References: <79973E2B-F5C4-4E7C-B92B-1C8D4441C7D1@yahoo.com> <3CA4C94F-A062-44FE-B507-948A6F88C83D@me.com> <085BCA2B-4451-406C-9CEE-57D8B8008201@yahoo.com> <9AEF5EB3-C393-44D1-9BD4-D0E59FE97CCE@me.com> <08B26F92-F1F5-4F51-8DC4-EDDC6DD493B2@yahoo.com> To: Warner Losh , Konstantin Belousov X-Mailer: Apple Mail (2.3445.9.1) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 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, 22 Oct 2018 17:01:22 -0000 [I will note the the loader problem has been shown to not be involved in the kernel problem that this "Subject:" was originally for.] On 2018-Oct-22, at 9:26 AM, Warner Losh wrote: > On Mon, Oct 22, 2018 at 6:39 AM Mark Millard = wrote: >> On 2018-Oct-22, at 4:07 AM, Toomas Soome wrote: >>=20 >> > On 22 Oct 2018, at 13:58, Mark Millard = wrote: >> >>=20 >> >> On 2018-Oct-22, at 2:27 AM, Toomas Soome wrote: >> >>>=20 >> >>>> On 22 Oct 2018, at 06:30, Warner Losh wrote: >> >>>>=20 >> >>>> On Sun, Oct 21, 2018 at 9:28 PM Warner Losh = wrote: >> >>>>=20 >> >>>>>=20 >> >>>>>=20 >> >>>>> On Sun, Oct 21, 2018 at 8:57 PM Mark Millard via freebsd-stable = < >> >>>>> freebsd-stable@freebsd.org> wrote: >> >>>>>=20 >> >>>>>> [I built based on WITHOUT_ZFS=3D for other reasons. But, >> >>>>>> after installing the build, Hyper-V based boots are >> >>>>>> working.] >> >>>>>>=20 >> >>>>>> On 2018-Oct-20, at 2:09 AM, Mark Millard wrote: >> >>>>>>=20 >> >>>>>>> On 2018-Oct-20, at 1:39 AM, Mark Millard wrote: >> >>>>>>> . . . >> >>>>=20 >> >>>=20 >> >>> It would help to get output from loader lsdev -v command. >> >>=20 >> >> That turned out to be very interesting: The non-ZFS loader >> >> crashes during the listing, during disk8, which shows a >> >> x0 instead of a x512. >> >>=20 >> >=20 >> > Yes, thats the root cause there. The non-zfs loader does only = *read* the boot disk, thats why the issue was not revealed there.=20 >> >=20 >> > It would help to identify the sector size for that disk, at least = from OS, so we can compare with what we can get from INT13. >> >=20 >> > I have pretty good idea what to look there, but I am afraid we need = to run few tests with you to understand why that disk is reporting = sector size 0 there. >> >=20 >> >=20 >>=20 >> Looks like I guessed wrong about the device >> for "drive8". >>=20 >> So I unplugged the only other external >> storage device, so the original drives >> 0-13 become 0-11 overall. >>=20 >> The machine has a multi-LUN media card reader with >> no cards plugged in. It is built-in rather than >> one that I plugged into a port. It has 4 LUN's. >>=20 >> So 8+4=3D12 and drives 0-7 show up with media before >> it tries any of the 4 LUN's with no card in place. >>=20 >> I conclude that "drive8" is an empty LUN in a media >> card reader. >>=20 >> I conclude that there is no sector size available for >> any of the empty LUNs in the media reader. >>=20 > I think you are probably right and we're hitting some divide by 0 = error when we should just ignore the disk. In the Hyper-V context, the loader and kernel do not see the 4-LUN media reader at all: only drives with normal freebsd-* style partitions and free space. This explains why I did not see a loader problem in that context. So I conclude that the kernel crash under Hyper-V associated with -r338807 is a separate issue even though WITHOUT_ZFS=3D seems to have avoided the crash. My plan is to continue with the -r338807 investigation after the loader problem is fixed in my builds. Then I've go back to trying builds using WITH_ZFS=3D (implicit), both native boots and Hyper-V based ones. =3D=3D=3D Mark Millard marklmi at yahoo.com ( dsl-only.net went away in early 2018-Mar)