[GIGABYTE GA-H77-D3H] When computer is ordered to shutdown it switches off and after several seconds starts again

[Selmi]

tested with
 - shutdown from Gnome
 - gnome-session-quit --power-off --force from terminal (with sudo)
 - shutdown -h now from terminal (with sudo)
 - shutdown -P now from terminal (with sudo)
 - poweroff from terminal (with sudo)

result is always the same. session closes, there are messages about switching off, screen goes black, all disks and fans switch off. the after 2-5 seconds computer starts again and boots into linux

this doesn't happen with windows 7 (i have dualboot system)

WORKAROUND: i installed linux-backports-modules-cw package for this and added alx into /etc/modules

i was just experimenting and before shutdown did 'sudo rmmod alx'. now computer after shutdown stays switched off. i hope it wasn't only accident, so far it seems to be reliable.

--
ProblemType: Bug
DistroRelease: Ubuntu 12.10
Package: linux-image-3.5.0-23-generic 3.5.0-23.35
ProcVersionSignature: Ubuntu 3.5.0-23.35-generic 3.5.7.2
Uname: Linux 3.5.0-23-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.6.1-0ubuntu10
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: selmi3 2165 F.... pulseaudio
 /dev/snd/controlC0: selmi3 2165 F.... pulseaudio
CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found.
Date: Sun Feb 10 23:18:21 2013
HibernationDevice: RESUME=UUID=cc63da1b-8661-464f-bd6a-0886318c13a3
InstallationDate: Installed on 2013-02-03 (7 days ago)
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
IwConfig:
 eth0 no wireless extensions.

 eth1 no wireless extensions.

 lo no wireless extensions.
MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
MarkForUpload: True
ProcFB:

ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-23-generic root=UUID=a041b2f5-45d4-4741-92e5-af5154358862 ro quiet splash
RelatedPackageVersions:
 linux-restricted-modules-3.5.0-23-generic N/A
 linux-backports-modules-3.5.0-23-generic N/A
 linux-firmware 1.95
RfKill:

SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/09/2012
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: F10
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: H77-D3H
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF10:bd08/09/2012:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnH77-D3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.name: To be filled by O.E.M.
dmi.product.version: To be filled by O.E.M.
dmi.sys.vendor: Gigabyte Technology Co., Ltd.

[Brad Figg (brad-figg)]

This change was made by a bot.

[Joseph Salisbury (jsalisbury)]

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.8 kernel[0] (Not a kernel in the daily directory) and install both the linux-image and linux-image-extra .deb packages.

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'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-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/v3.8-rc7-raring/

[Selmi (selmi)]

confirming bug with upstream kernel, its even the worse

with upstream not only computer starts again after shutdown, but it does it immediately and in addition in gets stuck on black screen with blinking cursor (before grub appears). only when i manually press reset button (and recover from small heart-attack) and let computer go through boot again grub appears

[Selmi (selmi)]

I tried to update BIOS to latest version (just in case), unfortunately it didn't made any difference

[Selmi (selmi)]

accidentaly i found possible solution

i have alx module inserted after every boot to make my network adapter work. (Atheros). i installed linux-backports-modules-cw package for this and added alx into /etc/modules

i was just experimenting and before shutdown did 'sudo rmmod alx'. now computer after shutdown stays switched off. i hope it wasn't only accident, so far it seems to be reliable

[Selmi (selmi)]

sorry for delay
i will test with newer bios tomorrow
so far i found that if iunload alx module before shutdown then everything works as expected. (i need alx module otherwise i have no networking)

[Selmi (selmi)]

i already had BIOS in latest version (see my comment #8 from 2013-03-18)

output of sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date
is
F11
08/21/2012

what happened is exactly what happened inmy original bug description, on shutdown computer switches off and after some time (several seconds) starts again. however i think that after bios upgrade it stays switched off a bit longer. but it might be just coincidence

if i remove alx module before shutdown then computer switches off and stays switched off
i am changing status back to confirmed, i hope it is ok

[penalvch (penalvch)]

Selmi, could you please confirm this issue exists with the latest development release of Ubuntu? ISO images are available from http://cdimage.ubuntu.com/daily-live/current/ . If the issue remains, please make a comment to this.

Also, could you please test the latest upstream kernel available following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Please do not test the daily kernel folder, but the one all the way at the bottom. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this bug is fixed in the mainline kernel, please add the following tags:
kernel-fixed-upstream
kernel-fixed-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested. For example:
kernel-fixed-upstream-v3.12-rc1

This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description. As well, please remove the tag:
needs-upstream-testing

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-VERSION-NUMBER

As well, please remove the tag:
needs-upstream-testing

Once testing of the upstream kernel is complete, please mark this bug's Status as Confirmed. Please let us know your results. Thank you for your understanding.

[Selmi (selmi)]

I didn't tested with latest development release of Ubuntu

But I tested with upstream kernels and found out that issue is fixed with v3.11.2-saucy/, but not fixed with v3.10.13-saucy/. I didn't checked versions between, I hope it is not neccessary

[Selmi (selmi)]

there is quite a lot of changes in alx module in http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.11-rc1-saucy/CHANGES
probably some of them fixed the problem i was experiencing

[penalvch (penalvch)]

Selmi, could you please confirm this issue exists with the latest development release of Ubuntu? ISO images are available from http://cdimage.ubuntu.com/daily-live/current/ . If the issue remains, could you please run the following command in the development release from a Terminal (Applications->Accessories->Terminal), as it will automatically gather and attach updated debug information to this report:

apport-collect -p linux <replace-with-bug-number>

[Selmi (selmi)]

tested with development release of Ubuntu 13.10 amd64 version
issue seems to be fixed there, so far every shutdown worked as expected

[penalvch (penalvch)]

Selmi, would you need a backport to a release prior to Saucy, or may we close this as Status Invalid?

[Selmi (selmi)]

you can close it, i will upgrade all my computers when final version will be out

[penalvch (penalvch)]

Selmi, this bug report is being closed due to your last comment https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1121489/comments/19 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.