tags 417917 unreproducible severity 417917 normal thanks Stefan Kluth <[EMAIL PROTECTED]> writes:
> After /etc/init.d/openafs-client stop I get from dmesg > ... > COLD shutting down of: CB... afs... BkG... CTrunc... AFSDB... RxEvent... > UnmaskRxkSignals... RxListener... Why are you getting a COLD shutdown instead of a WARM shutdown? That's strange. In any event, this isn't a universal problem. I can't duplicate this at all on my system; I can start and stop AFS without any trouble. > This behaviour started after the recent kernel upgrade to > 2.6.18.dfsg.1-12. The module was built with "m-a auto-install" which > reported no errors. I'm using the same kernel and the same openafs package that you are. > As a result stop/start of openafs-client is impossible (without a reboot) > and thus for a mobile user it is unusable. Well, I'm not sure why that would make it unusable for a mobile user. I can leave my AFS client running on my laptop and it doesn't hurt anything. In general, we haven't been treating problems with stopping and starting the client at that level of severity (it didn't used to work at all, although a lot of work has been put into it and it's now much better). I would like to get it working for you, though. I'm not sure the best place to start, however. One experiment I'd be interested in, if you're up for it, is to try installing openafs-modules-source from Debian experimental and seeing if 1.4.4 works any better for you. Does this happen every time you try to start and stop the client on your system? Also, are there any messages before that? I hardly ever see COLD shutdowns; I almost always get WARM shutdowns. I wonder if that may be somehow related. -- Russ Allbery ([EMAIL PROTECTED]) <http://www.eyrie.org/~eagle/> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
