OptiPlex 9020 and Wake-on-LAN: reboot instead of a shutdown

Bug #1236420 reported by Michael Korn on 2013-10-07
24
This bug affects 4 people
Affects Status Importance Assigned to Milestone
linux-lts-raring (Ubuntu)
Medium
Unassigned

Bug Description

We have several OptiPlex 9020 (with i7-4770) from Dell and we don't have any problems without WOL.
After activating WOL and disabling "Deep Sleep" in BIOS it is not possible to shutdown the machines with Ubuntu. It's still possible to shutdown with Windows 7 (and WOL is working).

- On shutdown (from the GUI OR poweroff OR halt) Ubuntu shutdowns and the computer is off for about 4 seconds, then it restarts (a normal restart is much faster)
- After this: If the computer is switched off with the power button during the bootmenu or before: the computer will reboot again like before
- After this: If the computer is switched off with the power button during the bootmenu or before a SECOND time: the computer stay off, but WOL don't work (The LED of the network card is on.)
- If the power button is pressed a few seconds during the login screen of ubuntu (or later) to switch of the computer immediately: the computer doesn't restart (In detail: the computer starts for two seconds again and goes out, but I thinks it's normal for dell computer) and WOL works.

We have tested:
- Ubuntu 14.04
- Ubuntu 12.04 with all Updates (including backports)
- Ubuntu 12.04 Live CD
- Ubuntu 13.04 Live CD
- Ubuntu 13.10 Live CD

We tried to boot with acpi=noirq and disabling of WOL with ethtools (The network cards are in 'g' mode by default.), too.
Unplugging the Ethernet cable don't help, too.

What works:
- use "halt -f"
- power off by pressing the power button a few seconds
After this the computer can be started (power button or WOL) and switched off (again and again)
But the issue re-appears if:
- Windows is booted
- BIOS is entered
- Computer is reboot from Ubuntu (poweroff and start again by power button or WOK is OK!)

WORKAROUND: sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date:
I02
01/13/2014

We got this BIOS Version from Dell, it isn't official. But it works better than any other Version, including A05. With a kernel modification and I02 everything is fine (see https://bugzilla.kernel.org/show_bug.cgi?id=66171#c65).

---
AlsaVersion: Advanced Linux Sound Architecture Driver Version k3.8.0-31-generic.
ApportVersion: 2.0.1-0ubuntu17.5
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: lightdm 1954 F.... pulseaudio
 /dev/snd/controlC0: lightdm 1954 F.... pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'MID'/'HDA Intel MID at 0xf7c34000 irq 49'
   Mixer name : 'Intel Haswell HDMI'
   Components : 'HDA:80862807,80860101,00100000'
   Controls : 14
   Simple ctrls : 2
Card1.Amixer.info:
 Card hw:1 'PCH'/'HDA Intel PCH at 0xf7c30000 irq 50'
   Mixer name : 'Realtek ALC280'
   Components : 'HDA:10ec0280,102805a4,00100003'
   Controls : 28
   Simple ctrls : 13
DistroRelease: Ubuntu 12.04
HibernationDevice: RESUME=UUID=ca091e57-337c-4b30-8168-8718472aaab2
InstallationMedia: Ubuntu 12.04.3 LTS "Precise Pangolin" - Release amd64 (20130820.1)
IwConfig:
 eth0 no wireless extensions.

 lo no wireless extensions.
MachineType: Dell Inc. OptiPlex 9020
MarkForUpload: True
Package: linux (not installed)
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 LC_MESSAGES=en_US.UTF-8
 SHELL=/bin/bash
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-31-generic root=UUID=f5ed194c-eb35-4d22-a9fc-faed6eede85d ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 3.8.0-31.46~precise1-generic 3.8.13.8
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
 linux-restricted-modules-3.8.0-31-generic N/A
 linux-backports-modules-3.8.0-31-generic N/A
 linux-firmware 1.79.6
RfKill:

Tags: precise
Uname: Linux 3.8.0-31-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

dmi.bios.date: 08/15/2013
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A02
dmi.board.name: 0PC5F7
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 6
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.:bvrA02:bd08/15/2013:svnDellInc.:pnOptiPlex9020:pvr01:rvnDellInc.:rn0PC5F7:rvrA00:cvnDellInc.:ct6:cvr:
dmi.product.name: OptiPlex 9020
dmi.product.version: 01
dmi.sys.vendor: Dell Inc.

Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage. You might also ask for help in the #ubuntu-bugs irc channel on Freenode.

To change the source package that this bug is filed about visit https://bugs.launchpad.net/ubuntu/+bug/1236420/+editstatus and add the package name in the text box next to the word Package.

[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]

tags: added: bot-comment
Michael Korn (w-michael) on 2013-10-08
description: updated
Michael Korn (w-michael) on 2013-10-08
description: updated
Michael Korn (w-michael) on 2013-10-08
affects: ubuntu → linux (Ubuntu)

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 1236420

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

Changed in linux (Ubuntu):
status: New → Incomplete

apport information

tags: added: apport-collected precise
description: updated

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Joseph Salisbury (jsalisbury) wrote :

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.12 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'.

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.12-rc4-saucy/

Changed in linux (Ubuntu):
importance: Undecided → Medium
status: Confirmed → Incomplete
tags: added: kernel-da-key
Michael Korn (w-michael) on 2013-10-08
tags: added: kernel-bug-exists-upstream
Michael Korn (w-michael) on 2013-10-09
Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Joseph Salisbury (jsalisbury) wrote :

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

