From: "Yinghai Lu" <yhlu.kernel@gmail.com>
To: "Justin Mattock" <justinmattock@gmail.com>
Cc: "Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
"Jack Howarth" <howarth@bromo.msbb.uc.edu>
Subject: Re: macbook2,2 latest git mmconfig issues
Date: Fri, 18 Jul 2008 21:45:55 -0700 [thread overview]
Message-ID: <86802c440807182145qa3d17e9k210c498109d86b58@mail.gmail.com> (raw)
In-Reply-To: <dd18b0c30807182039u3e590e50p5d76624dd9e5b1d8@mail.gmail.com>
On Fri, Jul 18, 2008 at 8:39 PM, Justin Mattock <justinmattock@gmail.com> wrote:
> Hello;
> Well I couldn't really see what was happening
> until I could experience this myself;
> It seems the macbook pro ati chipset
> is having the same problem as jack was with mmconfig yesterday.
> I'm confused as to why my system was able to run this kernel(2.6.26.git1)
> without a problem, now after doing a reinstall of the operating system
> I am confronted with this same issue. How do I find the 0x3f number on
> my system,
> so I could plug that into the patch? to see if I can boot up
> Now keep in mind the only difference with this install is the
> installer took a dump
> therefore you have to manually install grub(could this be the source
> of the issue?)
> regards;
can you disable ASPM in your config.?
YH
next prev parent reply other threads:[~2008-07-19 4:46 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 [this message]
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
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=86802c440807182145qa3d17e9k210c498109d86b58@mail.gmail.com \
--to=yhlu.kernel@gmail.com \
--cc=howarth@bromo.msbb.uc.edu \
--cc=justinmattock@gmail.com \
--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®