Panic during game installation with wine

Tobias Mohrlüder tobiasmo at
Sat Feb 2 22:02:31 UTC 2008


I get a panic during the installation of "Heroes of Might & Magic III"
via wine 0.9.54. This is with nvidia driver 100.14.19, with the FreeBSD AGP
driver enabled. I *did not* forget to rebuild the nvidia kernel module
after buildworld/buildkernel sessions. I updated to latest RELENG_7
today, same result. It does not occur with the nv driver.

This happens under FreeBSD 7.0-PRERELEASE i386 (RELENG_7 from january
24th and from today).


Unread portion of the kernel message buffer:
agp0: binding memory at bad offset 0x1f0a000

Fatal trap 12: page fault while in kernel mode
cpuid = 0; apic id = 00
fault virtual address   = 0xc
fault code              = supervisor read, page not present
instruction pointer     = 0x20:0xc08b6ed9
stack pointer           = 0x28:0xe99fc928
frame pointer           = 0x28:0xe99fc928
code segment            = base 0x0, limit 0xfffff, type 0x1b
                        = DPL 0, pres 1, def32 1, gran 1
processor eflags        = interrupt enabled, resume, IOPL = 0
current process         = 1140 (wine-pthread)
trap number             = 12
panic: page fault
cpuid = 0
Uptime: 26m41s
Physical memory: 991 MB
Dumping 119 MB: 104 88 72 56 40 24 8

#0  doadump () at pcpu.h:195
195     pcpu.h: No such file or directory.
        in pcpu.h
(kgdb) bt
#0  doadump () at pcpu.h:195
#1  0xc0736286 in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:409
#2  0xc0736479 in panic (fmt=Variable "fmt" is not available.
) at /usr/src/sys/kern/kern_shutdown.c:563
#3  0xc0a10bcc in trap_fatal (frame=0xe99fc8e8, eva=12)
    at /usr/src/sys/i386/i386/trap.c:899
#4  0xc0a10db0 in trap_pfault (frame=0xe99fc8e8, usermode=0, eva=12)
    at /usr/src/sys/i386/i386/trap.c:812
#5  0xc0a116f2 in trap (frame=0xe99fc8e8) at
#6  0xc09f9a7b in calltrap () at /usr/src/sys/i386/i386/exception.s:139
#7  0xc08b6ed9 in agp_memory_info (dev=0xc5455700, handle=0x0,
    at /usr/src/sys/pci/agp.c:968
#8  0xc1de8e07 in ?? ()
#9  0xc5455700 in ?? ()
#10 0x00000000 in ?? ()
#11 0xe99fc93c in ?? ()
#12 0xc062d267 in pci_read_config_method (dev=0xc545cc00, child=0x143,
    width=-375404180) at pcib_if.h:40
#13 0xc1de931d in ?? ()
[if you need the rest of the "... in ?? ()", please tell me]
#160 0xe99fcbc4 in ?? ()
#161 0xc070a2f6 in giant_ioctl (dev=0xc545cc00, cmd=323,
    data=0x1 <Address 0x1 out of bounds>, fflag=1, td=0x2)
    at /usr/src/sys/kern/kern_conf.c:349
Previous frame inner to this frame (corrupt stack?)
(kgdb) f 7
#7  0xc08b6ed9 in agp_memory_info (dev=0xc5455700, handle=0x0,
    at /usr/src/sys/pci/agp.c:968
(kgdb) l
963             return AGP_UNBIND_MEMORY(dev, mem);
964     }
966     void agp_memory_info(device_t dev, void *handle, struct
967                          agp_memory_info *mi)
968     {
969             struct agp_memory *mem = (struct agp_memory *) handle;
971             mi->ami_size = mem->am_size;
972             mi->ami_physical = mem->am_physical;

This is a vmcore from FreeBSD as of january the 24th. Unfortunatly I didn't
get a vmcore with buildworld from today, I don't know why.

The panic is reproducible (okay, I only gave it three shots, but it
happened in the same situation).

The kernel is GENERIC, but with SCHED_ULE and without I486_CPU and
I586_CPU. make.conf only has some CUPS and PERL defines (I don't
use src.conf yet).

Is this worth a bug report? Or should this be posted at the nvidia forums

I'm not on the list, so please CC me (*).

- Tobias Mohrlüder

(*) I still have no idea how to create emails the mailman software can
handle correctly. Last time my replies always initiated new threads.
Sorry, I usually only use forums.

More information about the freebsd-current mailing list