vt/console: try harder to print output when panicing

From: Jesse Barnes <[email protected]>

Jesse's initial patch commit said:

"At panic time (i.e. when oops_in_progress is set) we should try a bit harder to update the screen and make sure output gets to the VT, since some drivers are capable of flipping back to it.

So make sure we try to unblank and update the display if called from a panic context."

I've enhanced this to add a flag to the vc that console layer can set to indicate they want this behaviour to occur. This also adds support to fbcon for that flag and adds an fb flag for drivers to indicate they want to use the support. It enables this for KMS drivers.

Signed-off-by Dave Airlie <[email protected]>

---

From: Jesse Barnes <[email protected]>

Jesse's initial patch commit said:

"At panic time (i.e. when oops_in_progress is set) we should try a bit harder to update the screen and make sure output gets to the VT, since some drivers are capable of flipping back to it.

So make sure we try to unblank and update the display if called from a panic context."

I've enhanced this to add a flag to the vc that console layer can set to indicate they want this behaviour to occur. This also adds support to fbcon for that flag and adds an fb flag for drivers to indicate they want to use the support. It enables this for KMS drivers.

Signed-off-by Dave Airlie <[email protected]>

---

From: Jesse Barnes <[email protected]>

Jesse's initial patch commit said:

"At panic time (i.e. when oops_in_progress is set) we should try a bit harder to update the screen and make sure output gets to the VT, since some drivers are capable of flipping back to it.

So make sure we try to unblank and update the display if called from a panic context."

I've enhanced this to add a flag to the vc that console layer can set to indicate they want this behaviour to occur. This also adds support to fbcon for that flag and adds an fb flag for drivers to indicate they want to use the support. It enables this for KMS drivers.

Signed-off-by Dave Airlie <[email protected]>

---
 drivers/char/vt.c                       |   13 +++++++++----
 drivers/gpu/drm/i915/intel_fb.c         |    4 +---
 drivers/gpu/drm/nouveau/nouveau_fbcon.c |    1 +
 drivers/gpu/drm/radeon/radeon_fb.c      |    2 +-
 drivers/video/console/fbcon.c           |    4 +++-
 include/linux/console_struct.h          |    1 +
 include/linux/fb.h                      |    4 ++++
 include/linux/vt_kern.h                 |    7 +++++++
 8 files changed, 27 insertions(+), 9 deletions(-)

drivers/char/vt.c +9 -4

index 7cdb6ee..6e04c9e 100644
@@ -698,7 +698,10 @@ void redraw_screen(struct vc_data *vc, int is_switch)
 			update_attr(vc);
 			clear_buffer_attributes(vc);
 		}
-		if (update && vc->vc_mode != KD_GRAPHICS)
+
+		/* Forcibly update if we're panicing */
+		if ((update && vc->vc_mode != KD_GRAPHICS) ||
+		    vt_force_oops_output(vc))
 			do_update_region(vc, vc->vc_origin, vc->vc_screenbuf_size / 2);
 	}
 	set_cursor(vc);

@@ -736,6 +739,7 @@ static void visual_init(struct vc_data *vc, int num, int init)
 	vc->vc_hi_font_mask = 0;
 	vc->vc_complement_mask = 0;
 	vc->vc_can_do_color = 0;
+	vc->vc_panic_force_write = false;
 	vc->vc_sw->con_init(vc, init);
 	if (!vc->vc_complement_mask)
 		vc->vc_complement_mask = vc->vc_can_do_color ? 0x7700 : 0x0800;

@@ -2498,7 +2502,7 @@ static void vt_console_print(struct console *co, const char *b, unsigned count)
 		goto quit;
 	}
 
-	if (vc->vc_mode != KD_TEXT)
+	if (vc->vc_mode != KD_TEXT && !vt_force_oops_output(vc))
 		goto quit;
 
 	/* undraw cursor first */

@@ -3703,7 +3707,8 @@ void do_unblank_screen(int leaving_gfx)
 		return;
 	}
 	vc = vc_cons[fg_console].d;
