Reboot/ShutDown Message: "Urgh, 1 exception..."

System:  TPad T60, Core Duo
eCS 2.0 RC2 w/most fixes available
ACPI 3.05, APM 1.20
[If more specifics required, please ask]

Occasionally when I try to reboot [or just shutdown], the shutdown 
process never completes because there is a popup box with the message:
   "Urgh, 1 exception running, waiting..."
There is a count of 'something' [seconds?] while presumably waiting for 
the 'exception' to go away.  There are two buttons, both inactive.

I have allowed the count to get up over 2450 by just walking away from 
the system and doing other things.  Since it appears that whatever is 
bothering the reboot will never go away, I just C-A-D to force the 
reboot to continue.

This is a real PITA when you start a reboot and come back to the system 
expecting it to be all ready to go, only to find it is still in this 
'Urgh...' state.

What is causing this?  Why can't the shutdown recognize that, after some 
period of time, it is in an infinite wait state?
-- 
TIA,

Hi Carl

Carl Gehr wrote:
> System:  TPad T60, Core Duo
> eCS 2.0 RC2 w/most fixes available
> ACPI 3.05, APM 1.20
> [If more specifics required, please ask]
> 
> Occasionally when I try to reboot [or just shutdown], the shutdown 
> process never completes because there is a popup box with the message:
>   "Urgh, 1 exception running, waiting..."
> There is a count of 'something' [seconds?] while presumably waiting for 
> the 'exception' to go away.  There are two buttons, both inactive.
> 
> I have allowed the count to get up over 2450 by just walking away from 
> the system and doing other things.  Since it appears that whatever is 
> bothering the reboot will never go away, I just C-A-D to force the 
> reboot to continue.
> 
> This is a real PITA when you start a reboot and come back to the system 
> expecting it to be all ready to go, only to find it is still in this 
> 'Urgh...' state.
> 
> What is causing this?


Good question.

Check what is still running just before you try to shutdown/reboot; that 
may help identify the culprit.

Must admit I have never seen the "Urgh, 1 exception running,
waiting..." 
message so guess it is something you have installed that I do not.

An exception is usually some form of error. Could it be that there is 
already a process hanging prior to shutdown/reboot?



   Why can't the shutdown recognize that, after some
> period of time, it is in an infinite wait state?


And do what?

It sounds like something could be hanging instead of closing and that is 
preventing the system shutdown/reboot.

Use a tool such as WatchCat to check what is running - and what is 
already hung - "program exit T1" is usually shown by WatchCat against

the process name if it is hung - just before using shutdown/reboot.

Regards

On Tue, 5 Feb 2008 09:50:04 UTC, Peter Brown 
<losepeteSPAM-ME-NOT@ntlworld.com> wrote:

> Check what is still running just before you try to shutdown/reboot; that 
> may help identify the culprit.
> 

For me this tends to happen when something within XWorkplace crashes 
and restarts - the Xcenter, for example - or the WPS restarts.

> Must admit I have never seen the "Urgh, 1 exception running,
waiting..." 
> message so guess it is something you have installed that I do not.
> 

Yes, you don't use Xworkplace (or eWorkplace or whatever it is on eCS)
and, if it's what I think it is, this message comes out of the 
extended shutdown feature.

I vaguely remember that Ulrich (Xworkplace author) said that the 
message served no useful purpose and he should remove it and just 
force a shutdown. I don't know if it's that simple, though...

-- 

Regards

Sid Gale

For me as well, a crash of the eCenter or WPS will cause the exception upon 
shutdown, this is easily rectified however. I simply use CAD+TOP to end the 
pmshell.exe task and initiate shutdown again. So long as the WPS or eCenter 
dont crash again, it will shut down clean :) 

On 02/05/08 04:13 pm, Brett Carlock wrote:
> For me as well, a crash of the eCenter or WPS will cause the exception upon

> shutdown, this is easily rectified however. I simply use CAD+TOP to end the

> pmshell.exe task and initiate shutdown again. So long as the WPS or eCenter

> dont crash again, it will shut down clean :) 

First, almost every reboot I do is preceded by manually shutting down 
all of the 'user tasks' that I've started.

Everyone seems to have hit an additional symptom.  Yes, the problem was 
often preceded by:
*  An eCenter crash. [This seems to happen far too often, especially 
when using it:
    eCS_icon->Desktop->Local_System->Drives...
       [I get the directory/file that I want, but eCenter disappears.]
*  SeaMonkey has had some kind of hang that I've usually attributed to a 
Web site that has some fouled up script or flash or...
*  Acrobat 5 that cannot handle some request in one of several PDFs that 
  I have open.  Sometimes, I think it is just the number of PDFs open.

And, yes, C-A-D -> TOP usually, but not always, forces the reboot to 
continue.  Sometimes it takes a power-off to get moving.  Most of the 
time, TOP does not show anything obvious as the culprit.

Also, yes, that message box is a clear waste.  It should be retitled as: 
"Waiting for Gidot" 'cause it's never going to get free on it's own.

BTW, I've not added anything to the extended shutdown that was not part 
of eCS 2.0 RC2.  eCenter is an integral part of eCS as far as I know and