Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 24 Mar 2001 19:26:47 -0600 (CST)
From:      Nate Dannenberg <natedac@kscable.com>
To:        <freebsd-bugs@freebsd.org>
Subject:   Re: X 4.0.3 and Savage driver
Message-ID:  <Pine.BSF.4.33.0103241901360.47484-100000@daconcepts.dyndns.org>

next in thread | raw e-mail | index | archive | help

This message is being posted to the freebsd-bugs mailing list and to the
author of the XFree86 4.X "savage" driver (for the author's privacy, I
BCC'd this message to him).

As some probably have noticed (considering I'm persistant when it comes to
a program that is misbehaving), I have a problem running X 4.x.x on my
machine.  Specifically, XFree86 4.0.2 and 4.0.3 will crash the kernel on
my IBM Aptiva (550 MHz Athlon, 96MB Ram, Number Nine SR9 video with
Savage4 chipset and 8M ram).


UPDATE:

After much testing and fooling around, and even trying a complete reformat
and reinstall from scratch (now running FreeBSD 4.3-RC CVSup'ed around 8pm
March 23, fresh ports tree also fetched at the same time), I've finally
made some progress on my problem.  Note: the only things I kept from the
previous install were my /usr/pub and /usr/home trees.  Everything else
that didn't have the system "immutable" flag set has been wiped, and my
root and /var partitions were wiped clean during the new install (set the
newfs flag to "yes" in disklabel).

I managed to get FreeBSD's crashdump recovery thing to work (was pointing
to a filesystem with inadequate space to save the dump before), and got
102MB in two files, from which I managed to get the kernel panic message
extracted from those files after reading the FreeBSD handbook.  I wasn't
aware it contained this kind of information until I ran across a message
here in -bugs (or was it in -stable?  Anyway)....  RTFM right? :-)

Anyways, here is some information from the crash, as obtained with gdb:

----- Text Import Begin -----

IdlePTD 3465216
initial pcb at 2ba4a0
panicstr: general protection fault
panic messages:
---
Fatal trap 9: general protection fault while in kernel mode
instruction pointer     = 0x8:0xc024b4a3
stack pointer           = 0x10:0xc76a9cf0
frame pointer           = 0x10:0xc76a9d10
code segment            = base 0x0, limit 0xfffff, type 0x1b
                        = DPL 0, pres 1, def32 1, gran 1
processor eflags        = resume, IOPL = 3
current process         = 344 (XFree86)
interrupt mask          = none
trap number             = 9
panic: general protection fault
syncing disks... 30 29 21 10
done
Uptime: 11m46s
dumping to dev #ad/0x20001, offset 205184
dump ata0: resetting devices .. done
95 94 93 92 91 90 89 88 87 86 85 84 83 82 81 80 79 78 77 76 75 74 73 72 71
70 69 68 67 66 65 64 63 62 61 60 59 58 57 56 55 54 53 52 51 50 49 48 47 46
45 44 43 4 2 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 0xc013ebba in dumpsys ()

----- Text Import End -----

This looks like a standard Panic display like I would normally have
seen on the screen, had the console not been hosed at the time of
panic (since X was int he middle of changing video settings of
course).

Then as the handbook mentioned, I typed "where" at the (kgdb) prompt, and
it responded with this:

----- Text Import Begin -----

#0  0xc013ebba in dumpsys ()
#1  0xc013e9db in boot ()
#2  0xc013ed58 in poweroff_wait ()
#3  0xc02575bd in trap_fatal ()
#4  0xc0256fcb in trap ()
#5  0xc024b4a3 in i686_mrstoreone ()
#6  0xc024b3e9 in i686_mrstore ()
#7  0xc024ba21 in i686_mrset ()
#8  0xc0252a81 in mem_range_attr_set ()
#9  0xc02529fd in mem_ioctl ()
#10 0xc02528b4 in mmioctl ()
#11 0xc017545e in spec_ioctl ()
#12 0xc0175189 in spec_vnoperate ()
#13 0xc0209a3d in ufs_vnoperatespec ()
#14 0xc0171a44 in vn_ioctl ()
#15 0xc014d10e in ioctl ()
#16 0xc0257869 in syscall2 ()
#17 0xc0249b95 in Xint0x80_syscall ()
#18 0x8091059 in ?? ()
#19 0x80955c7 in ?? ()
#20 0x87760dd in ?? ()
#21 0x8758e32 in ?? ()
#22 0x806b7cc in ?? ()
#23 0x80bab12 in ?? ()
#24 0x806b045 in ?? ()

----- Text Import End -----

Do any of these messages help?  My kernel was built without debugging
symbols, so the information I can gather from these particular dumps is
probably limited.  If necessary, I'll rebuild my kernel with more
debugging information, and allow another crash to take place.

-- 
 /~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~___~~~~~\
|  natedac@kscable.com              //Z@|___  |
|  http://home.kscable.com/natedac |'(__ [_<  |
 \_C64/C128_-_What's_*YOUR*_hobby?__\___|____/




To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.33.0103241901360.47484-100000>