Messages in this thread | | | Date | Sun, 30 Mar 2003 16:38:08 -0800 (PST) | Subject | Re: 2.5.59: Input subsystem initialised really late | From | "Randy.Dunlap" <> |
| |
on 18-jan-2003 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? ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ and Vojtech replied: I think this should be possible, yes. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Any updates to this? Any clues?
I have changed 5 module_inits to be run a little earlier in the initcall sequence (the 5 being: atkbd_init, kbd_init, serio_init, input_init, and chr_dev_init). However, this still isn't enough to allow keyboard input (like ctrl-S, ctrl-Q, SysRq) during init messages as can be done with 2.4.20.
Thanks, ~Randy
- 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/
| |