From: Arjan van de Ven <arjan@infradead.org>
To: Andrew Morton <akpm@osdl.org>
Cc: Chuck Ebbert <76306.1226@compuserve.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Linux v2.6.18-rc5
Date: Mon, 28 Aug 2006 20:43:46 +0200 [thread overview]
Message-ID: <1156790626.3034.234.camel@laptopd505.fenrus.org> (raw)
In-Reply-To: <20060828114017.0c8d29c7.akpm@osdl.org>
On Mon, 2006-08-28 at 11:40 -0700, Andrew Morton wrote:
> On Mon, 28 Aug 2006 05:50:07 -0400
> Chuck Ebbert <76306.1226@compuserve.com> wrote:
>
> > > From: Chuck Ebbert <76306.1226@compuserve.com>
> > > Subject: PCI: Cannot allocate resource region 7 of bridge 0000:00:04.0
> >
> > Also happens on 2.6.16.28 and 2.6.17.11, so not a regression.
>
> Well it's not a post-2.6.17 regression. But it's something which quite a few
> people have been reporting in recent months. I don't _think_ it's associated
> with any consistent runtime failures, but otoh I don't think we know what
> caused it.
in itself this can just happen (bios issue, but if the bars are unused
no big deal)... the kernel has gotten more verbose afaik though.
It CAN cause real issues so I'm not saying there's no problem or no
regression, it's just that the printk alone isn't serious.
next prev parent reply other threads:[~2006-08-28 18:43 UTC|newest]
Thread overview: 59+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-28 9:50 Chuck Ebbert
2006-08-28 18:40 ` Andrew Morton
2006-08-28 18:43 ` Arjan van de Ven [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-08-29 5:36 Chuck Ebbert
2006-08-28 4:30 Linus Torvalds
2006-08-28 5:17 ` Marc Perkel
2006-08-28 5:52 ` Linus Torvalds
2006-08-28 6:13 ` Andi Kleen
2006-08-28 7:24 ` Prakash Punnoor
2006-08-28 12:05 ` Andi Kleen
2006-08-28 12:15 ` Prakash Punnoor
2006-08-28 16:02 ` Andi Kleen
2006-08-28 6:14 ` Andrew Morton
2006-08-28 6:19 ` Olaf Hering
2006-08-28 6:24 ` Andrew Morton
2006-08-28 14:41 ` Shailabh Nagar
2006-08-28 22:01 ` Shailabh Nagar
2006-08-28 6:29 ` Jeff Garzik
2006-08-28 7:25 ` Andi Kleen
2006-08-28 8:08 ` Thomas Gleixner
2006-08-28 17:20 ` Andrew Morton
2006-08-28 17:45 ` Thomas Gleixner
2006-08-28 8:05 ` Catalin Marinas
2006-08-28 8:25 ` Catalin Marinas
2006-08-28 8:34 ` Keith Owens
2006-08-28 8:42 ` Tejun Heo
2006-08-28 15:24 ` Keith Owens
2006-09-03 6:10 ` Tejun Heo
2006-09-06 6:42 ` Keith Owens
2006-09-13 14:41 ` Tejun Heo
2006-09-15 7:40 ` Keith Owens
2006-08-28 8:53 ` Beschorner Daniel
2006-08-28 15:26 ` Dmitry Torokhov
2006-08-29 2:01 ` Greg KH
2006-08-29 2:01 ` Greg KH
2006-08-29 14:50 ` Andreas Barth
2006-08-29 15:57 ` Brice Goglin
2006-08-30 15:54 ` Andrew Benton
2006-08-30 16:15 ` Takashi Iwai
2006-08-31 8:22 ` Takashi Iwai
2006-08-31 5:14 ` Len Brown
2006-09-02 1:40 ` Elias Holman
2006-09-02 1:50 ` Jeff Garzik
2006-08-28 10:10 ` Jesper Juhl
2006-08-28 10:27 ` Kasper Sandberg
2006-08-28 10:35 ` Jesper Juhl
2006-08-28 22:36 ` Nathan Scott
2006-08-28 23:30 ` Jesper Juhl
2006-08-30 8:14 ` Kasper Sandberg
2006-08-30 9:19 ` Jesper Juhl
2006-08-30 13:43 ` Jesper Juhl
2006-09-06 12:21 ` Paul Slootman
2006-08-28 13:04 ` Roger Luethi
2006-08-29 11:55 ` Olaf Hering
2006-08-29 13:06 ` Nathan Lynch
2006-08-29 15:52 ` Olaf Hering
2006-08-30 6:13 ` Paul Mackerras
2006-08-30 8:05 ` Olaf Hering
2006-08-30 9:00 ` Mikael Pettersson
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=1156790626.3034.234.camel@laptopd505.fenrus.org \
--to=arjan@infradead.org \
--cc=76306.1226@compuserve.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.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®