FS#42518 - [linux] Kernel does not shutdown and registers panic on startup

Attached to Project: Arch Linux
Opened by Jonathan (BeenEncoded) - Friday, 24 October 2014, 00:32 GMT
Last edited by Doug Newgard (Scimmia) - Thursday, 21 September 2017, 18:51 GMT
Task Type Bug Report
Category Kernel
Status Closed
Assigned To Tobias Powalowski (tpowa)
Architecture x86_64
Severity Critical
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 7
Private No

Details

Linux 3.17.1-1

Line 882:

[ 11.205337] i915 0000:00:02.0: fb0: inteldrmfb frame buffer device
[ 11.205339] i915 0000:00:02.0: registered panic notifier

When I shutdown, it doesn't power off. It reaches "power off", but never actually shuts down. During the shutdown process, it repeatedly re-mounts my root partition several times. It also attempts to kill systemd-udev several times as well. I can only speculate that it fails to kill those procs and that the filesystem remains mounted when I am forced to ungracefully terminate power. This issue did not exist in version 3.16. I have 4 computers, but only one experiences this problem.
This task depends upon

Closed by  Doug Newgard (Scimmia)
Thursday, 21 September 2017, 18:51 GMT
Reason for closing:  No response
Comment by Jonathan (BeenEncoded) - Friday, 24 October 2014, 16:05 GMT
I will comment later with more specs on my hardware so this issue can be reproduced. I can't provide them right now, but I will be able to tomorrow.
Comment by Doug Newgard (Scimmia) - Friday, 24 October 2014, 16:35 GMT
I'm thinking this is the same as  FS#42509 . Can you test it?
Comment by Doug Newgard (Scimmia) - Friday, 24 October 2014, 21:59 GMT
Another person with the same traces just tested, it is a different issue than  FS#42509 
Comment by Jonathan (BeenEncoded) - Friday, 24 October 2014, 22:54 GMT
I'm going to try and get the logs from the kernel shutdown, as it might reveal more about what's going on with it. If you need any more information about my hardware specs, please feel free to ask.

I can reproduce the problem consistently every time I turn the machine on and off. It doesn't seem to matter what I do: I get the same logs, and the same behavior. (shutdown from GUI, shutdown without logging in, shutdown through GUI, etc...)
Comment by Jonathan (BeenEncoded) - Sunday, 26 October 2014, 16:40 GMT
I wasn't able to get the logs, but I took a picture. The computer suffering this issue is an Asus X551MAV-RCLN06. A quick google of the brand and model will come up with it. It is a fairly new laptop I bought about a month ago.
Comment by revel (revel) - Monday, 27 October 2014, 19:13 GMT
Perhaps the microcode thing is related to this issue: https://www.archlinux.org/news/changes-to-intel-microcodeupdates/
Comment by Jonathan (BeenEncoded) - Thursday, 30 October 2014, 03:02 GMT
No. I updated the microcode. It had no effect at all on the system.
Comment by Jonathan (BeenEncoded) - Thursday, 30 October 2014, 03:04 GMT
What are you guys doing to fix this? I would like to help if I can. I am a software engineer (intern, right now).
Comment by moto (moto) - Saturday, 01 November 2014, 07:18 GMT
Also having this problem on ASUS X551MAV-EB01-B, linux 3.17.1-1-arch.
Comment by Edouard (madko) - Monday, 03 November 2014, 21:34 GMT
I don't have any response on  FS#42529  so I put it here:
https://bugzilla.kernel.org/show_bug.cgi?id=86551 <= upstream bug with patch that fix  FS#42529 

diff --git a/drivers/gpu/drm/i915/intel_panel.c b/drivers/gpu/drm/i915/intel_panel.c
index e18b3f49074c..33d14dcc1019 100644
--- a/drivers/gpu/drm/i915/intel_panel.c
+++ b/drivers/gpu/drm/i915/intel_panel.c
@@ -1098,7 +1098,7 @@ static u32 get_backlight_min_vbt(struct intel_connector *connector)
WARN_ON(panel->backlight.max == 0);

