[Bug 187015] [panic] make_dev_credv: bad si_name (error=17, si_name=agpgart)

[bugzilla-noreply at freebsd.org]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=187015

tatsuki_makino at hotmail.com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |tatsuki_makino at hotmail.com

--- Comment #3 from tatsuki_makino at hotmail.com ---
Created attachment 145022
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=145022&action=edit
test patch for 9-STABLE.

This problem also occurs my computer that is used Intel 855 GME chipset.

This problem also occurs in versions below.
9.3-RELEASE
9.2-RELEASE
10.0-RELEASE
9-STABLE
And I expect it also occurs in CURRENT, but I have not checked it yet.

The patch can avoid panic. And some informations are added to dmesg.boot.
Quote of part of the dmesg.boot:

pcib0: <ACPI Host-PCI bridge> port 0xcf8-0xcff on acpi0
pci0: <ACPI PCI bus> on pcib0
agp0: <Intel 82855GM host to AGP bridge> on hostb0
agp0: ==== make_dev agpgart for 0x35808086 ====
agp0: ==== sc->as_devnode: 0xc52e9c00 ====
agp0: ==== sc->as_devnode->si_drv1: 0 ====
agp0: ==== sc->as_devnode->si_drv1: 0xc52e8980 ====
pcib1: <PCI-PCI bridge> at device 1.0 on pci0
pci1: <PCI bus> on pcib1
vgapci0: <VGA-compatible display> port 0x1800-0x1807 mem
0xe8000000-0xefffffff,0xe0000000-0xe007ffff irq 9 at device 2.0 on pci0
agp1: <Intel 82855GME (855GME GMCH) SVGA controller> on vgapci0
agp1: ==== make_dev agpgart for 0x35828086 ====
agp1: ==== sc->as_devnode: 0 ====
agp1: aperture size is 128M, detected 8060k stolen memory
vgapci0: Boot video device
vgapci1: <VGA-compatible display> mem
0xf0000000-0xf7ffffff,0xe0080000-0xe00fffff at device 2.1 on pci0

Perhaps, agp0 is calling agp_generic_attach from sys/dev/agp/agp_intel.c. and
agp1 is calling agp_generic_attach from agp_generic_attach from
sys/dev/agp/agp_i810.c. But /dev/agpgart is already exists in second time of
calling agp_generic_attach.

Perhaps, this patch's agpgart is referring to agp0. It is not right.

-- 
You are receiving this mail because:
You are the assignee for the bug.