What is nash-hotplug and why is it consuming 100% CPU?“, someone asked in a Xen-related message I found after experiencing similar problems booting Mandriva 2008.1 with finit in the Asus Eeepc. This situation seems to be especially common in different Linux distributions running as Xen guests and the usual advice is to just kill nash-plugin after the system boots. Instead of doing that ugly workaround, we decided to investigate and find out what’s happening. Whatever nash-hotplug is supposed to do, I can’t say it keeps running consuming 100% of your cpu because it’s a well-written program (notice the bizarre IPC protocol, how it tries to read from a descriptor after closing it and how easily it can get trapped in infinite loops). Use the following quick fix to avoid the problem.

Die, nash, die.

2 Responses to “Killing a stuck nash-hotplug”

  1. CowboyBob says:

    Just wanted to follow-up on my experience with Mandriva 2008.1 RC2– I have to begin by summing it up in one word AWESOME! My install remain incredibly stable. Wireless works without a glitch. I have reported a few minor issues that hopefully will be resolved before release. One disappointment for me is the Fn F5 does not activate the external video. If I launch with a monitor attached, the system adopts the screen resolution for the external monitor making the internal LCD unusable as it just shows the top left corner of the display. If I boot without the external monitor attached Fn F5 seems to do nothing. A little disappointing for me as I give “Powerpoint” presentations all the time and would like to be able to use the eee for presentation purposes. The current functionality is not really usable.

    Big THANK YOU to the Madriva development team

  2. 27874a092aef says:

    27874a092aef…

    27874a092aefcb3ff044…

Leave a Reply