linux-kernel - Re: strange SysRq problem

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <200802141528.11519.hpj@urpla.net>
Date:	Thu, 14 Feb 2008 15:28:11 +0100
From:	Hans-Peter Jansen <hpj@...la.net>
To:	linux-kernel@...r.kernel.org
Cc:	Arnd Hannemann <hannemann@...informatik.rwth-aachen.de>
Subject: Re: strange SysRq problem

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
814

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..

Thanks,
Pete
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/