From: "Maciej W. Rozycki" <macro@linux-mips.org>
To: Bob Tracy <rct@gherkin.frus.com>
Cc: linux-kernel@vger.kernel.org, debian-alpha@lists.debian.org,
mcree@orcon.net.nz, jay.estabrook@gmail.com, mattst88@gmail.com
Subject: Re: [BUG] machine check Oops on Alpha
Date: Wed, 20 Apr 2016 01:46:13 +0100 (BST) [thread overview]
Message-ID: <alpine.LFD.2.20.1604200125480.28036@eddie.linux-mips.org> (raw)
In-Reply-To: <20160419235657.GA4404@gherkin.frus.com>
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
next prev parent reply other threads:[~2016-04-20 0:46 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-17 21:05 Bob Tracy
2016-04-18 1:32 ` Maciej W. Rozycki
2016-04-18 3:58 ` Bob Tracy
2016-04-18 12:31 ` Bob Tracy
2016-04-18 13:47 ` Maciej W. Rozycki
2016-04-19 2:52 ` Bob Tracy
2016-04-19 23:56 ` Bob Tracy
2016-04-20 0:46 ` Maciej W. Rozycki [this message]
2016-04-20 3:57 ` Bob Tracy
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.LFD.2.20.1604200125480.28036@eddie.linux-mips.org \
--to=macro@linux-mips.org \
--cc=debian-alpha@lists.debian.org \
--cc=jay.estabrook@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mattst88@gmail.com \
--cc=mcree@orcon.net.nz \
--cc=rct@gherkin.frus.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome