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: Tue, 19 Apr 2016 22:57:58 -0500 [thread overview]
Message-ID: <20160420035758.GA5015@gherkin.frus.com> (raw)
In-Reply-To: <alpine.LFD.2.20.1604200125480.28036@eddie.linux-mips.org>
On Wed, Apr 20, 2016 at 01:46:13AM +0100, Maciej W. Rozycki wrote:
> 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.
:-)
Regrettably, the constituent object files of the 4.5.0 kernel that was
generating the "Oopses" are no longer available. I *do* have the
"vmlinux.gz" image, the corresponding "System.map-4.5.0", and all the
related modules if those would be of any use. With a bit of guidance, I
could probably extract the desired objects from the kernel image.
Alternatively, if there's an upload location where I could leave you the
image and map files, that might work as well.
Pending your reply, I'll see if I can figure out how to dump/extract the
requested object code from the kernel image file.
--Bob
prev parent reply other threads:[~2016-04-20 3:58 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
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 [this message]
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=20160420035758.GA5015@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).