Question!
Have you booted into Windows at any time before going into Linux?  Does the machine restart, should you select restart and not shutdown from Linux?  Again, be sure to check your bios settings for the power settings and PNP setting.  Windows has been known to create problems that seem unexplainable and I'm guessing you have never really shutdown, just hit the reset button, but during that time you've booted into Windows?  If that's the case, turn the machine off for 5 minutes, then power on, booting directly into Linux, no Windows at all.  See if Linux will shut it down then.

figment

As far as I can understand this problem that I can't reproduce : it's related to the 2.6.21.1 kernel and some old/buggy Bios. I hope that 2.6.21.2 will fix this.

Please be ready to test the next kernel package : I need your feedback.

To wait for this : please downgrade your kernel to 2.6.20.7 , I need to know if it fix the reboot problem.

Thanks

JP

For completeness: I will not be booting into windows any time soon. I flatly refuse to install any windows on this or any other of my '.home' machines.    On a more serious note: If a windows-trick is the cause of this problem, then i can not be of any help: All my machines are 100% MS-clean.

@JP: i can present one machine that has gone through the following cycle:

- It did a clean shutdown with the 2.6.21.1 kernel
- I ran 'netpkg upgrade' (snapshot mirror) with it.
- It no longer did a clean shutdown
- I added the packages as mentioned in a previous post
- It now -once again- shuts down cleanly

Please note the absence of any mention of the machine's BIOS and kernel up/down grades in this list of operations.

I noticed the same behavior, it didn't hang until after I did the package upgrade...although I've yet to determine the guilty package


ggordon

Spent a lot of time yesterday testing my system trying to figure out what causes the hanging at shutdown.  I decided to concentrate only on the shutdown command to see if I could get consistent results form that command.  In all case yesterday I only did shutdowns. The cycle I used was to start the system by press in the power on button on the front of the computer and letting it boot into ZW right to the login screen.  From there I would select Action >> Shutdown.  I did this several time, maybe up to thirty times, trying to determine if there was some sequence which would consistently get the system to shutdown normally.  The conclusion I came to are:

1) Although the system did shutdown completely at a higher rate than I’ve experienced in the past few weeks, there was nothing I could do to consistently get it to shutdown.  At the most, I got the system to shutdown normally, just two time in a row.
2) Booting into windows and then into ZW had no consistent affect on shutdowns.  In some cases, ZW would shutdown normally, other times it did not.
3) Changing BIOS setting (any) would consistently get a normal shutdown of ZW on the first boot of the computer after the bios change, but following shutdowns would hang.

The last thing I did last night was to upgrade the latest snapshot and then called it a day.  When I shutdown after the update, the system shutdown normally.  I will try over the next few days to see if I get consistent shutdown with this new update.

Regards
Rich

I made modifications in rc.6 lately (rc.0 is symlinked to rc.6, so they concern both shutdown and reboot).

I don't see anything that could cause this problem in my modifications, ....

Maybe someone could take a look and tell me what I'm missing ? (It **could** have something to do with disc syncing...)

Please try several methods : adding sleep commands before final "halt"...

I can't reproduce the problem here, so I hope you'll find my bug

Cheers

JP

Mine does the same thing but instead of stopping at the “md: stopping all md devices."  It stops at INIT: no more processes left in this runlevel

Hope this gives some insight into what the problem is.


Rob1

Please read the Changelog carefully and upgrade from the main repository : http://download.zenwalk.org/i486/snapshot

Waiting for feedback



JP



edit : take care to a last minute sysvinit update (46.13)

Updated tonight to snapshot and carefully followed the change log (touch /dev/touch /dev/.inetflag).  Actually I attempted three shutdowns before I did the touch command.  All three resulted in hangs.  After doing the touch command, I reboot and the system reboot normally, no hangs. I was somewhat elated hoping that the problem was resolved .  But on my next boot up and shutdown it hung again and then also on the following three shutdowns.  Looking back through my notes, I noticed that I had made a change to my bios (needed to disable the on board  audio hardware) just before doing the touch command.  If you recall my earlier post, I came to the conclusion that the system shuts down normally after a change to the bios.  Anyway, it still seems to be a problem on my machine.

Also observed something that may or may not be significant. I'll explain and let you decide if it gives you any clues.  I was looking through this complete thread to see if there was any suggestion that I had not tried yet and saw that Jokas suggested that a USB device could be the cause of the problem.  I have had three usb devices ( two cameras, and a scanner) connected  to my computer throughout this problem, so I disconnected them and did several shutdown to see if this would solve the problem.  The system still hung at the same place.  But after the last hung shutdown, I reconnected the three usb devices before I reset the computer and notice that the computer had recognized that the three devices were plugged in.  Here's the messages that I got after plugging in the usb devices;


system is hung a this point
now after a plugging in the devices it looked like this:


So it not sitting there hung and dumb, but something is still running.

It's the kernel

Well, I downgraded my kernel to 2.6.20 from current tonight (5/23).  Reinstalled the NVidia driver and tested shutdowns and reboots.  All five attempts to shutdown and two reboots were successful, no hangs.  Looks like I'll stay with the kernel until the new 2.6.21 is out.

Hi,

Upgraded from snapshot and everything till now work as expected. I was stuck with sysvinit included in beta 1 CD, as the versions that came after it caused my system to produce this error during shutdown/reboot:



But this last version seems to work like a charm.

Thank you,

Upgraded via netpkg snapshot tonight including kernel 2.6.21.2.  First two shut downs after upgrade were succesfull.  After that got several hung shutdowns and reboots.        I'm back to 2.6.20 for now

Downgraded the kernel with the one in snapshot and that fixed it for me....restarts normally now....no hang.




ggordon

ggordon : do you mean "Upgraded" ?