Ubuntu

Juanty not shutting down after a usb subsystem crash?

Asked by Lucian

Sometimes a driver for something like a game controller gets written but then there are some bad liners in the script that need patched of course therefore causing a "modprobe abnormal exit" when enabling it. This will more likely cause a usb subsystem crash leaving modprobe in a limbo state. Now for some reason when trying to reboot/shutdown Ubuntu 9.04 Jaunty, It hangs in the middle of the process because of this modprobe abnormal exit. My guess is Jaunty is waiting for the modprobe to finish a task but it cant because its frozen.

What I'd like to ask is can the developers fix it so that if a usb subsystem crash occurs, Ubuntu 9.04 can still shutdown/reboot regardless? I know that Hardy can shutdown with this issue but Jaunty cant. So can someone produce a modprobe usb crash and then try to shutdown Jaunty so this can be reported?

thanks

Question information

Language:
English Edit question
Status:
Answered
For:
Ubuntu Edit question
Assignee:
No assignee Edit question
Last query:
Last reply:
Revision history for this message
Wim (launchpad-xs4all) said : 		#1

Lucian,

i have a suggestion that works for you now, so you do not have to wait for the developers:
before shutting down, open a terminal window, and enter this command

   ps -ef | grep modprobe

you will see a process with the name modprobe; in the first column is the name of the user who started this modprobe, the second column is the Process IDentification (PID)

you can ask linux to stop a process with the next command

   kill -1 <the_PID-number_here>

this command will kindly "ask" the process with that PID-number to stop; you can increase the force to stop by highing up the option, e.g.

   kill -1 8765 kindly asks process 8765 to stop soon
   kill -2 8765 demands process 8765 to stop now
   kill -3 8765 forces the process to stop

After the process is stopped (can be checked with the ps-command),
close the terminal-window with key-combination <Ctrl>-<d>, or by giving the command

   exit

Now shut down Ubuntu; it does not have to wait for modprobe to stop.

Can you help with this problem?

Provide an answer of your own, or ask Lucian for more information if necessary.

To post a message you must log in.