FC 2 Hangs On Shutdown
 

Just about every second time I shut down FC 2 it hangs , can anybody tell me why the system hangs when it either hangs on one of these shutdown messages

1) Sending all processes the TERM signal.
2) Saving mixer settings.
3) Syncing hardware clock to system time.


I have tried using the command sync to flush the buffers but this hasn't worked and I have been told that I should reset my motherboard settings back to the default factory settings to see if that fixes the problem.

The only other abnormal shutdown message that I get has to do with unmounting NFS , I keep getting the message twice :

unmounting NFS filesystem (retry)

So far , after all the problems I have had with FC 2 , I have finally got
the system working good except for the hanging on shutdown , if I can get
rid of this hanging on shutdown , then FC 2 will be working really good.

Has anybody got any ideas why the system keeps hanging on shutdown ?

Thanks.

System specs :
P3 866 Mhz Cpu
Asus CUSL2 motherboard
512 Mb of Ram
64 Mb Gf 4 440 MX video card
40 Gb Seagate HDD
Dual boot set-up with Windows 98SE

Do you have anything in the log ? /var/log/messages ?
Philippe

Thanks for your reply.

The only things that I can see in the log files is that I have a failure on mdmpd and fatal error running install command for sound_slot_1.

On boot up I get some abnormal messages these messages are :
1) agpgart : Detected an Intel i815 chipset , but could not find secondary device.

2) Failed to bind key 255 to value 2379

3) KDSKBENT : Invalid argument.

Do you have any clues as to what these boot up error message mean ?

Thanks.

Unfortunately no, and Google did not help us a lot.

The mdmpd is about mdadm, which one controls the Raid system. If you dont use it, you can uninstall te package.

The sound-slot come from RH8 or 9 already ... no problem just forget it. Something to do with /etc/modprobe.conf, if my more is still good.

2) Failed to bind key 255 to value 2379
3) KDSKBENT : Invalid argument.

https://bugzilla.redhat.com/bugzilla....cgi?id=125133

For the rest, you'd better open a bug on bugzilla.redhat ... it can be many things, including a hardware incompatibility, an acpi problem ... etc ?

By the way, if your NF server is shut down before your client, you can have these RETRY forever ... just shutdown the clients BEFORE the NFS server. This can be the reason of the hangup

Philippe

Hi Philippe ,

Sorry to take a while to reply to your post .

I have been doing a bit of fiddling with FC2 to find out what is happening to my system.

From what you have said and from what I have checked out , I seem to have 2 main problems.

1) A network problem
From your suggestions , I decided to try shutting down my client machine first before I shut down the host FC 2 box and this resulted in a clean shutdown without any hanging.

I have also discovered that I can shutdown my FC 2 box while I have the client box running RH 9 without any problems also , but if I try to shut down the FC 2 while I have Windows 98 SE running on the other box , then that's when my FC 2 box hangs on shutdown.

Also , if I stop the samba service before I shutdow the FC 2 box , with Windows 98 running on the other machine then the FC 2 box also shuts down cleanly without any hanging.

So essentially , it's the network setup with the Windows 98 box that is causing all the shutdown problems on the FC 2 box.

The set-up I have is that I have samba running on the FC2 and have set up my other machine with samba when running Windows 98.
I also have the FC 2 box setup with NFS while I am running RH 9 on the other box.

2) A bug in FC2 with SELinux

With the error messages that I have been getting ,
1) Failed to bind key 255 to value 2379
2) KDSKBENT : Invalid argument.

These errors messages both relate to the keyboard , SELinux and to Loadkeys and it is a common occurance with a lot of people.
I did a search on the word KDSKBENT and came up with a whole lot of info about these error messages and there is also a bug report with Bugzilla.

https://bugzilla.redhat.com/bugzilla....cgi?id=125133

So all I have got to do now is to fix the network problem and see if I can find a patch / workaround with the keyboard problem.

Thanks for your interest and replies.

Hi,

I thought that SELinux was not activated by default with FC2, du to some problems, bugs or instability ?

For Samba, I am not a specialist, but I think that many people are running FC2 with Samba and a Windows client on the LAN. You should find your answers easily.

Good luck,

Philippe