Hello all. Without the attached patch, SysRq doesn't work over a serial
console here. Has anyone else seen this problem?
--
Tom Rini (TR1265)
http://gate.crashing.org/~trini/
On Sat, Mar 31, 2001 at 04:38:08PM -0700, Tom Rini wrote:
> Hello all. Without the attached patch, SysRq doesn't work over a serial
> console here. Has anyone else seen this problem?
It is handled at the serial port driver level, not the tty level. You need
to turn on CONFIG_SERIAL_CONSOLE and CONFIG_MAGIC_SYSRQ, and issue a break
followed by the relevent character within 5 seconds on the serial TTY being
used as the kernel console.
--
Russell King ([email protected]) The developer of ARM Linux
http://www.arm.linux.org.uk/personal/aboutme.html
On Tue, Apr 03, 2001 at 09:07:44PM +0100, Russell King wrote:
> On Sat, Mar 31, 2001 at 04:38:08PM -0700, Tom Rini wrote:
> > Hello all. Without the attached patch, SysRq doesn't work over a serial
> > console here. Has anyone else seen this problem?
>
> It is handled at the serial port driver level, not the tty level. You need
> to turn on CONFIG_SERIAL_CONSOLE and CONFIG_MAGIC_SYSRQ, and issue a break
> followed by the relevent character within 5 seconds on the serial TTY being
> used as the kernel console.
That wasn't working here however. Unless minicom isn't sending the proper
break. Doing the keycombo which slips my mind to send a break, followed by
'h' in minicom does nothing.
--
Tom Rini (TR1265)
http://gate.crashing.org/~trini/
On Tue, Apr 03, 2001 at 09:07:44PM +0100, Russell King wrote:
> On Sat, Mar 31, 2001 at 04:38:08PM -0700, Tom Rini wrote:
> > Hello all. Without the attached patch, SysRq doesn't work over a serial
> > console here. Has anyone else seen this problem?
>
> It is handled at the serial port driver level, not the tty level. You need
> to turn on CONFIG_SERIAL_CONSOLE and CONFIG_MAGIC_SYSRQ, and issue a break
> followed by the relevent character within 5 seconds on the serial TTY being
> used as the kernel console.
After talking with the person who originally did the patch, yeah, that does
make sense (and the serial driver we're using needs to be fixed). Thanks.
--
Tom Rini (TR1265)
http://gate.crashing.org/~trini/