linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Antonino A. Daplas" <adaplas@gmail.com>
To: Hai Zaar <haizaar@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: vesa fb is slow on 2.6.15.1
Date: Sat, 28 Jan 2006 01:21:05 +0800	[thread overview]
Message-ID: <43DA5681.2020305@gmail.com> (raw)
In-Reply-To: <cfb54190601270832x29681873i624818603d5db26e@mail.gmail.com>

Hai Zaar wrote:
>>> But anyway, do you have a clue why do I still get this error?
>>> PCI: Failed to allocate mem resource #6:20000@f8000000 for 0000:40:00.0
>>> I've several workstations with _exactly_ the same hardware. I've tried
>>> two of them - both give the error with 2.6.15.1 (and no errors with
>>> 2.6.11.12).
>> Can you post the entire dmesg?
>>
>> Tony
>>
> 
> Attached.
> 

Looks harmless to me.

Can you check /proc/iomem just to verify if that particular address has
been reserved by the OS.

And, are you experiencing any problems with your nvidia card, ie, are
you able to launch X?

Tony

  reply	other threads:[~2006-01-27 17:20 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-26 14:20 vesa fb is slow on 2.6.15.1 Hai Zaar
2006-01-26 14:51 ` 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 [this message]
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=43DA5681.2020305@gmail.com \
    --to=adaplas@gmail.com \
    --cc=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).