Fabian Keil <[EMAIL PROTECTED]> wrote: > Fabian Keil <[EMAIL PROTECTED]> wrote: > > > Robert Watson <[EMAIL PROTECTED]> wrote: > > > > It sounds like your serial console server may not know how to map > > > SSH break signals into remote serial break signals. Try > > > ALT_BREAK_TO_DEBUGGER. Here's the description from NOTES: > > > > > > # Solaris implements a new BREAK which is initiated by a character > > > # sequence CR ~ ^b which is similar to a familiar pattern used on > > > # Sun servers by the Remote Console. > > > options ALT_BREAK_TO_DEBUGGER > > > > It took me several attempts to get the character sequence right, > > but yes, this one works. Thanks. > > Unfortunately it didn't work while the system was hanging > this morning.
Since then I got one or two hangs a day and entering the debugger never worked out, even if my console connection was opened a few minutes before the hang. I no longer think it has anything to do with the terminal server, but assume the hang takes the console with it. sio0 is running on acpi0, so I tried to disable acpi to see if it changes anything, but the only change I got was that fxp0 stopped working (it is up but only produces timeout warnings). I tried to partly disable acpi subsystems like described in acpi(4), but either I got the syntax wrong, or it just isn't working. Can someone on this list confirm or deny if something like debug.acpi.disabled=isa in /boot/loader.conf makes sense? That's how I understand the man page, but I don't see any reaction. I also tried /etc/sysctl.conf (which probably is parsed too late anyway) but I just got a message that the sysctl does not exists. sysctl debug.acpi indeed only shows: debug.acpi.do_powerstate: 1 debug.acpi.acpi_ca_version: 0x20041119 debug.acpi.semaphore_debug: 0 so maybe I need some special acpi options or it just doesn't work if acpi is loaded as a module, but as least the man page has no such hints. Fabian -- http://www.fabiankeil.de/
signature.asc
Description: PGP signature
