All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bob Tracy <rct@frus.com>
To: debian-alpha@lists.debian.org
Cc: Michael Cree <mcree@orcon.net.nz>, linux-alpha@vger.kernel.org
Subject: Re: 5.17.0 boot issue on Miata
Date: Fri, 8 Apr 2022 08:02:29 -0500	[thread overview]
Message-ID: <YlAyZdZ6afL58Ege@gherkin.frus.com> (raw)
In-Reply-To: <Yk4XsdHvjrLqN1LR@gherkin.frus.com>

On Wed, Apr 06, 2022 at 05:44:01PM -0500, Bob Tracy wrote:
> v5.17-rc2 ok.  v5.17-rc3 I get the disk sector errors and hang that I
> reported in the first message in this thread.
> 
> I'm going to try a native build of '-rc3' just to rule out any
> cross-compiler strangeness.  Should have something to report in another
> 34 hours or so :-(.

Confirmed: the native build was just as broken as the cross build.  The bug
was introduced somewhere between v5.17-rc2 and v5.17-rc3.  But at least I
have a bit more confidence in the integrity of what the cross tools build.

Interesting aside: the cross build's vmlinux.gz was approx. 200k larger.
That might be due to gcc version differences (native toolchain is 11.2,
and the cross toolchain is 11.1).

I'll start the actual bisection process today.  If I don't finish today,
it will be at least another week before I can get back to this, so
apologies in advance.

--Bob

  reply	other threads:[~2022-04-08 13:02 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-25  2:54 5.17.0 boot issue on Miata Bob Tracy
2022-03-26 22:21 ` Michael Cree
2022-04-05  1:42   ` Bob Tracy
2022-04-05  5:01     ` Michael Cree
2022-04-05 13:55       ` Bob Tracy
2022-04-05 18:22         ` Helge Deller
2022-04-06 22:44           ` Bob Tracy
2022-04-08 13:02             ` Bob Tracy [this message]
2022-04-19  4:53               ` Bob Tracy
2022-04-25  9:26                 ` John Garry
2022-04-25  9:26                   ` John Garry
2022-05-03 15:50                   ` Bob Tracy

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=YlAyZdZ6afL58Ege@gherkin.frus.com \
    --to=rct@frus.com \
    --cc=debian-alpha@lists.debian.org \
    --cc=linux-alpha@vger.kernel.org \
    --cc=mcree@orcon.net.nz \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.