Re: [PATCH] powernv/hmi: Use the "unknown" checkstop type as a fallback

[PATCH] powernv/hmi: Use the "unknown" checkstop type as a fallback · Russell Currey <hidden> · 2016-03-15
Re: [PATCH] powernv/hmi: Use the "unknown" checkstop type as a fallback · Daniel Axtens <hidden> · 2016-03-15
Re: [PATCH] powernv/hmi: Use the "unknown" checkstop type as a fallback · Andrew Donnellan <hidden> · 2016-03-15
Re: [PATCH] powernv/hmi: Use the "unknown" checkstop type as a fallback · Russell Currey <hidden> · 2016-03-15
Re: [PATCH] powernv/hmi: Use the "unknown" checkstop type as a fallback · Andrew Donnellan <hidden> · 2016-03-15
Re: [PATCH] powernv/hmi: Use the "unknown" checkstop type as a fallback · Russell Currey <hidden> · 2016-03-15
Re: [PATCH] powernv/hmi: Use the "unknown" checkstop type as a fallback · Michael Ellerman <mpe@ellerman.id.au> · 2016-03-15

From: Andrew Donnellan <hidden>
Date: 2016-03-15 05:37:23

On 15/03/16 16:15, Russell Currey wrote:

quoted

Would it be useful to print xstop_type in the unknown case?

I don't think so - if there's a new checkstop type, specific handling for
it should be implemented in the kernel, and if you're getting unknown
checkstops that are bringing down your machine you should be looking at the
OPAL firmware log anyway, which would contain details if there was
something "new".

That's fair, would primarily help debugging in the rather corner case of 
new skiboot, old kernel, and no access to the OPAL log...

-- 
Andrew Donnellan              Software Engineer, OzLabs
andrew.donnellan@au1.ibm.com  Australia Development Lab, Canberra
+61 2 6201 8874 (work)        IBM Australia Limited

`h`	back out one level
`j`	next message in thread
`k`	previous message in thread
`l`	drill in
`Esc`	close help / fold thread tree
`?`	toggle this help