/* vbt value is a coefficient in range [0..255] */
- return scale(dev_priv->vbt.backlight.min_brightness, 0, 255,
+ return scale(dev_priv->vbt.backlight.min_brightness, 0, 512,
0, panel->backlight.max);
}
Comment by Jonathan (BeenEncoded) - Tuesday, 04 November 2014, 04:57 GMT
the most recent update of the kernel did not fix this issue for me.
Comment by Jonathan (BeenEncoded) - Sunday, 16 November 2014, 19:53 GMT
The most recent update of the Kernel fixed this problem for me.
Comment by Edouard (madko) - Monday, 17 November 2014, 07:45 GMT
  • Field changed: Percent Complete (100% → 0%)
no this is not fixed! still can't use my computer, kernel hangs at boot
Comment by Edouard (madko) - Monday, 17 November 2014, 08:12 GMT
I tried the patch in #comment129453 and it works but it seems I loose the backlight control. But at least it boots.

Patch is upstream:
commit e1c412e75754ab7b7002f3e18a2652d999c40d4b

I will give it an other try or should I open a new bug if backlight is not working any more?
Comment by Ernesto Acosta (elav) - Monday, 24 November 2014, 17:32 GMT
Same situation in my Lenovo Ideapad U510. When I shutdown, it doesn't power off. It reaches "power off", but never actually shuts down. During the shutdown process, it repeatedly re-mounts my root partition several times.

:(
Comment by Edouard (madko) - Friday, 28 November 2014, 17:21 GMT
Startup is now fine with latest kernel (3.17.4-1) but lost blacklight control :(
Comment by Edouard (madko) - Tuesday, 23 December 2014, 12:40 GMT
Adding acpi_osi= at kernel boot opts and now it's fine, backlight control is back (at leat on 3.18.1-1)
Comment by jb (jb.1234abcd) - Thursday, 25 December 2014, 19:50 GMT
It does not reboot. Tested from tty console.
# reboot

Debug with: systemd.log_level=debug systemd.log_target=kmsg log_buf_len=1M

See attachment: reboot.log
followed by tty console messages:
[ OK ] Reached target Shutdown.
[...] watchdog watchdog0: watchdog did not stop!
[...] watchdog watchdog0: watchdog did not stop!
[...] cgroup: option or name mismatch, new: 0x0 "", old: 0x4 "systemd"
[...] reboot: Restarting system

Waited for ca. 10 min, but no effect.

Laptop hp nx6110
00:00.0 Host bridge: Intel Corporation Mobile 915GM/PM/GMS/910GML Express Processor to DRAM Controller (rev 03)

Linux myhost 3.17.6-1-ARCH #1 SMP PREEMPT Sun Dec 7 23:58:19 UTC 2014 i686 GNU/Linux
libsystemd 218-1
systemd 218-1
systemd-sysvcompat 218-1
Comment by Dave Reisner (falconindy) - Thursday, 25 December 2014, 20:02 GMT
Can you try a different reboot method, e.g. add reboot=triple or reboot=bios to your kernel commandline? Rebooting is a fairly magical process which has to contend with all sorts of broken hardware. The kernel maintains a long list of quirks to handle this.
Comment by jb (jb.1234abcd) - Thursday, 25 December 2014, 20:54 GMT
reboot=pci fixed it.
I did not have this problem before (but do not remember which kernel caused it - quite long time ago).
Thanks.
Comment by webnull (webnull) - Saturday, 28 November 2015, 09:58 GMT
I have similar problem on Dell Inspiron 5537 with Intel Corporation Haswell-ULT Integrated Graphics Controller (rev 09)
Comment by Nicholas Sielicki (sielicki) - Monday, 21 August 2017, 20:54 GMT
This ticket is old. Is anyone still seeing this issue? If so, please post how you're booting the kernel (EFI or MBR/legacy, which specific loader you're using, etc.), and check that your firmware is up to date.

I suspect that this ticket can be chalked up as symptoms of buggy BIOS/EFI implementations.

Loading...