From: Nigel Cunningham <ncunningham@linuxmail.org>
To: "Linux Kernel Mailing List, " <linux-kernel@vger.kernel.org>
Subject: PCIE region size issue?
Date: Tue, 6 Jun 2006 17:46:50 +1000 [thread overview]
Message-ID: <200606061746.55391.ncunningham@linuxmail.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1539 bytes --]
Hi.
I purchased an AMD64 laptop last December, and have never had perfect success
in getting suspend to disk to work reliably. I thought maybe I had a bug in
Suspend2, but careful diagnosis kept pointing in the direction of drivers. In
addition, from time to time, the screen goes plain white and the system stops
responding, requiring a hard power off.
The other day, I saw a report of bios settings for the uma aperature not
matching what Linux was detecting. I checked my machine, and found that this
issue is occuring here. If I set the bios to 32 meg, lspci says it's 64, and
so on. If I set the bios to 256 meg, the system is unbootable. (Forgive me if
my terminology is a bit messed up - I'm not a pci expert!).
I've seen a number of other reports of issues with pci region sizes, not
always graphics related.
http://www.linuxforums.org/forum/redhat-fedora-linux-help/32870-pci-failed-allocate-mem-resource-error-pcie-fc3-64bit.html
http://linux.derkeiler.com/Mailing-Lists/Fedora/2005-11/4702.html
http://www.nvnews.net/vbulletin/showthread.php?t=42597&page=5
I'm therefore wondering, could there be some bug in the sizing of regions
that's leading to the sizes being doubled?
I have also emailed my laptop manufacturer to see if there are any bios
updates available.
Regards,
Nigel
--
Nigel, Michelle and Alisdair Cunningham
5 Mitchell Street
Cobden 3266
Victoria, Australia
--
Nigel, Michelle and Alisdair Cunningham
5 Mitchell Street
Cobden 3266
Victoria, Australia
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
reply other threads:[~2006-06-06 7:45 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=200606061746.55391.ncunningham@linuxmail.org \
--to=ncunningham@linuxmail.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.