You are not logged in.
Pages: 1
Hello,
since some days I have a problem with a simple "sudo halt". If my PC is powered off for some hours and I then power it on it does not "halt" properly. If I do a "sudo halt" it first shuts down completely (no standby light is blinking, fans are all off), but after about 5 seconds it just goes on again.
So the machine reboots and a second "sudo halt" then finally shuts the pc down completely.
I have made some observations:
- it doesn't matter how long the PC is on (some hours or just one minute) - the first halt after a longer period of being powered off fails
- I first had this issue with kernel 3.1 (self configured one), I will test the official arch kernel probably tomorrow
- I have not changed my hardware nor done a bios update (there is none available, too) since about 2 years
Does anybody have a clue what's going on here?
Greetings
matse
Last edited by matse (2011-11-05 14:48:33)
Offline
Same problem here with a Sony VAIO notebook. I already suspected a hardware defect, but as I know read your post, I'll try downgrading kernels.
Can you post some details about your hardware and maybe your kernel config, please?
Greetings,
lynix
Offline
So today I tried the official arch kernel (3.0.7) in combination with the kernel parameter "acpi=noirq" without luck. The "halt" result was again a rebooting computer. My main hardware components are:
- Asus rampage formula (x48 chipset)
- ATI graphics card (4870x2) with fglrx driver in use
Any suggestions?
Greetings,
matse
Offline
Sounds similar, but not the same as I problem I had with double resume. The cause and solution may be similar.
Offline
Hi David,
I really can't imagine how your problem should have something to do with mine... since I don't shutdown my PC with hotkeys nor do I want a "suspend feature".
matse
Offline
Similar problem here with my desktop.I shutdown it and after 1-2min it boots again.
I have this problem (maybe) after the installation of udev (i've got messages during the shutdown**).
After this i can shutdown my pc properly without any problems or messages.
**
/sbin/blkid -o udev -p /dev/sdb1 terminated by signal 15
where /dev/sdb1 is my swap.
Last edited by thanos (2011-11-07 12:17:54)
Offline
I have exactly the same problem on my desktop, system boots again after 5-10 seconds, it isn't an immediate reboot.
Offline
So today I tested kernel 3.0.4 (which worked fine for weeks) with the same result. So I guess it's no kernel regression. I guess it's time to downgrade udev then to test it... But this has to wait for some days, I have no time for experiments like this these days. Thanos, maybe you could give this a try?
Greetings
matse
Last edited by matse (2011-11-07 10:30:39)
Offline
Downgrading to udev 173-3 (with the dependencies) seems that problem have gone.I still get the previous message but my system's shutdown works properly.
Offline
Hi David,
I really can't imagine how your problem should have something to do with mine... since I don't shutdown my PC with hotkeys nor do I want a "suspend feature".
matse
Ok. Well the point really was that suspend was being called twice by two different methods in my case. I had to disable one of the methods. You may be having a similar issue when you click on shutdown.
It also seems to me your computer is not really shutting down completely if it restarts by itself.
Anyway, I'm out of here. Hope you find the answer.
Offline
For me downgrading udev to 173-3 did not solve the problem. I have really no idea what to check next.
@David: I got your point, but since I don't use a hotkey, shortcut or anything like this (yes, I manually type "sudo halt") I guess our problems are not connected in any way. If you understood me wrong: I did not want to insult you, it's just simply that I believe your problem has nothing to do with mine (maybe I'm wrong...).
So any suggestions?
Greetings
matse
Offline
Small update:
Today morning I booted directly from a Knoppix (6.7) live CD and the shutdown afterwards worked fine. So I guess it's no hardware issue. Pretty weirt...
matse
Offline
I have the same problem with my hardware (Vostro 3500).
It halts, leds aren't shining so it seems that the shutdown succeded. It randomly powers up after a random number of minutes. (I only checked with AC adapter plugged in)
Sometimes it's a matter of a few minutes, and once, I was off to another city and I left it at home. I came back home to find my laptop powered up. It was up for 12hrs and I was off more than 48hrs.
I'm using self-packaged linux-ck: 3.1.0-1-ck.
I also have 3.0.6 installed and I yet have to check if it occurs on this kernel.
@thanos mentioned that downgrading to udev 173-3 helps, but it is my version and i never had newer udev on my system.
Maybe it has sth to do with brcmsmac driver? I also have some problems with it.
UPDATE: I updated ck kernel to 3.1.1-1-ck and it still occurs.
Last edited by AndrewPL (2011-11-13 09:17:49)
Offline
/sbin/blkid -o udev -p /dev/sdb1 terminated by signal 15
where /dev/sdb1 is my swap.
I'm having the same problem only when it's using the battery, after a few seconds it reboots. If it's on AC my laptop shutdown normally. This problem started when I reinstalled arch using LXDE.
Offline
A little update from me: 2 weeks ago I encrypted my whole "/" hdd and set lvm on top of it, since then I haven't had any problems with an "automated reboot". So that's a great workaround, isn't it
But maybe the problem is related to a hdd-thing...
Greetings
matse
Offline
The problem seems to have vanished for me with the latest kernel update.
Offline
Pages: 1