Crash on Shutdown

Question

Hi there,
Long time lurker here but just made the account. I've been having problems lately when trying to shutdown the system freezes/hangs/crashes or whichever one of those. It seems that this happens as soon as network manager is put down. That being said, problems with the ath9k drivers are not new to me, but now that the driver IS working it seems to cause a crash as soon as it is terminated. This also happens if I manually shutdown the networkmanager daemon with "rc.d stop networkmanager".
These are the last lines from the log after a reboot:
Oct 12 13:38:20 willy-arch shutdown[4253]: shutting down for system reboot
Oct 12 13:38:20 willy-arch init: Switching to runlevel: 6
Oct 12 13:38:23 willy-arch NetworkManager[458]: <info> caught signal 15, shutting down normally.
Oct 12 13:38:23 willy-arch NetworkManager[458]: <info> (wlan0): now unmanaged
Oct 12 13:38:23 willy-arch NetworkManager[458]: <info> (wlan0): device state change: activated -> unmanaged (reason 'removed') [100 10 36]
I would like to know if this is just happening to me or if it a known problem and if there is any solution. Having to hard reset your computer every time you try to shutdown can't possibly do any good to the hardware.
Thanks,
Isaac

Answer 1

Have you tried systemd?  Since dbus is packaged with systemd these days, it is simply a matter of putting init=/lib/systemd/systemd on the bootloader command line.  Might I suggest also seeing if using a different network management system might yeild different results.  I am a former wicd user, and it was great while I used it.  But I have moved on to netcfg.  Who knows, maybe I will continue to progress to simpler things and evertually be doing it manually.  BTW, what happens if you diable the network-manager daemon, and then connect manually, then shut down?