Bug 83971

Summary:	improve "fixing recursive fault but reboot is needed" message
Product:	Other	Reporter:	Dan Jacobson (jidanni)
Component:	Other	Assignee:	other_other
Status:	NEW ---
Severity:	normal
Priority:	P1
Hardware:	All
OS:	Linux
Kernel Version:	3.14	Subsystem:
Regression:	No	Bisected commit-id:

Description Dan Jacobson 2014-09-06 11:17:39 UTC

The user boots or reboots.

The user might see
 'Error “fixing recursive fault but reboot is needed”'
upon which the system stops. His panic=33 parameter is ignored, as this
is not a panic.

The user wonders: didn't I just (re)boot? What magic has been repaired
that will now work better if I boot yet again?

The user obediently reboots, and indeed the boot goes fine.

Problems: probably nothing has actually been fixed that will be
remembered through a reboot. Therefore the message should be improved.

In actual practice other factors are at work. It may take a few reboots
until the message goes away and one can finally fully boot up.
It would be good to mention the other factors found.

If something has really been repaired, can there please be found a way
to then let the boot proceed. Imagine if the user gets these every boot
and never can get in.

Also note bug 83961, to ensure the stack trace is not shoving whatever
rest of the message there was off of the screen!

Yes, the message appears at times other than a boot/reboot. But for when it does, it is confusing.