2.5.59: Input subsystem initialised really late

From: Russell King (rmk@arm.linux.org.uk)
Date: Sat Jan 18 2003 - 11:56:51 EST

Next message: Russell King: "SCSI/Block boot problems"
Previous message: Russell King: "[PATCH] 2.5.59: show_task() oops"
Next in thread: Vojtech Pavlik: "Re: 2.5.59: Input subsystem initialised really late"
Reply: Vojtech Pavlik: "Re: 2.5.59: Input subsystem initialised really late"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

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?

--
Russell King (rmk@arm.linux.org.uk)                The developer of ARM Linux
             http://www.arm.linux.org.uk/personal/aboutme.html
-
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: Russell King: "SCSI/Block boot problems"
Previous message: Russell King: "[PATCH] 2.5.59: show_task() oops"
Next in thread: Vojtech Pavlik: "Re: 2.5.59: Input subsystem initialised really late"
Reply: Vojtech Pavlik: "Re: 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:19 EST