Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 1 Oct 2022 21:08:32 -0600
From:      Warner Losh <imp@bsdimp.com>
To:        Larry Rosenman <ler@freebsd.org>
Cc:        Freebsd current <freebsd-current@freebsd.org>, Mark Johnston <markj@freebsd.org>
Subject:   Re: BOOT CRASH -- Current -CURRENT
Message-ID:  <CANCZdfoSqNsTP=rbo-4RuSuCBujhMFWTH_eYu%2B29sTk2ep42NQ@mail.gmail.com>
In-Reply-To: <aa3db45d9e37c1b18050cdf063da3e87@FreeBSD.org>
References:  <9de62c1d7c3eae83b97a1004780a8d0d@FreeBSD.org> <CANCZdfr4Ko5C6MUEQrM3Ae-f5JRomFzJV74Dvk2ezf-Ua9eUnA@mail.gmail.com> <aa3db45d9e37c1b18050cdf063da3e87@FreeBSD.org>

next in thread | previous in thread | raw e-mail | index | archive | help
--00000000000065ac9c05ea048b2a
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Sat, Oct 1, 2022 at 9:06 PM Larry Rosenman <ler@freebsd.org> wrote:

> On 10/01/2022 10:04 pm, Warner Losh wrote:
>
> Do  you have a /boot tarball that can be loaded in a VM that recreates th=
e
> problem (along with a clean hash)?
>
> But before you try that, have you tried a completely clean rebuild of the
> kernel to preclude the possibility that something is somehow cross thread=
ed?
>
> Warner
>
> On Sat, Oct 1, 2022 at 8:39 PM Larry Rosenman <ler@freebsd.org> wrote:
>
>
> =E2=9D=AF more info.11
> Dump header from device: /dev/mfid0p3
>    Architecture: amd64
>    Architecture Version: 2
>    Dump Length: 126748815
>    Blocksize: 512
>    Compression: zstd
>    Dumptime: 2022-10-01 21:26:40 -0500
>    Hostname:
>    Magic: FreeBSD Kernel Dump
>    Version String: FreeBSD 14.0-CURRENT #168
> ler/freebsd-main-changes-n258354-6cdd871ebc4: Sat Oct  1 21:13:01 CDT
> 2022
>      root@borg.lerctr.org:/usr/obj/usr/src/amd64.amd64/sys/LER-MINIMAL
>    Panic String: page fault
>    Dump Parity: 501115454
>    Bounds: 11
>    Dump Status: good
>
> I do have source and debug stuff, BUT kgdb croaks on me.
>
> I *CAN* give access to the machine.
>
> the console backtrace showed something about the kld load of
> dependencies.
>
>
>
> --
> Larry Rosenman                     http://people.freebsd.org/~ler
> Phone: +1 214-642-9640                 E-Mail: ler@FreeBSD.org
> US Mail: 5708 Sabbia Dr, Round Rock, TX 78665-2106
>
> let me wipe /usr/obj, and rebuild everything (I *DO* use meta-mode).
>

I've had fewer problems with it than non-meta mode, but this looks like a
'corruption' or 'cross threaded' crash I've chased in the past that went
away with a rebuild. So it's better to be sure...

Warner

--00000000000065ac9c05ea048b2a
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr"><br></div><br><div class=3D"gmail_quote">=
<div dir=3D"ltr" class=3D"gmail_attr">On Sat, Oct 1, 2022 at 9:06 PM Larry =
Rosenman &lt;<a href=3D"mailto:ler@freebsd.org">ler@freebsd.org</a>&gt; wro=
te:<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px =
0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div style=
=3D"font-size:10pt;font-family:Arial,Helvetica,sans-serif">
<p id=3D"m_4022102228487947788reply-intro">On 10/01/2022 10:04 pm, Warner L=
osh wrote:</p>
<blockquote type=3D"cite" style=3D"padding:0px 0.4em;border-left:2px solid =
rgb(16,16,255);margin:0px">
<div id=3D"m_4022102228487947788replybody1">
<div dir=3D"ltr">Do=C2=A0 you have a /boot tarball that can be loaded in a =
VM that recreates the problem (along with a clean hash)?
<div>=C2=A0</div>
<div>But before you try that, have you tried a completely clean rebuild of =
the kernel to preclude the possibility that something is somehow cross thre=
aded?</div>
<div>=C2=A0</div>
<div>Warner</div>
</div>
<br>
<div>
<div dir=3D"ltr">On Sat, Oct 1, 2022 at 8:39 PM Larry Rosenman &lt;<a href=
=3D"mailto:ler@freebsd.org" rel=3D"noreferrer" target=3D"_blank">ler@freebs=
d.org</a>&gt; wrote:</div>
<blockquote style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204=
,204,204);padding-left:1ex"><br>=E2=9D=AF more info.11<br>Dump header from =
device: /dev/mfid0p3<br>=C2=A0 =C2=A0Architecture: amd64<br>=C2=A0 =C2=A0Ar=
chitecture Version: 2<br>=C2=A0 =C2=A0Dump Length: 126748815<br>=C2=A0 =C2=
=A0Blocksize: 512<br>=C2=A0 =C2=A0Compression: zstd<br>=C2=A0 =C2=A0Dumptim=
e: 2022-10-01 21:26:40 -0500<br>=C2=A0 =C2=A0Hostname:<br>=C2=A0 =C2=A0Magi=
c: FreeBSD Kernel Dump<br>=C2=A0 =C2=A0Version String: FreeBSD 14.0-CURRENT=
 #168 <br>ler/freebsd-main-changes-n258354-6cdd871ebc4: Sat Oct=C2=A0 1 21:=
13:01 CDT <br>2022<br>=C2=A0 =C2=A0 =C2=A0root@borg.lerctr.org:/usr/obj/usr=
/src/amd64.amd64/sys/LER-MINIMAL<br>=C2=A0 =C2=A0Panic String: page fault<b=
r>=C2=A0 =C2=A0Dump Parity: 501115454<br>=C2=A0 =C2=A0Bounds: 11<br>=C2=A0 =
=C2=A0Dump Status: good<br><br>I do have source and debug stuff, BUT kgdb c=
roaks on me.<br><br>I *CAN* give access to the machine.<br><br>the console =
backtrace showed something about the kld load of <br>dependencies.<br><br><=
br><br>-- <br>Larry Rosenman=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0<a href=3D"http://people.freebsd.org/~ler" r=
el=3D"noopener noreferrer" target=3D"_blank">http://people.freebsd.org/~ler=
</a><br>Phone: +1 214-642-9640=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0E-Mail: ler@FreeBSD.org<br>US Mail: 5708 Sabbia Dr, Round =
Rock, TX 78665-2106<br><br></blockquote>
</div>
</div>
</blockquote>
<p>let me wipe /usr/obj, and rebuild everything (I *DO* use meta-mode).</p>=
</div></blockquote><div><br></div><div>I&#39;ve had fewer problems with it =
than non-meta mode, but this looks like a &#39;corruption&#39; or &#39;cros=
s threaded&#39; crash I&#39;ve chased in the past that went away with a reb=
uild. So it&#39;s better to be sure...</div><div><br></div><div>Warner=C2=
=A0</div></div></div>

--00000000000065ac9c05ea048b2a--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CANCZdfoSqNsTP=rbo-4RuSuCBujhMFWTH_eYu%2B29sTk2ep42NQ>