On Thu, Mar 05, 2015 at 01:24:47AM +, Horiguchi Naoya(堀口 直也) wrote:
...
> > Is the "UC" entry at the end of the severities[] table just a catch-all for
> > things that made it
> > past all the other entries? Does it ever really get used?
>
> I read through the severity check table and it seem
On Wed, Mar 04, 2015 at 11:12:33PM +, Luck, Tony wrote:
> > - fixed AR and UC order in enum severity_level because UC is severer than AR
> > by definition. Current code is not affected by this wrong order by chance.
>
> AR and AO are both UC errors - that happen also to be recoverable. Are y
On Wed, Mar 04, 2015 at 11:12:33PM +, Luck, Tony wrote:
> > - fixed AR and UC order in enum severity_level because UC is severer than AR
> > by definition. Current code is not affected by this wrong order by chance.
>
> AR and AO are both UC errors - that happen also to be recoverable.
Maybe
> - fixed AR and UC order in enum severity_level because UC is severer than AR
> by definition. Current code is not affected by this wrong order by chance.
AR and AO are both UC errors - that happen also to be recoverable. Are you
really sure
about this re-order not affecting existing code? Yo
On Tue, Mar 03, 2015 at 06:09:27PM +, Luck, Tony wrote:
> +static void machine_check_under_kdump(struct pt_regs *regs, long error_code)
> +{
> + if (mca_cfg.kdump_cpu == smp_processor_id())
> + pr_emerg("MCE triggered when kdumping. If you are lucky enough,
> you will have a kd
5 matches
Mail list logo