From: David Airlie <airlied@redhat.com>
To: "Paweł Sikora" <pawel.sikora@agmk.net>
Cc: linux-kernel@vger.kernel.org, Don Morris <don.morris@hp.com>
Subject: Re: [3.6.2] oops @ opteron server: mgag200 Fatal error during GPU init
Date: Tue, 30 Oct 2012 17:30:18 -0400 (EDT) [thread overview]
Message-ID: <771860661.14080204.1351632618095.JavaMail.root@redhat.com> (raw)
In-Reply-To: <1528950.lfMO1YRB8m@localhost>
> On Friday 19 of October 2012 07:37:55 Don Morris wrote:
> > [drm:mga_vram_init] ERROR can't reserve VRAM
>
> Hi again, small update.
>
> i've figured out that loading uvesafb before mgag200 is causing this
> vram-reserve-error.
I think we need to kick uvesafb off like we kick efi and vesafb.
and then block it from loading afterwards.
Dave.
prev parent reply other threads:[~2012-10-30 21:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-19 11:53 [3.6.2] oops @ opteron server: mgag200 Fatal error during GPU init Paweł Sikora
2012-10-19 14:37 ` Don Morris
2012-10-28 15:09 ` Paweł Sikora
2012-10-30 17:43 ` Paweł Sikora
2012-10-30 21:30 ` David Airlie [this message]
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=771860661.14080204.1351632618095.JavaMail.root@redhat.com \
--to=airlied@redhat.com \
--cc=don.morris@hp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pawel.sikora@agmk.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