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] [day] [month] [year] [list]

Date:	Tue, 19 Apr 2016 22:57:58 -0500
From:	Bob Tracy <rct@...rkin.frus.com>
To:	"Maciej W. Rozycki" <macro@...ux-mips.org>
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 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