Swap your mouse and keyboard. It appears you have them plugged in
backwards.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Brent Casavant
Sent: Tuesday, September 13, 2005 9:48 AM
To: freebsd-stable@freebsd.org
Subject: Garbled VGA text console
Hello,
I've searched the bug database and Googled for the following problem,
to no avail, but hopefully querying -stable will help.
I am experiencing garbled text consoles on 5.4-RELEASE (sorry, no
prior data). All sc consoles have repeated/missing/overwritten
characters across the entire screen. Furthermore, as I move the
mouse cursor across the screen, the incorrect display continually
changes in the rows and columns near the cursor. However, the mouse
is not a necessary component of the dyslexic (no offense intended,
I can certainly believe this is just what dyslexia sufferers would
perceive in their daily life) display -- a kernel configured without
mouse support at all still exhibits the problem.
The problem occurs as soon as the kernel is handed control from
the loader (the loader has no such problem, for what its worth) --
boot messages and the like are corrupted with the duplicated and
missing and overwritten characters. This is an important point,
I believe, as corruption occurs even before the APs are launched.
As an example, here's what ttyv0 looks like at this moment:
--- cut here ---
Starting sshd.
StStting sendmail.
Initial i3i386 intialization.
dititial ABIBIupuprt: : svipipsynuxpostfix/postfix-script: starting
thththstfi
x maililys s s s s
vr4.4.
Startiti cron.
vfs ruleset: error converting to n nber:r:/usrsrocalaltc/d/dfs.r.res
/etc/rc: WARNING: defvf_set_ruruset: unablblto s s
rululuseseses/localaltc/devfs
.rules to /dev
devfs ruleleleror cocococong t tnumbmbo o usr/lolol/etc/devfs.rules
/etctc: WARNIARAR devfsvfs_s_s_ruleset: unable to apply ruleset
$/usr/l/l/l/ltc/
devevevuleseso /d/d
Local packagaginititlization:Starting saslauthd1.
.
Additional TCP options:.
t n moused:.
Starting inetd.
Starting backgrorod file sle m sm chchks i i60 s sonds.
Tue SeSeSeSe9:4747:5:5:5200505
eeBSD/i386 (chenjesususutyv0v0
login:
--- cut here ---
The most relevant details that I can think of that might matter are
that the machine is quad-processor (4x500MHz PIII Xeon), and has
two seperate VGA controllers. The onboard VGA controller is a
Cirrus Logic GD 5480, but is (mostly?) disabled by the BIOS when
it detects the Matrox G400 card (dual-head configuration).
The X server doesn't encounter any problem, and configuring with
option VGA_SLOW_IOACCESS doesn't help.
To me this smells like a multiprocessor problem (e.g. we see some
output repeated 4 times in the example above, but never more than 4).
Does this sound familiar to anyone?
dmesg output and an lspci -v output are included below. Note that
the Matrox card is identified as AGP in the lspci output, even
though it is actually a PCI card. *shrug*
--- cut here ---
chenjesu# dmesg
Copyright (c) 1992-2005 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
The Regents of the University of California. All rights
reserved.
FreeBSD 5.4-RELEASE-p7 #15: Mon Sep 12 20:11:55 CDT 2005
[EMAIL PROTECTED]:/usr/obj/usr/src/sys/chenjesu
ACPI APIC Table:
Timecounter "i8254" frequency 1193182 Hz quality 0
CPU: Pentium III/Pentium III Xeon/Celeron (500.15-MHz 686-class CPU)
Origin = "GenuineIntel" Id = 0x672 Stepping = 2
Features=0x387fbff
real memory = 3221200896 (3071 MB)
avail memory = 3150848000 (3004 MB)
FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs
cpu0 (BSP): APIC ID: 3
cpu1 (AP): APIC ID: 0
cpu2 (AP): APIC ID: 1
cpu3 (AP): APIC ID: 2
ioapic0 irqs 0-63 on motherboard
lapic3: Forcing LINT1 to edge trigger
npx0: on motherboard
npx0: INT 16 interface
acpi0: on motherboard
acpi0: Power Button (fixed)
Timecounter "ACPI-safe" frequency 3579545 Hz quality 1000
acpi_timer0: <24-bit timer at 3.579545MHz> port 0xc08-0xc0b on acpi0
cpu0: on acpi0
cpu1: on acpi0
cpu2: on acpi0
cpu3: on acpi0
pcib0: port 0xcf8-0xcff on acpi0
pci0: on pcib0
pcib1: at device 6.0 on pci0
pci1: on pcib1
pci1: at device 0.0 (no driver attached)
pcm0: port 0x2400-0x241f irq 17 at device 7.0 on pci0
pcm0:
sym0: <810a> port 0x2000-0x20ff mem 0xf810-0xf81000ff irq 58 at
device 8.0 on pci0
sym0: No NVRAM, ID 7, Fast-10, SE, parity checking
fxp0: port 0x2420-0x243f mem
0xf800-0xf80f,0xf920-0xf9200fff irq 18 at device 9.0 on pci0
miibus0: on fxp0
inphy0: on miibus0
inphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
fxp0: Ethernet address: 00:90:27:aa:39:13
pci0: at device 10.0 (no driver attached)
pci0: at device 11.0 (no driver
attached)
isab0: at device 12.0 on pci0
isa0: on isab0
atapci0: port
0x2460-0x246f,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 at device 12.1 on pci0
ata0: channel #0 on atapci0
ata1: channel #1 on atapci0
uhci0: port 0x2440-0x245f irq
54 at devi
