From: Andrew Morton <akpm@osdl.org>
To: linux-fbdev-devel@lists.sourceforge.net
Subject: Fw: [Bugme-new] [Bug 7176] New: Mach64 framebuffer console hangs when compiled with gcc 4.1
Date: Thu, 21 Sep 2006 10:09:36 -0700 [thread overview]
Message-ID: <20060921100936.6bfad4ba.akpm@osdl.org> (raw)
Begin forwarded message:
Date: Thu, 21 Sep 2006 05:51:41 -0700
From: bugme-daemon@bugzilla.kernel.org
To: bugme-new@lists.osdl.org
Subject: [Bugme-new] [Bug 7176] New: Mach64 framebuffer console hangs when compiled with gcc 4.1
http://bugzilla.kernel.org/show_bug.cgi?id=7176
Summary: Mach64 framebuffer console hangs when compiled with gcc
4.1
Kernel Version: 2.6.18
Status: NEW
Severity: normal
Owner: jsimmons@infradead.org
Submitter: jernej-bugzilla.kernel@ena.si
Most recent kernel where this bug did not occur: ?
Distribution: Gentoo
Hardware Environment: 1) Compaq ProLiant ML330 G2 server [Pentium III 1066MHz]
2) HP ML350G4 [Xeon 3GHz EM64T]
Software Environment:
Problem Description: I first noticed the problem with Gentoo's 2.6.16-r8 kernel
on ML330 server (running Debian Etch, but with Gentoo kernel) - kernel compiled
with GCC 4.0, worked fine, but when I recompiled the same kernel with gcc
4.1.2, the kernel locks up at bootup, when it's supposed to switch to graphic
console. I confirmed the same lockup with vanilla 2.6.18 kernel (which is why
I'm reporting here).
The same thing also happens on ML350G4 server with kernel 2.6.17-gentoo-r8
[running in 64bit mode] (previous kernel, compiled with gcc 3.4.6 works, but
when recompiled with gcc 4.1.1, it too locks up in apparently the same way;
unfortunately I'm not able to test with a vanilla kernel there).
Steps to reproduce: Enable Device Drivers -> Graphics support -> <*> Support
for frame buffer devices -> <*> ATI Mach64 display support, [*] Mach64 CT/VT/
GT/LT (incl. 3D RAGE) support, [*] Mach64 GX support; compile with gcc 4.1.1
or 4.1.2, boot.
------- 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:[~2006-09-21 17:09 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=20060921100936.6bfad4ba.akpm@osdl.org \
--to=akpm@osdl.org \
--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 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).