[1.2 installer]: Kernel panic when attempting to reboot after install.

  • Open
  • quality assurance status badge
Details
4 participants
  • Ludovic Courtès
  • Brendan Tildesley
  • Tobias Geerinckx-Rice
  • Mathieu Othacehe
Owner
unassigned
Submitted by
Brendan Tildesley
Severity
normal
B
B
Brendan Tildesley wrote on 18 Oct 2020 06:03
(address . bug-guix@gnu.org)
499b6483-191a-a445-6930-fd2f4804fca6@brendan.scot
I generated an installer for myself from
5d4ad8e1be6d60c38577e2f3d92cc5642b12eff0 + Miguel's patch (I think
unrelated to this bug) here https://paste.debian.net/plain/1167398

After the install completed I pulled out the USB as per instruction on
the screen, and pressed the Reboot button. The system then Kernel panic
with the following messages:


Sorry I don't have it in textual form.
M
M
Mathieu Othacehe wrote on 18 Oct 2020 21:16
(name . Brendan Tildesley)(address . mail@brendan.scot)(address . 44054@debbugs.gnu.org)
874kmrwdiu.fsf@gnu.org
Hello Brendan,

Toggle quote (8 lines)
> After the install completed I pulled out the USB as per instruction on the
> screen, and pressed the Reboot button. The system then Kernel panic with the
> following messages:
>
> https://brendan.scot/p/IMG_20201018_140343.png
>
> Sorry I don't have it in textual form.

Is the installed system functional? The kernel panic may come from the
fact that the installation support was removed while still needed.

In that case, we could stop advising users to remove the installation
device before rebooting.

Thanks,

Mathieu
B
B
Brendan Tildesley wrote on 19 Oct 2020 07:45
(name . Mathieu Othacehe)(address . othacehe@gnu.org)(address . 44054@debbugs.gnu.org)
bc4c1655-0055-7b00-e41f-bcea6608f908@brendan.scot
On 19/10/20 5:16 am, Mathieu Othacehe wrote:
Toggle quote (11 lines)
> Hello Brendan,
>
>> After the install completed I pulled out the USB as per instruction on the
>> screen, and pressed the Reboot button. The system then Kernel panic with the
>> following messages:
>>
>> https://brendan.scot/p/IMG_20201018_140343.png
>>
>> Sorry I don't have it in textual form.
> Is the installed system functional? The kernel panic may come from the
> fact that the installation support was removed while still needed.
Yes the system was functional. From memory, other distro installers
recommend removing
the device and rebooting too. So its curious that Guix somehow has an
issue with it.
Although this is only one data point. I'd like other people to test it
to be sure.
L
L
Ludovic Courtès wrote on 21 Oct 2020 12:41
(name . Brendan Tildesley)(address . mail@brendan.scot)
878sbz6eui.fsf@gnu.org
Hi,

Brendan Tildesley <mail@brendan.scot> skribis:

Toggle quote (9 lines)
> On 19/10/20 5:16 am, Mathieu Othacehe wrote:
>> Hello Brendan,
>>
>>> After the install completed I pulled out the USB as per instruction on the
>>> screen, and pressed the Reboot button. The system then Kernel panic with the
>>> following messages:
>>>
>>> https://brendan.scot/p/IMG_20201018_140343.png

This panic says that PID 1 was terminated by signal 7 (SIGBUS), which is
a bit alarming.

Toggle quote (8 lines)
>>> Sorry I don't have it in textual form.
>> Is the installed system functional? The kernel panic may come from the
>> fact that the installation support was removed while still needed.
> Yes the system was functional. From memory, other distro installers
> recommend removing
> the device and rebooting too. So its curious that Guix somehow has an
> issue with it.

Did you remove the device right after the “installation complete”
message?

Mathieu, are there other file system operations happening beyond that?

Thanks,
Ludo’.
T
T
Tobias Geerinckx-Rice wrote on 21 Oct 2020 13:19
(name . Brendan Tildesley)(address . mail@brendan.scot)
875z73akrt.fsf@nckx
Brendan,

Brendan Tildesley ???
Toggle quote (4 lines)
> From memory, other distro installers recommend removing
> the device and rebooting too. So its curious that Guix
> somehow has an issue with it.

Not really: you're ripping out the root file system while the full
system is happily running, then initiating a graceful shutdown
sequence that's going to try to read from disc. No distro will
survive that.

Some bad installers pretend to. After all: the persistent target
device is safely unmounted; let's quietly hard-reset the system!

What I've seen the better ones do is display the ‘plz remove USB’
message very late in the shutdown sequence, when it's actually
safe to do so.

Kind regards,

T G-R
-----BEGIN PGP SIGNATURE-----

iIMEARYKACsWIQT12iAyS4c9C3o4dnINsP+IT1VteQUCX5AZVg0cbWVAdG9iaWFz
LmdyAAoJEA2w/4hPVW15UFMA/jpZJqua3fT2cYG+opzC9ACLwwouCTicue0ki7zl
QHC1AP4thNiE2zXus7YvloJAkLNR/TOj7xDH+AjI3eASIf9oCA==
=Oh2W
-----END PGP SIGNATURE-----

M
M
Mathieu Othacehe wrote on 22 Oct 2020 10:17
(name . Ludovic Courtès)(address . ludo@gnu.org)
87mu0eznbt.fsf@gnu.org
Hey,

Toggle quote (2 lines)
> Mathieu, are there other file system operations happening beyond that?

The final "sync" call is done just after the user clicks on "Reboot", so
if the flash drive is removed before clicking on "Reboot" I guess things
can go wrong.

I'll see if I can reproduce this issue.

Thanks,

Mathieu
?
Your comment

Commenting via the web interface is currently disabled.

To comment on this conversation send an email to 44054@debbugs.gnu.org

To respond to this issue using the mumi CLI, first switch to it
mumi current 44054
Then, you may apply the latest patchset in this issue (with sign off)
mumi am -- -s
Or, compose a reply to this issue
mumi compose
Or, send patches to this issue
mumi send-email *.patch