linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: linux-fbdev-devel@lists.sourceforge.net,
	"sparclinux@vger.kernel.org" <sparclinux@vger.kernel.org>
Cc: mt1@systella.fr,
	"bugme-daemon@kernel-bugs.osdl.org"
	<bugme-daemon@bugzilla.kernel.org>
Subject: Re: [Bugme-new] [Bug 8232] New: Creator3D Framebuffer (sparc64) on Sbus/UPA workstation
Date: Mon, 19 Mar 2007 03:34:25 -0800	[thread overview]
Message-ID: <20070319033425.b0be2d95.akpm@linux-foundation.org> (raw)
In-Reply-To: <200703191019.l2JAJVH5018137@fire-2.osdl.org>

On Mon, 19 Mar 2007 03:19:31 -0700 bugme-daemon@bugzilla.kernel.org wrote:

> http://bugzilla.kernel.org/show_bug.cgi?id=8232
> 
>            Summary: Creator3D Framebuffer (sparc64) on Sbus/UPA workstation
>     Kernel Version: ALL 2.6
>             Status: NEW
>           Severity: normal
>              Owner: jsimmons@infradead.org
>          Submitter: mt1@systella.fr
> 
> 
> Most recent kernel where this bug did *NOT* occur: 2.4.34.1
> Distribution: Debian/testing
> Hardware Environment: U1E/170 with Creator3D (UPA), U2 with creator3D
> Software Environment: debian without X on U1E, debian with Xorg on U2
> Problem Description: Console is white foreground and blanck background by
> default. Sometimes, the screen is cut like this :
> 
> N | N | N | N
> --+---+---+---
> N | G | G | G
> --+---+---+---
> N | W | W | W
> --+---+---+---
> N | G | G | G
> 
> 
> where N is a 'normal' console, 'G' a 'like grey' console (black and white pixels
> like snow), and 'W' a white console (many white pixels). I have tested some
> differents Creator3D fb and this trouble only occurs on Sbus/UPA workstation. On
> a U60 (PCI/UPA), I never see it.
> 
> When I launch Xorg, problem goes away.
> 
> Sometimes, on the same configuration, when X is running, console is not usable
> because foreground _and_ background are black (and a signal is given by the
> framebuffer, screen remains on).
> 
> Steps to reproduce: U1 or U2 with 2.6 kernel and Creator3D fb on UPA Slot.
> I have tested with Creator3D Rev1.
> 
> Regards,
> 
> JKB
> 
> ------- You are receiving this mail because: -------
> You are on the CC list for the bug, or are watching someone who is.

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV

       reply	other threads:[~2007-03-19 11:35 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200703191019.l2JAJVH5018137@fire-2.osdl.org>
2007-03-19 11:34 ` Andrew Morton [this message]
2007-03-26 23:12   ` [Bugme-new] [Bug 8232] New: Creator3D Framebuffer (sparc64) on Sbus/UPA workstation David Miller
2007-03-27  7:54     ` BERTRAND Joël
2007-03-27  8:04       ` David Miller
2007-03-27  8:18         ` BERTRAND Joël
2007-03-27  8:24           ` David Miller
2007-03-27  9:25     ` David Johnson
2007-07-02 18:03     ` BERTRAND Joël

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=20070319033425.b0be2d95.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=bugme-daemon@bugzilla.kernel.org \
    --cc=linux-fbdev-devel@lists.sourceforge.net \
    --cc=mt1@systella.fr \
    --cc=sparclinux@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).