> >>>> Does the RED state exception trigger if you manually break to the prom > >>>> command line and issue a boot command? > >>> > >>> It seems I can not break from running kernel to PROM by sending break > >>> from minicom. PROM itself reacts to my break (during memory test for > >>> example) so it's Linux not accepting the break. I seem to remember it > >>> having worked some time ago, although not when the kergel hung. > >> > >> Argghh. > >> > >> There were some changes to sunsab.c a couple of versions ago; maybe we > >> broke it. > >> > >> Can you confirm BRKs are being received with > >> 'sudo cat /proc/tty/driver/serial' > > > > In 3.12: > > > > # cat /proc/tty/driver/sunsab > > serinfo:1.0 driver revision: > > 0: uart:SAB82532 V3.2 mmio:0x1FFF1400000 irq:5 tx:5163 rx:0 CTS|DSR|CD > > 1: uart:SAB82532 V3.2 mmio:0x1FFF1400040 irq:5 tx:0 rx: > > > > cat /proc/sys/kernel/stop-a > > 1 > > > > # cat /proc/sys/kernel/reboot-cmd > > > > (it was empty, so default "boot" should be used AFAIK) > > Meelis, > > Would you please re-test trying to break to the PROM with this debug > patch? As with the bootpromfs debug patch, the output is in > '/sys/kernel/debug/trace'. Should I activate tracing somehow? I enabled some trace options in the kernel and got a bunch of files under /sys/kernel/debug/tracing/ but /sys/kernel/debug/tracing/trace show only the header and /sys/kernel/debug/tracing/enabled_functions is empty. /sys/kernel/debug/tracing/tracing_on is "1" and /sys/kernel/debug/tracing/current_tracer is "nop". -- Meelis Roos (mroos@xxxxxxxx) -- To unsubscribe from this list: send the line "unsubscribe sparclinux" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
