All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@osdl.org>
To: linux-fbdev-devel@lists.sourceforge.net
Cc: Petr Vandrovec <VANDROVE@vc.cvut.cz>
Subject: Fw: [Bugme-new] [Bug 6720] New: mga framebuffer flickers after upgrading to 2.6.17
Date: Mon, 19 Jun 2006 16:09:34 -0700	[thread overview]
Message-ID: <20060619160934.488944da.akpm@osdl.org> (raw)



Begin forwarded message:

Date: Mon, 19 Jun 2006 13:42:51 -0700
From: bugme-daemon@bugzilla.kernel.org
To: bugme-new@lists.osdl.org
Subject: [Bugme-new] [Bug 6720] New: mga framebuffer flickers after upgrading to 2.6.17


http://bugzilla.kernel.org/show_bug.cgi?id=6720

           Summary: mga framebuffer flickers after upgrading to 2.6.17
    Kernel Version: 2.6.17
            Status: NEW
          Severity: normal
             Owner: ak@suse.de
         Submitter: markus.gapp@ktv-one.at


Most recent kernel where this bug did not occur: 2.6.16.20
Distribution: gentoo -- vanilla sources
Hardware Environment: dual opteron, mga g550, lcd connected via dvi
Software Environment: framebuffer console
Problem Description: after upgrading to 2.6.17 on an opteron smp machine 
(x86_64 kernel) with a mga g550 vga several dots around letters on a 
framebuffer console are flickering. matroxfb is compiled as a module. 
this also happens to an X server using mga and fbhw submodule.

Steps to reproduce:

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.

                 reply	other threads:[~2006-06-19 23:06 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=20060619160934.488944da.akpm@osdl.org \
    --to=akpm@osdl.org \
    --cc=VANDROVE@vc.cvut.cz \
    --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 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.