From: "H. Peter Anvin" <hpa@zytor.com>
To: linux-kernel@vger.kernel.org
Subject: Re: How to send a break?
Date: Sun, 28 May 2006 16:06:06 -0700 (PDT) [thread overview]
Message-ID: <e5dacu$v33$1@terminus.zytor.com> (raw)
In-Reply-To: 01b701c6818d$4bcd37b0$1800a8c0@dcccs
Followup to: <01b701c6818d$4bcd37b0$1800a8c0@dcccs>
By author: =?iso-8859-2?Q?Haar_J=E1nos?= <djani22@netcenter.hu>
In newsgroup: linux.dev.kernel
>
> Hello, list,
>
> I wish to know, how to send a "BREAK" to trigger the sysreq functions on the
> serial line, using echo.
>
> I mean like this:
>
> #!/bin/bash
> echo "?BREAK?" >/dev/ttyS0
> sleep 2
> echo "m" >/dev/ttyS0
>
You can't use it using echo, however, you can do it using Perl:
perl -e 'use POSIX; tcsendbreak(1,0);' > /dev/ttyS0
-hpa
next prev parent reply other threads:[~2006-05-28 23:06 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-27 12:58 How to send a break? Haar János
2006-05-27 23:43 ` Jim Crilly
2006-05-28 7:04 ` How to send a break? - dump from frozen 64bit linux Haar János
2006-05-28 16:17 ` Jesper Juhl
2006-05-28 17:34 ` Haar János
2006-05-29 4:37 ` Jesper Juhl
2007-08-20 7:44 ` Andev Debi
2006-05-30 10:22 ` Janos Haar
2006-05-30 19:03 ` Valdis.Kletnieks
2006-05-30 21:44 ` Janos Haar
2006-05-31 1:20 ` Steven Rostedt
2006-05-31 4:38 ` XFS related hang (was Re: How to send a break? - dump from frozen 64bit linux) Nathan Scott
2006-05-31 8:00 ` Janos Haar
2006-05-31 21:54 ` Jan Engelhardt
2006-06-01 7:29 ` Janos Haar
2006-06-01 9:44 ` Jan Engelhardt
2006-06-01 22:04 ` Nathan Scott
2006-06-02 5:11 ` Jan Engelhardt
2006-06-01 21:58 ` Nathan Scott
2006-06-01 22:14 ` Janos Haar
2006-06-01 23:43 ` Nathan Scott
2006-06-02 8:01 ` Janos Haar
2006-05-28 23:06 ` H. Peter Anvin [this message]
2006-05-29 15:08 ` How to send a break? linux-os (Dick Johnson)
2006-05-29 15:35 ` Valdis.Kletnieks
2006-05-29 17:32 ` Haar János
-- strict thread matches above, loose matches on Subject: below --
2006-05-29 7:51 Haar János
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='e5dacu$v33$1@terminus.zytor.com' \
--to=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
/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.