Hi, I just bought a new Dell XPS 9315 and am experiencing some issues. One of which is that I cannot halt or reboot the computer.
I get a message in the console after the halt signal:
“Watchdog did not stop!”
“Waiting for process: 341 (systemd-udev)”
I have to long-press the power button to shut the machine down.
This is my hardware info:
P.S. Other problems are:
Sound only works with headphones
Draining batter when shutting the lid (no sleep?)
I suggest to check out the systemd article in the arch wiki and troubleshoot. There is a process still running that avoids your system to shut down. You need to figure out which one.
Please avoid this, as it can corrupt a file system, and read
The Linux kernel authors have provided a very nice feature of issuing low-level commands to the kernel directly, regardless of the state the system is in. This is called the “Magic SysRq Key”, because these commands are issued by pressing the SysRq key on the keyboard (if you can’t find it, typically, it shares the same physical key as the Print Screen key, but on some laptops it can be elsewhere).
A common use is to reboot when the computer freezes and becomes unresponsive due to some software…
That could be a bios setting that needs to be changed to allow for deep sleep 3.
Some vendors stopped allowing this by restricting bios config, hopefully that is not the case. I had that recently with Lenovo yoga slim 7.
I was wondering, how do you deal with the deep sleep issue in bios?
Windows has apparently managed to introduce a new suspend mode similar to what happens on cellphones, meaning the computer drains more battery than conventual suspend (aka deep sleep S3) so it can retrieve emails and other things like that while in sleep/suspend mode.
What that means for Linux, that the computer drains battery while on sus…
Something about the soundcard driver here.
12:57PM - 09 Aug 22 UTC
On the Dell XPS 13 9315 with Debian sid/unstable and Linux 5.19 from the suite *
… experimental*, very often no soundcards are found.
00:1f.3 Multimedia audio controller : Intel Corporation Device [8086:51cc] (rev 01)
[Output of `/usr/sbin/alsa-info`](https://alsa-project.org/db/?f=debacf544a4340e3f6013a102a235acfe777ca73)
[ 14.611798] soundwire sdw:2:025d:1316:01: Probe not complete, timed out
[ 14.611813] soundwire sdw:2:025d:1316:01: Update Slave status failed:-110
[ 14.611853] soundwire sdw:3:025d:0714:01: Probe not complete, timed out
[ 14.611855] soundwire sdw:3:025d:0714:01: Update Slave status failed:-110
As reported in issue https://github.com/thesofproject/linux/issues/3777 unloading the module `snd_sof_pci_intel_tgl` and loading it again works around the issue.
October 10, 2022, 7:17am
This is a natural behavior, sometimes the shutdown lasts for a certain period of time, usually no more than two minutes. The long press of the shutdown button should only be used as a last resort, as it may cause the file system to crash. During the shutdown process, in the virtual terminal, according to my memories, the remaining time until shutdown was visible. Check this out.
The watchdog seems to be waiting on some device to disconnect (systemd-udev). If I don’t intervene, the computer is stuck till the battery drains.
October 10, 2022, 8:40am
You could try disabling watchdog:
You might also need to blacklist its modules thus preventing it from loading:
October 10, 2022, 4:46pm
I have EOS running on several laptops, and I have never had to wait more than two minutes on any of them before it completely shuts down.
Isn’t this an issue for the EndeavourOS developers to troubleshoot? I have little idea what it all means.
No it’s not… The EOS devs provide this distro and support to run and install it for free. They don’t provide hardware support (in the sense that they cant change code to make each hardware work). Either the drivers are implemented in the Linux Kernel, or if proprietary, some drivers are provided in the AUR, and others need some special settings. Other problems like the sleep mode in bios is a stupidity that was driven by windows and is up to the laptop vendors to implement or not. We can’t really change code in their bios.
In most cases, as Linux user we need to do some homework before purchasing hardware as not every drivers are available. Else fixes might be needed. I know it is annoying but I guess the little sacrifice to pay to get awesome open source operating system and software for free.