From mboxrd@z Thu Jan 1 00:00:00 1970 From: Benjamin Herrenschmidt Subject: Re: [PATCH 1/3] Input: sysrq - drop tty argument from sysrq ops handlers Date: Thu, 05 Aug 2010 12:03:05 +1000 Message-ID: <1280973785.1902.167.camel@pasglop> References: <20100804075602.30647.91462.stgit@localhost.localdomain> <20100804075900.30647.46910.stgit@localhost.localdomain> <1280910830.1902.144.camel@pasglop> <4C59570F.7040201@windriver.com> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit Return-path: Received: from gate.crashing.org ([63.228.1.57]:36540 "EHLO gate.crashing.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1759439Ab0HECD3 (ORCPT ); Wed, 4 Aug 2010 22:03:29 -0400 In-Reply-To: <4C59570F.7040201@windriver.com> Sender: linux-input-owner@vger.kernel.org List-Id: linux-input@vger.kernel.org To: Jason Wessel Cc: Dmitry Torokhov , linux-input@vger.kernel.org, linux-kernel@vger.kernel.org, David Airlie , David Miller , Fenghua Yu , Greg Kroah-Hartman , Martin Schwidefsky , Russell King , Tony Luck On Wed, 2010-08-04 at 07:03 -0500, Jason Wessel wrote: > The usb serial has the same kind of problem with all sorts of locks. > I > had resorted to using a tasklet or workqueue to get the sysrq to > execute > just outside the usb serial driver context. This work never made it > upstream because it was part of another series, but the reference is: > http://lkml.org/lkml/2010/3/9/17 > > For the standard serial you might be able to get away with dropping > the > lock for the sysrq. > > Did you have a particular way to trigger the problem or was it just > completely random, because I don't know that I have observed this > behavior with the typical 8250 driver. Yes, I do actually :-) A 64-way machine and a bunch of processes flooding the console will do it just fine :-) Cheers, Ben.