From: "Vegard Nossum" <vegard.nossum@gmail.com>
To: "Ingo Molnar" <mingo@elte.hu>,
"Alexey Starikovskiy" <astarikovskiy@suse.de>,
"Thomas Gleixner" <tglx@linutronix.de>,
venkatesh.pallipadi@intel.com,
"Huang Ying" <ying.huang@intel.com>,
"Andi Kleen" <andi@firstfloor.org>
Cc: linux-kernel@vger.kernel.org, linux-acpi@vger.kernel.org
Subject: v2.6.26-rc9: ACPI PCI irq routing on NUMA? + early_ioremap trouble
Date: Sun, 6 Jul 2008 15:47:19 +0200 [thread overview]
Message-ID: <19f34abd0807060647k54490088uf8859d8a1646fd41@mail.gmail.com> (raw)
Hi,
I have produced a config which doesn't boot correctly on either of my
computers with v2.6.26-rc9.
The first problem is with my laptop, which hangs on boot, see
screenshot (sorry for the bad quality, I was in a hurry):
http://folk.uio.no/vegardno/linux/DSCF3026.JPG
I figured there's something wrong with ACPI PCI irq routing as I'm
missing a message that shows up in my usual configs:
calling ide_scan_pcibus+0x0/0xf0
ICH8M: IDE controller (0x8086:0x2850 rev 0x03) at PCI slot 0000:00:1f.1
--- HERE: ---
ACPI: PCI Interrupt 0000:00:1f.1[A] -> GSI 18 (level, low) -> IRQ 18
----
ICH8M: not 100% native mode: will probe irqs later
...and as can be seen in the screenshot, ide-cd "lost interrupt".
Unfortunately, I don't have a serial line on this machine, so it's
hard to get the full log. (Maybe I can try netconsole, it seems to be
up by the time this happens.)
(I also tried booting with acpi=off, acpi=noirq, pci=noacpi, to no avail.)
Note that this does not seem to be a regression; I get the same thing
with -rc8 as well. I'm guessing it's config-induced, here are my
config changes that triggered it:
http://folk.uio.no/vegardno/linux/config-diff
I'll make a guess for the NUMA/ACPI stuff. And this is the full
config: http://folk.uio.no/vegardno/linux/config-bisect
I decided to also try this kernel with my desktop machine. This one
boots (probably because ACPI is disabled?), but I get the following
warning:
[ 0.000000] Begin SRAT table scan....
[ 0.000000] ------------[ cut here ]------------
[ 0.000000] WARNING: at arch/x86/mm/ioremap.c:553 early_ioremap+0x1c1/0x200()
[ 0.000000] Pid: 0, comm: swapper Not tainted 2.6.26-rc9 #201
[ 0.000000] [<c0157d6f>] warn_on_slowpath+0x4f/0x70
[ 0.000000] [<c01708db>] ? up+0x2b/0x40
[ 0.000000] [<c01586f1>] ? release_console_sem+0x1c1/0x1f0
[ 0.000000] [<c05c0132>] ? _spin_unlock_irqrestore+0x32/0x70
[ 0.000000] [<c05c0143>] ? _spin_unlock_irqrestore+0x43/0x70
[ 0.000000] [<c0158705>] ? release_console_sem+0x1d5/0x1f0
[ 0.000000] [<c0158aff>] ? vprintk+0x1cf/0x430
[ 0.000000] [<c0158b0b>] ? vprintk+0x1db/0x430
[ 0.000000] [<c07c0b24>] ? __early_set_fixmap+0xb4/0xd0
[ 0.000000] [<c07c1231>] early_ioremap+0x1c1/0x200
[ 0.000000] [<c07bd48e>] get_memcfg_from_srat+0x15e/0x6d0
[ 0.000000] [<c01314be>] ? post_set+0x4e/0x50
[ 0.000000] [<c01315fa>] ? generic_get_mtrr+0x2a/0x100
[ 0.000000] [<c07c154d>] setup_memory+0xd/0x280
[ 0.000000] [<c07b3c7e>] setup_arch+0x2ee/0x4e0
[ 0.000000] [<c0158d7b>] ? printk+0x1b/0x20
[ 0.000000] [<c07ab842>] start_kernel+0x82/0x390
[ 0.000000] [<c07ab028>] i386_start_kernel+0x8/0x10
[ 0.000000] =======================
[ 0.000000] ---[ end trace 4eaa2a86a8e2da22 ]---
[ 0.000000] failed to get NUMA memory information from SRAT table
[ 0.000000] NUMA - single node, flat memory mode
What really puzzles me is the line number of the WARN -- it says
arch/x86/mm/ioremap.c:553. But this line does not contain any WARNs.
In fact, it's not even the right function. But this is a clean
v2.6.26-rc9 compile, as can be seen from the kernel version above.
There's also one a bit later:
[ 7.746346] please boot with early_ioremap_debug and report the dmesg.
[ 7.746460] ------------[ cut here ]------------
[ 7.746569] WARNING: at arch/x86/mm/ioremap.c:524
check_early_ioremap_leak+0x3f/0x50()
See full dmesg at: http://folk.uio.no/vegardno/linux/dmesg-2.6.26-rc9
With early_ioremap_debug enabled:
http://folk.uio.no/vegardno/linux/dmesg-early_ioremap_debug
My apologies if I got the recipients wrong; I picked them off the
git-log for relevant files. Please Cc in the right direction if needed
:-)
Thanks!
Vegard
--
"The animistic metaphor of the bug that maliciously sneaked in while
the programmer was not looking is intellectually dishonest as it
disguises that the error is the programmer's own creation."
-- E. W. Dijkstra, EWD1036
next reply other threads:[~2008-07-06 13:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-06 13:47 Vegard Nossum [this message]
2008-07-17 18:45 ` Bjorn Helgaas
2008-07-17 20:58 ` Vegard Nossum
2008-07-18 0:47 ` Maciej W. Rozycki
2008-07-18 7:51 ` Vegard Nossum
2008-07-18 12:59 ` Maciej W. Rozycki
2008-07-18 12:26 ` 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=19f34abd0807060647k54490088uf8859d8a1646fd41@mail.gmail.com \
--to=vegard.nossum@gmail.com \
--cc=andi@firstfloor.org \
--cc=astarikovskiy@suse.de \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
--cc=venkatesh.pallipadi@intel.com \
--cc=ying.huang@intel.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
all inboxes | Powered by JetHome®