Re: 2.5.59: Input subsystem initialised really late

From: Vojtech Pavlik (vojtech@suse.cz)
Date: Sat Jan 18 2003 - 18:44:47 EST

Next message: Max Valdez: "Re: Why kernel 2.5.58 only mounts / (not home etc)"
Previous message: Andrew Morton: "Re: Why kernel 2.5.58 only mounts / (not home etc)"
In reply to: Russell King: "2.5.59: Input subsystem initialised really late"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

On Sat, Jan 18, 2003 at 04:56:51PM +0000, Russell King wrote:

> It appears to be impossible to get a SysRQ-T dump out of a kernel which
> has hung during (eg) the SCSI initialisation with 2.5.
>
> Unlike previous 2.4 kernels, the keyboard is no longer initialised until
> fairly late - after many of the other drivers have initialised.
> Unfortunately, this means that it is quite difficult to debug these hangs
> (we'll leave discussion about in-kernel debuggers for another time!)
>
> Can we initialise the input subsystem earlier (eg, after pci bus
> initialisation, before disks etc) so that we do have the ability to use
> the SysRQ features?

I think this should be possible, yes.

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

Next message: Max Valdez: "Re: Why kernel 2.5.58 only mounts / (not home etc)"
Previous message: Andrew Morton: "Re: Why kernel 2.5.58 only mounts / (not home etc)"
In reply to: Russell King: "2.5.59: Input subsystem initialised really late"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

This archive was generated by hypermail 2b29 : Thu Jan 23 2003 - 22:00:20 EST