Bug#775812: base: HP EliteBook 840 G1 laptop fails to halt/poweroff after 15/12/2015 upgrade
Hi all,
First of all, thank you for your time investigating the bug.
I ran a few tests today, trying to help pinpointing the exact cause of
the bug.
On Mon, 2015-03-30 at 16:55 -0300, Henrique de Moraes Holschuh wrote:
> For those affected (i.e. if your HP Elitebook 840 G1 DOES have
> halt/poweroff issues right now), please do this:
> [...]
My HP Elitebook 840 G1 did not shutdown (but kept on rebooting) so I
purged 'intel-microcode', ran 'update-initramfs -u' to be sure,
validated that '/lib/firmware/intel-ucode' was removed from the system,
rebooted the system, and finally tried to power off the system. The
notebook did not power off properly, but rebooted instead—just as
before. Like you said, I think we can now conclude it is not
intel-microcode's fault.
On Mon, 2015-03-30 at 18:54 +0200, Samuel Thibault wrote:
> > I would like to add that I also didn't succeed in halting the
> > notebook by using the GRUB command 'halt', it just rebooted after
> > entering this command.
>
> Is this after a cold reboot (thus no uploaded microcode) or only after
> a hot reboot?
>
> Also, just to make sure: with systemd the "halt" command doesn't power
> off, "poweroff" needs to be used instead.
Next, I tried to power off the system with the GRUB command 'halt'.
There is no GRUB command 'poweroff' so I had to use 'halt'. The problem
still persisted and the notebook rebooted instead of powering off.
Next I tried to 'cold reboot': I powered off the notebook by hitting the
power button at the GRUB boot menu, started the notebook (hitting the
power button again), and entered the GRUB command 'halt'. Now the
notebook did properly power off. I started the notebook again, let it
boot al the way to the GNOME desktop and shut it down again from there.
I was able to properly power down the system three times in a row.
I had the idea the network connection (similar to Miguel) was cosing
trouble, since I was not always able to reliably replicate the bug when
I used the wired ethernet connection. For clarity, I had the suspicion
that switching between wired and wireless network connections sometimes
caused the bug to occur again.
Continuing with my tests, I installed 'intel-microcode' again, switched
wireless on—hoping to trigger the bug again. However, I shutdown and
started the notebook four times, enabling and disabling the wireless
network, but I did not succeed in triggering the bug to happen again.
On Tue, 2015-03-31 at 08:11 -0300, Henrique de Moraes Holschuh wrote:
> Please also attach the output of "lspci -v -v" (run as root).
I can send you this next time when I'm using the notebook again. I
forgot to check it last time!
Hope this extensive description of what I've tried helps!
Cheers,
Tim
Reply to: