reboot after shutdown Gigabyte GA-P41T-D3 motherboard, Intel G41 Express chipset

[Csipak Attila]

This bug is pretty similar to the one described in #1409279: shutdown from GUI results in shutdown, some seconds of silence, then reboot. Hardware shutdown (holding power button for 4 secs) works OK.

Last kernel update happened on 2015.01.10, but I just started noticing this bug today (2015.01.25), so it may not be a kernel issue.

WORKAROUND: shutdown -H

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: linux-image-3.13.0-44-generic 3.13.0-44.73
ProcVersionSignature: Ubuntu 3.13.0-44.73-generic 3.13.11-ckt12
Uname: Linux 3.13.0-44-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.14.1-0ubuntu3.6
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC2: corphicks 1877 F.... pulseaudio
 /dev/snd/controlC0: corphicks 1877 F.... pulseaudio
 /dev/snd/controlC1: corphicks 1877 F.... pulseaudio
CurrentDesktop: XFCE
Date: Sun Jan 25 22:20:00 2015
HibernationDevice: RESUME=UUID=cf5c04c0-7bdb-41f5-b91c-6c9bb0fdaf90
InstallationDate: Installed on 2014-04-30 (270 days ago)
InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2)
IwConfig:
 eth0 no wireless extensions.

 lo no wireless extensions.
MachineType: Gigabyte Technology Co., Ltd. P41T-D3
ProcFB:

ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-44-generic root=UUID=2e1f47f8-1d20-48a6-9354-5ba871c8bfc8 ro quiet splash
RelatedPackageVersions:
 linux-restricted-modules-3.13.0-44-generic N/A
 linux-backports-modules-3.13.0-44-generic N/A
 linux-firmware 1.127.11
RfKill:

SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/31/2010
dmi.bios.vendor: Award Software International, Inc.
dmi.bios.version: F1
dmi.board.name: P41T-D3
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF1:bd05/31/2010:svnGigabyteTechnologyCo.,Ltd.:pnP41T-D3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnP41T-D3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
dmi.product.name: P41T-D3
dmi.sys.vendor: Gigabyte Technology Co., Ltd.

[Brad Figg (brad-figg)]

This change was made by a bot.

[Csipak Attila (corphicks)]

I was able to reproduce the bug with the following kernel versions:

3.19.0-031900rc5 (latest mainline kernel)
3.13.0-44 (latest stock ubuntu kernel)
3.13.0-43
3.13.0-40
3.13.0-39

[Joseph Salisbury (jsalisbury)]

This issue appears to be an upstream bug, since you tested the latest upstream kernel. Would it be possible for you to open an upstream bug report[0]? That will allow the upstream Developers to examine the issue, and may provide a quicker resolution to the bug.

Please follow the instructions on the wiki page[0]. The first step is to email the appropriate mailing list. If no response is received, then a bug may be opened on bugzilla.kernel.org.

Once this bug is reported upstream, please add the tag: 'kernel-bug-reported-upstream'.

[0] https://wiki.ubuntu.com/Bugs/Upstream/kernel

New Bug:Try Previous Kernel Version:

[Joseph Salisbury (jsalisbury)]

Does selecting the prior kernel version, prior to 2015.01.10, resolve this bug?

[Csipak Attila (corphicks)]

In reply to comment #5, see comment #3 - I successfully reproduced the same bug on 3 earlier kernel versions.

Also, as I stated it in the description, I'm not entirely sure of whether this is a kernel issue or not.

[penalvch (penalvch)]

Csipak Attila, could you please advise on your update history, with emphasis on any updates you performed on 1/25 and 1/24?

[Csipak Attila (corphicks)]

I attached /var/log/apt/history.log which covers January. Some explanation on 2015.01.25-26 entries:

2015-01-25 11:05:48
Bunch of updates, looks like it was initiated by Software Updater. I didn't spot anything closely related to the bug, but then, I'm not really an expert on this...

2015-01-25 22:57:34
This was shortly after I encountered the bug. I googled around, looked at some other existing bug tickets, and found some general advice on how to check BIOS via the fwts tool. Unfortunately, I didn't found any official updates for my motherboard on Gigabyte's website, and also didn't really grok most of fwts's output.

Start-Date: 2015-01-25 23:25:47
I switched from the nvidia to nouveau before trying to install a mainline kernel version.

Start-Date: 2015-01-25 23:50:24
I installed the mainline kernel based on what I read at https://wiki.ubuntu.com/Kernel/MainlineBuilds, this log entry marks the removal.

Start-Date: 2015-01-25 23:52:35
Switching back from nouveau to nvidia.

Start-Date: 2015-01-26 20:04:35
Updates initiated by Software Updater.

Start-Date: 2015-01-26 21:18:42
Switching from nvidia to nouveau. (After which I installed another mainline kernel version via dpkg.)

[penalvch (penalvch)]

Set to Confirmed for now, as it's not clear this is a kernel bug.

[Csipak Attila (corphicks)]

Meanwhile I could reproduce the bug on mainline kernel version 3.19-rc6.

Also I noticed that shutdown -H (halt) does work, only shutdown -P (power off) is malfunctioning.

[Csipak Attila (corphicks)]

Since we are not sure if this is a kernel issue, I added upstart to the affected projects.

If someone from the upstart maintainers is able to cross out upstart as the source of the bug, then I will open an upstream bug report against the latest kernel.

To penalvch: halting instead of poweroff is not really a workaround IMHO. (Maybe you meant shutdown -H, then power off via power button?)

[Csipak Attila (corphicks)]

Looks like today's ubuntu updates fixed the bug, which is strange. The /var/log/apt/history.log entry produced by the update is:

Start-Date: 2015-02-03 22:51:31
Commandline: aptdaemon role='role-commit-packages' sender=':1.136'
Install: linux-image-extra-3.13.0-45-generic:amd64 (3.13.0-45.74), linux-image-3.13.0-45-generic:amd64 (3.13.0-45.74), linux-headers-3.13.0-45-generic:amd64 (3.13.0-45.74), linux-headers-3.13.0-45:amd64 (3.13.0-45.74)
Upgrade: linux-headers-generic:amd64 (3.13.0.44.51, 3.13.0.45.52), python3-software-properties:amd64 (0.92.37.2, 0.92.37.3), unzip:amd64 (6.0-9ubuntu1.1, 6.0-9ubuntu1.2), software-properties-common:amd64 (0.92.37.2, 0.92.37.3), linux-libc-dev:amd64 (3.13.0-44.73, 3.13.0-45.74), software-properties-gtk:amd64 (0.92.37.2, 0.92.37.3), linux-image-generic:amd64 (3.13.0.44.51, 3.13.0.45.52), linux-generic:amd64 (3.13.0.44.51, 3.13.0.45.52)
End-Date: 2015-02-03 22:53:23

At first glance, I thought that the 3.13.0-45 kernel version fixed it. But then I rebooted into kernel version 3.13.0-44, and couldn't reproduce the original bug, neither. What caused the bug and what solved it?