Bug 885 - neofb has issue with scrollback
Summary: neofb has issue with scrollback
Status: REJECTED INSUFFICIENT_DATA
Alias: None
Product: Drivers
Classification: Unclassified
Component: Console/Framebuffers (show other bugs)
Hardware: i386 Linux
: P2 normal
Assignee: James Simmons
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-07-07 11:52 UTC by Leslie Donaldson
Modified: 2005-07-31 13:52 UTC (History)
2 users (show)

See Also:
Kernel Version: 2.5.74
Subsystem:
Regression: ---
Bisected commit-id:


Attachments

Description Leslie Donaldson 2003-07-07 11:52:26 UTC
Distribution: redahat 7.2
Hardware Environment: son vaio (PCG-F490) intel laptop
Software Environment:Redhat
Problem Description:
1. When booting no penguin :(
2. After dumping a large section of text to the screen (console mode)
   the frame buffer moves it's virtual window to the top of the buffer.
   A switch between virtual consoles brings it back correctly.
3. On a side note, compile time options for selecting external output would be 
   cool because it dosen't listen to module arguments when compiled in...

Info follows:

#
# Graphics support
#
CONFIG_FB=y
# CONFIG_FB_CIRRUS is not set
# CONFIG_FB_PM2 is not set
# CONFIG_FB_CYBER2000 is not set
# CONFIG_FB_IMSTT is not set
# CONFIG_FB_VGA16 is not set
# CONFIG_FB_VESA is not set
CONFIG_VIDEO_SELECT=y
# CONFIG_FB_HGA is not set
# CONFIG_FB_RIVA is not set
# CONFIG_FB_I810 is not set
# CONFIG_FB_MATROX is not set
# CONFIG_FB_RADEON is not set
# CONFIG_FB_ATY128 is not set
# CONFIG_FB_ATY is not set
# CONFIG_FB_SIS is not set
CONFIG_FB_NEOMAGIC=y
# CONFIG_FB_3DFX is not set
# CONFIG_FB_VOODOO1 is not set
# CONFIG_FB_TRIDENT is not set
# CONFIG_FB_PM3 is not set
# CONFIG_FB_VIRTUAL is not set

#
# Console display driver support
#
CONFIG_VGA_CONSOLE=y
# CONFIG_MDA_CONSOLE is not set
CONFIG_DUMMY_CONSOLE=y
CONFIG_FRAMEBUFFER_CONSOLE=y
CONFIG_PCI_CONSOLE=y
# CONFIG_FONTS is not set
CONFIG_FONT_8x8=y
CONFIG_FONT_8x16=y

#
# Logo configuration
#
CONFIG_LOGO=y
CONFIG_LOGO_LINUX_MONO=y
CONFIG_LOGO_LINUX_VGA16=y
CONFIG_LOGO_LINUX_CLUT224=y

dmesg info:

ory: 256672k/262080k available (1317k kernel code, 5020k reserved, 525k data,
96k init, 0k highmem)
Dentry cache hash table entries: 32768 (order: 6, 262144 bytes)
Inode cache hash table entries: 16384 (order: 5, 131072 bytes)
Mount cache hash table entries: 512 (order: 0, 4096 bytes)
Buffer-cache hash table entries: 16384 (order: 4, 65536 bytes)
Page-cache hash table entries: 65536 (order: 6, 262144 bytes)
CPU: L1 I cache: 16K, L1 D cache: 16K
CPU: L2 cache: 256K
Intel machine check architecture supported.
Intel machine check reporting enabled on CPU#0.
CPU:     After generic, caps: 0383f9ff 00000000 00000000 00000000
CPU:             Common caps: 0383f9ff 00000000 00000000 00000000
CPU: Intel Pentium III (Coppermine) stepping 01
Enabling fast FPU save and restore... done.
Enabling unmasked SIMD FPU exception support... done.
Checking 'hlt' instruction... OK.
POSIX conformance testing by UNIFIX
mtrr: v1.40 (20010327) Richard Gooch (rgooch@atnf.csiro.au)
mtrr: detected mtrr type: Intel
PCI: PCI BIOS revision 2.10 entry at 0xfd99e, last bus=1
PCI: Using configuration type 1
PCI: Probing PCI hardware
PCI: Using IRQ router PIIX [8086/7110] at 00:07.0
PCI: Found IRQ 9 for device 00:0c.0
Limiting direct PCI/PCI transfers.
Linux NET4.0 for Linux 2.4
Based upon Swansea University Computer Society NET3.039
Initializing RT netlink socket
apm: BIOS version 1.2 Flags 0x03 (Driver version 1.16)
Starting kswapd
Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
neofb: mapped io at d0800000
Panel is a 1024x768 color TFT display
neofb: mapped framebuffer at d0a01000
neofb v0.3.2: 6144kB VRAM, using 1024x768, 48.361kHz, 60Hz
Console: switching to colour frame buffer device 128x48
fb0: MagicGraph 256XL+ frame buffer device
pty: 256 Unix98 ptys configured
Real Time Clock Driver v1.10e
Uniform Multi-Platform E-IDE driver Revision: 7.00beta4-2.4
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
PIIX4: IDE controller at PCI slot 00:07.1
PIIX4: chipset revision 1
PIIX4: not 100% native mode: will probe irqs later
    ide0: BM-DMA at 0xfcf0-0xfcf7, BIOS settings: hda:DMA, hdb:pio
    ide1: BM-DMA at 0xfcf8-0xfcff, BIOS settings: hdc:DMA, hdd:pio
hda: IBM-DARA-218000, ATA DISK drive
blk: queue c03104e0, I/O limit 4095Mb (mask 0xffffffff)
hdc: TORiSAN DVD-ROM DRD-U624, ATAPI CD/DVD-ROM drive
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
ide1 at 0x170-0x177,0x376 on irq 15
hda: attached ide-disk driver.
hda: host protected area => 1
hda: 35433216 sectors (18142 MB) w/418KiB Cache, CHS=2205/255/63, UDMA(33)
Partition check:
 hda: hda1 hda2 hda4 < hda5 hda6 hda7 >
ohci1394: $Rev: 896 $ Ben Collins <bcollins@debian.org>
PCI: Enabling device 00:08.0 (0000 -> 0002)
PCI: Assigned IRQ 9 for device 00:08.0
PCI: Sharing IRQ 9 with 00:07.2
ohci1394_0: Remapped memory spaces reg 0xd1002000
ohci1394_0: Soft reset finished

Steps to reproduce:
Comment 1 Philip Armstrong 2003-10-28 08:54:21 UTC
I'm seeing very similar problems with neofb on a Thinkpad 600E (neomagic
magicgraph 256AV) fwiw. Kernel is 2.6.0-test9
Comment 2 Philip Armstrong 2004-12-06 03:14:58 UTC
Fwiw, I'm still seeing on screen corruption with neofb in 2.6.9

It's not as bad as it used to be -- heavy scrolling no longer hangs the machine
and you don't get the 'half your screen has just disappeared for good' issues --
but editing in vi is pretty much guarenteed to corrupt the display (deleting a
character with 'x' seems to cause an entire line to be currupted for instance).

Viewing webpages with links seems to cause random littering of characters all
over the place after a suiable amount of scrolling.

Machine is a Thinkpad 600E as before.

Steps to reproduce: modprobe neofb, fbcon. Start vi on a suitable text file,
delete a character with 'x'. Usually instant screen corruption.
Comment 3 Nishanth Aravamudan 2005-02-17 11:06:51 UTC
Thanks for the update, Philip. These problems still exist with 2.6.11-rc4? Would
you be willing to test patches (just verifying you still have access to hw)?
Comment 4 Adrian Bunk 2005-07-31 13:52:11 UTC
There was no answer to the question whether this issue is still present in
recent kernels.

Please reopen this bug if it is still present.

Note You need to log in before you can comment on or make changes to this bug.