[DragonFlyBSD - Bug #2467] Intel 945GME agp Fatal trap 12 with ACPI disabled

David Shao via Redmine bugtracker-admin at leaf.dragonflybsd.org
Tue Dec 4 16:41:33 PST 2012

Issue #2467 has been updated by David Shao.

The same problem occurs on an actual Intel IronLake machine, an Asus UL20FT laptop.  It therefore does not appear to be related to ACPI being disabled or enabled; instead, it appears to be a problem with machines using Intel AGP at least.

There is a similar error message, here are some snippets:

pci1: <ACPI PCI bus> on pcib1
vgapci10: <VGA-compatible display> port 0xe080-0xe087 mem 0xe0000000-0xefffffff,0xf0000000-0xf03fffff irq 16 at device 2.0 on pci0
agp0: <Intel Ironlake (M) SVGA controller> on vgapci0

Fatal trap 12: page fault while in kernel mode
CPU0 stopping CPUs: 0x0000000e
Stopped at   2+0x12b:   movq  %r12,0x98(%rax)
Bug #2467: Intel 945GME agp Fatal trap 12 with ACPI disabled

Author: David Shao
Status: New
Priority: Normal
Target version: 

ACPI disabled on a Lenovo Ideapad netbook:

MPTABLE: 0:31 INTB routed to irq 19
vgapci0: <VGA-compatible display> [tentative] port 0x1800-0x1807 mem 0xf0600000-0xf063ffff,0xd0000000-0xdfffffff,0xf0500000-0xf057ffff irq 16 at device 2.0 on pci0
agp0: <Intel 945GME SVGA controller> [tentative] on vgapci0
vgapci0: Reserved 0x10000000 bytes for rid 0x18 type 3 at 0xd0000000

Fatal trap 12: page fault while in kernel mode
cpuid = 0; lapic.id = 00000000
fault virtual address  = 0x78
fault code             = supervisor write, page not present
instruction pointer    = 0x8:0xc052b97e
stack pointer          = 0x10:0xc0ef5984
frame pointer          = 0x10:0xc0ef59a8
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        = 0 (swapper)
current thread         = pri 12
 <- SMP: XXX
kernel: type 12 trap, code=2

CPU0 stopping CPUs: 0x00000002
Stopped at   agp_generic_attach+0x13f:   movl  %esi,0x78(%eax)

You have received this notification because you have either subscribed to it, or are involved in it.
To change your notification preferences, please click here: http://bugs.dragonflybsd.org/my/account

More information about the Bugs mailing list