Bug 36282

Summary:	framebuffer console corrupted with 2.4.22 kernel
Product:	Gentoo Linux	Reporter:	André Terpstra <andre>
Component:	[OLD] Core system	Assignee:	Brian Jackson (RETIRED) <iggy>
Status:	RESOLVED FIXED
Severity:	major	CC:	x86-kernel
Priority:	High
Version:	unspecified
Hardware:	x86
OS:	Linux
Whiteboard:
Package list:		Runtime testing required:	---

Description André Terpstra 2003-12-22 00:35:36 UTC

I have been using a VESA VGA framebuffer console from the 2.4.20 kernels for months without any problem. However, in the new 2.4.22 kernel the console has become corrupted. After every 25 lines or so, the screen is filled with white bars covering the whole line. After another few lines (about the same 25 I estimate) the screen suddenly returns.

Reproducible: Always
Steps to Reproduce:
1. Enable framebuffer in the kernel the ususal way (with MTRR, only VESA VGA driver etc.)
2. Rebuild the kernel & nVidia drivers & ALSA drivers
3. Reboot with framebuffer selected (kernel (hd0,11)/boot/bzImage root=/dev/hda13 vga=0x31A video=vesa:ywrap,mtrr hdd=ide-scsi)
4. Start working from the console (not X)

Actual Results:  
See above 

Expected Results:  
See above 

Portage 2.0.49-r15 (default-x86-1.4, gcc-3.2.3, glibc-2.3.2-r3, 2.4.22-gentoo-r2) 
================================================================= 
System uname: 2.4.22-gentoo-r2 i686 Intel(R) Pentium(R) 4 CPU 2.40GHz 
Gentoo Base System version 1.4.3.10 
ACCEPT_KEYWORDS="x86" 
AUTOCLEAN="yes" 
CFLAGS="-O3 -march=pentium4 -funroll-loops -pipe" 
CHOST="i686-pc-linux-gnu" 
COMPILER="gcc3" 
CONFIG_PROTECT="/etc /var/qmail/control /usr/kde/2/share/config 
/usr/kde/3/share/config /usr/X11R6/lib/X11/xkb /usr/kde/3.1/share/config 
/usr/share/texmf/tex/generic/config/ /usr/share/texmf/tex/platex/config/ 
/usr/share/config" 
CONFIG_PROTECT_MASK="/etc/gconf /etc/env.d" 
CXXFLAGS="-O3 -march=pentium4 -funroll-loops -pipe" 
DISTDIR="/usr/portage/distfiles" 
FEATURES="sandbox ccache autoaddcvs" 
GENTOO_MIRRORS="ftp://Gentoomirror/gentoo" 
MAKEOPTS="-j2" 
PKGDIR="/usr/portage/packages" 
PORTAGE_TMPDIR="/var/tmp" 
PORTDIR="/usr/portage" 
PORTDIR_OVERLAY="" 
SYNC="rsync://Gentoomirror/gentoo-portage" 
USE="x86 oss avi crypt cups encode foomaticdb gif gtk2 jpeg libg++ mad mikmod 
mpeg ncurses nls pdflib png quicktime spell truetype xml2 xmms xv zlib directfb alsa 
gdbm berkdb slang readline arts tetex aalib svga X sdl gpm tcpd pam libwww ssl perl 
python imlib oggvorbis qt kde motif opengl gphoto2 cdr scanner 3dnow acpi acpi4linux 
amd artswrappersuid autofs cgi dga doc dvd fastcgi fax fbcon foreign-package 
foreign-sysvinit freetype fs imap java javascript mmx mozilla msn nocd nvidia oav 
offensive openssh pcap ppds samba sasl slp snmp sse tiff transcode type1 usb X509 
xvid -apm -gnome -gtk"

Comment 1 Tim Yamin (RETIRED) gentoo-dev

2003-12-22 13:37:52 UTC

Do you get this both in -r1 and -r2?

Comment 2 André Terpstra 2003-12-22 15:02:10 UTC

Yes. I'm using a 2.4.22-gentoo-r2 kernel right now, but I'm pretty sure that it was the same under r1. In fact the error started to show up after trying gentoo-test-sources on request of Bob Johnson (I think) because of another bug in the 2.4.20 kernel series, which is now solved and seems to be closed.

Comment 3 Brian Jackson (RETIRED) gentoo-dev

2003-12-22 20:31:04 UTC

Can you tell me if a vanilla kernel exibits this as well? Also can you try taking that video= stuff out of your grub config.

Comment 4 André Terpstra 2003-12-23 00:14:45 UTC

Wow: taking "video=vesa:ywrap,mtr"r out of the grub line completely solved the problem! Did I miss something in the documentation?

Also, I only did a brief check because I'm in a hurry, but it looks OK now. Thanks so far.

Comment 5 Tim Yamin (RETIRED) gentoo-dev

2003-12-23 06:43:58 UTC

This looks like it's fixed. If you still get this, feel free to reopen this bug.

Comment 6 divin4fun 2003-12-29 10:44:22 UTC

I also have this problem, which has also caused my machine to poweroff in a repeatable manner when I was trying to emerge pcmcia-cs.  Removing the video line from the kernel boot parameters did seem to resolve this, but then I don't have framebuffer support, so my console is back to the default.  Should this bug really be closed or am I missing something?

Comment 7 André Terpstra 2003-12-29 10:59:49 UTC

I don't follow you. You say you don't have FB? Well that was my start. So if you have the same problem I used to have (but now it's gone) without FB it may be a new bug...

Comment 8 divin4fun 2003-12-29 11:52:10 UTC

Perhaps I stated it poorly.  Without that parameter the video mode isn't changed, so your console will look like a standard console without framebuffer support, unless I'm missing something.