From: Bjorn Helgaas <bjorn.helgaas@hp.com>
To: Frans Pop <elendil@planet.nl>
Cc: Jesper Krogh <jesper@krogh.cc>,
torvalds@linux-foundation.org, linux-kernel@vger.kernel.org,
Avuton Olrich <avuton@gmail.com>
Subject: Re: Linux 2.6.26-rc5
Date: Sun, 8 Jun 2008 21:39:45 -0600 [thread overview]
Message-ID: <200806082139.45829.bjorn.helgaas@hp.com> (raw)
In-Reply-To: <200806072350.59976.elendil@planet.nl>
On Saturday 07 June 2008 3:50:59 pm Frans Pop wrote:
> Jesper Krogh wrote:
> > Not that they seem critical to the system but I do get alot of these. I
> > cant remember having seen that before.
> >
> > [ 2.904467] system 00:06: iomem range 0x0-0x0 could not be reserved
> > [ 2.904469] system 00:06: iomem range 0x0-0x0 could not be reserved
> > [ 2.904471] system 00:06: iomem range 0x0-0x0 could not be reserved
> > [ 2.904473] system 00:06: iomem range 0x0-0x0 could not be reserved
>
> [...]
>
> I'm getting these too. Not present in the last -rc4 kernel I built.
>
> Reverting this commit (the only recent one to the file the message
> originates from), gets rid of the extra zero-range messages:
>
> commit 4b34fe156455d26ee6ed67b61539f136bf4e439c
> Author: Bjorn Helgaas <bjorn.helgaas@hp.com>
> Date: Mon Jun 2 16:42:49 2008 -0600
>
> PNP: mark resources that conflict with PCI devices "disabled"
>
> Both the PNP/PCI conflict detection quirk and the PNP system
> driver must use the same mechanism to mark resources as disabled.
>
> I think it's best to keep the resource and to keep the type bit
> (IORESOURCE_MEM, etc), so that we match the list from firmware
> as closely as possible.
>
> Fixes this regression from 2.6.25: http://lkml.org/lkml/2008/6/1/82
>
> Signed-off-by: Bjorn Helgaas <bjorn.helgaas@hp.com>
> Tested-by: Avuton Olrich <avuton@gmail.com>
> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
>
> Relevant CCs added.
The patch below should fix this and is already in Linus' tree.
Can you give it a whirl to confirm? Thanks!
PNP: skip UNSET MEM resources as well as DISABLED ones
We don't need to reserve "unset" resources. Trying to reserve
them results in messages like this, which are ugly but harmless:
system 00:08: iomem range 0x0-0x0 could not be reserved
Future PNP patches will remove use of IORESOURCE_UNSET, but
we still need it for now.
Signed-off-by: Bjorn Helgaas <bjorn.helgaas@hp.com>
Index: work11/drivers/pnp/system.c
===================================================================
--- work11.orig/drivers/pnp/system.c 2008-06-05 09:46:33.000000000 -0600
+++ work11/drivers/pnp/system.c 2008-06-05 10:29:10.000000000 -0600
@@ -81,7 +81,7 @@ static void reserve_resources_of_dev(str
}
for (i = 0; (res = pnp_get_resource(dev, IORESOURCE_MEM, i)); i++) {
- if (res->flags & IORESOURCE_DISABLED)
+ if (res->flags & (IORESOURCE_UNSET | IORESOURCE_DISABLED))
continue;
reserve_range(dev, res->start, res->end, 0);
next prev parent reply other threads:[~2008-06-09 3:40 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-05 3:36 Linus Torvalds
2008-06-05 11:24 ` Olaf Hering
2008-06-05 12:09 ` Linux 2.6.26-rc5 (G5 SATA broken) Hugh Dickins
2008-06-05 12:54 ` Alan Cox
2008-06-05 13:44 ` [PATCH] libata: fix G5 SATA broken on -rc5 Hugh Dickins
2008-06-05 14:45 ` Olaf Hering
2008-06-06 4:36 ` Linux 2.6.26-rc5 (G5 SATA broken) Benjamin Herrenschmidt
2008-06-05 12:42 ` Linux 2.6.26-rc5 Alan Cox
2008-06-05 13:03 ` Alejandro Riveira Fernández
2008-06-05 14:54 ` Linus Torvalds
2008-06-05 15:12 ` Bjorn Helgaas
2008-06-05 16:12 ` Bjorn Helgaas
2008-06-05 16:19 ` Linus Torvalds
2008-06-05 16:32 ` Bjorn Helgaas
2008-06-05 14:43 ` Ben Dooks
2008-06-06 18:35 ` Linus Torvalds
2008-06-10 12:57 ` ACPI pull for 2.6.26? Adrian Bunk
2008-06-10 15:23 ` Len Brown
2008-06-10 15:39 ` Adrian Bunk
2008-06-05 14:47 ` Linux 2.6.26-rc5 Alex Romosan
2008-06-07 19:44 ` Jesper Krogh
2008-06-07 21:50 ` Frans Pop
2008-06-09 3:39 ` Bjorn Helgaas [this message]
2008-06-09 10:01 ` Frans Pop
2008-06-07 19:52 ` Jesper Krogh
2008-06-05 15:04 Lior Dotan
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=200806082139.45829.bjorn.helgaas@hp.com \
--to=bjorn.helgaas@hp.com \
--cc=avuton@gmail.com \
--cc=elendil@planet.nl \
--cc=jesper@krogh.cc \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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®