From owner-freebsd-stable@freebsd.org Tue Oct 23 01:43:29 2018 Return-Path: Delivered-To: freebsd-stable@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 05224FF0DC3 for ; Tue, 23 Oct 2018 01:43:28 +0000 (UTC) (envelope-from marklmi@yahoo.com) Received: from sonic304-12.consmr.mail.bf2.yahoo.com (sonic304-12.consmr.mail.bf2.yahoo.com [74.6.128.35]) (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 8D14B80950 for ; Tue, 23 Oct 2018 01:43:28 +0000 (UTC) (envelope-from marklmi@yahoo.com) X-YMail-OSG: .FqKwM4VM1kvm6HuSbkUubvD1CfRWK8UaOtmkzZ_._EBC.ecC3.F41ytmoRRDNE iV7cpHptQ9QTx8VQYCFcSi7hKADlEvDqahE_xlzRuYd.WehjYJ387t6ohq2xaXR_XIFyJj3I.Fqz uxGAzXu2BCYgSAFAbpNaukseUcQXSmwXQAClr2itL1sDpZXCKqeCAoq_Av6u.Z3WBOKN.qEQkYI8 RObafkHbYq1xaoTpitTnqb0.FFm_vG2keRk5Tzbde0lRZ6d2qNKsiwn2mWoF5v3xIj2YKcunmWU5 0D3ShbK49fsg5lztYMtIypEEB2zPS2k04Ho1FSOnvFx3e_FQ78tCRN2l5L08KHbRqA_OrnKVOW.X dCRRRNvCd_fzO8lwUVGYFcoWknrg3ihWjkwlKq53GLlveuy3eAuOGTDVzN4Proe1xjUZs0TWPiwF bExFEsD_YtFDO.fVPbPEm0de5Ku1tx3fPU8AUSLb1JIdPjz5vsMOH3UdwkGlAuLPvjaM3FxA6yfb kv0fKr_feS3T.W3GKyOFc0tzTvkZRLNj33D.NAy9BP8bT4ex0o6LpUFT89DgRczQ_nRGmuVreV.Z tlV6B7q2VeU3L34vUmZk9xP0MdyQijq0iRP_ojiQz5Av2nMUgjpEvy5pTEc89FLrVMY7MS1HACPV _avD8k4wOP4gkoIq9jd3K81dCPb5S9X1wSKrUyWHiZBIqHFMxLO4dIzcpnmWz5906avnQNES5wxV HFfW6bBg_X0Ao7dJpBCoDhTioDlbznr8DkcXP9Pia4Oic0Q.HYzDDG8KHl5_8AP9YCTvUQRk6Hoq oOhBKIOzn4QP_yugtu78_DGYCTDW5gu7Vi_eEPDI6Tg1Wkzd7iNd.djUSc.HGNCFe5R.F.LqwdjQ hKbIf3xe_qM9ZFXcGGYAeUqOA._sPl0sOIRfE5GIJ.L1RwDAT1fQO24QnvaMUxWWDyoUbtiIzegD yrHSAAzA5sEj4RKRkfLT__D3kj4bmz41r9Vo7_XknoGbh5b9VjrdCivIXJukz7bpKTFmEaZA7Wvy bk6S1cvSr.17jAv7qAEBCshliLGKvoxpiwOvVkzrNfgozJY.itUi9Po3X5QRxfpeAYQd_TUIpepP GfKx_2j0- Received: from sonic.gate.mail.ne1.yahoo.com by sonic304.consmr.mail.bf2.yahoo.com with HTTP; Tue, 23 Oct 2018 01:43:27 +0000 Received: from c-76-115-7-162.hsd1.or.comcast.net (EHLO [192.168.1.25]) ([76.115.7.162]) by smtp420.mail.bf1.yahoo.com (Oath Hermes SMTP Server) with ESMTPA ID 04876bb04a8c3eb2f8320caaf7413218; Tue, 23 Oct 2018 01:43:23 +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: <16BF1504-AD3B-4B5F-A728-43C2A777A082@yahoo.com> Date: Mon, 22 Oct 2018 18:43:21 -0700 Cc: Toomas Soome , FreeBSD Current , FreeBSD-STABLE Mailing List Content-Transfer-Encoding: quoted-printable Message-Id: <302639EA-55AA-4A41-BC03-4D48E6A09000@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> <16BF1504-AD3B-4B5F-A728-43C2A777A082@yahoo.com> To: Warner Losh , Konstantin Belousov X-Mailer: Apple Mail (2.3445.9.1) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 Oct 2018 01:43:29 -0000 [I' unable to reproduce the under-Hyper-V early kernel crash for WITH_ZFS=3D (implicit) build that includes the for-loaders patch I was given to try.] On 2018-Oct-22, at 10:01 AM, Mark Millard wrote: > [I will note the the loader problem has been shown to > not be involved in the kernel problem that this > "Subject:" was originally for.] >=20 > On 2018-Oct-22, at 9:26 AM, Warner Losh wrote: >=20 >> 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. >=20 > 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. >=20 > 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. >=20 > 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. So much for my ability to make that inference correctly: The WITH_ZFS=3D (implicit) build worked fine for booting natively and via Hyper-V when the patch to fix the loaders was included in what to build. I'm now unable to reproduce this kernel-time crash. The patch was from: https://reviews.freebsd.org/D11174 The empty LUN's in the media reader now get messages that look something like: disk8: Read 1 sector(s) from 0 to 0xffffe000 (0x8000): 0x31 early in the loader activity. =3D=3D=3D Mark Millard marklmi at yahoo.com ( dsl-only.net went away in early 2018-Mar)