mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Yinghai Lu" <yhlu.kernel@gmail.com>
To: "Ingo Molnar" <mingo@elte.hu>
Cc: "Thomas Gleixner" <tglx@linutronix.de>,
	"H. Peter Anvin" <hpa@zytor.com>,
	"Andrew Morton" <akpm@linux-foundation.org>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] x86: order functions in cpu/common.c and cpu/common_64.c
Date: Thu, 4 Sep 2008 12:59:45 -0700	[thread overview]
Message-ID: <86802c440809041259i8982000yb0f68aeb2842caf0@mail.gmail.com> (raw)
In-Reply-To: <20080904194127.GA2542@elte.hu>

On Thu, Sep 4, 2008 at 12:41 PM, Ingo Molnar <mingo@elte.hu> wrote:
>
> * Ingo Molnar <mingo@elte.hu> wrote:
>
>> hm, something in your patch series is early-crashing tip/master with
>> this config:
>>
>>  http://redhat.com/~mingo/misc/config-Thu_Sep__4_21_23_20_CEST_2008.bad
>>
>> the early-RIP is 0xffffffff804365b0:
>>
>> ffffffff8043656a <proc_bus_pci_release>:
>>
>> ffffffff804365b0:       be d0 00 00 00          mov    $0xd0,%esi
>> ffffffff804365b5:       e8 ad 28 e7 ff          callq  ffffffff802a8e67 <kmem_cache_alloc>
>>
>> fault 0xd, general protection fault. Given that it's an immediate
>> constant load, something really serious happened.
>
> ah, that's _another_ -tip testbox that broke at the same time, with a
> different kernel image. The RIP that corresponds to this box is
> 0xffffffff80420470:
>
> ffffffff8042045b <strnlen>:
> ffffffff8042045b:       55                      push   %rbp
>
> ffffffff80420470:       80 38 00                cmpb   $0x0,(%rax)
>
>
> which could be consistent with the printk messup ...
>
>> i've pushed out the broken tree into tip/tmp.master.broken (havent
>> updated tip/master with the breakage). I've removed the broken printk
>> in kernel/resource.c that Andrew found, see commit 06e44f6af324 - so
>> that's not the cause.
>
> i've double checked that 06e44f6af324 is applied. I'll bisect this.
>
or by
ca81beb4a340ee690803fcb1498f863d0e68843f

YH

  reply	other threads:[~2008-09-04 19:59 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-02  5:05 Yinghai Lu
2008-09-04 19:12 ` Ingo Molnar
2008-09-04 19:37   ` Ingo Molnar
2008-09-04 19:41     ` Ingo Molnar
2008-09-04 19:59       ` Yinghai Lu [this message]
2008-09-04 20:04       ` Ingo Molnar
2008-09-04 20:07         ` Yinghai Lu
2008-09-04 20:32           ` Yinghai Lu
2008-09-04 20:37             ` Yinghai Lu
2008-09-04 20:58               ` Ingo Molnar

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=86802c440809041259i8982000yb0f68aeb2842caf0@mail.gmail.com \
    --to=yhlu.kernel@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=tglx@linutronix.de \
    /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®