From: cfowler <cfowler@outpostsentinel.com>
To: Russell King <rmk@arm.linux.org.uk>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Break on serial port
Date: 11 Jun 2002 13:14:36 -0400 [thread overview]
Message-ID: <1023815676.6689.35.camel@moses.outpostsentinel.com> (raw)
In-Reply-To: <20020611173520.D3665@flint.arm.linux.org.uk>
I can not find that ocnfig option anywher in my 2.4.17 tree. I also
added CONFIG_MAGIC_SYSRQ=y to the top of .config and then did a make
dep and make bzImage. Upon boot I did not see a /proc/sys/kernel/sysrq
I did notice this feature in architectures other than i386.
Chris
On Tue, 2002-06-11 at 12:35, Russell King wrote:
> On Tue, Jun 11, 2002 at 11:41:26AM -0400, cfowler wrote:
> > I remeber a while back being able to send a break on serial console.
> > I've been unable to do this under 2.4.17. Has this feature been turned
> > off? Is there a way to turn it back on?
>
> It works fine here. Please confirm that:
>
> 1. your kernel is built with CONFIG_MAGIC_SYSRQ
> 2. cat /proc/sys/kernel/sysrq returns '1'
> 3. the serial console port is being held open by some user program (eg,
> getty or init)
>
> If any of the three above are not true, then break<sysrq-key> doesn't work.
>
> --
> Russell King (rmk@arm.linux.org.uk) The developer of ARM Linux
> http://www.arm.linux.org.uk/personal/aboutme.html
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
>
next prev parent reply other threads:[~2002-06-11 17:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-11 15:41 Break on serial port cfowler
2002-06-11 16:35 ` Russell King
2002-06-11 17:14 ` cfowler [this message]
2002-06-11 18:13 ` Russell King
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1023815676.6689.35.camel@moses.outpostsentinel.com \
--to=cfowler@outpostsentinel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rmk@arm.linux.org.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.