Hanging on shutdown

[andrewr]

Hi everyone,

I've installed Puppy on a bootable USB stick (ext2 partition) which I use with a Panasonic Toughbook CF-29. Puppy boots and runs fine on the Toughbook from the USB or a live-CD.

However when I shutdown Puppy it gets to the "Puppy is now shutting down ..." screen after which I know it should ask me where to save the settings file (proven by using the live-CD in another box) - on the Toughbook it just hangs at this point using either the live-CD or the USB stick.

Can anyone suggest why it is hanging or give me an idea (eg boot options etc) to get around this problem?

I'm happy to provide more debugging info if required...

Thanks in advnace,

Andrew

[WhoDo]

Can anyone suggest why it is hanging or give me an idea (eg boot options etc) to get around this problem?

Try booting with either acpi=off ... which is default for PC's > 2001 and sometimes gives boot/shutdown problems.

[andrewr]

Try booting with either acpi=off ... which is default for PC's > 2001 and sometimes gives boot/shutdown problems.

Thanks WhoDo .... noticed you had acpi=force as well originally.

Tried both, no joy..... still hangs.... next suggestion?

Thanks

[WhoDo]

Try booting with either acpi=off ... which is default for PC's > 2001 and sometimes gives boot/shutdown problems.

Thanks WhoDo .... noticed you had acpi=force as well originally.

Tried both, no joy..... still hangs.... next suggestion?

Try pci=biosirq ... after that we need to consider which Puppy version, which video chip, whether dma is enabled in your bios, etc.

[andrewr]

Try pci=biosirq ... after that we need to consider which Puppy version, which video chip, whether dma is enabled in your bios, etc.

No joy again.

ok...

Latest Puppy Stable (4.2.1)

Intel(R) 915GM/GMS, 910GML Express Chipset v6.14.10.4277

Bios is a PhoenixBIOS that does not appear to have the capability of specifying DMA. Does have an entry mentioning "Legacy USB Support" which is currently enabled though... possibility?

Cheers

[mikeb]

do you have initrd.gz on anywhere else (eg hard drive )other than the usb stick?
Have you renamed the initrd.gz?

mike

[Bruce B]

/sbin/poweroff does two things

1) runs /etc/rc.d/rc.shutdown

2) executes /bin/busybox poweroff

If it gets through rc.shutdown you add some options to help
the shutdown in the busybox part if that's the hang

BusyBox v1.13.3 (2009-03-19 17:52:06 GMT-8)
multi-call binary

Usage: poweroff [-d delay] [-n] [-f]

Halt and shut off power

Options:
-d Delay interval for halting
-n No call to sync()
-f Force power off (don't go through init)

[andrewr]

do you have initrd.gz on anywhere else (eg hard drive )other than the usb stick?
Have you renamed the initrd.gz?

mike

Thanks for the suggestion Mike - nope no other instances of initrd.gz elsewhere on the Toughbook drives. That said, both the live-CD and USB stick work fine (eg don't hang) if used on two other boxes.

[xdna]

Hi... anyone can help me?

When I install something big, like scribus, tetex or other, when I shutdown my computer then it save puppy to disk are to slow.

It's take for 5 minute or more.

Can I save directly? so I don't need waiting for this job?

Tks

[andrewr]

/sbin/poweroff does two things

1) runs /etc/rc.d/rc.shutdown

2) executes /bin/busybox poweroff

If it gets through rc.shutdown you add some options to help
the shutdown in the busybox part if that's the hang

I believe its hanging in rc.shutdown, as evidenced by the "Puppy is now shutting down ..." being the only thing on the screen... obviously the trick now is to work out *where* in rc.shutdown it's hanging....

[mawebb88]

/sbin/poweroff does two things

1) runs /etc/rc.d/rc.shutdown

2) executes /bin/busybox poweroff

If it gets through rc.shutdown you add some options to help
the shutdown in the busybox part if that's the hang

I believe its hanging in rc.shutdown, as evidenced by the "Puppy is now shutting down ..." being the only thing on the screen... obviously the trick now is to work out *where* in rc.shutdown it's hanging....

As a matter of interest what then does wmpoweroff do?
Rgds Mike

[mikeb]

Code: Select all

Thanks for the suggestion Mike - nope no other instances of initrd.gz elsewhere on the Toughbook drives. That said, both the live-CD and USB stick work fine (eg don't hang) if used on two other boxes.

Ok , found a quirk that produces similar symptoms...just checking.

Hi... anyone can help me?
When I install something big, like scribus, tetex or other, when I shutdown my computer then it save puppy to disk are to slow.
It's take for 5 minute or more.
Can I save directly? so I don't need waiting for this job?
Tks

you should start a fresh thread with this. for a flash stick this is normal.

As a matter of interest what then does wmpoweroff do?

Cleanly shuts down X and puppy daemon for drive icons etc then sets a flag to poweroff and returns control to xwin which calls poweroff. Xwin only completes at shutdown and this nested setup can get stuck if something gets upset.

mike

[andrewr]

A bit of further investigation has revealed the following....

The shutdown sequence is hanging a the point in rc.shutdown which has the following code:

for service_script in /etc/init.d/*
do
[ -x $service_script ] && $service_script stop
done


If I comment this section out..... BINGO!!! Houston, we have shutdown!

Its a step in the right direction and I'm happy that I nutted it out - I guess the gurus can tell me why that section is hanging now.

Thanks,

Andrew

[mikeb]

Well it's tring to stop various background daemons cleanly (used to just kill kill kill lol).
You could try manually killing each one in htop and see which one of those is hanging shutdown.

mike

[andrewr]

Success - nailed what was causing the issue. Had a look in init.d to see what was being started - the thing that caught my eye was a modem driver... then the penny dropped.

I'd had a Xircom RealPort Ethernet/Modem card plugged into the PCMCIA slot - removed this and it now shuts down perfectly with the original rc.shutdown script in place. The card isn't really required so I'll leave it out - it was causing some sort of issue possibly in conjunction with the ToughBooks own internal modem.

Many thanks to everyone who has given suggestions to help.

Cheers

Andrew

[mikeb]

-->>mike does a successful shutdown celebration dance <<--