From: Otto Solares <solca@guug.org>
To: linux-fbdev-devel@lists.sourceforge.net
Subject: ioremap problem on highmem
Date: Mon, 13 Oct 2003 13:18:31 -0600 [thread overview]
Message-ID: <20031013191831.GB454@guug.org> (raw)
Hi!
FYI radeonfb is failing when highmem enabled, workaround with kernel param 'mem' < 896M.
Interesting bits from dmesg:
Linux version 2.6.0-test6-bk7 (solca@solcahomedesk) (gcc version 3.3.2 20030908 (Debian prerelease)) #10 SMP Mon Oct 6 11:37:35 CST 2003
Video mode to be used for restore is ffff
BIOS-provided physical RAM map:
BIOS-e820: 0000000000000000 - 000000000009f800 (usable)
BIOS-e820: 000000000009f800 - 00000000000a0000 (reserved)
BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved)
BIOS-e820: 0000000000100000 - 000000007ffec000 (usable)
BIOS-e820: 000000007ffec000 - 000000007ffef000 (ACPI data)
BIOS-e820: 000000007ffef000 - 000000007ffff000 (reserved)
BIOS-e820: 000000007ffff000 - 0000000080000000 (ACPI NVS)
BIOS-e820: 00000000fec00000 - 00000000fec01000 (reserved)
BIOS-e820: 00000000fee00000 - 00000000fee01000 (reserved)
BIOS-e820: 00000000ffff0000 - 0000000100000000 (reserved)
1151MB HIGHMEM available.
896MB LOWMEM available.
found SMP MP-table at 000f7e90
hm, page 000f7000 reserved twice.
hm, page 000f8000 reserved twice.
hm, page 000f7000 reserved twice.
hm, page 000f8000 reserved twice.
On node 0 totalpages: 524268
DMA zone: 4096 pages, LIFO batch:1
Normal zone: 225280 pages, LIFO batch:16
HighMem zone: 294892 pages, LIFO batch:16
Kernel command line: BOOT_IMAGE=Linux ro root=303 video=radeonfb:1024x768-8@60
Console: colour VGA+ 80x25
Memory: 2072716k/2097072k available (1575k kernel code, 23240k reserved, 472k data, 148k init, 1179568k highmem)
radeonfb_pci_register BEGIN
radeonfb: ref_clk=2700, ref_div=12, xclk=16600 from BIOS
radeonfb: probed DDR SGRAM 262144k videoram
radeon_get_moninfo: bios 4 scratch = 2000002
radeonfb: cannot map FB
Total HugeTLB memory allocated, 0
highmem bounce pool size: 64 pages
-solca
-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
SourceForge.net hosts over 70,000 Open Source Projects.
See the people who have HELPED US provide better services:
Click here: http://sourceforge.net/supporters.php
next reply other threads:[~2003-10-13 19:19 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-13 19:18 Otto Solares [this message]
2003-10-13 20:30 ` ioremap problem on highmem Jon Smirl
2003-10-14 0:14 ` Otto Solares
2003-10-14 0:46 ` Jon Smirl
2003-10-14 1:56 ` Otto Solares
2003-10-14 4:51 ` Jon Smirl
2003-10-15 1:13 ` Otto Solares
2003-10-15 1:37 ` Jon Smirl
2003-10-15 23:11 ` James Simmons
2003-10-16 10:15 ` Benjamin Herrenschmidt
2003-10-16 16:56 ` Otto Solares
2003-10-17 16:58 ` James Simmons
2003-10-14 8:30 ` Geert Uytterhoeven
2003-10-14 8:34 ` Geert Uytterhoeven
2003-10-14 14:42 ` Jon Smirl
2003-10-14 17:25 ` James Simmons
2003-10-14 17:23 ` James Simmons
2003-10-14 16:49 ` James Simmons
2003-10-14 17:59 ` Jon Smirl
2003-10-15 23:17 ` James Simmons
2003-10-16 0:34 ` Jon Smirl
2003-10-16 10:12 ` Benjamin Herrenschmidt
2003-10-16 0:43 ` I2C standalone vs integrated? Jon Smirl
2003-10-16 10:14 ` Benjamin Herrenschmidt
2003-10-17 16:43 ` James Simmons
2003-10-16 10:09 ` ioremap problem on highmem Benjamin Herrenschmidt
2003-10-15 16:46 ` Benjamin Herrenschmidt
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=20031013191831.GB454@guug.org \
--to=solca@guug.org \
--cc=linux-fbdev-devel@lists.sourceforge.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;
as well as URLs for NNTP newsgroup(s).