-	if (vc->vc_mode != KD_TEXT)
+	/* Try to unblank in oops case too */
+	if (vc->vc_mode != KD_TEXT && !vt_force_oops_output(vc))
 		return; /* but leave console_blanked != 0 */
 
 	if (blankinterval) {

@@ -3712,7 +3717,7 @@ void do_unblank_screen(int leaving_gfx)
 	}
 
 	console_blanked = 0;
-	if (vc->vc_sw->con_blank(vc, 0, leaving_gfx))
+	if (vc->vc_sw->con_blank(vc, 0, leaving_gfx) || vt_force_oops_output(vc))
 		/* Low-level driver cannot restore -> do it ourselves */
 		update_screen(vc);
 	if (console_blank_hook)

drivers/gpu/drm/i915/intel_fb.c +1 -3

index c3c5052..bd5d87a 100644
@@ -128,7 +128,7 @@ static int intelfb_create(struct intel_fbdev *ifbdev,
 
 	strcpy(info->fix.id, "inteldrmfb");
 
-	info->flags = FBINFO_DEFAULT;
+	info->flags = FBINFO_DEFAULT | FBINFO_CAN_FORCE_OUTPUT;
 	info->fbops = &intelfb_ops;
 
 	/* setup aperture base/size for vesafb takeover */

@@ -146,8 +146,6 @@ static int intelfb_create(struct intel_fbdev *ifbdev,
 	info->fix.smem_start = dev->mode_config.fb_base + obj_priv->gtt_offset;
 	info->fix.smem_len = size;
 
-	info->flags = FBINFO_DEFAULT;
-
 	info->screen_base = ioremap_wc(dev->agp->base + obj_priv->gtt_offset,
 				       size);
 	if (!info->screen_base) {

drivers/gpu/drm/nouveau/nouveau_fbcon.c +1 -0

index c9a4a0d..9b2d3b7 100644
@@ -250,6 +250,7 @@ nouveau_fbcon_create(struct nouveau_fbdev *nfbdev,
 		info->flags = FBINFO_DEFAULT | FBINFO_HWACCEL_COPYAREA |
 			      FBINFO_HWACCEL_FILLRECT |
 			      FBINFO_HWACCEL_IMAGEBLIT;
+	info->flags |= FBINFO_CAN_FORCE_OUTPUT;
 	info->fbops = &nouveau_fbcon_ops;
 	info->fix.smem_start = dev->mode_config.fb_base + nvbo->bo.offset -
 			       dev_priv->vm_vram_base;

drivers/gpu/drm/radeon/radeon_fb.c +1 -1

index dc1634b..dbf8696 100644
@@ -224,7 +224,7 @@ static int radeonfb_create(struct radeon_fbdev *rfbdev,
 
 	drm_fb_helper_fill_fix(info, fb->pitch, fb->depth);
 
-	info->flags = FBINFO_DEFAULT;
+	info->flags = FBINFO_DEFAULT | FBINFO_CAN_FORCE_OUTPUT;
 	info->fbops = &radeonfb_ops;
 
 	tmp = radeon_bo_gpu_offset(rbo) - rdev->mc.vram_start;

drivers/video/console/fbcon.c +3 -1

index b0a3fa0..7eadb35 100644
@@ -283,7 +283,8 @@ static inline int fbcon_is_inactive(struct vc_data *vc, struct fb_info *info)
 	struct fbcon_ops *ops = info->fbcon_par;
 
 	return (info->state != FBINFO_STATE_RUNNING ||
-		vc->vc_mode != KD_TEXT || ops->graphics);
+		vc->vc_mode != KD_TEXT || ops->graphics) &&
+		!vt_force_oops_output(vc);
 }
 
 static inline int get_color(struct vc_data *vc, struct fb_info *info,

@@ -1073,6 +1074,7 @@ static void fbcon_init(struct vc_data *vc, int init)
 	if (p->userfont)
 		charcnt = FNTCHARCNT(p->fontdata);
 
+	vc->vc_panic_force_write = !!(info->flags & FBINFO_CAN_FORCE_OUTPUT);
 	vc->vc_can_do_color = (fb_get_color_depth(&info->var, &info->fix)!=1);
 	vc->vc_complement_mask = vc->vc_can_do_color ? 0x7700 : 0x0800;
 	if (charcnt = 256) {

include/linux/console_struct.h +1 -0

index 38fe59d..d7d9acd 100644
@@ -105,6 +105,7 @@ struct vc_data {
 	struct vc_data **vc_display_fg;		/* [!] Ptr to var holding fg console for this display */
 	unsigned long	vc_uni_pagedir;
 	unsigned long	*vc_uni_pagedir_loc;  /* [!] Location of uni_pagedir variable for this console */
+	bool vc_panic_force_write; /* when oops/panic this VC can accept forced output/blanking */
 	/* additional information is in vt_kern.h */
 };
 

include/linux/fb.h +4 -0

index 8e5a9df..25f4950 100644
@@ -812,6 +812,10 @@ struct fb_tile_ops {
  */
 #define FBINFO_BE_MATH  0x100000
 
+/* report to the VT layer that this fb driver can accept forced console
+   output like oopses */
+#define FBINFO_CAN_FORCE_OUTPUT     0x200000
+
 struct fb_info {
 	int node;
 	int flags;

include/linux/vt_kern.h +7 -0

index 7f56db4..56cce34 100644
@@ -100,6 +100,13 @@ extern int unbind_con_driver(const struct consw *csw, int first, int last,
 			     int deflt);
 int vty_init(const struct file_operations *console_fops);
 
+static inline bool vt_force_oops_output(struct vc_data *vc)
+{
+	if (oops_in_progress && vc->vc_panic_force_write)
+		return true;
+	return false;
+}
+
 /*
  * vc_screen.c shares this temporary buffer with the console write code so that
  * we can easily avoid touching user space while holding the console spinlock.

Signature · 6 lines

1.7.1

--
To unsubscribe from this list: send the line "unsubscribe linux-fbdev" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html

From: Jesse Barnes <[email protected]>

Jesse's initial patch commit said:

"At panic time (i.e. when oops_in_progress is set) we should try a bit harder to update the screen and make sure output gets to the VT, since some drivers are capable of flipping back to it.

So make sure we try to unblank and update the display if called from a panic context."

I've enhanced this to add a flag to the vc that console layer can set to indicate they want this behaviour to occur. This also adds support to fbcon for that flag and adds an fb flag for drivers to indicate they want to use the support. It enables this for KMS drivers.

Signed-off-by Dave Airlie <[email protected]>

---
 drivers/char/vt.c                       |   13 +++++++++----
 drivers/gpu/drm/i915/intel_fb.c         |    4 +---
 drivers/gpu/drm/nouveau/nouveau_fbcon.c |    1 +
 drivers/gpu/drm/radeon/radeon_fb.c      |    2 +-
 drivers/video/console/fbcon.c           |    4 +++-
 include/linux/console_struct.h          |    1 +
 include/linux/fb.h                      |    4 ++++
 include/linux/vt_kern.h                 |    7 +++++++
 8 files changed, 27 insertions(+), 9 deletions(-)

drivers/char/vt.c +9 -4

index 7cdb6ee..6e04c9e 100644
@@ -698,7 +698,10 @@ void redraw_screen(struct vc_data *vc, int is_switch)
 			update_attr(vc);
 			clear_buffer_attributes(vc);
 		}
-		if (update && vc->vc_mode != KD_GRAPHICS)
+
+		/* Forcibly update if we're panicing */
+		if ((update && vc->vc_mode != KD_GRAPHICS) ||
+		    vt_force_oops_output(vc))
 			do_update_region(vc, vc->vc_origin, vc->vc_screenbuf_size / 2);
 	}
 	set_cursor(vc);

@@ -736,6 +739,7 @@ static void visual_init(struct vc_data *vc, int num, int init)
 	vc->vc_hi_font_mask = 0;
 	vc->vc_complement_mask = 0;
 	vc->vc_can_do_color = 0;
+	vc->vc_panic_force_write = false;
 	vc->vc_sw->con_init(vc, init);
 	if (!vc->vc_complement_mask)
 		vc->vc_complement_mask = vc->vc_can_do_color ? 0x7700 : 0x0800;

@@ -2498,7 +2502,7 @@ static void vt_console_print(struct console *co, const char *b, unsigned count)
 		goto quit;
 	}
 
-	if (vc->vc_mode != KD_TEXT)
+	if (vc->vc_mode != KD_TEXT && !vt_force_oops_output(vc))
 		goto quit;
 
 	/* undraw cursor first */

@@ -3703,7 +3707,8 @@ void do_unblank_screen(int leaving_gfx)
 		return;
 	}
 	vc = vc_cons[fg_console].d;
-	if (vc->vc_mode != KD_TEXT)
+	/* Try to unblank in oops case too */
+	if (vc->vc_mode != KD_TEXT && !vt_force_oops_output(vc))
 		return; /* but leave console_blanked != 0 */
 
 	if (blankinterval) {

@@ -3712,7 +3717,7 @@ void do_unblank_screen(int leaving_gfx)
 	}
 
 	console_blanked = 0;
-	if (vc->vc_sw->con_blank(vc, 0, leaving_gfx))
+	if (vc->vc_sw->con_blank(vc, 0, leaving_gfx) || vt_force_oops_output(vc))
 		/* Low-level driver cannot restore -> do it ourselves */
 		update_screen(vc);
 	if (console_blank_hook)

drivers/gpu/drm/i915/intel_fb.c +1 -3

index c3c5052..bd5d87a 100644
@@ -128,7 +128,7 @@ static int intelfb_create(struct intel_fbdev *ifbdev,
 
 	strcpy(info->fix.id, "inteldrmfb");
 
-	info->flags = FBINFO_DEFAULT;
+	info->flags = FBINFO_DEFAULT | FBINFO_CAN_FORCE_OUTPUT;
 	info->fbops = &intelfb_ops;
 
 	/* setup aperture base/size for vesafb takeover */

@@ -146,8 +146,6 @@ static int intelfb_create(struct intel_fbdev *ifbdev,
 	info->fix.smem_start = dev->mode_config.fb_base + obj_priv->gtt_offset;
 	info->fix.smem_len = size;
 
-	info->flags = FBINFO_DEFAULT;
-
 	info->screen_base = ioremap_wc(dev->agp->base + obj_priv->gtt_offset,
 				       size);
 	if (!info->screen_base) {

drivers/gpu/drm/nouveau/nouveau_fbcon.c +1 -0

index c9a4a0d..9b2d3b7 100644
@@ -250,6 +250,7 @@ nouveau_fbcon_create(struct nouveau_fbdev *nfbdev,
 		info->flags = FBINFO_DEFAULT | FBINFO_HWACCEL_COPYAREA |
 			      FBINFO_HWACCEL_FILLRECT |
 			      FBINFO_HWACCEL_IMAGEBLIT;
+	info->flags |= FBINFO_CAN_FORCE_OUTPUT;
 	info->fbops = &nouveau_fbcon_ops;
 	info->fix.smem_start = dev->mode_config.fb_base + nvbo->bo.offset -
 			       dev_priv->vm_vram_base;

drivers/gpu/drm/radeon/radeon_fb.c +1 -1

index dc1634b..dbf8696 100644
@@ -224,7 +224,7 @@ static int radeonfb_create(struct radeon_fbdev *rfbdev,
 
 	drm_fb_helper_fill_fix(info, fb->pitch, fb->depth);
 
-	info->flags = FBINFO_DEFAULT;
+	info->flags = FBINFO_DEFAULT | FBINFO_CAN_FORCE_OUTPUT;
 	info->fbops = &radeonfb_ops;
 
 	tmp = radeon_bo_gpu_offset(rbo) - rdev->mc.vram_start;

drivers/video/console/fbcon.c +3 -1

index b0a3fa0..7eadb35 100644
@@ -283,7 +283,8 @@ static inline int fbcon_is_inactive(struct vc_data *vc, struct fb_info *info)
 	struct fbcon_ops *ops = info->fbcon_par;
 
 	return (info->state != FBINFO_STATE_RUNNING ||
-		vc->vc_mode != KD_TEXT || ops->graphics);
+		vc->vc_mode != KD_TEXT || ops->graphics) &&
+		!vt_force_oops_output(vc);
 }
 
 static inline int get_color(struct vc_data *vc, struct fb_info *info,

@@ -1073,6 +1074,7 @@ static void fbcon_init(struct vc_data *vc, int init)
 	if (p->userfont)
 		charcnt = FNTCHARCNT(p->fontdata);
 
+	vc->vc_panic_force_write = !!(info->flags & FBINFO_CAN_FORCE_OUTPUT);
 	vc->vc_can_do_color = (fb_get_color_depth(&info->var, &info->fix)!=1);
 	vc->vc_complement_mask = vc->vc_can_do_color ? 0x7700 : 0x0800;
 	if (charcnt == 256) {

include/linux/console_struct.h +1 -0

index 38fe59d..d7d9acd 100644
@@ -105,6 +105,7 @@ struct vc_data {
 	struct vc_data **vc_display_fg;		/* [!] Ptr to var holding fg console for this display */
 	unsigned long	vc_uni_pagedir;
 	unsigned long	*vc_uni_pagedir_loc;  /* [!] Location of uni_pagedir variable for this console */
+	bool vc_panic_force_write; /* when oops/panic this VC can accept forced output/blanking */
 	/* additional information is in vt_kern.h */
 };
 

include/linux/fb.h +4 -0

index 8e5a9df..25f4950 100644
@@ -812,6 +812,10 @@ struct fb_tile_ops {
  */
 #define FBINFO_BE_MATH  0x100000
 
+/* report to the VT layer that this fb driver can accept forced console
+   output like oopses */
+#define FBINFO_CAN_FORCE_OUTPUT     0x200000
+
 struct fb_info {
 	int node;
 	int flags;

include/linux/vt_kern.h +7 -0

index 7f56db4..56cce34 100644
@@ -100,6 +100,13 @@ extern int unbind_con_driver(const struct consw *csw, int first, int last,
 			     int deflt);
 int vty_init(const struct file_operations *console_fops);
 
+static inline bool vt_force_oops_output(struct vc_data *vc)
+{
+	if (oops_in_progress && vc->vc_panic_force_write)
+		return true;
+	return false;
+}
+
 /*
  * vc_screen.c shares this temporary buffer with the console write code so that
  * we can easily avoid touching user space while holding the console spinlock.

Signature · 6 lines

1.7.1

--
To unsubscribe from this list: send the line "unsubscribe linux-fbdev" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Jesse's initial patch commit said:

"At panic time (i.e. when oops_in_progress is set) we should try a bit harder to update the screen and make sure output gets to the VT, since some drivers are capable of flipping back to it.

So make sure we try to unblank and update the display if called from a panic context."

I've enhanced this to add a flag to the vc that console layer can set to indicate they want this behaviour to occur. This also adds support to fbcon for that flag and adds an fb flag for drivers to indicate they want to use the support. It enables this for KMS drivers.

Quoted 6 lines · On Wed, 23 Jun 2010 13:12:59 +1000 Dave Airlie <[email protected]> wrote:

Jesse's initial patch commit said:

"At panic time (i.e. when oops_in_progress is set) we should try a bit harder to update the screen and make sure output gets to the VT, since some drivers are capable of flipping back to it.

Quoted 7 lines

So make sure we try to unblank and update the display if called from a panic context."

I've enhanced this to add a flag to the vc that console layer can set to indicate they want this behaviour to occur. This also adds support to fbcon for that flag and adds an fb flag for drivers to indicate they want to use the support. It enables this for KMS drivers.

Interesting. Getting real oops traces from machines running X will make Rusty happy, and that's what we're all here for.

How well does this all work? How reliable is it? What's the success rate?

What's the downside here? After all, not all oopses are catastrophic - sometimes the machine will go blurt and keep running so the user can take a look in the logs then perform an orderly reboot, etc. As I understand it, those non-catastrophic oopses will now flip the machine from X and into the vt display, yes? Can the user get it back to X mode?

Worse, there's also a risk that doing all this new work within the oopsing context will screw the machine up, so the user will be _deprived_ of an oops report which he otherwise would have been able to get from the logs. This is particularly the case when it's the DRI stuff which oopsed, which is not exactly an uncommon occurrence lately ;)

Oh well, the best way to tell is to ship-it-and-see.

Quoted 24 lines · On Wed, 23 Jun 2010 12:56:05 -0700 Andrew Morton <[email protected]>…

Quoted 6 lines · On Wed, 23 Jun 2010 13:12:59 +1000 Dave Airlie <[email protected]> wrote:

Jesse's initial patch commit said:

"At panic time (i.e. when oops_in_progress is set) we should try a bit harder to update the screen and make sure output gets to the VT, since some drivers are capable of flipping back to it.

Quoted 7 lines

So make sure we try to unblank and update the display if called from a panic context."

I've enhanced this to add a flag to the vc that console layer can set to indicate they want this behaviour to occur. This also adds support to fbcon for that flag and adds an fb flag for drivers to indicate they want to use the support. It enables this for KMS drivers.

Interesting. Getting real oops traces from machines running X will make Rusty happy, and that's what we're all here for.

How well does this all work? How reliable is it? What's the success rate?

Quoted 6 lines

What's the downside here? After all, not all oopses are catastrophic - sometimes the machine will go blurt and keep running so the user can take a look in the logs then perform an orderly reboot, etc. As I understand it, those non-catastrophic oopses will now flip the machine from X and into the vt display, yes? Can the user get it back to X mode?

No, we'll only flip from the panic notifier chain.

Quoted 34 lines · On Wed, 23 Jun 2010 13:05:47 -0700 Jesse Barnes <[email protected]>…

Quoted 30 lines · On Wed, 23 Jun 2010 12:56:05 -0700 Andrew Morton <[email protected]>…

Quoted 6 lines · On Wed, 23 Jun 2010 13:12:59 +1000 Dave Airlie <[email protected]> wrote:

Jesse's initial patch commit said:

"At panic time (i.e. when oops_in_progress is set) we should try a bit harder to update the screen and make sure output gets to the VT, since some drivers are capable of flipping back to it.

Quoted 7 lines

So make sure we try to unblank and update the display if called from a panic context."

I've enhanced this to add a flag to the vc that console layer can set to indicate they want this behaviour to occur. This also adds support to fbcon for that flag and adds an fb flag for drivers to indicate they want to use the support. It enables this for KMS drivers.

Interesting. Getting real oops traces from machines running X will make Rusty happy, and that's what we're all here for.

How well does this all work? How reliable is it? What's the success rate?

What's the downside here? After all, not all oopses are catastrophic - sometimes the machine will go blurt and keep running so the user can take a look in the logs then perform an orderly reboot, etc. As I understand it, those non-catastrophic oopses will now flip the machine from X and into the vt display, yes? Can the user get it back to X mode?

Quoted 1 line

No, we'll only flip from the panic notifier chain.

So we still don't get to see the output from BUGs and random oopses? I don't think panics are all that common.

So am I correct in believing that if a user is getting invisible-oopses then he can set /proc/sys/kernel/panic_on_oops, and then the oops should be visible?

(Shouldn't all this stuff be explained in the changlog?)

Quoted 34 lines · On Wed, 23 Jun 2010 13:05:47 -0700 Jesse Barnes <[email protected]>…

Quoted 30 lines · On Wed, 23 Jun 2010 12:56:05 -0700 Andrew Morton <[email protected]>…

Quoted 6 lines · On Wed, 23 Jun 2010 13:12:59 +1000 Dave Airlie <[email protected]> wrote:

Jesse's initial patch commit said:

"At panic time (i.e. when oops_in_progress is set) we should try a bit harder to update the screen and make sure output gets to the VT, since some drivers are capable of flipping back to it.

Quoted 7 lines

So make sure we try to unblank and update the display if called from a panic context."

I've enhanced this to add a flag to the vc that console layer can set to indicate they want this behaviour to occur. This also adds support to fbcon for that flag and adds an fb flag for drivers to indicate they want to use the support. It enables this for KMS drivers.

Interesting. Getting real oops traces from machines running X will make Rusty happy, and that's what we're all here for.

How well does this all work? How reliable is it? What's the success rate?

What's the downside here? After all, not all oopses are catastrophic - sometimes the machine will go blurt and keep running so the user can take a look in the logs then perform an orderly reboot, etc. As I understand it, those non-catastrophic oopses will now flip the machine from X and into the vt display, yes? Can the user get it back to X mode?

Quoted 1 line

No, we'll only flip from the panic notifier chain.

So we still don't get to see the output from BUGs and random oopses? I don't think panics are all that common.

So am I correct in believing that if a user is getting invisible-oopses then he can set /proc/sys/kernel/panic_on_oops, and then the oops should be visible?

(Shouldn't all this stuff be explained in the changlog?)

Quoted 24 lines · On Wed, 23 Jun 2010 12:56:05 -0700 Andrew Morton <[email protected]>…

Quoted 6 lines · On Wed, 23 Jun 2010 13:12:59 +1000 Dave Airlie <[email protected]> wrote:

Jesse's initial patch commit said:

"At panic time (i.e. when oops_in_progress is set) we should try a bit harder to update the screen and make sure output gets to the VT, since some drivers are capable of flipping back to it.

Quoted 7 lines

So make sure we try to unblank and update the display if called from a panic context."

I've enhanced this to add a flag to the vc that console layer can set to indicate they want this behaviour to occur. This also adds support to fbcon for that flag and adds an fb flag for drivers to indicate they want to use the support. It enables this for KMS drivers.

Interesting. Getting real oops traces from machines running X will make Rusty happy, and that's what we're all here for.

How well does this all work? How reliable is it? What's the success rate?

Quoted 6 lines

What's the downside here? After all, not all oopses are catastrophic - sometimes the machine will go blurt and keep running so the user can take a look in the logs then perform an orderly reboot, etc. As I understand it, those non-catastrophic oopses will now flip the machine from X and into the vt display, yes? Can the user get it back to X mode?

No, we'll only flip from the panic notifier chain.

Quoted 6 lines · On Wed, 23 Jun 2010 13:12:59 +1000 Dave Airlie <[email protected]> wrote:

Jesse's initial patch commit said:

"At panic time (i.e. when oops_in_progress is set) we should try a bit harder to update the screen and make sure output gets to the VT, since some drivers are capable of flipping back to it.

Quoted 7 lines

So make sure we try to unblank and update the display if called from a panic context."

I've enhanced this to add a flag to the vc that console layer can set to indicate they want this behaviour to occur. This also adds support to fbcon for that flag and adds an fb flag for drivers to indicate they want to use the support. It enables this for KMS drivers.

Interesting. Getting real oops traces from machines running X will make Rusty happy, and that's what we're all here for.

How well does this all work? How reliable is it? What's the success rate?

What's the downside here? After all, not all oopses are catastrophic - sometimes the machine will go blurt and keep running so the user can take a look in the logs then perform an orderly reboot, etc. As I understand it, those non-catastrophic oopses will now flip the machine from X and into the vt display, yes? Can the user get it back to X mode?

Worse, there's also a risk that doing all this new work within the oopsing context will screw the machine up, so the user will be _deprived_ of an oops report which he otherwise would have been able to get from the logs. This is particularly the case when it's the DRI stuff which oopsed, which is not exactly an uncommon occurrence lately ;)

Oh well, the best way to tell is to ship-it-and-see.

Jesse's initial patch commit said:

"At panic time (i.e. when oops_in_progress is set) we should try a bit harder to update the screen and make sure output gets to the VT, since some drivers are capable of flipping back to it.

So make sure we try to unblank and update the display if called from a panic context."

I've enhanced this to add a flag to the vc that console layer can set to indicate they want this behaviour to occur. This also adds support to fbcon for that flag and adds an fb flag for drivers to indicate they want to use the support. It enables this for KMS drivers.