linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Hai Zaar <haizaar@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: vesa fb is slow on 2.6.15.1
Date: Thu, 26 Jan 2006 16:20:58 +0200	[thread overview]
Message-ID: <cfb54190601260620l5848ba3ai9d7e06c41d98c362@mail.gmail.com> (raw)

Dear list,
I have framebuffer problems with vanilla 2.6.15.1 - its very slow.
I'm using vesafb and booting with 'vga=795'.
I've used 2.6.11.12 before, and running 'cat
/usr/share/man/man1/bash.1' on tty1 took
12 seconds. Now, with 2.6.15.1 it takes 3 minutes.

Now the details of 2.6.15.1 system:

During boot I have:
PCI: Failed to allocate mem resource #6:20000@f8000000 for 0000:40:00.0

relevant snip of the .config
#
# Graphics support
#
CONFIG_FB=y
CONFIG_FB_CFB_FILLRECT=y
CONFIG_FB_CFB_COPYAREA=y
CONFIG_FB_CFB_IMAGEBLIT=y
CONFIG_FB_MODE_HELPERS=y
CONFIG_FB_VESA=y
CONFIG_VIDEO_SELECT=y

And as I've said, I boot with 'vga=795'. Graphics card is Nvidia
Quadro FX1500 (PCIE).

# lspci  -vv -s 40:00.0
40:00.0 VGA compatible controller: nVidia Corporation: Unknown device
00ce (rev a2) (prog-if 00 [VGA])
	Subsystem: nVidia Corporation: Unknown device 0243
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR+ FastB2B-
	Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort-
<TAbort- <MAbort- >SERR- <PERR-
	Latency: 0
	Interrupt: pin A routed to IRQ 169
	Region 0: Memory at f8000000 (32-bit, non-prefetchable) [size=16M]
	Region 1: Memory at f0000000 (64-bit, prefetchable) [size=128M]
	Region 3: Memory at f9000000 (64-bit, non-prefetchable) [size=16M]
	Capabilities: [60] Power Management version 2
		Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
		Status: D0 PME-Enable- DSel=0 DScale=0 PME-
	Capabilities: [68] Message Signalled Interrupts: 64bit+ Queue=0/0 Enable-
		Address: 0000000000000000  Data: 0000
	Capabilities: [78] #10 [0001]

# cat /proc/mtrr
reg00: base=0x00000000 (   0MB), size=2048MB: write-back, count=1
reg01: base=0x80000000 (2048MB), size=1024MB: write-back, count=1
reg02: base=0xc0000000 (3072MB), size= 512MB: write-back, count=1
reg03: base=0x100000000 (4096MB), size= 512MB: write-back, count=1
reg04: base=0xfeda0000 (4077MB), size= 128KB: uncachable, count=1

No 'write-combining' entry! But with 2.6.11.12 I do have one:
<2.6.11.12 system> cat /proc/mtrr
reg00: base=0x00000000 (   0MB), size=2048MB: write-back, count=1
reg01: base=0x80000000 (2048MB), size=1024MB: write-back, count=1
reg02: base=0xc0000000 (3072MB), size= 512MB: write-back, count=1
reg03: base=0x100000000 (4096MB), size= 512MB: write-back, count=1
reg04: base=0xfeda0000 (4077MB), size= 128KB: uncachable, count=1
reg05: base=0xf0000000 (3840MB), size= 128MB: write-combining, count=1


Where to continue to?
P.S. I'm not on the list, so please CC me.
--
Zaar

             reply	other threads:[~2006-01-26 14:21 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-26 14:20 Hai Zaar [this message]
2006-01-26 14:51 ` vesa fb is slow on 2.6.15.1 Antonino A. Daplas
2006-01-26 16:06   ` Hai Zaar
2006-01-26 16:40     ` Alistair John Strachan
2006-01-26 22:04     ` Antonino A. Daplas
2006-01-27  0:10       ` Hai Zaar
2006-01-27  0:19         ` Hai Zaar
2006-01-27  6:02         ` Antonino A. Daplas
2006-01-27 16:32           ` Hai Zaar
2006-01-27 17:21             ` Antonino A. Daplas
2006-01-28  0:31               ` Hai Zaar
     [not found]               ` <cfb54190601271628j774df3d0xce0ab24c8abca845@mail.gmail.com>
     [not found]                 ` <43DABCF6.4000904@gmail.com>
2006-01-28  0:54                   ` Hai Zaar
2006-01-28  1:02                     ` Antonino A. Daplas

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=cfb54190601260620l5848ba3ai9d7e06c41d98c362@mail.gmail.com \
    --to=haizaar@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;
as well as URLs for NNTP newsgroup(s).