Messages in this thread | | | Subject | Re: oops pauser. | From | Alan Cox <> | Date | Fri, 06 Jan 2006 13:31:10 +0000 |
| |
On Iau, 2006-01-05 at 15:52 -0500, Dave Jones wrote: > The huge number of oopses never hit the logs. > They either hit early in boot before syslog is even running, or > they kill the box.
So you don't need a two minute delay for those because as you said it froze the box > > > and continuing generally will hang the box > > stopping the scroll keys being used or dmesg being used to get the data > > out. > > This is exactly the problem this patch addresses. > The 'scroll keys' do not work in cases where we lock up after an oops.
And in those cases the 2 minute freeze is meaningless
> The real-world disagrees with you. In the few weeks it's been in Fedora, > several previously undiagnosable oopses were caught, and even *users* > agreed it was a useful addition. If the two minutes is excessive, we can > lower it, or even make it a boot-option.
Any change will capture different oopses. A boot option isnt a bad idea, or for that matter also truncating the call trace to the *top* few (or as Bryce suggested on irc reversing the printing order)
> Another possibility is instantly continuing after a keypress.
If the input layer is running that would be sensible.
> > The console has awareness of graphic/text mode at all times and knows > > what is going on. Why not use that information if you must go this way ? > > If we've just oopsed, the console may have no awareness of what day it is, > yet alone anything about video modes. I'm not entirely sure what you're > suggesting, but it gives me the creeps. Are you talking about switching > away from X back to a tty when we oops?
Well you could try and do that but I was more thinking that if the console has been told we are in graphics mode then the 2 minute delay shouldn't occur.
Alan
- 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/
| |