Bug 21599

I should have said that the computer hangs with a blank screen and that Alt+PrtSc + (R S E I U B O) does nothing: I need to manually press its power button to shut it down.

Hi.

I've seen this too, but pressing Ctrl-Alt-Del 7 times within 2 seconds will force a reboot.

Cheers,
Stig

CC: (none) => smelror

@ Denis

Thanks for your report. I understand this always happens when rebooting or shutting down Mageia, regardless of used Desktop Environment.

Could you please boot into Mageia one more time and then run, as root:


   journalctl -ab -1 > log.txt

and attach log.txt to this report.

Please do also attach lspci.txt that is the result of running

  lspcidrake -v > lspci.txt

Thanks!

(In reply to Stig-Ørjan Smelror from comment #2)

> I've seen this too, but pressing Ctrl-Alt-Del 7 times within 2 seconds will
> force a reboot.
> 

Did that help, _even_ when the Alt-SysRq keycombinations no longer worked?

CC: (none) => marja11
Summary: Reboot hangs => Hard freeze when trying to reboot or shut down.
Keywords: (none) => NEEDINFO

Marja,

Yes, it has worked almost every time I've seen this issue.


Cheers,
Stig

Created attachment 9626 [details]
Output of 'journalctl -ab -1 > log.txt'

Created attachment 9627 [details]
Output of 'lspcidrake -v > lspci.txt'

@Marja Reports attached

@Stig-Ørjan I'll try next time I'll shut the computer down.

@Stig-Ørjan I hit Ctrl-Alt-Del 7 times within 2 seconds, and also tried by continuously pressing this key combination during more than 2 seconds, but no success.

(In reply to Denis Bitouzé from comment #8)
> @Stig-Ørjan I hit Ctrl-Alt-Del 7 times within 2 seconds, and also tried by
> continuously pressing this key combination during more than 2 seconds, but
> no success.

Hmm.

Just to clarify. Did you press and hold Ctrl-Alt and hit Del 7 times?
If so, I'm out of suggestions.

Cheers,
Stig

> Did you press and hold Ctrl-Alt and hit Del 7 times?
Yes, as usually used in order to force a reboot, isn't it?

>If so, I'm out of suggestions.
That's a pity! ;) Many thanks, anyway!

@Stig-Ørjan  BTW, is your trick documented somewhere? Why this magic number "7"?

(In reply to Denis Bitouzé from comment #11)
> @Stig-Ørjan  BTW, is your trick documented somewhere? Why this magic number
> "7"?

I happened upon it by accident as I just hit Del several times in a row one time and saw a message about hitting it 7 times. Haven't searched for the reason it is 7 :-)

Cheers,
Stig

@Stig-Ørjan Dark magic! ;)

Try to add different reboot options to kernel command line (try one at a time) when you boot the system:

reboot=acpi
reboot=bios
reboot=efi
reboot=pci

and report back if any of those options allows your system to reboot properly

CC: (none) => tmb

@Thomas If I'm right, the way for this is the one explained here (with 'linuxefi' instead of 'linux'):

https://wiki.mageia.org/en/How_to_set_up_kernel_options#Temporary_options_to_the_boot_loader

If so (tested with a reboot from SSMD):

- 'reboot=acpi': doesn't work
- 'reboot=bios': doesn't work
-  'reboot=efi': doesn't work (plus error message after Ctrl-x: some (strange: haven't notice) command not found)
-  'reboot=pci': doesn't work

BTW, I used to try with 'acpi=force' kernel option.

Thanks!

(In reply to Denis Bitouzé from comment #5)
> Created attachment 9626 [details]
> Output of 'journalctl -ab -1 > log.txt'

After 

> août 23 20:43:43 portable-fanny.chezmoi.fr sddm[1725]: Message received from
> greeter: PowerOff

There's:
> août 23 20:43:43 portable-fanny.chezmoi.fr sddm[1725]: Error from greeter
> session: "Process crashed"
> août 23 20:43:43 portable-fanny.chezmoi.fr sddm[1725]: Auth: sddm-helper
> crashed (exit code 15)
> août 23 20:43:43 portable-fanny.chezmoi.fr sddm[1725]: Error from greeter
> session: "Process crashed"
> août 23 20:43:43 portable-fanny.chezmoi.fr sddm[1725]: Auth: sddm-helper
> exited with 15

CC'ing KDE (SDDM) maintainers for those errors.

Does poweroff and/or reboot work well from a VT or in a terminal/konsole?



Something else that looks odd to me is:

> août 23 20:43:47 portable-fanny.chezmoi.fr systemd[1]: Requested transaction
> contradicts existing jobs: Transaction is destructive.

But that seems to be about stopping enp4s0 and that succeeds right after that, so I guess that shouldn't matter.... CC'ing the basesystem maintainers, though, in case it does matter, after all.

CC: (none) => basesystem, kde

> Does poweroff and/or reboot work well from a VT or in a terminal/konsole?
No.

to see if kernel is the cause, remove theese from kernel command line:

splash quiet acpi=force

and then add a:

3

(single digit 3, to have system boot to runlevel 3)


and boot with that.


when you get to login prompt, login as root and type: reboot

If it then reboots properly, it's not kernel at fault.

if it does not reboot properly, then hopefully it will print out a stack trace or something that could give a hint of what fails...

If so, take a picture of the messages on the screen and attach it here

@Thomas Boot to runlevel 3, login as root, reboot but same problem. Unfortunately, I can't take any picture since the screen, after displaying few messages I haven't time to read (but as far as I could see, all being "[OK]"), becomes blank.

In case of interest, the current (quite) complete line in the kernel options is:

linuxefi /boot/vmlinuz-4.9.43-desktop-1.mga6 root=UUID=... ro splash quiet noiswmd resume=UUID=... audit =0 acpi=force

Why are you using "acpi=force" ?

And exactly what laptop is this?

please do a: dmidecode >dmidecode.txt and attatch the resulting dmidecode.txt to this report...

@Thomas I added "acpi=force" after I read somewhere (I don't retrieve where) it could be helpful against freeze when trying to reboot or shut down.

The laptop is a Compaq 15-s017nf, dmidecode.txt attached.

Created attachment 9630 [details]
Output of dmidecode > dmidecode.txt

Assigning to kernel and drivers maintainer group, because this seems to be a kernel bug.

Removing NEEDINFO, because AFAICS all requested information was provided.

Assignee: bugsquad => kernel
Keywords: NEEDINFO => (none)

This message is a reminder that Mageia 6 is end of life.

Mageia stopped maintaining and issuing updates for Mageia 6. At that time this bug will be closed as OLD (EOL).

Package Maintainer: If you wish for this bug to remain open because you plan to 
fix it in a currently maintained version, simply change the 'version' to a later 
Mageia version prior to Mageia 6's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that we cannot 
be able to fix it before Mageia 6 was end of life.
If you would still like to see this bug fixed and are able to reproduce it against a later version of Mageia, you are encouraged to click on "Version" and change it against that version of Mageia.

Although we aim to fix as many bugs as possible during every release's lifetime, 
sometimes those efforts are overtaken by events. Often a more recent Mageia 
release includes newer upstream software that fixes bugs or makes them obsolete.

--
Mageia Bugsquad

Status: NEW => RESOLVED
Resolution: (none) => OLD
CC: (none) => ouaurelien