From: Voluspa <lista1@telia.com>
To: Greg KH <greg@kroah.com>
Cc: linux-kernel@vger.kernel.org, rajesh.shah@intel.com,
kjarvel@home.se, howarth@bromo.msbb.uc.edu
Subject: Re: PCI error on x86_64 2.6.13 kernel
Date: Sat, 19 Nov 2005 06:06:10 +0100 [thread overview]
Message-ID: <20051119060610.08515fa7.lista1@telia.com> (raw)
In-Reply-To: <20051119011840.GB28175@kroah.com>
On Fri, 18 Nov 2005 17:18:40 -0800 Greg KH wrote:
> On Fri, Nov 18, 2005 at 08:04:40AM +0100, Voluspa wrote:
> >
> > On 2005-11-18 0:24:51 Rajesh Shah wrote:
> > >On Wed, Oct 26, 2005 at 11:06:05PM +0200, Niklas Kallman wrote:
> > >>Jack Howarth wrote:
> > >>> Has anyone reported the following? For both of the 2.6.13 based
> > >>> kernels released so far on Fedora Core 4 for x86_64, we are seeing
> > >>> error messages of the form...
> > >>>
> > >>> Oct 3 11:21:48 XXXXX kernel: MEM window: d0200000-d02fffff
> > >>> Oct 3 11:21:48 XXXXX kernel: PREFETCH window: disabled.
> > >>> Oct 3 11:21:48 XXXXX kernel: PCI: Failed to allocate mem resource #6:20000 \
> > >>> f0000000 for 0000:09:00.0
> > >
> > >I ran into a similar problem, and posted a fix, see
> > >http://marc.theaimsgroup.com/?l=linux-pci&m=113225006603745&w=2
> > >
> > >Can you try it to see if this problem goes away?
> >
> > Even though your patch touched arch/i386/pci/i386.c I tried it in my pure AMD64
> > environment. No luck... I remember when this PCI error turned up, but since it
> > was non-fatal I shrugged it off. Early 2.6.13 it was. Booting back on my
> > non-distro, plain kernel.org notebook I indeed see that 2.6.11.11 and 2.6.12
> > are fine.
>
> Others are reporting this problem too.
>
> Is there any way you could be able to run 'git bisect' between 2.6.12
> and 2.6.13 to try to find the offending changeset? I would really
> appreciate it.
I have to do all the groundwork first (getting git, some dataset, read an howto),
but I'll try to return with some answers by weekend's end or Monday morning. If I fail,
the pointer will be the oldfashioned -rcX is Ok but -rcY not.
Mvh
Mats Johannesson
--
next prev parent reply other threads:[~2005-11-19 5:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-18 7:04 PCI error on x86_64 2.6.13 kernel Voluspa
2005-11-19 1:18 ` Greg KH
2005-11-19 5:06 ` Voluspa [this message]
2005-11-19 12:05 ` Voluspa
[not found] <fa.gf7dlu0.a4g9qo@ifi.uio.no>
2005-10-26 21:06 ` Niklas Kallman
2005-11-18 0:24 ` Rajesh Shah
-- strict thread matches above, loose matches on Subject: below --
2005-10-26 13:53 Jack Howarth
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=20051119060610.08515fa7.lista1@telia.com \
--to=lista1@telia.com \
--cc=greg@kroah.com \
--cc=howarth@bromo.msbb.uc.edu \
--cc=kjarvel@home.se \
--cc=linux-kernel@vger.kernel.org \
--cc=rajesh.shah@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