On Fri, Feb 24, 2023 at 06:30:27PM +0100, Valerio Vanni wrote:
> https://bugzilla.kernel.org/show_bug.cgi?id=217083
Placing a descriptive subject and a summary here will certainly
encourage more readers to read your report. You should repost
with the subject you used there:
Kernel panic - not syncing: Attempted to kill init! exitcode=0x00007f00
and it's useful to mention the version ranges you've spotted (4.19-5.10).
Just my two cents,
Willy
Il 24/02/2023 18:36, Willy Tarreau ha scritto:
> On Fri, Feb 24, 2023 at 06:30:27PM +0100, Valerio Vanni wrote:
>> https://bugzilla.kernel.org/show_bug.cgi?id=217083
>
> Placing a descriptive subject and a summary here will certainly
> encourage more readers to read your report. You should repost
> with the subject you used there:
>
> Kernel panic - not syncing: Attempted to kill init! exitcode=0x00007f00
>
> and it's useful to mention the version ranges you've spotted (4.19-5.10).
Thank you, I reposted. I don't report bugs often, so I probably miss
something. Now I'll try other versions, collect more data etc, but it
will be enough to update bugzilla case or should I update also mailing list?
On Fri, Feb 24, 2023 at 12:53 PM Valerio Vanni <[email protected]> wrote:
> Thank you, I reposted. I don't report bugs often, so I probably miss
> something. Now I'll try other versions, collect more data etc, but it
> will be enough to update bugzilla case or should I update also mailing list?
I'd say both. We've got a whole thread on bugzilla and not all
developers here on LKML use it. (Some do, though.)
Ultimately it's up to you.
-- Slade
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.