Unexpected shutdown

[Sam_]

This happens twice in between a short time, 2-5 minutes, after the computer was turned on and Ubuntu desktop has started.
It never happens a third time.
From Ubuntu desktop, the cooler starts to run, a shutdown dialog with four options appears and computer turns off.
I turn it on again and watch the same procedure happen again.
I turn it on the third time, all is fine.

4.4.0-47.68
ACPI: Thermal Zone [TZ0] (11 C)

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-47-generic 4.4.0-47.68 and 4.4.0-49.70
ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24
Uname: Linux 4.4.0-47-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: zootie 1897 F.... pulseaudio
CurrentDesktop: Unity
Date: Sun Nov 20 17:19:01 2016
HibernationDevice: RESUME=UUID=6a848b08-24f4-499b-8281-8ba10097226d
InstallationDate: Installed on 2016-11-02 (18 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Beta amd64 (20160823)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 004: ID 046d:c52f Logitech, Inc. Unifying Receiver
 Bus 001 Device 003: ID 8087:0a2a Intel Corp.
 Bus 001 Device 002: ID 5986:055c Acer, Inc
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Notebook W65_W67RB
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-47-generic root=UUID=31f6cc2f-d9df-473c-be2d-fd1abf719500 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-4.4.0-47-generic N/A
 linux-backports-modules-4.4.0-47-generic N/A
 linux-firmware 1.157.5
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/16/2015
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 5.11
dmi.board.asset.tag: Tag 12345
dmi.board.name: W65_W67RB
dmi.board.vendor: Notebook
dmi.board.version: Not Applicable
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Notebook
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5.11:bd10/16/2015:svnNotebook:pnW65_W67RB:pvrNotApplicable:rvnNotebook:rnW65_W67RB:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:
dmi.product.name: W65_W67RB
dmi.product.version: Not Applicable
dmi.sys.vendor: Notebook

[Brad Figg (brad-figg)]

This change was made by a bot.

[Joseph Salisbury (jsalisbury)]

Can you reproduce this bug?

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.9 kernel[0].

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.9-rc6

[Sam_ (and-sam)]

Tested. 16 minutes uptime, no fan, no shutdown.
uname -a
Linux zoo 4.9.0-040900rc6-generic #201611201731 SMP Sun Nov 20 22:33:21 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux

[Sam_ (and-sam)]

This is kern.log from
Linux version 4.4.0-49-generic (buildd@lgw01-55) (gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.4) ) #70-Ubuntu SMP Fri Nov 11 16:40:34 UTC 2016 (Ubuntu 4.4.0-49.70-generic 4.4.30)
where Computer shuts down again
and with
Nov 27 16:34:58 zoo kernel: [ 0.000000] Command line: BOOT_IMAGE=/boot/vmlinuz-4.9.0-040900rc6-generic root=UUID=31f6cc2f-d9df-473c-be2d-fd1abf719500 ro
still running.

[Sam_ (and-sam)]

Same problem with recently updated
linux-generic 4.4.0.52.55
linux-image-4.4.0-52-generic 4.4.0-52.73

[Sam_ (and-sam)]

Still no luck with recent updated
Linux version 4.4.0-53-generic (buildd@lcy01-28) (gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.4))

[Sam_ (and-sam)]

dito linux-image-4.4.0-57-generic 4.4.0-57.78

[penalvch (penalvch)]

Sam_, to see if this is already resolved in Ubuntu, could you please test http://cdimage.ubuntu.com/daily-live/current/ and advise to the results?

[Sam_ (and-sam)]

Tested Zesty daily and the fan started immediately after boot. When I do nothing the system shuts down shortly after it enters the desktop.

But I found out following: I can reproduce it with Zesty daily and Xenial 4.4.0-57.78 kernel.
The fan is on after boot. As soon as I enter the Desktop, I press FN+F12 which puts the system in sleep mode and the fan stops.
(In German the manual translates it with "toggle energy savings mode", in English it says "sleep toggle".)
After a waiting moment I press the power button, it enters the desktop (in Xenial after login) and the fan doesn't start again, System works fine.

Obviously kernel 4.9.0-040900rc6 does not trigger this. After a cold start it proceeds without ever running the fan and shutdown.

[penalvch (penalvch)]

Sam_, to help narrow this down, the Zesty kernel was rebased against 4.9. Hence, if you test 4.9 in your current install is the issue still fixed?

[Sam_ (and-sam)]

When I boot with kernel 4.9.0-040900rc6 there is no issue. It's the only one I can boot and the system doesn't start the fan and shuts down after short time.

[penalvch (penalvch)]

Sam_, to clarify, you did, or did not test Zesty within the last day?

[Sam_ (and-sam)]

Yes, I did test Zesty, within the last day. I've downloaded the daily as advised.

[penalvch (penalvch)]

Sam_, to confirm if there was an upstream regression, could you please test 4.9 via http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.9/ and advise to the results?

[Sam_ (and-sam)]

Kernel v4.9 was perfectly working, no fan, no shut down.

[penalvch (penalvch)]

Sam_, to clarify, is the shutdown due to the computer overheating?

To observe internal temperatures, one may utilize https://help.ubuntu.com/community/SensorInstallHowto .

If high internal temperature is the symptom, would a WORKAROUND be provided via https://help.ubuntu.com/community/PowerManagement/ReducedPower ?

[Sam_ (and-sam)]

No, it's not overheated, I have conky running in autostart which shows me the output of sensors and cpu's, mainboard are between 32-48°.

I've searched my uploaded kernel logfiles and found following:

4.4.0-57.78
ACPI: Thermal Zone [TZ0] (46 C)

4.9.0-040900rc6
ACPI: Thermal Zone [TZ0] (11 C)

4.9.0-040900
ACPI: Thermal Zone [TZ0] (43 C)

[Sam_ (and-sam)]

Still the same with 4.4.0-59.80 - after 1½ minutes the fan starts, temperature moves from 42 to 24° then appears shutdown dialog and computer turns off.
I need to run mainline kernel otherwise I wouldn't be able to proceed updates. Mainline kernels make no trouble at all.
From kern.log
4.9.0-040900rc6 ACPI: Thermal Zone [TZ0] (35 C)
4.4.0-59.80 ACPI: Thermal Zone [TZ0] (40 C)
4.9.0-040900 ACPI: Thermal Zone [TZ0] (11 C)

[Sam_ (and-sam)]

With 4.4.0-62.83 it took about 15-20 minutes till it triggered the fan and shut down.
4.9.0-040900rc6 ACPI: Thermal Zone [TZ0] (11 C)
4.4.0-62.83 ACPI: Thermal Zone [TZ0] (50 C)
4.9.0-040900rc6 ACPI: Thermal Zone [TZ0] (42 C)

[Sam_ (and-sam)]

Since 30 minutes now running hwe-stack, without a fan starting and unexpected shutdown. Yeah!
Linux 4.8.0-36-generic #36~16.04.1-Ubuntu SMP Sun Feb 5 09:39:57 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
I'll watch it a while and if it stays this way would say hwe-stack fixed it.

[penalvch (penalvch)]

Sam_, this bug report is being closed due to your last comment https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1643341/comments/21 regarding this being fixed with an update. For future reference you can manage the status of your own bugs by clicking on the current status in the yellow line and then choosing a new status in the revealed drop down box. You can learn more about bug statuses at https://wiki.ubuntu.com/Bugs/Status. Thank you again for taking the time to report this bug and helping to make Ubuntu better. Please submit any future bugs you may find.

[Sam_ (and-sam)]

Christopher, I'm aware on how to change the status, as said, I'd wanted to test 4.8 again to make sure it wasn't a coincidence. Finally also the updated hwe-stack of 4.8 works as expected. Thanks for your work. This bug was never invalid, 4.4 was always an issue which 4.8-hwe fixed.