[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20110301180429.GD27560@core.coreip.homeip.net>
Date: Tue, 1 Mar 2011 10:04:29 -0800
From: Dmitry Torokhov <dmitry.torokhov@...il.com>
To: Alexey Dobriyan <adobriyan@...il.com>
Cc: linux-kernel@...r.kernel.org
Subject: Re: 2.6.38-rc6: SysRq broken?
On Tue, Mar 01, 2011 at 12:04:47AM +0200, Alexey Dobriyan wrote:
> On Mon, Feb 28, 2011 at 01:57:21PM -0800, Dmitry Torokhov wrote:
> > On Monday, February 28, 2011 01:40:54 pm Alexey Dobriyan 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".
> >
> > What does /proc/bus/input/devices show?
>
>
> I: Bus=0003 Vendor=046d Product=c30e Version=0110
> N: Name="Logitech HID compliant keyboard"
> P: Phys=usb-0000:00:1d.0-1.2/input0
> S: Sysfs=/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.2/2-1.2:1.0/input/input3
> U: Uniq=
> H: Handlers=sysrq kbd event3
> B: PROP=0
> B: EV=120013
> B: KEY=1000000000007 ff800000000007ff febeffdff3cfffff fffffffffffffffe
> B: MSC=10
> B: LED=7
>
Hmm, looks like we bound sysrq handler here and the device has both alt
and SysRq keys. Is it only help that is not working? What abouth other
functions (reboot, etc)?
--
Dmitry
--
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/
Powered by blists - more mailing lists