lkml.org 
[lkml]   [2014]   [Apr]   [23]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [PATCH RFC] sysrq: rcu-ify __handle_sysrq
On Wed, 23 Apr 2014, Andrew Morton wrote:

> > > > Echoing values into /proc/sysrq-trigger seems to be a popular way to
> > > > get information out of the kernel. However, dumping information about
> > > > thousands of processes, or hundreds of CPUs to serial console can
> > > > result in IRQs being blocked for minutes, resulting in various kinds
> > > > of cascade failures.
> > > >
> > > > The most common failure is due to interrupts being blocked for a very
> > > > long time. This can lead to things like failed IO requests, and other
> > > > things the system cannot easily recover from.
> > >
> > > I bet nobody wants that console output anyway. You do the sysrq then
> > > run dmesg or look in /var/log/messages to see what happened. People
> > > who are experiencing problems such as this should run `dmesg -n 1'
> > > before writing to sysrq-trigger.
> >
> > I don't agree. I have used sysrq-t multiple times in situations where
> > userspace was already dead, but sysrq was still able to provide valuable
> > information about the state of the kernel.
> >
>
> I'm talking about /proc/sysrq-trigger, not the magic key combo.

At the end of the day, that reaches the same __handle_sysrq() codepath,
no?

--
Jiri Kosina
SUSE Labs


\
 
 \ /
  Last update: 2014-04-24 00:01    [W:0.107 / U:1.152 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site