linux-kernel - Re: [BUG] machine check Oops on Alpha

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <alpine.LFD.2.20.1604200125480.28036@eddie.linux-mips.org>
Date:	Wed, 20 Apr 2016 01:46:13 +0100 (BST)
From:	"Maciej W. Rozycki" <macro@...ux-mips.org>
To:	Bob Tracy <rct@...rkin.frus.com>
cc:	linux-kernel@...r.kernel.org, debian-alpha@...ts.debian.org,
	mcree@...on.net.nz, jay.estabrook@...il.com, mattst88@...il.com
Subject: Re: [BUG] machine check Oops on Alpha

On Tue, 19 Apr 2016, Bob Tracy wrote:

> > 4.6.0-rc4 build complete, including suggested (by Alan Young) "Verbose
> > Machine Checks" option set to level 2 by default.  System rebooted, and
> > now we wait...  Thanks for everyone's continued patience.
> 
> Within three minutes of rebooting, I got a machine check, but perhaps
> significantly, no "Oops".  I'm guessing the only reason I'm seeing the
> ECC errors now (haven't seen them before) is because of the stepped-up
> debug output.  Syslog output attached...

 If this is a code generation bug, which I now suspect even more highly 
than before, then the debug verbosity configuration change may well have 
made the compiler behave indeed.  As you can see from the log the logout 
area pointer is not null:

machine check: LA: fffffc0000006000

(of course the lone insertion of this `printk' call may have covered the 
bug, regardless of the debug verbosity change).  Consequently further 
information is printed -- the:

CIA machine check: vector=0x630 pc=0xfffffc00005b66ac code=0x86

line would have been printed anyway -- in fact the Oops previously 
happened in an attempt to retrieve `code' to print with this line.

 I can see if I can find anything suspicious there if you send me original 
copies (i.e. those that oopsed) of arch/alpha/kernel/irq_alpha.o and 
arch/alpha/kernel/core_cia.o.

> Machine has been stable since the machine check.  Kernel is 4.6.0-rc4.

 Yeah, it was a correctable error after all.

  Maciej