public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ciaran McCreesh <ciaran.mccreesh@googlemail.com>
To: "Yinghai Lu" <yhlu.kernel@gmail.com>
Cc: mingo@elte.hu, linux-kernel@vger.kernel.org
Subject: Re: kernel boot hangs after x86: insert_resorce for lapic addr after e820_reserve_resources
Date: Sun, 18 May 2008 16:41:27 +0100	[thread overview]
Message-ID: <20080518164127.2236d82a@googlemail.com> (raw)
In-Reply-To: <86802c440805172055x30c2c6feg441e16f5fb24f64f@mail.gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 932 bytes --]

On Sat, 17 May 2008 20:55:20 -0700
"Yinghai Lu" <yhlu.kernel@gmail.com> wrote:
> On Sat, May 17, 2008 at 5:41 PM, Ciaran McCreesh
> <ciaran.mccreesh@googlemail.com> wrote:
> > The commit 3def3d6ddf43dbe20c00c3cbc38dfacc8586998f (x86:
> > insert_resorce for lapic addr after e820_reserve_resources) causes
> > my x86_64 box to to lock up early on in the boot process. Reverting
> > only this commit with current git head gives a successful boot.
>
> can you try to boot with apic=verbose? please don't revert that
> patch...
> 
> wonder if init_apic_mapping need some delay with that strange chipset.

I don't see any additional information with apic=verbose with the
broken kernel (although I only have a screen's worth of text that I can
see -- the kernel doesn't get far enough to let me grab it). I've
attached dmesg from a working kernel with apic=verbose in case that
helps.

Thanks,
-- 
Ciaran McCreesh

[-- Attachment #1.2: dmesg-apic-verbose.txt.gz --]
[-- Type: application/octet-stream, Size: 10315 bytes --]

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 197 bytes --]

  reply	other threads:[~2008-05-18 15:41 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-18  0:41 kernel boot hangs after x86: insert_resorce for lapic addr after e820_reserve_resources Ciaran McCreesh
2008-05-18  3:55 ` Yinghai Lu
2008-05-18 15:41   ` Ciaran McCreesh [this message]
2008-05-18 21:00     ` Yinghai Lu
2008-05-18 22:23       ` Ciaran McCreesh
2008-05-19  3:43         ` Yinghai Lu
2008-05-20  0:44           ` Ciaran McCreesh
2008-05-20  1:22             ` Yinghai Lu
2008-05-20  1:24               ` Ciaran McCreesh
2008-05-20  2:48                 ` Yinghai Lu
2008-05-20  3:16                   ` Ciaran McCreesh
2008-05-20  3:22                     ` Yinghai Lu
2008-05-20  3:25                       ` Yinghai Lu
2008-05-23 23:50                       ` Ciaran McCreesh
2008-05-24  0:05                         ` Yinghai Lu
2008-05-24  1:09                           ` Ciaran McCreesh
2008-05-24  1:51                             ` Yinghai Lu
2008-05-24  2:29                               ` Yinghai Lu

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=20080518164127.2236d82a@googlemail.com \
    --to=ciaran.mccreesh@googlemail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=yhlu.kernel@gmail.com \
    /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