SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Hello,
I was running Slackware 14.1 stable on my desktop then decided to move to "-current" and after moved, I encountered a bug. When shutting down, it will only halt and then the machine freezes and I have to shut it down "manually" (by press the power button for > 5 sec.) but rebooting is fine.
With the kernel 3.10.17 (shipped on the installation disk) it works. But with kernel 4.1.6 (shipped on -current branch), it does not work anymore and find same problem exist on other distributions also with kernel 4.x.x like (Fedora 22, KaOS .... etc) So I guess there's a problem with the Kernel.
Any ideas how to fix?
Quote:
# shutdown -h now
Running shutdown script /etc/rc.d/rc.0:
Saving systems time to the hardware clock (UTC).
Stopping systems message bus...
Unmounting remote filesystems:
Stopping udevd
Sending all processes the SIGKILL signal.
acpid: exiting
Sending all processes the SIGKILL signal.
Saving random seed from /dev/urandom in /etc/random-seed.
Turing off swap.
Unmounting local file susyems:
/dev/shm has been successfully unmounted.
/home has been successfully unmounted.
/ has been successfully unmounted.
Remounting root filesystem read-only:
mount: /dev/sda1 mounted on /.
[ 2016.733526 ] reboot: Power down
_
Quote:
My Desktop Details:
# uname -a
Linux trex-gnu-linux 4.1.6 #1 SMP Fri Aug 21 01:21:18 CDT 2015 x86_64 Intel(R) Core(TM)2 Quad CPU Q6600 @ 2.40GHz GenuineIntel GNU/Linux
# lscpu
Architecture: x86_64
CPU op-mode(s): 32-bit, 64-bit
Byte Order: Little Endian
CPU(s): 4
On-line CPU(s) list: 0-3
Thread(s) per core: 1
Core(s) per socket: 4
Socket(s): 1
Vendor ID: GenuineIntel
CPU family: 6
Model: 15
Model name: Intel(R) Core(TM)2 Quad CPU Q6600 @ 2.40GHz
Stepping: 11
CPU MHz: 2394.000
CPU max MHz: 2394.0000
CPU min MHz: 1596.0000
BogoMIPS: 4800.12
Virtualization: VT-x
L1d cache: 32K
L1i cache: 32K
L2 cache: 4096K
If it returns with version information, read no further.
If it doesn't return, then you've hit a problem in -current which has already been discussed - read a few entries in this thread from here up until patience is recommended in waiting for a new build of procps-ng (which provides fuser). Basically a recompile of procps-ng package was required with a slightly different configuration; that has already happened in -current but probably won't happen in 14.1 (its not normally an issue there). Since you upgraded to the -current kernel in 14.1, you may have to rebuild procps - I'm not actually sure about how differences between procps & procps-ng may affect how this problem manifests in in 14.1 with a kernel from -current - but thats a good place to start testing.
HI Chris, here is output of "fuser -V" on my Slackware -current
Quote:
# fuser -V
fuser (PSmisc) 22.21
Copyright (C) 1993-2010 Werner Almesberger and Craig Small
PSmisc comes with ABSOLUTELY NO WARRANTY.
This is free software, and you are welcome to redistribute it under
the terms of the GNU General Public License.
For more information about these matters, see the files named COPYING.
Same issue with the fresh Slackware current installation on the same desktop. i m not able to fix it yet. i think, kernel 4.x.x is not liking my desktop's hardware.
Last edited by vineetpratap; 10-09-2015 at 01:48 PM.
This problem seem to be ACPI (power management) related. So the relevant options should be in the section "Power" of the BIOS setup and by setting "Wake on LAN" from "Stay Off" to "Power On" seemed to solve the problem.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.