From: "Beschorner Daniel" <Daniel.Beschorner@facton.com>
To: "Suresh Siddha" <suresh.b.siddha@intel.com>,
"Ingo Molnar" <mingo@elte.hu>
Cc: "Andrew Morton" <akpm@linux-foundation.org>,
"Arjan van de Ven" <arjan@infradead.org>,
"Pallipadi, Venkatesh" <venkatesh.pallipadi@intel.com>,
"Yinghai Lu" <yinghai@kernel.org>,
"Thomas Gleixner" <tglx@linutronix.de>,
"H. Peter Anvin" <hpa@zytor.com>,
"Rafael J. Wysocki" <rjw@sisk.pl>, <spender@grsecurity.net>,
<pageexec@freemail.hu>, <linux-kernel@vger.kernel.org>
Subject: Re: Fw: hwinfo problem since 2.6.28
Date: Sat, 10 Jan 2009 00:09:54 +0100 [thread overview]
Message-ID: <3C59DB883F7B0B4D8096010D45ACCD13C73ECC@exch.facton.local> (raw)
In-Reply-To: <20090109222552.GB6472@linux-os.sc.intel.com>
> > > Since 2.6.28 my hwinfo tool crashes badly on 2 years old
> OpenSuSE 10.2
> > > x64/SMP.
> > > Older kernels run fine, I did a "make oldconfig" and rather used
> > > defaults (just skipping low-64k checks).
> > > This seems to be the only affected binary as far I can see.
> > > Did I miss a new legacy/compat option or is it a bug?
> > >
> > > Thank you!
> > > Daniel
> > >
> > > hwinfo: Corrupted page table at address 7fd04de3ec00
> > > PGD 7dc33067 PUD 3efe067 PMD 27b83067 PTE fffffffffffffbff
> > > Bad pagetable: 000d [#9] SMP
>
> Daniel, Can you please check and ack if the appended patch fixes this
> page table corruption issue? We tried to reproduce your issue
> locally here but didn't succeed because of different hwinfo versions.
>
> thanks,
> suresh
> ---
Works great! hwinfo runs fine again.
Thank you!
Daniel
prev parent reply other threads:[~2009-01-09 23:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20090108015424.e9443521.akpm@linux-foundation.org>
[not found] ` <20090108112543.GA25606@elte.hu>
2009-01-09 22:25 ` Suresh Siddha
2009-01-09 23:09 ` Beschorner Daniel [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=3C59DB883F7B0B4D8096010D45ACCD13C73ECC@exch.facton.local \
--to=daniel.beschorner@facton.com \
--cc=akpm@linux-foundation.org \
--cc=arjan@infradead.org \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=pageexec@freemail.hu \
--cc=rjw@sisk.pl \
--cc=spender@grsecurity.net \
--cc=suresh.b.siddha@intel.com \
--cc=tglx@linutronix.de \
--cc=venkatesh.pallipadi@intel.com \
--cc=yinghai@kernel.org \
/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
all inboxes | Powered by JetHome®