public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Wink Saville <wink@saville.com>
To: Matthias Hentges <oe@hentges.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: PCI: BIOS Bug: MCFG area at f0000000 is not E820-reserved with 2.6.18 kernel
Date: Mon, 02 Oct 2006 21:12:22 -0700	[thread overview]
Message-ID: <4521E326.2000406@saville.com> (raw)
In-Reply-To: <1159808447.4652.6.camel@mhcln03>

Matthias,

Thanks, I tried your config file on 2.6.18 and it works!

The first time I tried my command line was:

Command line: root=/dev/sda2 ro quiet splash initcall_debug 
console=ttyS0,115200n8 loglevel=7 video=nvidiafb:nomtrr

and it came up but no keyboard or mouse, I changed it too:

Command line: root=/dev/sda2 ro quiet splash

You mentioned you "saw some hangs", I assume with the current 
configuration your having no problems with stability?

Thanks again,

Wink


  reply	other threads:[~2006-10-03  4:12 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-02  1:12 PCI: BIOS Bug: MCFG area at f0000000 is not E820-reserved with 2.6.18 kernel Wink Saville
2006-10-02  9:54 ` Andi Kleen
2006-10-02 15:10   ` Wink Saville
2006-10-02 15:22     ` Andi Kleen
2006-10-02 16:08       ` Wink Saville
2006-10-02 17:00 ` Matthias Hentges
2006-10-03  4:12   ` Wink Saville [this message]
2006-10-03 12:23     ` Matthias Hentges
2006-10-03 16:33       ` Wink Saville
2006-10-03 13:30     ` Arjan van de Ven
2006-10-03 16:37       ` Wink Saville
2006-10-04 16:26       ` Hang in fb_notifier_call_chain with nvidia framebuffer Wink Saville
2006-10-08  6:01         ` Andrew Morton
2006-10-08  8:14           ` Wink Saville
2006-10-08  9:07             ` Andrew Morton
2006-10-08 18:06               ` Wink Saville
2006-10-05  6:28       ` 2.6.18 Hang in fb_notifier_call_chain while booting " Wink Saville

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=4521E326.2000406@saville.com \
    --to=wink@saville.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=oe@hentges.net \
    /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