From: Andrew Morton <akpm@osdl.org>
To: linux-fbdev-devel@lists.sourceforge.net
Subject: Fw: [Bugme-new] [Bug 3778] New: neofb: screen corruption
Date: Fri, 19 Nov 2004 16:08:27 -0800 [thread overview]
Message-ID: <20041119160827.64201d6f.akpm@osdl.org> (raw)
Begin forwarded message:
Date: Fri, 19 Nov 2004 15:36:37 -0800
From: bugme-daemon@osdl.org
To: bugme-new@lists.osdl.org
Subject: [Bugme-new] [Bug 3778] New: neofb: screen corruption
http://bugme.osdl.org/show_bug.cgi?id=3778
Summary: neofb: screen corruption
Kernel Version: 2.6.10-rc2
Status: NEW
Severity: blocking
Owner: aridtech@gmail.com
Submitter: aridtech@gmail.com
Distribution: Gentoo
Hardware Environment: IBM ThinkPad 570
Neomagic Corporation NM2200 [MagicGraph256AV] (rev 20)
440BX Motherboard
Software Environment:
It happens during kernel loading
Problem Description: It happens when kernal begin to load. All characters on the
screen are unreadable and contsist of lines and pixels. i can't attach dmesg
because i can't see what i type when this bug occurs.
As i discovered this bug was born after convertion MODULE_PARM to module_param
in neofb module because if copy unconverted neofb from 2.6.10-rc1 to rc2 and
compile it everything works ok.
Steps to reproduce:
Recompile kernel with neofb.
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
-------------------------------------------------------
This SF.Net email is sponsored by: InterSystems CACHE
FREE OODBMS DOWNLOAD - A multidimensional database that combines
robust object and relational technologies, making it a perfect match
for Java, C++,COM, XML, ODBC and JDBC. www.intersystems.com/match8
reply other threads:[~2004-11-20 0:04 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=20041119160827.64201d6f.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).