From owner-freebsd-questions Thu Dec 26 07:30:31 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id HAA24314 for questions-outgoing; Thu, 26 Dec 1996 07:30:31 -0800 (PST) Received: from westlake.tkg.com (westlake.tkg.com [198.3.130.68]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id HAA24309 for ; Thu, 26 Dec 1996 07:30:28 -0800 (PST) Received: from spycam.tkg.com (spycam.tkg.com [198.3.130.106]) by westlake.tkg.com (8.7.5/8.7.3) with SMTP id JAA16014; Thu, 26 Dec 1996 09:30:23 -0600 (CST) Date: Thu, 26 Dec 1996 09:30:22 -0600 (CST) From: Curt Finch To: Greg Lehey cc: FreeBSD Questions Subject: Re: crash traceback In-Reply-To: <199612260254.DAA26571@freebie.lemis.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-questions@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk this has been fixed with a change to the mouse driver /dev/mse0 by wunsch and dropped into latest freebsd src thanx anyway On Thu, 26 Dec 1996, Greg Lehey wrote: > Curt Finch writes: > > > > > > this is a traceback from a crash that occurs on my machine whenever i > > try to fire up X. This happens with two completely different video > > cards (one S3 and one S3V) with no other hardware (i.e. no ethernet > > card or sound card) in the machine. > > I wonder how "completely different" these two boards are. Can you try > it with a completely different chip set (say, ATI or Cirrus)? > > > anyone have a clue? > > > > freebsd2.1.5 xfree86 3.2 vga16 xserver in this case but the s3v and s3 > > xservers also crash me > > > > i can make the dump and kernel available for analysis > > > > > > GDB 4.13 (i386-unknown-freebsd), > > Copyright 1994 Free Software Foundation, Inc... > > IdlePTD 207000 > > current pcb at 1f9210 > > panic: page fault > > #0 boot (howto=256) at ../../i386/i386/machdep.c:912 > > 912 dumppcb.pcb_ptd = rcr3(); > > (kgdb) #0 boot (howto=256) at ../../i386/i386/machdep.c:912 > > #1 0xf0112b73 in panic (fmt=0xf01a724c "page fault") > > at ../../kern/subr_prf.c:116 > > #2 0xf01a7d82 in trap_fatal (frame=0xefbffd6c) at ../../i386/i386/trap.c:748 > > #3 0xf01a78f4 in trap_pfault (frame=0xefbffd6c, usermode=0) > > at ../../i386/i386/trap.c:670 > > #4 0xf01a7563 in trap (frame={tf_es = 16, tf_ds = -257425392, tf_edi = 27, > > tf_esi = -1073545062, tf_ebp = -272630344, tf_isp = -272630380, > > tf_ebx = -2147483648, tf_edx = 0, tf_ecx = -266316512, tf_eax = 0, > > tf_trapno = 12, tf_err = 0, tf_eip = 0, tf_cs = 8, tf_eflags = 78470, > > tf_esp = -266598368, tf_ss = 0}) at ../../i386/i386/trap.c:310 > > This doesn't look nice. Your crash has wiped out the EIP register > (program counter), so you don't know where it happened. > > > #5 0xf019d451 in calltrap () > > #6 0xf012fb53 in spec_open (ap=0xefbffe1c) > > at ../../miscfs/specfs/spec_vnops.c:181 > > This is the function that called the function which crapped out. The > code at line 81 is: > > VOP_UNLOCK(vp); > error = (*cdevsw[maj].d_open)(dev, ap->a_mode, S_IFCHR, ap->a_p); > VOP_LOCK(vp); > > This looks as if you may have a corrupted cdevsw entry. With this > dump, try: > > (kgdb) f 6 (select this stack frame) > (kgdb) p maj (show the major device number) > (kgdb) p cdevsw [maj] (show the contents of the entry) > > I'd guess you'll find that cdevsw[maj].d_open is 0. > > Let me know what the results are, and we can look further. I don't > have time to go through a full dump analysis, however. > > Greg > -- Curt Finch - The Kernel Group Inc. - curt@tkg.com - (512)413-8005 - Find memory bugs even in stripped AIX binaries with a 7 day - - FREE Evaluation of ZeroFault at ... http://www.TKG.com/ -