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: "Bjorn Helgaas" <bjorn.helgaas@hp.com>,
	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: Sat, 24 May 2008 02:09:50 +0100	[thread overview]
Message-ID: <20080524020950.1538624a@snowcone> (raw)
In-Reply-To: <86802c440805231705g534e9245oc359dc316ae5b1cd@mail.gmail.com>


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

On Fri, 23 May 2008 17:05:34 -0700
"Yinghai Lu" <yhlu.kernel@gmail.com> wrote:
> > Without the ram_reserve
> > patch, /proc/iomem is as it was earlier in the discussion.
> >
> >> can you boot with pnpacpi=off ?
> >
> > No, that doesn't help either.
>
> how about /proc/iomem with pnpacpi=off?

I've attached /proc/iomem from current head minus the original patch,
with and without pnpacpi=off.

Thanks,
-- 
Ciaran McCreesh

[-- Attachment #1.2: iomem-normal.txt --]
[-- Type: text/plain, Size: 1657 bytes --]

00000000-0009ffff : pnp 00:09
000f0000-000fffff : pnp 00:09
00100000-d7feffff : pnp 00:09
d7ff0000-d7ffffff : pnp 00:09
d8000000-dfffffff : PCI Bus 0000:01
  d8000000-dfffffff : 0000:01:05.0
e0000000-efffffff : PCI MMCONFIG 0
  e0000000-efffffff : pnp 00:08
fdb00000-fdbfffff : PCI Bus 0000:03
fdc00000-fdcfffff : PCI Bus 0000:03
  fdcff000-fdcff0ff : 0000:03:05.0
    fdcff000-fdcff0ff : 8139too
fdd00000-fddfffff : PCI Bus 0000:02
  fdd00000-fdd1ffff : 0000:02:00.0
fde00000-fdefffff : PCI Bus 0000:02
  fdeff000-fdefffff : 0000:02:00.0
    fdeff000-fdefffff : r8169
fdf00000-fdffffff : PCI Bus 0000:01
  fdf00000-fdf03fff : 0000:01:05.2
    fdf00000-fdf03fff : ICH HD audio
  fdff0000-fdffffff : 0000:01:05.0
fe024000-fe027fff : 0000:00:14.2
  fe024000-fe027fff : ICH HD audio
fe029000-fe0290ff : 0000:00:13.5
  fe029000-fe0290ff : ehci_hcd
fe02a000-fe02afff : 0000:00:13.4
  fe02a000-fe02afff : ohci_hcd
fe02b000-fe02bfff : 0000:00:13.3
  fe02b000-fe02bfff : ohci_hcd
fe02c000-fe02cfff : 0000:00:13.2
  fe02c000-fe02cfff : ohci_hcd
fe02d000-fe02dfff : 0000:00:13.1
  fe02d000-fe02dfff : ohci_hcd
fe02e000-fe02efff : 0000:00:13.0
  fe02e000-fe02efff : ohci_hcd
fe02f000-fe02f3ff : 0000:00:12.0
  fe02f000-fe02f3ff : ahci
fec00000-fec00fff : IOAPIC 0
  fec00000-fec00fff : pnp 00:09
fed00000-fed003ff : HPET 0
  fed00000-fed003ff : 0000:00:14.0
    fed00000-fed000ff : pnp 00:09
fee00000-fee00fff : Local APIC
  fee00000-fee00fff : pnp 00:09
ffff0000-ffffffff : pnp 00:09
100000000-11fffffff : System RAM
  00200000-005d356d : Kernel code
  005d356e-00770927 : Kernel data
  007df000-0085f74f : Kernel bss

[-- Attachment #1.3: iomem-pnpacpi-off.txt --]
[-- Type: text/plain, Size: 1368 bytes --]

d8000000-dfffffff : PCI Bus 0000:01
  d8000000-dfffffff : 0000:01:05.0
e0000000-efffffff : PCI MMCONFIG 0
fdb00000-fdbfffff : PCI Bus 0000:03
fdc00000-fdcfffff : PCI Bus 0000:03
  fdcff000-fdcff0ff : 0000:03:05.0
    fdcff000-fdcff0ff : 8139too
fdd00000-fddfffff : PCI Bus 0000:02
  fdd00000-fdd1ffff : 0000:02:00.0
fde00000-fdefffff : PCI Bus 0000:02
  fdeff000-fdefffff : 0000:02:00.0
    fdeff000-fdefffff : r8169
fdf00000-fdffffff : PCI Bus 0000:01
  fdf00000-fdf03fff : 0000:01:05.2
    fdf00000-fdf03fff : ICH HD audio
  fdff0000-fdffffff : 0000:01:05.0
fe024000-fe027fff : 0000:00:14.2
  fe024000-fe027fff : ICH HD audio
fe029000-fe0290ff : 0000:00:13.5
  fe029000-fe0290ff : ehci_hcd
fe02a000-fe02afff : 0000:00:13.4
  fe02a000-fe02afff : ohci_hcd
fe02b000-fe02bfff : 0000:00:13.3
  fe02b000-fe02bfff : ohci_hcd
fe02c000-fe02cfff : 0000:00:13.2
  fe02c000-fe02cfff : ohci_hcd
fe02d000-fe02dfff : 0000:00:13.1
  fe02d000-fe02dfff : ohci_hcd
fe02e000-fe02efff : 0000:00:13.0
  fe02e000-fe02efff : ohci_hcd
fe02f000-fe02f3ff : 0000:00:12.0
  fe02f000-fe02f3ff : ahci
fec00000-fec00fff : IOAPIC 0
fed00000-fed003ff : HPET 0
  fed00000-fed003ff : 0000:00:14.0
fee00000-fee00fff : Local APIC
100000000-11fffffff : System RAM
  00200000-005d356d : Kernel code
  005d356e-00770927 : Kernel data
  007df000-0085f74f : Kernel bss

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

  reply	other threads:[~2008-05-24  1:10 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
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 [this message]
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=20080524020950.1538624a@snowcone \
    --to=ciaran.mccreesh@googlemail.com \
    --cc=bjorn.helgaas@hp.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