Changed in linux (Ubuntu):
status: Confirmed → Triaged
tags: added: bios-outdated-a03

Michael Korn, as per http://www.dell.com/support/drivers/us/en/19/Product/optiplex-9020-desktop an update is available for your BIOS (A03). If you update to this following https://help.ubuntu.com/community/BiosUpdate , does it change anything?

If not, could you please both specify what happened, and provide the output of the following terminal command:
sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date

Please note your current BIOS is already in the Bug Description, so posting this on the old BIOS would not be helpful.

For more on BIOS updates and linux, please see https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette .

Thank you for your understanding.

Changed in linux (Ubuntu):
status: Triaged → Incomplete
Michael Korn (w-michael) wrote :

We tested BIOS version A03 and we didn't found any differences regarding Ubuntu. If WOL is on we still can not shutdown.

But we have observed a change if we use Windows 7: The network card is disabled during shutdown. We tried several BIOS and Windows configurations, but with the new BIOS version we can not use WOL any longer.

Obviously, this is not or not only a Ubuntu problem. We already contacted the dell support.

Launchpad Janitor (janitor) wrote :

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]

Changed in linux (Ubuntu):
status: Incomplete → Expired
Michael Korn (w-michael) wrote :

Just to complete this issue:
The Bug was fixed with Kernel 3.8.0-34.49~precise1: xhci: Fix spurious wakeups after S5 on Haswell
But it reoccurs since Kernel 3.8.0-37.53~precise1: xhci: Limit the spurious wakeup fix only to HP machines

tags: added: bios-outdated-a05
removed: bios-outdated-a03
affects: linux (Ubuntu) → linux-lts-raring (Ubuntu)
Changed in linux-lts-raring (Ubuntu):
status: Expired → New
Michael Korn (w-michael) on 2014-03-14
tags: removed: bios-outdated-a05
Michael Korn (w-michael) wrote :

We tested the newest BIOS Version already:
- wol and shutdown is working again with Windows
- wol and shutdown is working with Ubuntu 12.04, if we use 3.8.0-34.49~precise1, 3.8.0-34.50~precise1, 3.8.0-34.51~precise1 or 3.8.0-34.52~precise1

Michael Korn (w-michael) wrote :

Sorry, small correction:
- wol and shutdown is working with Ubuntu 12.04, if we use 3.8.0-34.49~precise1, 3.8.0-35.52~precise1 or 3.8.0-36.52~precise1

Michael Korn, could you please post the results of the following terminal command:
sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date

Michael Korn (w-michael) wrote :

sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date:
I02
01/13/2014

We got this BIOS Version from Dell, it isn't official. But it works better than any other Version, including A05.
With a kernel modification and I02 everything is fine (see https://bugzilla.kernel.org/show_bug.cgi?id=66171#c65).

description: updated
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in linux-lts-raring (Ubuntu):
status: New → Confirmed
Michael Korn (w-michael) on 2014-04-29
description: updated
Michael Korn (w-michael) wrote :

There exists a kernel fix: https://github.com/torvalds/linux/commit/c09ec25d3684cad74d851c0f028a495999591279

Due to kernel 3.13(Ubuntu 14.04) is EOF I suppose the Ubuntu community muss backport this fix.

Michael Korn, did you personally test that patch on your machine and verify it to work?

As well, I'm not sure what you mean by "Due to kernel 3.13(Ubuntu 14.04) is EOF" but neither kernel series 3.13.x or Ubuntu 14.04 is EoL (End of Life) as outlined in:
http://lkml.iu.edu/hypermail/linux/kernel/1404.2/05016.html
https://wiki.ubuntu.com/Releases

Changed in linux-lts-raring (Ubuntu):
status: Confirmed → Incomplete
Michael Korn (w-michael) wrote :

Yes, I compiled the kernel myself and I personally tested that patch.

Kernel 3.13.x is EOL (www.kernel.org), but it is forked by the Ubuntu Kernel Team.
I don't know if that patch will be applied by the Ubuntu Kernel Team. I hope so, because it would solve this issue.

tags: added: cherry-pick
Changed in linux-lts-raring (Ubuntu):
status: Incomplete → Triaged
tags: added: saucy
Michael Korn (w-michael) on 2014-05-30
tags: added: trusty
madbiologist (me-again) wrote :

The abovementioned patch has a side effect of causing the same issue on other hardware that didn't have the issue before. A modified patch will be in the 3.16 kernel - see https://<email address hidden>/msg42829.html

Michael Korn (w-michael) wrote :

The patch was backported to 3.13.0-32. The problem is fixed for my system with Ubuntu 14.04!
But I'm not sure if this bug report can be closed, because this problem still exists, depending on the hardware.

@madbiologist: THX, but many to this problem related patches had side effects. I discovered this problem nearly a year ago and I wasted a lot of time. There was a fix, but this patch had side effects and the new fix caused the old problems on my system. In my eyes this is a fix for a fix for a fix.

Michael Korn, this bug report is being closed due to your last comment https://bugs.launchpad.net/ubuntu/+source/linux-lts-raring/+bug/1236420/comments/37 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.

Changed in linux-lts-raring (Ubuntu):
status: Triaged → Invalid
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.