Date: Mon, 9 Jul 2001 22:25:18 +0100 From: Nuno Subtil <nsubtil@subtil.dhis.dee.uc.pt> To: freebsd-mobile@freebsd.org Subject: Toshiba Satellite Pro 4290 and VESA_800x600 console Message-ID: <20010709222518.A50189@subtil.dhis.dee.uc.pt>
next in thread | raw e-mail | index | archive | help
I have a Satellite Pro 4290 from Toshiba, running 5-CURRENT (updated
yesterday). It shows strange behaviour when switching the console to
VESA_800x600 mode: sometimes it panics with a black screen, sometimes it hangs
with a black screen (plus a constant beep ocasionally), sometimes it just
works. What's really amazing is that if I manage, for example, to set the first
vty to VESA_800x600, while leaving the second in 80x25 text mode, I can switch
between them with impunity --- the machine has never crashed that way, while it
crashes 9 times out of 10 when switching to VESA_800x600 mode.
I have captured a crash dump from one of the panics:
IdlePTD 4341760
initial pcb at 36dde0
panicstr: page fault
panic messages:
---
Fatal trap 12: page fault while in vm86 mode
fault virtual address = 0xc51e4
fault code = user read, page not present
instruction pointer = 0xc000:0x51e4
stack pointer = 0x0:0xf98
frame pointer = 0x0:0xfce
code segment = base 0x4c031, limit 0x1818, type 0x0
= DPL 0, pres 0, def32 0, gran 0
processor eflags = interrupt enabled, resume, vm86, IOPL = 0
current process = 38 (vidcontrol)
trap number = 12
panic: page fault
syncing disks...
done
Uptime: 4m5s
dumping to dev ad0s3b, offset 131328
dump ata0: resetting devices .. done
63 62 61 60 59 58 57 56 55 54 53 52 51 50 49 48 47 46 45 44 43 42 41 40 39 38 37 36 35 34 33 32 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
---
#0 dumpsys () at ../../../kern/kern_shutdown.c:478
478 if (dumping++) {
(kgdb) bt
#0 dumpsys () at ../../../kern/kern_shutdown.c:478
#1 0xc01d1e67 in boot (howto=256) at ../../../kern/kern_shutdown.c:321
#2 0xc01d2268 in poweroff_wait (junk=0xc030b9cf, howto=-981498560)
at ../../../kern/kern_shutdown.c:600
#3 0xc02c3e08 in trap_fatal (frame=0xc0427fa8, eva=807396)
at ../../../i386/i386/trap.c:932
#4 0xc02c3b79 in trap_pfault (frame=0xc0427fa8, usermode=0, eva=807396)
at ../../../i386/i386/trap.c:846
#5 0xc02c3583 in trap (frame={tf_fs = 0, tf_es = 0, tf_ds = 0,
tf_edi = 22522, tf_esi = 4212, tf_ebp = 4046, tf_isp = -1069383724,
tf_ebx = 21, tf_edx = 128, tf_ecx = 21507, tf_eax = 0, tf_trapno = 12,
tf_err = 4, tf_eip = 20964, tf_cs = 49152, tf_eflags = 721478,
tf_esp = 3992, tf_ss = 0}) at ../../../i386/i386/trap.c:405
#6 0x51e4 in ?? ()
Cannot access memory at address 0xfce.
The graphics chip is an S3 Savage IX/MV. The following appears on dmesg after a
verbose boot:
VESA: information block
56 45 53 41 00 02 a7 88 00 c0 00 00 00 00 22 00
00 01 80 00 00 01 5d 81 00 c0 6e 81 00 c0 76 81
00 c0 00 01 01 01 02 01 03 01 04 01 05 01 06 01
07 01 0e 01 0f 01 11 01 12 01 14 01 15 01 17 01
VESA: 48 mode(s) found
VESA: v2.0, 8192k memory, flags:0x0, mode table:0xc0384c42 (1000022)
VESA: S3 Incorporated. M7 BIOS
VESA: S3 Incorporated. VBE 2.0 Rev 1.1
Using $PIR table, 9 entries at 0xc00f0190
Any help would be greatly appreciated. This machine has a DSTN screen, so
VESA_800x600 is especially useful for me, since 80x25 text mode only uses about
half the screen.
Nuno Subtil
nsubtil@subtil.dhis.dee.uc.pt
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-mobile" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20010709222518.A50189>