mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Yinghai Lu" <yinghai@kernel.org>
To: "Beschorner Daniel" <Daniel.Beschorner@facton.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: hwinfo problem since 2.6.28
Date: Thu, 8 Jan 2009 02:03:04 -0800	[thread overview]
Message-ID: <86802c440901080203m221def59qf1cd9fa3d017fd38@mail.gmail.com> (raw)
In-Reply-To: <3C59DB883F7B0B4D8096010D45ACCD13C73EA2@exch.facton.local>

On Tue, Jan 6, 2009 at 12:53 AM, Beschorner Daniel
<Daniel.Beschorner@facton.com> wrote:
> 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
> last sysfs file: /sys/devices/pci0000:00/0000:00:1e.0/0000:06:05.0/class
> CPU 0
> Modules linked in:
> Pid: 13700, comm: hwinfo Tainted: G      D    2.6.28 #7
> RIP: 0033:[<00007fd04d66f7f2>]  [<00007fd04d66f7f2>] 0x7fd04d66f7f2
> RSP: 002b:00007fff55ed2c68  EFLAGS: 00010202
> RAX: 00000000015d1fb0 RBX: 0000000000001000 RCX: fefefefefefefeff
> RDX: 0000000000000001 RSI: 00007fd04de3ec00 RDI: 00000000015d1fb0
> RBP: 000000000009fc00 R08: ffffffffff000000 R09: 00007fd04d6fbd60
> R10: ffffffffffffffff R11: 0000000000000000 R12: 00007fd04d9a72f6
> R13: 000000000009f000 R14: 0000000000000003 R15: 00000000015b4010
> FS:  00007fd04dec06f0(0000) GS:ffffffff80619540(0000)
> knlGS:0000000000000000
> CS:  0010 DS: 0000 ES: 0000 CR0: 000000008005003b
> CR2: 00007fd04de3ec00 CR3: 000000007de55000 CR4: 00000000000006e0
> DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
> DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
> Process hwinfo (pid: 13700, threadinfo ffff88007dff2000, task
> ffff88007ed934a0)
>
> RIP  [<00007fd04d66f7f2>] 0x7fd04d66f7f2
>  RSP <00007fff55ed2c68>
> ---[ end trace 742092d3bead57cc ]---
>

bootlog with debug in command line?

YH

  reply	other threads:[~2009-01-08 10:03 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <Aclv3DYqPGwhSzk9Qg22IVoJDubF+w==>
2009-01-06  8:53 ` Beschorner Daniel
2009-01-08 10:03   ` Yinghai Lu [this message]
2009-01-08 17:41     ` Beschorner Daniel

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=86802c440901080203m221def59qf1cd9fa3d017fd38@mail.gmail.com \
    --to=yinghai@kernel.org \
    --cc=Daniel.Beschorner@facton.com \
    --cc=linux-kernel@vger.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®