Gavin Denby wrote:

You should be ok.

Sounds like the acpi shutdown issue. The kernel does not have the required ACPI support to actually turn of the machine, although its trying to.

ACPI support is getting better, but not quite there yet.

It won't be ACPI - I'd suspec that if it stopped at the "Power down" part.

That message should really read sending all processes -that init started- the TERM signal. One of these isn't shutting down cleanly, possibly due to trouble unmounting:

There is a problem, relating to "init" busying the /usr/share on shutdown If this fs is on a separate drive partition, it might not umount cleanly. This hangs up shutdown. I use a -l (lazy) umount preceded by sync and with sleeps to try to get arouind all this. Shutdown works, the partitions (ext3) recovers with its journal on next bootup and all is clean and fine.

But this "init" problem has been going on for a while--would like to see this fixed :-)

http://lists.debian.org/debian-user/2004/12/msg01010.html

(first hit on Google btw)

Craig

ok I reread the message and I concede being wrong

if it stops AT the message .. yep its wrong.

Mine stops after that as a result of acpi, so it was me mis-reading it .

my laptop says something like

Sending all processes the TERM signal shutdown now

and just sits there, but yes, i should have read it properly before hitting reply... sorry

Greig McGill wrote:

On Thu, 2004-12-23 at 09:32 +1300, Gavin Denby wrote:

...

You should be ok.

Sounds like the acpi shutdown issue. The kernel does not have the required ACPI support to actually turn of the machine, although its trying to.

ACPI support is getting better, but not quite there yet.

Nope. The ACPI or APM problem would not manifest at that point. The system has not asked the hardware to shutdown yet. Some process is blocking... Now, how to find out which? :)

G.

---

wlug mailing list | wlug@list.waikato.ac.nz Unsubscribe: http://list.waikato.ac.nz/mailman/listinfo/wlug