From: Bob Tracy <rct@gherkin.frus.com>
To: "Maciej W. Rozycki" <macro@linux-mips.org>
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: Mon, 18 Apr 2016 07:31:36 -0500 [thread overview]
Message-ID: <20160418123136.GA30382@gherkin.frus.com> (raw)
In-Reply-To: <20160418035848.GA28637@gherkin.frus.com>
On Sun, Apr 17, 2016 at 10:58:48PM -0500, Bob Tracy wrote:
> On Mon, Apr 18, 2016 at 02:32:54AM +0100, Maciej W. Rozycki wrote:
> > I'd be tempted to run with the patch below to see what's the value of
> > `la_ptr' early on in processing (`entInt' code in entry.S looks sane to
> > me, doesn't touch a2). NB a rebuild doesn't have to be costly if you only
> > poke at a single file or a few which aren't e.g. headers included from
> > everywhere.
>
> Applied. Build started. Report to follow in a day or so: I've applied
> other patches to my kernel source tree in the meantime, so a full build
> is unavoidable at this point... I'll hold off applying any updates
> after this to minimize what must be rebuilt while this issue is being
> worked. Thank you for your time and trouble!
Build delayed slightly. Ran into "fs/binfmt_em86.o" build failure
patched by Daniel Wagner back in February (incompatible-pointer-types
warning treated as error by compiler). Is Daniel's patch queued for
incorporation into the main kernel source tree?
--Bob
next prev parent reply other threads:[~2016-04-18 12:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-17 21:05 [BUG] machine check Oops on Alpha Bob Tracy
2016-04-18 1:32 ` Maciej W. Rozycki
2016-04-18 3:58 ` Bob Tracy
2016-04-18 12:31 ` Bob Tracy [this message]
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
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=20160418123136.GA30382@gherkin.frus.com \
--to=rct@gherkin.frus.com \
--cc=debian-alpha@lists.debian.org \
--cc=jay.estabrook@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=macro@linux-mips.org \
--cc=mattst88@gmail.com \
--cc=mcree@orcon.net.nz \
/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;
as well as URLs for NNTP newsgroup(s).