LKML Archive on
help / color / mirror / Atom feed
From: Hans-Peter Jansen <>
Cc: Arnd Hannemann <>
Subject: Re: strange SysRq problem
Date: Thu, 14 Feb 2008 15:28:11 +0100	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

Am Donnerstag, 14. Februar 2008 schrieb Arnd Hannemann:
> Hans-Peter Jansen wrote:
> > I'm suffering from a strange SysRq problem:
> >
> > syslog shows haphazardly "SysRq : HELP" lines, while I definitely
> > didn't triggered them, neither via (PS/2) keyboard, nor via
> > /proc/sysrq-trigger. This is accompanied with stalls of about 15-60
> > secs.
> Any chance that a device connected via serial (or an USB device which
> uses USB/Serial conversion) triggers them? My cheap pl2303 device seems
> to send spurious BREAKs every once in a while, which results in the
> described behavior, as the kernel will print the help line for any
> character which is not a valid sysrq. (The probability to trigger another
> sysrq with random data is much lower, but did you find any other printout
> of an sysrq in your logs?)

Hmm, keyboard (Cherry G80-3000 LPCDE-2) and mouse (Logitech RX300) are 
connected via an equip KVM 2 port switch, but everything else is behaving 
properly, and no serial devices connected ATM. It only triggers the help 
messages, other sysrq messages are triggered at will (AFAIKS).

# grep "SysRq : HELP" /var/log/messages | wc -l

syslog starts at Jan 16, so you can imagine how disturbing this behavior is.

I cannot outrule some hardware defects. Will start to eliminate the KVM 
switch, but I thought, I ask here before since google also didn't revealed 
any hints..


      reply	other threads:[~2008-02-14 14:28 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-14  0:02 Hans-Peter Jansen
2008-02-14 12:27 ` Arnd Hannemann
2008-02-14 14:28   ` Hans-Peter Jansen [this message]

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \
    --subject='Re: strange SysRq problem' \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).