LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: "Luming Yu" <luming.yu@gmail.com>
To: "Martin Drab" <drab@kepler.fjfi.cvut.cz>
Cc: "Oleg Verych" <olecom@flower.upol.cz>,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>
Subject: Re: Intel PCI-E bridge ACPI resources and possibly related SATA unstability problems on ASUS A8Js
Date: Fri, 26 Jan 2007 23:03:14 +0800 [thread overview]
Message-ID: <3877989d0701260703q37bd586awabdeb172f63a8018@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0701261320260.6213@kepler.fjfi.cvut.cz>
On 1/26/07, Martin Drab <drab@kepler.fjfi.cvut.cz> wrote:
> On Thu, 25 Jan 2007, Oleg Verych wrote:
>
> > On Thu, Jan 25, 2007 at 01:28:56PM +0100, Martin Drab wrote:
> > > On Thu, 25 Jan 2007, Oleg Verych wrote:
> > >
> > > > gmane.linux.kernel:
> > > > > recently I got my hands on an ASUS A8Js notebook (Core 2 Duo T7200,
> > > > > Intel 945 PM PCI-E Chipset, for details see attached log). After booting
> > > > > the latest 2.6.20-rc5-git3 kernel (but the same behaviour occurs also with
> > > > > the 2.6.19.2, didn't try any other), some strange behaviour can be
> > > > > observed.
> > > >
> > > > There were disscussions about mmconfig and what nightmare it brought to
> > > > PCI(E) configuration in scope of BIOS, chip bugs. Here's (one of) such:
> > > > <http://marc.theaimsgroup.com/?l=linux-kernel&m=116007091004503&w=2>
> > > >
> > > > > At first the following messages appear in the log:
> > > > >
> > > > > ...
> > [ 40.303154] PCI: BIOS *Bug*: MCFG area at e0000000 is not E820-reserved
> > > > > [ 40.303157] PCI: Not using MMCONFIG.
> > > > >
> > > > > (not sure whether this is really a problem)
> > > >
> > > > I think it may be the major problem.
> > >
> > > Hmm, it may be. Was there suggested any solution (or at least proposal)
> > > that I may try?
> >
> > Try fix BIOS bugs: <http://permalink.gmane.org/gmane.linux.kernel/462632>
>
> ASUS refused to help fixing the BIOS with words that ASUS notebooks do not
> support Linux. So if we do not workaround this somehow, Linux would really
> be unusable on this HW. :(
>
Does pci=nommconf work for you. Also why not use memmap=exactmap ...
boot command line to workaround this bios bug?
next prev parent reply other threads:[~2007-01-26 15:03 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-25 2:57 Martin Drab
2007-01-25 3:26 ` Martin Drab
2007-01-25 10:04 ` Oleg Verych
2007-01-25 12:28 ` Martin Drab
2007-01-25 13:58 ` Oleg Verych
2007-01-25 16:57 ` Martin Drab
2007-01-26 12:23 ` Martin Drab
2007-01-26 15:03 ` Luming Yu [this message]
2007-01-26 17:18 ` Martin Drab
[not found] <fa.PpxpQ7nMZSyaD7q+Ht9cGg0CIiw@ifi.uio.no>
[not found] ` <fa.wqPyXXdyh/mi1huaDG6ytwgWGls@ifi.uio.no>
[not found] ` <fa./T3sQPFQFuD91GZzkxPLpnq+daI@ifi.uio.no>
[not found] ` <fa.pgpxy1bTTJGfmjQzrCFr6RYyJZ8@ifi.uio.no>
[not found] ` <fa.ZnWRVfns13JT5BT7zPCIOVH11yw@ifi.uio.no>
2007-01-26 14:35 ` Robert Hancock
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=3877989d0701260703q37bd586awabdeb172f63a8018@mail.gmail.com \
--to=luming.yu@gmail.com \
--cc=drab@kepler.fjfi.cvut.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=olecom@flower.upol.cz \
--subject='Re: Intel PCI-E bridge ACPI resources and possibly related SATA unstability problems on ASUS A8Js' \
/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
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).