mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Justin Mattock" <justinmattock@gmail.com>
To: "Jack Howarth" <howarth@bromo.msbb.uc.edu>
Cc: "Yinghai Lu" <yhlu.kernel@gmail.com>,
	"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>
Subject: Re: macbook2,2 latest git mmconfig issues
Date: Sat, 19 Jul 2008 07:53:34 -0700	[thread overview]
Message-ID: <dd18b0c30807190753q22259690jcae780de13c8560d@mail.gmail.com> (raw)
In-Reply-To: <20080719131038.GA13168@bromo.msbb.uc.edu>

On Sat, Jul 19, 2008 at 6:10 AM, Jack Howarth <howarth@bromo.msbb.uc.edu> wrote:
> Justin,
>   I never saw any error messages like that. If you are seeing the
> same problem under 2.6.25 suddenly it might suggest a hardware
> failure, no? That or something else has corrupted on your linux
> volume. What happens if you boot from a linux rescue DVD? Does that
> give the same error?
>                      Jack
>
> On Fri, Jul 18, 2008 at 11:54:38PM -0700, Justin Mattock wrote:
>> applied both patches and messed with boot options
>> but no go:
>> this is what I'm seeing
>> PCI: Fatal no config space access function found
>> ata-piix 0000:00:1f11 device not available
>> because of BAR0 [0xf0-0x1f7] collisions
>>
>>
>> interesting how this kernel was running fine, and then
>> BAM all of a sudden f*&^ed up, This tells me that this was something
>> happening a while ago, or always happening just not
>> noticed i.g. I plugged in 2.6.25-rc9(my favorite)
>> and it too was giving the same response.
>> after tracing back my steps the only application that might be causing
>> this or hiding this is grub but could be wrong.
>>
>> any ideas or patches would be appreciated, until further
>> notice I'll be using osx until there is a
>> regards;   : (
>>
>> --
>> Justin P. Mattock
>

could be; but  loading an iso works i.g.
after installing it and starting up.
these two messages came from after applying
the two patches(keep in mind I was tired so maybe
plugged them in wrong) before the two patches
the MMCONFIG disable message with f0000000
that you where receiving. maybe the manufacture
on mine needs to be MacBookPro2,2 and the 0x3f
needs to be 0x1f. Where do I find these numbers
and names on the system? I've done dmidecode
but can't seem to make out any of the info

-- 
Justin P. Mattock

  reply	other threads:[~2008-07-19 14:53 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-19  3:39 Justin Mattock
2008-07-19  4:45 ` Yinghai Lu
2008-07-19  5:54   ` Justin Mattock
2008-07-19  6:54     ` Justin Mattock
2008-07-19  6:58       ` Yinghai Lu
2008-07-19  7:30         ` Justin Mattock
2008-07-19 13:10       ` Jack Howarth
2008-07-19 14:53         ` Justin Mattock [this message]
2008-07-19 15:14           ` Jack Howarth
2008-07-19 15:54             ` Justin Mattock
2008-07-19 16:28               ` Jack Howarth
2008-07-19 17:15                 ` Justin Mattock
2008-07-19 17:58                   ` Jack Howarth
2008-07-19 19:35                     ` Justin Mattock

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=dd18b0c30807190753q22259690jcae780de13c8560d@mail.gmail.com \
    --to=justinmattock@gmail.com \
    --cc=howarth@bromo.msbb.uc.edu \
    --cc=linux-kernel@vger.kernel.org \
    --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

all inboxes | Powered by JetHome®