Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 13 Aug 2022 20:01:03 -0600
From:      Warner Losh <imp@bsdimp.com>
To:        Oleg Lelchuk <oleglelchuk@gmail.com>
Cc:        Yasuhiro Kimura <yasu@freebsd.org>, FreeBSD Current <freebsd-current@freebsd.org>
Subject:   Re: Updating EFI boot loader results in boot hangup
Message-ID:  <CANCZdfp4Har%2BrLV5kg94EWO_Uc767K7ga9AKLTznvqoC2JvQXw@mail.gmail.com>
In-Reply-To: <CA%2BGqWgsMYEp4goeLBO4%2BufDU_ap5Opmf4udL_WSd-NZU1Q3dog@mail.gmail.com>
References:  <CA%2BGqWgtZM0Hwz9rw0zvj60WkVpQHxwR3bEaCJ4SJ8kx2tpd-bg@mail.gmail.com> <20220814.084037.1953883684410810254.yasu@FreeBSD.org> <CA%2BGqWguZBp6XWz_L=RB7ou1%2BEUMwa4EsXzB%2BosDvXzFVdNRh%2BQ@mail.gmail.com> <20220814.095721.849461222067829352.yasu@FreeBSD.org> <CA%2BGqWgsMYEp4goeLBO4%2BufDU_ap5Opmf4udL_WSd-NZU1Q3dog@mail.gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help
--000000000000e013d705e629e315
Content-Type: text/plain; charset="UTF-8"

UFS or ZFS?

Warner

On Sat, Aug 13, 2022 at 7:31 PM Oleg Lelchuk <oleglelchuk@gmail.com> wrote:

> I don't understand what your command does. All I can see is that
> https://cgit.freebsd.org/src/commit/?id=ec9f3e776f39286ccec9915f38cca9729e6f9241
> causes the error that we currently see, and the commit that precedes it
> https://cgit.freebsd.org/src/commit/?id=ad759c73522efb606135e2891ac03864926b80a3
> causes a different kind of error.
>
> On Sat, Aug 13, 2022 at 8:58 PM Yasuhiro Kimura <yasu@freebsd.org> wrote:
>
>> From: Oleg Lelchuk <oleglelchuk@gmail.com>
>> Subject: Re: Updating EFI boot loader results in boot hangup
>> Date: Sat, 13 Aug 2022 20:28:09 -0400
>>
>> > I can already see that commit
>> >
>> > c32dde3166922f55927764464d13f1bc9640f5f6 causes breakage, but the
>> commit that precedes it
>> >
>> > f197c0bf3e075286ccea32cd12023f3317474c5a doesn't cause breakage and the
>> system boots just fine with it. But
>> > the error that the c32dd commit causes is different from the error that
>> we see now, so maybe there is a
>> > possibility that one of the commits that follow it fixed the breakage,
>> but then yet another commit caused a
>> > different kind of breakage again.
>>
>> With the command `git bisect start --first-parent 9d16275c65b a69c0964625
>> -- stand`
>> I got just same result.
>>
>> ---
>> Yasuhiro Kimura
>>
>

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

<div dir=3D"ltr">UFS or ZFS?<div><br></div><div>Warner</div></div><br><div =
class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Sat, Aug 13,=
 2022 at 7:31 PM Oleg Lelchuk &lt;<a href=3D"mailto:oleglelchuk@gmail.com">=
oleglelchuk@gmail.com</a>&gt; wrote:<br></div><blockquote class=3D"gmail_qu=
ote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,20=
4);padding-left:1ex"><div dir=3D"ltr">I don&#39;t understand what your comm=
and does. All I can see is that=C2=A0<a href=3D"https://cgit.freebsd.org/sr=
c/commit/?id=3Dec9f3e776f39286ccec9915f38cca9729e6f9241" target=3D"_blank">=
https://cgit.freebsd.org/src/commit/?id=3Dec9f3e776f39286ccec9915f38cca9729=
e6f9241</a> causes the error that we currently see, and the commit that pre=
cedes it <a href=3D"https://cgit.freebsd.org/src/commit/?id=3Dad759c73522ef=
b606135e2891ac03864926b80a3" target=3D"_blank">https://cgit.freebsd.org/src=
/commit/?id=3Dad759c73522efb606135e2891ac03864926b80a3</a> causes a differe=
nt kind of error.</div><br><div class=3D"gmail_quote"><div dir=3D"ltr" clas=
s=3D"gmail_attr">On Sat, Aug 13, 2022 at 8:58 PM Yasuhiro Kimura &lt;<a hre=
f=3D"mailto:yasu@freebsd.org" target=3D"_blank">yasu@freebsd.org</a>&gt; wr=
ote:<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">From: Oleg =
Lelchuk &lt;<a href=3D"mailto:oleglelchuk@gmail.com" target=3D"_blank">oleg=
lelchuk@gmail.com</a>&gt;<br>
Subject: Re: Updating EFI boot loader results in boot hangup<br>
Date: Sat, 13 Aug 2022 20:28:09 -0400<br>
<br>
&gt; I can already see that commit<br>
&gt; <br>
&gt; c32dde3166922f55927764464d13f1bc9640f5f6=C2=A0causes breakage, but the=
 commit that precedes it<br>
&gt; <br>
&gt; f197c0bf3e075286ccea32cd12023f3317474c5a=C2=A0doesn&#39;t cause breaka=
ge and the system boots just fine with it. But<br>
&gt; the error that the c32dd commit causes is different from the error tha=
t we see now, so maybe there is a<br>
&gt; possibility that one of the commits that follow it fixed the breakage,=
 but then yet another commit caused a<br>
&gt; different kind of breakage again.<br>
<br>
With the command `git bisect start --first-parent 9d16275c65b a69c0964625 -=
- stand`<br>
I got just same result.<br>
<br>
---<br>
Yasuhiro Kimura<br>
</blockquote></div>
</blockquote></div>

--000000000000e013d705e629e315--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CANCZdfp4Har%2BrLV5kg94EWO_Uc767K7ga9AKLTznvqoC2JvQXw>