From: Valerio Vanni <valerio.vanni@inwind.it>
To: Slade Watkins <srw@sladewatkins.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Bugzilla 217083
Date: Fri, 10 Mar 2023 02:26:59 +0100 [thread overview]
Message-ID: <6b65e5dd-a940-a176-fa86-5c2babac805c@inwind.it> (raw)
In-Reply-To: <CA+pv=HNUMqtFGEdcsgxEq6+UpqVj95o89rc4D7zSJyGnvHLHNw@mail.gmail.com>
Il 24/02/2023 19:06, Slade Watkins ha scritto:
>> https://bugzilla.kernel.org/show_bug.cgi?id=217083
>>
>> I got this error after upgrading a Debian machine (x86-64) from Stretch
>> to Buster. Upgrade is successful, but the next boot it crashes.
>
> Thanks for the details. What was the last known good kernel version
> that did not exhibit this issue on your system?
I updated bugzilla and I update also here.
I use serial console to collect diagnostic data, but now I've found that
it misses lines.
In kernel boot line I put "console=ttyS0 console=tty0" so I get both
local and serial console.
But the issue is: tty0 shows more messages. Is there a way to get
everything also on ttyS0? It would be useful, since you cant' scroll
tty0 after a kernel panic.
When kernel loads, tty0 scrolls very fast. I could see some more line
but wasn't able to read them.
The only way I found was adding a (slow) speed to ttyS0,
"console=ttyS0,1200" on kernel boot line.
This slowed down ttyS0, and tty0 was forced to go at the same pace.
So I could read a line (only on tty0), between "Run /sbin/init as init
process" and start of kernel panic.
That line complained that it could not find something in /usr/lib/....
At that stage, /usr was not mounted yet.
Then I restored full disk image on the machine, an before upgrading from
stretch to buster I merged / and /usr, so that /usr/lib/... was
available from / mount.
After that, kernel panic did not show anymore.
prev parent reply other threads:[~2023-03-10 1:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-24 17:30 Valerio Vanni
2023-02-24 17:36 ` Willy Tarreau
2023-02-24 17:53 ` Valerio Vanni
2023-02-24 18:00 ` Slade Watkins
2023-03-10 1:26 ` Valerio Vanni [this message]
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=6b65e5dd-a940-a176-fa86-5c2babac805c@inwind.it \
--to=valerio.vanni@inwind.it \
--cc=linux-kernel@vger.kernel.org \
--cc=srw@sladewatkins.net \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®