On Monday 02 July 2007 13:43:23 Indan Zupancic wrote: > On Mon, July 2, 2007 01:59, Andi Kleen wrote: > > Well only those that could be already hung from user space > > with setleds (that was also confirmed). Actually I thought > > they didn't hang completely, but just stopped reacting to > > the keyboard (which is actually pretty bad for every user > > to be able to trigger) > > Pavel's lost key events, mine stopped reacting altogether.
Did you try if the network was still alive? Perhaps it was just a locked up keyboard. > > > I guess the better way to handle those would be to find out the > > minimum frequency of blinking that is still ok and rate limit it to that in > > the keyboard driver. > > Dmitry already has a patch for that. He limited it to one event each 50 ms. Great. > > > Anyways, Stephen's patch just doesn't make sense: > > he clearly didn't understand the code at all. Before you > > apply it and cripple it better drop the driver completely. > > CC'ing Dmitry, as I think he doesn't like the blink driver much either. ;-) Perhaps one of you geniuses who all hate it can find a better way to solve the "video output dead after kexec; but need visual feedback to the user while crash dumping" problem. I'm waiting for your patches. -Andi - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
