Bug#184624: reboots unexpectedly after panic

[Marcus Brinkmann]

At Tue,  2 Mar 2004 11:43:06 +0100,
marco_g wrote:
> 
> Quoting Robert Millan <zeratul2@wanadoo.es>:
> 
> > > {MB} Pass the `-H' option to init (add it to the boot command line), and
> > > `init' will tell Mach to enter the kernel debugger instead to rebooting
> > > it. At the debugger prompt (`db>'), you can type `reboot' any time to
> > > reboot the system. 
> > > --8<--
> > > 
> > > 
> > > Maybe that helps in your case?
> > 
> > I'm not working on GNU/Hurd currently, but I think the default behaviour
> > instead of reboot should either be halt or enter the debugger.
> 
> The `-H' option does not work anymore (please correct me if I am wrong).
> This used to work with serverboot, I think there is something wrong with the
> bootscript or how Mach or ext2fs.static passes the argument to init.

If you can fix that, this would be useful.
 
> It is easy to change GNU Mach so it just stops (for (;;); or perhaps just
> halting the system) instead of rebooting.  This might be useful when GNU Mach
> crashes and you want to report it.
> 
> I already have the "for (;;);" hack in my tree.  Perhaps I can even change GNU
> Mach so this becomes the default behaviour and you can use an argument to 
> switch
> to the old behavior.

The default behaviour is reboot, because otherwise if it is a server
or remote, you are screwed up if it hangs.  It's the right thing to
do.  If you are developing, this is not so convenient of course.  Then
you can either use -H or I think gnumach-dbg enters the debugger by default.

However.  Note that if you are running X or the new console, you won't
see anything.  No kernel message, and also not the debugger.  How
useful is that?

Thanks,
Marcus