#WAKEONLAN DELL OPTIPLEX 9020 UBUNTU INSTALL#
#WAKEONLAN DELL OPTIPLEX 9020 UBUNTU PATCH#
#WAKEONLAN DELL OPTIPLEX 9020 UBUNTU WINDOWS#

> Haswell LynxPoint and LynxPoint-LP with the recent Intel BIOS show (In reply to Giorgos aka shad0w from comment #6) The thing is I really can't say if it ever worked because I don't have this laptop for long enough and there really is little reason to power off a laptop, I tend to reboot for updates and suspend when I don't use it so, at least this issue is only mildly annoying but I'd still like to see it fixed as it is I need to do 'systemctl halt' and then press the power button if I want to shut down properly and safely.

As I said it is clearly related to this issue though possibly more kernel commits are involved but bisecting is very hard because I'd have to test every bisect about 10 times because it tends to work quite a couple of times in a row. Also I can't really see the point with your suggestions for finding the issue. I think the fast that /sys/firmware/acpi/pm_profile is not writeable is also supposed to be like that, I was merely pointing out that I don't know which /sys file is used to turn off PM. It shuts completely off and only after about 3 seconds it turns itself back on. Also note that these are not normal reboots, Why exactly do you think there are non kernel related issues? My system works great except for the power off issue.

#WAKEONLAN DELL OPTIPLEX 9020 UBUNTU INSTALL#

Then poweroff machine under text console with command: sudo shutdown -h now Ģ, Test with other distro LiveCD with kernel 3.11 or before ģ, Install a fresh Linux only with command line, no X Ĥ, Remove all power managment components, such as: acpid, pm-utils, cpufreq-utils, etc. I suppose except for this bug #66171, you have some kernel unrelated issue too.ġ, Test kernel 3.11 or before, don't start the GUI desktop(like gnome, kde, xfce, etc.), this can be done by forbid GUI login service(e.g., sudo chmod -x /etc/init.d/gdm3).

#WAKEONLAN DELL OPTIPLEX 9020 UBUNTU PATCH#

> kernels without the patch I consistently get 100% reboots. > somewhat 50% correct shutdowns while with the HP quirk, that is newer with older kernels or witch the patch from comment 16 I get I still think it's related with this issue though, because without > Ok, I will open a new bug report as soon as I've got a little more time on

(In reply to Niklas Schnelle from comment #45) I don't distinguish very clearly between shutdown with xhci_hcd loaded and unloaded. > (And we know that it's not a rare case that people don't read the context > quirk won't be needed urgently because unloading xhci_hcd doesn't happen > quirk this is another BIOS bug, after all. > For fixing the shutdown hang after module unload, we'd need yet another > The rare case mentioned there is that the system goes shutdown after Then, the common user will get a unnormal system.

#WAKEONLAN DELL OPTIPLEX 9020 UBUNTU WINDOWS#

> asrock motherboard, they support Windows officially, so Linux user is a > now.', if both Linux kernel and Asrock think this is a rare case(for this > As Takashi Iwai said: 'this should be a rare case, so we may ignore for

> (In reply to littlebat from comment #20) (In reply to Takashi Iwai from comment #22) This patch should be backported to kernels as old as 3.0, thatĬontain the commit 1c12443ab8eba71a658fae4572147e56d1f84f66 'xhci: Add Same time, by changing the xhci->quirks bit from 17 to 18.] Sarah also fixed a collision with a quirk submitted around the XHCI_SPURIOUS_WAKEUP, since none of the other quirks have system names [Note: Sarah changed the quirk name from XHCI_HSW_SPURIOUS_WAKEUP to The PCI D3 call is based on the initial fix patch by Oliver Neukum. Shutdown ops as done in xhci_stop(), and setting the device to PCI D3 This patch introduces a new quirk, XHCI_SPURIOUS_WAKEUP, forįixing the spurious wakeups at S5 by calling xhci_reset() in the xhci The system is going to sleep or power off, but the current xhci driverĭoesn't do this properly (partly intentionally). Wakeup sources are cleared and set to D3 for all wakeup devices when After discussing withīIOS engineers, they explained that the new BIOS expects that the Mysterious wakeups after shutdown occasionally. Haswell LynxPoint and LynxPoint-LP with the recent Intel BIOS show Xhci: Fix spurious wakeups after S5 on Haswell Patch fixing spurious wakeup and spurious reboot problems (at least for our HP machines but should work for other vendors).Īdd Signed-off-by: line to the previous patchĦ38298dc66ea36623dbc2757a24fc2c4ab41b016 is the first bad commitĬommit 638298dc66ea36623dbc2757a24fc2c4ab41b016 XHCI_SPURIOUS_WAKEUP for Panther Point devices from Asus & Lenovo XHCI_SPURIOUS_WAKEUP for Panther Point devices from Lenovo

Wakeonlan dell optiplex 9020 ubuntu