Date: Fri, 17 Dec 1999 09:33:58 -0500 From: "Brian J. McGovern" <mcgovern@spoon.beta.com> To: Colin <cwass99@home.com> Cc: freebsd-qa@FreeBSD.ORG Subject: Re: Kernel Panic when VESA support compiled in Message-ID: <199912171433.JAA89085@spoon.beta.com> In-Reply-To: Your message of "Thu, 16 Dec 1999 22:33:55 EST." <XFMail.19991216223355.cwass99@home.com>
next in thread | previous in thread | raw e-mail | index | archive | help
"Next day or so" might be too long. Jordan is chomping at the bit to get 3.4 out :) Try toggling just the VESA part in and out, and see if its the VESA code, or the VM86 code that is causing the panic. -Brian > I compiled in VESA support to use a better splash.bmp, and imagine my > surprise when I saw a kernel panic. The applicable information is as follow s: > > changing root device to wd0s1a > > > Fatal trap 18: integer divide fault while in kernel mode > * > * > * > code segment = base 0x0, limit 0xfffff, type 0x1b > = DPL 0, pres 1, def32 1, gran 1 > processor eflags = interrupt enabled, resume, IOPL=8 > current process = 5(init) > interupt mask = net tty bio cam > trap number = 18 > panic: integer divide fault > > uname -a > ************************************************************************** > FreeBSD tristan.net 3.4-RC FreeBSD 3.4-RC #3: Thu Dec 16 21:47:26 EST 1999 > root@tristan.net:/usr/src/sys/compile/MARVIN i386 > > dmesg > **************************************************************************** ** > FreeBSD 3.4-RC #3: Thu Dec 16 21:47:26 EST 1999 > root@tristan.net:/usr/src/sys/compile/MARVIN > Timecounter "i8254" frequency 1193182 Hz > Timecounter "TSC" frequency 116611094 Hz > CPU: AMD-K5(tm) Processor (116.61-MHz 586-class CPU) > Origin = "AuthenticAMD" Id = 0x524 Stepping = 4 > Features=0x21bf<FPU,VME,DE,PSE,TSC,MSR,MCE,CX8,PGE> > AMD Features=0x0 > real memory = 67108864 (65536K bytes) > avail memory = 62480384 (61016K bytes) > Preloaded elf kernel "kernel" at 0xc02a7000. > Preloaded elf module "splash_bmp.ko" at 0xc02a709c. > Preloaded splash_image_data "/boot/splash.bmp" at 0xc02a7140. > Probing for devices on PCI bus 0: > chip0: <Intel 82437VX PCI cache memory controller> rev 0x02 on pci0.0.0 > chip1: <Intel 82371SB PCI to ISA bridge> rev 0x01 on pci0.7.0 > ide_pci0: <Intel PIIX3 Bus-master IDE controller> rev 0x00 on pci0.7.1 > ed1: <NE2000 PCI Ethernet (RealTek 8029)> rev 0x00 int a irq 11 on pci0.10.0 > ed1: address 00:00:b4:59:37:bd, type NE2000 (16 bit) > vga0: <ATI Mach64-VT graphics accelerator> rev 0x48 on pci0.11.0 > Probing for PnP devices: > CSN 1 Vendor ID: CTL0070 [0x70008c0e] Serial 0xffffffff Comp ID: PNPb02f > [0x2fb0d041] > Probing for devices on the ISA bus: > ...etc... > (only my 2 IDE disk drives found from here) > > The most important bit is that the video card is a Mach 64-VT, 2 Meg RA M, > and this happens with 320X200 and 640X480 bitmaps for the splash. To > confirm, I rebuilt my kernel without the 2 lines: > > #options "VM86" > #options "VESA" > > (no other changes) and the panic stopped, but the splash works great. Tried > rebooting from the previos kernel (as kernel.old...sometimes it's good to ke ep > a known problem kernel ;)), it didn't load the splash but it still panicked. > I don't see this as a release stopper, but it's a problem. Are there a ny > known problems with Mach 64's? Or VESA support in general? > Let me know if any further information would help. I plan to root thro ugh > the source for VESA support over the next day or so, maybe I can see somethi ng. > > Cheers, > Colin > > ---------------------------------- > E-Mail: Colin <cwass99@home.com> > Date: 16-Dec-1999 > Time: 22:09:18 > > This message was sent by XFMail > ---------------------------------- > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-qa" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-qa" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199912171433.JAA89085>