From: "Bruno Prémont" <bonbons@linux-vserver.org>
To: linux-kernel@vger.kernel.org
Cc: Alexey Dobriyan <adobriyan@gmail.com>, dmitry.torokhov@gmail.com
Subject: Re: 2.6.38-rc6: SysRq broken?
Date: Tue, 1 Mar 2011 22:39:32 +0100 [thread overview]
Message-ID: <20110301223932.609a4a59@neptune.home> (raw)
In-Reply-To: <20110228225003.2cb4f62d@neptune.home>
On Mon, 28 February 2011 Bruno Prémont <bonbons@linux-vserver.org> wrote:
> On Mon, 28 February 2011 Alexey Dobriyan <adobriyan@gmail.com> wrote:
> > It just strikes me that SysRq is broken here:
> > Alt+SysRq+h doesn't print anything
> >
> > CONFIG_MAGIC_SYSRQ=y
> > CONFIG_INPUT_EVDEV=y
> > kernel.sysrq=1
> > echo h >/proc/sysrq-trigger works
> >
> > Keyboard is USB one, "Logitech HID compliant keyboard".
>
> I've seen same kind of issue with built-in keybaord (PS2) of my laptop.
>
> Sysrq-Sync, Sysrq-Umount, Sysrq-Help didn't work but Sysrq-reBoot did.
>
> In my case it was during "stuck" shutdown process, caps key was still
> working and toggled caps LED anything else didn't trigger anything visible.
>
> Bruno
Well it worked (half way?) though fb was probably frozen (vt-deadlock?)
as I have traces in my log:
[14382.063476] pcmanfm[28117]: segfault at 8 ip b772e5b5 sp bfcfba30 error 4 in libfm-gtk.so.0.0.0[b7700000+34000]
[43437.896858] SysRq : Emergency Sync
[43572.221361] SysRq : Keyboard mode set to system default
[43575.574551] SysRq : Emergency Sync
[43590.513441] SysRq : Emergency Remount R/O
[43605.923769] SysRq : Emergency Sync
[43607.320324] SysRq : Emergency Remount R/O
[43627.329605] SysRq : HELP : loglevel(0-9) reBoot Crash terminate-all-tasks(E) memory-full-oom-kill(F) kill-all-tasks(I)
thaw-filesystems(J) saK show-memory-usage(M) nice-all-RT-tasks(N) powerOff show-registers(P) show-all-timers(Q) unRaw Sync show-task-states(T) Unmount force-fb
(V) show-blocked-tasks(W)
[43676.561306] SysRq : Emergency Sync
[43690.319213] SysRq : SAK
[43690.319245] SAK: killed process 1926 (Xorg): task_session(p)==tty->session
[43690.319313] SAK: killed process 1926 (Xorg): task_session(p)==tty->session
[43690.319345] SAK: killed process 2801 (rc): fd#0 opened to the tty
[43690.319358] SAK: killed process 2802 (rc): fd#0 opened to the tty
[43690.319368] SAK: killed process 2890 (ntpd): fd#0 opened to the tty
[43690.319378] SAK: killed process 2891 (runscript.sh): fd#0 opened to the tty
[43690.319387] SAK: killed process 2898 (start-stop-daem): fd#0 opened to the tty
[43694.809374] SysRq : Keyboard mode set to system default
[43797.368728] SysRq : SAK
[43797.368768] SAK: killed process 1926 (Xorg): task_session(p)==tty->session
[43797.368829] SAK: killed process 1926 (Xorg): task_session(p)==tty->session
[43797.368864] SAK: killed process 2898 (start-stop-daem): fd#0 opened to the tty
But then, "Emergency Remount R/O" should have prevented anything further
from hitting the disk. (and after sysrq-reboot filesystems were dirty)
Bruno
next prev parent reply other threads:[~2011-03-01 21:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-28 21:40 Alexey Dobriyan
2011-02-28 21:50 ` Bruno Prémont
2011-03-01 21:39 ` Bruno Prémont [this message]
2011-02-28 21:57 ` Dmitry Torokhov
2011-02-28 22:04 ` Alexey Dobriyan
2011-03-01 18:04 ` Dmitry Torokhov
2011-03-01 21:00 ` Alexey Dobriyan
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=20110301223932.609a4a59@neptune.home \
--to=bonbons@linux-vserver.org \
--cc=adobriyan@gmail.com \
--cc=dmitry.torokhov@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®