Re: [issue713] shutdown freeze and forced unmounts

[Peter Avalos <pavalos@xxxxxxxxxxxx>]

On Tue, Jul 10, 2007 at 03:43:31PM -0700, Matthew Dillon wrote:
> 
> :Unfortunately, it still freezes after the Uptime: message.  I've tried this
> :with and without ACPI.
> :
> :Any other ideas?
> :
> :Am I the only one that is not able to 'reboot' their machine?
> 
>     I think so :-).

Sucks ;)

>     Start adding kprintf()'s to the kernel in the code paths after the
>     Uptime message is printed.  In paricular, the device shutdown
>     path (device_shutdown() line 1198 in kern/subr_bus.c).  Also boot
>     with verbose mode so the shutdown is verbose too.

Okay, I'll give it a shot.

>     Now that we've gotten one issue out of the way at least, is it
>     possible to break into the debugger after it freezes or is that still
>     a no go?

No workie.

>     Another thing to try, drop into single user by killing init
>     i.e.  'kill 1', do a ps to make sure everything has been killed
>     (the only user processes left should be init, -sh, and your ps),
>     and then see if a reboot freezes the system.

Indeed, only kernel threads and init, sh, and ps, but a reboot still freezes
after "Uptime: xxxx"

>     It's got to be something stupid simple.  Literally.  The shutdown
>     got through all the hard stuff already.  It's like it can't reset
>     the cpu or something.
> 

BTW, with verbose logging, that's where I was getting the acpi_button
messages from.

Attachment: pgp00011.pgp
Description: PGP signature