Re: [PANIC] recent 7.2-STABLE when probing drm
Kostik Belousov wrote: On Tue, May 05, 2009 at 12:12:31PM +0100, Gavin Atkinson wrote: On Tue, 2009-05-05 at 13:06 +0200, Guido Falsi wrote: Hi! I'm using FreeBSD/i386 stable on a HP DC7800 PC. It has an Intel Q35 graphic chip. After upgrading to a recent stable I experienced a pani on boot, just after probing drm. I investigated a little and found out that reverting the file src/sys/dev/pci/pci.c to rev. 1.355.2.9 (SVN Rev 190092) solves the crash. I could not investigatte urther right away, but some regression was introduced with this rev. Is any more information needed? When it panics, can you please type "bt" (assuming you have the debugger compiled in) and show the output? I have this too. I have dump too. Sorry about that. I merged the fixes to vgapci this morning so this should be fixed now. -- John Baldwin ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: [PANIC] recent 7.2-STABLE when probing drm
On Tue, 2009-05-05 at 13:35 +0100, Gavin Atkinson wrote: > On Tue, 2009-05-05 at 15:12 +0300, Kostik Belousov wrote: > > On Tue, May 05, 2009 at 12:12:31PM +0100, Gavin Atkinson wrote: > > > On Tue, 2009-05-05 at 13:06 +0200, Guido Falsi wrote: > > > > Hi! > > > > > > > > I'm using FreeBSD/i386 stable on a HP DC7800 PC. > > > > > > > > It has an Intel Q35 graphic chip. > > > > > > > > After upgrading to a recent stable I experienced a pani on boot, just > > > > after probing drm. > > > > > > > > I investigated a little and found out that reverting the file > > > > > > > > src/sys/dev/pci/pci.c > > > > > > > > to rev. 1.355.2.9 (SVN Rev 190092) solves the crash. > > > > > > > > I could not investigatte urther right away, but some regression was > > > > introduced with this rev. > > > > > > > > Is any more information needed? > > > > > > When it panics, can you please type "bt" (assuming you have the debugger > > > compiled in) and show the output? > > > > I have this too. I have dump too. > > > > drm0: on vgapci0 > > panic: resource_list_alloc: resource entry is busy > > KDB: stack backtrace: > > db_trace_self_wrapper(c07214ff,c2b46764,c04c928f,c071f823,c078b080,...) at > > 0xc044df46 = db_trace_self_wrapper+0x26 > > kdb_backtrace(c071f823,c078b080,c07211b1,c2b46770,c2b46770,...) at > > 0xc04f41f9 = kdb_backtrace+0x29 > > panic(c07211b1,3,10,c04e9484,c2e37000,...) at 0xc04c928f = panic+0xaf > > resource_list_alloc(c2cffb04,c2d00a80,c2d00c80,3,c2d2a1fc,...) at > > 0xc04f0c06 = resource_list_alloc+0xd6 > > pci_alloc_resource(c2d00a80,c2d00c80,3,c2d2a1fc,0,,1,4) at > > 0xc045a2d1 = pci_alloc_resource+0x581 > > bus_alloc_resource(c2d00c80,3,c2d2a1fc,0,,...) at 0xc04f0a8c = > > bus_alloc_resource+0x7c > > vga_pci_alloc_resource(c2d00c80,c2cfa080,3,c2d2a1fc,0,,1,4) at > > 0xc04600ab = vga_pci_alloc_resource+0x3b > [...] > > I wonder if r189373 also needs merging? Yes, that looks right, resources are owned by both agp and drm on Intel. robert. > > Gavin > ___ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org" -- Robert Noland FreeBSD signature.asc Description: This is a digitally signed message part
Re: [PANIC] recent 7.2-STABLE when probing drm
On Tue, May 05, 2009 at 02:51:16PM +0100, Gavin Atkinson wrote: > On Tue, 2009-05-05 at 13:35 +0100, Gavin Atkinson wrote: > > [...] > > > > I wonder if r189373 also needs merging? > > Looking at a thread on -current, it looks like this is probably the > case. It's not a straight merge from head as other bits have changed, > but you could test http://people.freebsd.org/~gavin/189373_7.diff > (warning: compile tested only) Tested the patch, it solves the problem. The system now boots cleanly. Im using the PC as normal with no ill effects with this new kernel. -- Guido Falsi ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: [PANIC] recent 7.2-STABLE when probing drm
On Tue, 2009-05-05 at 13:06 +0200, Guido Falsi wrote: Hi! I'm using FreeBSD/i386 stable on a HP DC7800 PC. It has an Intel Q35 graphic chip. After upgrading to a recent stable I experienced a pani on boot, just after probing drm. I investigated a little and found out that reverting the file src/sys/dev/pci/pci.c to rev. 1.355.2.9 (SVN Rev 190092) solves the crash. I could not investigatte urther right away, but some regression was introduced with this rev. Is any more information needed? I want to add a "me too". I can't compile in a debugger as my sources are updated to 7.2, and any kernel built panics with the same message. I did find this on the CURRENT mailing list, but it wont apply cleanly: http://www.mailinglistarchive.com/freebsd-curr...@freebsd.org/msg26975.html vgap...@pci0:0:2:0: class=0x03 card=0x25821043 chip=0x25828086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' device = '82915G/GV/GL, 82910GL Integrated Graphics Device' class = display subclass = VGA vgap...@pci0:0:2:1: class=0x038000 card=0x25821043 chip=0x27828086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' device = '82915G Graphics device: 82915G/GV/910GL Express Chipset Family' class = display From a 7.2-PRERELEASE kernel. vgapci0: port 0x6800-0x6807 mem 0xcfd8-0xcfdf,0xd000-0xdfff,0xcfe8-0xcfeb at device 2.0 on pci0 agp0: on vgapci0 drm0: on vgapci0 vgapci0: child drm0 requested pci_enable_busmaster vgapci1: mem 0xcfe0-0xcfe7 at device 2.1 on pci0 vga0: at port 0x3c0-0x3df iomem 0xa-0xb on isa0 drm0: on vgapci0 vgapci0: child drm0 requested pci_enable_busmaster info: [drm] AGP at 0xd000 256MB info: [drm] Initialized i915 1.6.0 20080730 drm0: [ITHREAD] drm0: [ITHREAD] -- Over the years I've come to regard you as people I've met. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: [PANIC] recent 7.2-STABLE when probing drm
On Tue, May 05, 2009 at 01:35:27PM +0100, Gavin Atkinson wrote:
> On Tue, 2009-05-05 at 15:12 +0300, Kostik Belousov wrote:
> > On Tue, May 05, 2009 at 12:12:31PM +0100, Gavin Atkinson wrote:
> > > On Tue, 2009-05-05 at 13:06 +0200, Guido Falsi wrote:
> > > > Hi!
> > > >
> > > > I'm using FreeBSD/i386 stable on a HP DC7800 PC.
> > > >
> > > > It has an Intel Q35 graphic chip.
> > > >
> > > > After upgrading to a recent stable I experienced a pani on boot, just
> > > > after probing drm.
> > > >
> > > > I investigated a little and found out that reverting the file
> > > >
> > > > src/sys/dev/pci/pci.c
> > > >
> > > > to rev. 1.355.2.9 (SVN Rev 190092) solves the crash.
> > > >
> > > > I could not investigatte urther right away, but some regression was
> > > > introduced with this rev.
> > > >
> > > > Is any more information needed?
> > >
> > > When it panics, can you please type "bt" (assuming you have the debugger
> > > compiled in) and show the output?
> >
> > I have this too. I have dump too.
> >
> > drm0: on vgapci0
> > panic: resource_list_alloc: resource entry is busy
> > KDB: stack backtrace:
> > db_trace_self_wrapper(c07214ff,c2b46764,c04c928f,c071f823,c078b080,...) at
> > 0xc044df46 = db_trace_self_wrapper+0x26
> > kdb_backtrace(c071f823,c078b080,c07211b1,c2b46770,c2b46770,...) at
> > 0xc04f41f9 = kdb_backtrace+0x29
> > panic(c07211b1,3,10,c04e9484,c2e37000,...) at 0xc04c928f = panic+0xaf
> > resource_list_alloc(c2cffb04,c2d00a80,c2d00c80,3,c2d2a1fc,...) at
> > 0xc04f0c06 = resource_list_alloc+0xd6
> > pci_alloc_resource(c2d00a80,c2d00c80,3,c2d2a1fc,0,,1,4) at
> > 0xc045a2d1 = pci_alloc_resource+0x581
> > bus_alloc_resource(c2d00c80,3,c2d2a1fc,0,,...) at 0xc04f0a8c =
> > bus_alloc_resource+0x7c
> > vga_pci_alloc_resource(c2d00c80,c2cfa080,3,c2d2a1fc,0,,1,4) at
> > 0xc04600ab = vga_pci_alloc_resource+0x3b
> [...]
>
> I wonder if r189373 also needs merging?
Thanks for the hint. We need both r183095 and r189373, but the
actual bugfix is r189373, as you rightly pointed out. Below is the patch
that works for me.
Index: dev/pci/vga_pci.c
===
--- dev/pci/vga_pci.c (revision 191816)
+++ dev/pci/vga_pci.c (working copy)
@@ -42,10 +42,22 @@
#include
#include
#include
+#include
+#include
#include
#include
+struct vga_resource {
+ struct resource *vr_res;
+ int vr_refs;
+};
+
+struct vga_pci_softc {
+ device_tvga_msi_child; /* Child driver using MSI. */
+ struct vga_resource vga_res[PCIR_MAX_BAR_0 + 1];
+};
+
static int
vga_pci_probe(device_t dev)
{
@@ -110,7 +122,27 @@
vga_pci_alloc_resource(device_t dev, device_t child, int type, int *rid,
u_long start, u_long end, u_long count, u_int flags)
{
+ struct vga_pci_softc *sc;
+ int bar;
+ switch (type) {
+ case SYS_RES_MEMORY:
+ case SYS_RES_IOPORT:
+ /*
+* For BARs, we cache the resource so that we only allocate it
+* from the PCI bus once.
+*/
+ bar = PCI_RID2BAR(*rid);
+ if (bar < 0 || bar > PCIR_MAX_BAR_0)
+ return (NULL);
+ sc = device_get_softc(dev);
+ if (sc->vga_res[bar].vr_res == NULL)
+ sc->vga_res[bar].vr_res = bus_alloc_resource(dev, type,
+ rid, start, end, count, flags);
+ if (sc->vga_res[bar].vr_res != NULL)
+ sc->vga_res[bar].vr_refs++;
+ return (sc->vga_res[bar].vr_res);
+ }
return (bus_alloc_resource(dev, type, rid, start, end, count, flags));
}
@@ -118,7 +150,38 @@
vga_pci_release_resource(device_t dev, device_t child, int type, int rid,
struct resource *r)
{
+ struct vga_pci_softc *sc;
+ int bar, error;
+ switch (type) {
+ case SYS_RES_MEMORY:
+ case SYS_RES_IOPORT:
+ /*
+* For BARs, we release the resource from the PCI bus
+* when the last child reference goes away.
+*/
+ bar = PCI_RID2BAR(rid);
+ if (bar < 0 || bar > PCIR_MAX_BAR_0)
+ return (EINVAL);
+ sc = device_get_softc(dev);
+ if (sc->vga_res[bar].vr_res == NULL)
+ return (EINVAL);
+ KASSERT(sc->vga_res[bar].vr_res == r,
+ ("vga_pci resource mismatch"));
+ if (sc->vga_res[bar].vr_refs > 1) {
+ sc->vga_res[bar].vr_refs--;
+ return (0);
+ }
+ KASSERT(sc->vga_res[bar].vr_refs > 0,
+ ("vga_pci resource reference count underflow"));
+ error = bus_release_resource(dev, type, rid, r);
+ if (error == 0) {
+ sc->vga_res[bar].vr_res = NULL;
+
Re: [PANIC] recent 7.2-STABLE when probing drm
On Tue, 2009-05-05 at 13:35 +0100, Gavin Atkinson wrote: > On Tue, 2009-05-05 at 15:12 +0300, Kostik Belousov wrote: > > On Tue, May 05, 2009 at 12:12:31PM +0100, Gavin Atkinson wrote: > > > On Tue, 2009-05-05 at 13:06 +0200, Guido Falsi wrote: > > > > Hi! > > > > > > > > I'm using FreeBSD/i386 stable on a HP DC7800 PC. > > > > > > > > It has an Intel Q35 graphic chip. > > > > > > > > After upgrading to a recent stable I experienced a pani on boot, just > > > > after probing drm. > > > > > > > > I investigated a little and found out that reverting the file > > > > > > > > src/sys/dev/pci/pci.c > > > > > > > > to rev. 1.355.2.9 (SVN Rev 190092) solves the crash. > > > > > > > > I could not investigatte urther right away, but some regression was > > > > introduced with this rev. > > > > > > > > Is any more information needed? > > > > > > When it panics, can you please type "bt" (assuming you have the debugger > > > compiled in) and show the output? > > > > I have this too. I have dump too. > > > > drm0: on vgapci0 > > panic: resource_list_alloc: resource entry is busy > > KDB: stack backtrace: > > db_trace_self_wrapper(c07214ff,c2b46764,c04c928f,c071f823,c078b080,...) at > > 0xc044df46 = db_trace_self_wrapper+0x26 > > kdb_backtrace(c071f823,c078b080,c07211b1,c2b46770,c2b46770,...) at > > 0xc04f41f9 = kdb_backtrace+0x29 > > panic(c07211b1,3,10,c04e9484,c2e37000,...) at 0xc04c928f = panic+0xaf > > resource_list_alloc(c2cffb04,c2d00a80,c2d00c80,3,c2d2a1fc,...) at > > 0xc04f0c06 = resource_list_alloc+0xd6 > > pci_alloc_resource(c2d00a80,c2d00c80,3,c2d2a1fc,0,,1,4) at > > 0xc045a2d1 = pci_alloc_resource+0x581 > > bus_alloc_resource(c2d00c80,3,c2d2a1fc,0,,...) at 0xc04f0a8c = > > bus_alloc_resource+0x7c > > vga_pci_alloc_resource(c2d00c80,c2cfa080,3,c2d2a1fc,0,,1,4) at > > 0xc04600ab = vga_pci_alloc_resource+0x3b > [...] > > I wonder if r189373 also needs merging? Looking at a thread on -current, it looks like this is probably the case. It's not a straight merge from head as other bits have changed, but you could test http://people.freebsd.org/~gavin/189373_7.diff (warning: compile tested only) Gavin ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: [PANIC] recent 7.2-STABLE when probing drm
On Tue, May 05, 2009 at 12:12:31PM +0100, Gavin Atkinson wrote: > > Is any more information needed? > > When it panics, can you please type "bt" (assuming you have the debugger > compiled in) and show the output? I did not have a kernel with debugger handy. Here you go (copying by hand...): drm0: on vgapci0 panic: resource_list_alloc: resource entry busy cpuid = 0 KDB: enter: panic [thread pid 0 tid 0 ] Stopped atkdb_enter_why+0x3a:movl$0,kdb_why db> bt kdb_enter_why(c07d0374,c07d0374,c07d2cf1,c0c20760,0,...) at kdb_enter_why+0x3a panic(c07d2cf1,3,10,c086a7b4,c0c20788,...) at panic+0x131 resource_list_alloc(c6d56604,c6d88a80,c6d88a80,3,c6d79dfc,...) at resource_list_alloc+0xee pci_alloc_resource(c6d88a80,c6d88a80,3,c6d79dfc,0,,1,4) at pci_alloc_resource+0x554 bus_alloc_resource(c6d88a80,3,c6d79dfc,0,,...) at bus_alloc_resource+0x7e vga_pci_alloc_resource(c6d88a80,c6d81d80,3,c6d79dfc,0,,1,4) at vga_pci_alloc_resource+0x3b bus_alloc_resource(c6d88a80,3,c6d79dfc,0,,...) at bus_alloc_resource+0x7e drm_alloc_resource(c6d88b80,c6d88b80,c6d79c00,c0c208fc,c04a6946,...) at drm_alloc_resource+0xea drm_get_resource_start(c6d79c00,0,1,8,c07b652b,...) at drm_get_resource_start0x17 i915_driver_load(c6d79c00,6,c07b652b,1c2,,...) at i915_driver_load+0x139 drm_attach(c6d81d80,c08078a0,102) at drm_attach+0x604 i915_attach(c6d81d80,c6d0f858,c0818470,c07d2b42,8000,...) at i915_attach+0x10a device_attach(c6d81d80,c6d81d80,c07d2aa0,932,c6d81d80,...) at device+attach+0x36a device_probe_and_attach(c6d81d80,c6d88b80,c0c209f4,c04dc7f8,c6d88b80,...) at device_probe_and_attach+0xfd bus_generic_attach(...) at bus_generic_attach+0x19 vga_pci_attach(...) at vga_pci_attach+0x32 device_attach(...) at device_attach+0x36a device_probe_and_attach(...) at device_probe_and_attach+0xfd bus_generic_attach(...) at bus_generic_attach+0x19 acpi_pci_attach(...) at acpi_pci_attach+0x171 device_attach(...) at device_attach+0x36a device_probe_and_attach(...) at device_probe_and_attach+0xfd bus_generic_attach(...) at bus_generic_attach+0x19 acpi_pcib_attach(...) at acpi_pcib_attach+0x18e acpi_pcib_acpi_attach(...) at acpi_pcib_acpi_attach+0x1ad device_attach(...) at device_attach+0x36a device_probe_and_attach(...) at device_probe_and_attach+0xfd bus_generic_attach(...) at bus_generic_attach+0x19 acpi_pci_attach(...) at acpi_pci_attach+0x171 device_attach(...) at device_attach+0x36a device_probe_and_attach(...) at device_probe_and_attach+0xfd bus_generic_attach(...) at bus_generic_attach+0x19 nexus_attach(...) at nexus_attach+0x1a device_attach(...) at device_attach+0x36a device_probe_and_attach(...) at device_probe_and_attach+0xfd root_bus_configure(...) at root_bus_configure+0x1b configure(...) at configure0xc mi_startup() at mi_startup+0x90 begin() at begin+0x2c (I cut some parameters, hope they were not important) Contact me as you wish if any other information or tests are needed. -- Guido Falsi ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: [PANIC] recent 7.2-STABLE when probing drm
On Tue, 2009-05-05 at 15:12 +0300, Kostik Belousov wrote: > On Tue, May 05, 2009 at 12:12:31PM +0100, Gavin Atkinson wrote: > > On Tue, 2009-05-05 at 13:06 +0200, Guido Falsi wrote: > > > Hi! > > > > > > I'm using FreeBSD/i386 stable on a HP DC7800 PC. > > > > > > It has an Intel Q35 graphic chip. > > > > > > After upgrading to a recent stable I experienced a pani on boot, just > > > after probing drm. > > > > > > I investigated a little and found out that reverting the file > > > > > > src/sys/dev/pci/pci.c > > > > > > to rev. 1.355.2.9 (SVN Rev 190092) solves the crash. > > > > > > I could not investigatte urther right away, but some regression was > > > introduced with this rev. > > > > > > Is any more information needed? > > > > When it panics, can you please type "bt" (assuming you have the debugger > > compiled in) and show the output? > > I have this too. I have dump too. > > drm0: on vgapci0 > panic: resource_list_alloc: resource entry is busy > KDB: stack backtrace: > db_trace_self_wrapper(c07214ff,c2b46764,c04c928f,c071f823,c078b080,...) at > 0xc044df46 = db_trace_self_wrapper+0x26 > kdb_backtrace(c071f823,c078b080,c07211b1,c2b46770,c2b46770,...) at 0xc04f41f9 > = kdb_backtrace+0x29 > panic(c07211b1,3,10,c04e9484,c2e37000,...) at 0xc04c928f = panic+0xaf > resource_list_alloc(c2cffb04,c2d00a80,c2d00c80,3,c2d2a1fc,...) at 0xc04f0c06 > = resource_list_alloc+0xd6 > pci_alloc_resource(c2d00a80,c2d00c80,3,c2d2a1fc,0,,1,4) at 0xc045a2d1 > = pci_alloc_resource+0x581 > bus_alloc_resource(c2d00c80,3,c2d2a1fc,0,,...) at 0xc04f0a8c = > bus_alloc_resource+0x7c > vga_pci_alloc_resource(c2d00c80,c2cfa080,3,c2d2a1fc,0,,1,4) at > 0xc04600ab = vga_pci_alloc_resource+0x3b [...] I wonder if r189373 also needs merging? Gavin ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: [PANIC] recent 7.2-STABLE when probing drm
On Tue, May 05, 2009 at 12:12:31PM +0100, Gavin Atkinson wrote: > On Tue, 2009-05-05 at 13:06 +0200, Guido Falsi wrote: > > Hi! > > > > I'm using FreeBSD/i386 stable on a HP DC7800 PC. > > > > It has an Intel Q35 graphic chip. > > > > After upgrading to a recent stable I experienced a pani on boot, just > > after probing drm. > > > > I investigated a little and found out that reverting the file > > > > src/sys/dev/pci/pci.c > > > > to rev. 1.355.2.9 (SVN Rev 190092) solves the crash. > > > > I could not investigatte urther right away, but some regression was > > introduced with this rev. > > > > Is any more information needed? > > When it panics, can you please type "bt" (assuming you have the debugger > compiled in) and show the output? I have this too. I have dump too. drm0: on vgapci0 panic: resource_list_alloc: resource entry is busy KDB: stack backtrace: db_trace_self_wrapper(c07214ff,c2b46764,c04c928f,c071f823,c078b080,...) at 0xc044df46 = db_trace_self_wrapper+0x26 kdb_backtrace(c071f823,c078b080,c07211b1,c2b46770,c2b46770,...) at 0xc04f41f9 = kdb_backtrace+0x29 panic(c07211b1,3,10,c04e9484,c2e37000,...) at 0xc04c928f = panic+0xaf resource_list_alloc(c2cffb04,c2d00a80,c2d00c80,3,c2d2a1fc,...) at 0xc04f0c06 = resource_list_alloc+0xd6 pci_alloc_resource(c2d00a80,c2d00c80,3,c2d2a1fc,0,,1,4) at 0xc045a2d1 = pci_alloc_resource+0x581 bus_alloc_resource(c2d00c80,3,c2d2a1fc,0,,...) at 0xc04f0a8c = bus_alloc_resource+0x7c vga_pci_alloc_resource(c2d00c80,c2cfa080,3,c2d2a1fc,0,,1,4) at 0xc04600ab = vga_pci_alloc_resource+0x3b bus_alloc_resource(c2cfa080,3,c2d2a1fc,0,,...) at 0xc04f0a8c = bus_alloc_resource+0x7c drm_alloc_resource(fff4,c2d2a000,c2b468fc,c36a0b9b,c2d2a000,...) at 0xc36b7726 = drm_alloc_resource+0xf6 drm_get_resource_start(c2d2a000,0,1,4,c04d2010,...) at 0xc36b780c = drm_get_resource_start+0x1c i915_driver_load(c2d2a000,6,c36bfe5c,1c2,,...) at 0xc36a0b9b = i915_driver_load+0x13b drm_attach(c2cfa080,c36a59a0,102,c2d00c80,c2cfa0cc,...) at 0xc36bb0e1 = drm_attach+0x4b1 i915_attach(c2cfa080,c32a9054,c0748368,c0721002,8000,...) at 0xc36a0f41 = i915_attach+0x111 device_attach(c2cfa080,c2cfa080,c2d00c80,c2cfa080,c2d00c80,...) at 0xc04ef707 = device_attach+0x387 device_probe_and_attach(c2cfa080,c2d00c80,c0748358,c2d00c80,0,...) at 0xc04f0702 = device_probe_and_attach+0xe2 bus_generic_driver_added(c2d00c80,c36a5b7c,101,0,c36a5b68,...) at 0xc04f07d5 = bus_generic_driver_added+0x75 devclass_add_driver(c2ca4480,c36a5b7c,c2b46a2c,2d,c36a5b7c,...) at 0xc04ee4c8 = devclass_add_driver+0xc8 driver_module_handler(c2e420c0,0,c36a5b68,0,0,...) at 0xc04ef2a9 = driver_module_handler+0x79 module_register_init(c36a5b5c,c071dad9,c2b46c10,c2b46c0c,0,...) at 0xc04b9d25 = module_register_init+0x105 linker_load_module(0,c2b46c40,2,c2b46c58,c04b7b99,...) at 0xc04b2462 = linker_load_module+0xa02 kern_kldload(c2e79af0,c2d12000,c2b46c70,0,0,...) at 0xc04b294c = kern_kldload+0xec kldload(c2e79af0,c2b46cfc,4,c2b46d38,c2b46d2c,...) at 0xc04b2ae4 = kldload+0x74 syscall(c2b46d38) at 0xc06f6eb5 = syscall+0x3a5 Xint0x80_syscall() at 0xc06de760 = Xint0x80_syscall+0x20 --- syscall (304, FreeBSD ELF32, kldload), eip = 0x28566d57, esp = 0xbfbfe89c, ebp = 0xbfbfe8a8 --- pgpHwPqaHfawd.pgp Description: PGP signature
Re: [PANIC] recent 7.2-STABLE when probing drm
On Tue, 2009-05-05 at 13:06 +0200, Guido Falsi wrote: > Hi! > > I'm using FreeBSD/i386 stable on a HP DC7800 PC. > > It has an Intel Q35 graphic chip. > > After upgrading to a recent stable I experienced a pani on boot, just > after probing drm. > > I investigated a little and found out that reverting the file > > src/sys/dev/pci/pci.c > > to rev. 1.355.2.9 (SVN Rev 190092) solves the crash. > > I could not investigatte urther right away, but some regression was > introduced with this rev. > > Is any more information needed? When it panics, can you please type "bt" (assuming you have the debugger compiled in) and show the output? Gavin ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
[PANIC] recent 7.2-STABLE when probing drm
Hi! I'm using FreeBSD/i386 stable on a HP DC7800 PC. It has an Intel Q35 graphic chip. After upgrading to a recent stable I experienced a pani on boot, just after probing drm. I investigated a little and found out that reverting the file src/sys/dev/pci/pci.c to rev. 1.355.2.9 (SVN Rev 190092) solves the crash. I could not investigatte urther right away, but some regression was introduced with this rev. Is any more information needed? Thank you in advance for any help or information on this. Here is the dmesg from the working kernel the other one panics just after the line marked with [*]: Copyright (c) 1992-2009 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 7.2-STABLE #16: Tue May 5 12:32:40 CEST 2009 r...@vwg82.hq.ignesti.it:/usr/obj/usr/src/sys/VWG82 Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: Intel(R) Core(TM)2 Duo CPU E6550 @ 2.33GHz (2327.51-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x6fb Stepping = 11 Features=0xbfebfbff Features2=0xe3fd AMD Features=0x2010 AMD Features2=0x1 Cores per package: 2 real memory = 3740987392 (3567 MB) avail memory = 3661430784 (3491 MB) ACPI APIC Table: FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 ioapic0: Changing APIC ID to 1 ioapic0 irqs 0-23 on motherboard netsmb_dev: loaded kbd1 at kbdmux0 acpi0: on motherboard acpi0: [ITHREAD] acpi0: Power Button (fixed) acpi0: reservation of 0, a (3) failed acpi0: reservation of 10, dff0 (3) failed Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0xf808-0xf80b on acpi0 acpi_hpet0: iomem 0xfed0-0xfed003ff on acpi0 Timecounter "HPET" frequency 14318180 Hz quality 900 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 vgapci0: port 0x1230-0x1237 mem 0xf010-0xf017,0xe000-0xefff,0xf000-0xf00f irq 16 at device 2.0 on pci0 agp0: on vgapci0 agp0: detected 6140k stolen memory agp0: aperture size is 256M drm0: on vgapci0 [*] vgapci0: child drm0 requested pci_enable_busmaster info: [drm] AGP at 0xe000 256MB info: [drm] Initialized i915 1.6.0 20080730 pci0: at device 3.0 (no driver attached) atapci0: port 0x1238-0x123f,0x1270-0x1273,0x1240-0x1247,0x1274-0x1277,0x11e0-0x11ef irq 18 at device 3.2 on pci0 atapci0: [ITHREAD] ata2: on atapci0 ata2: [ITHREAD] ata3: on atapci0 ata3: [ITHREAD] pci0: at device 3.3 (no driver attached) em0: port 0x1100-0x111f mem 0xf018-0xf019,0xf01a5000-0xf01a5fff irq 19 at device 25.0 on pci0 em0: Using MSI interrupt em0: [FILTER] em0: Ethernet address: 00:1e:0b:ab:e6:a7 uhci0: port 0x1120-0x113f irq 20 at device 26.0 on pci0 uhci0: [GIANT-LOCKED] uhci0: [ITHREAD] usb0: on uhci0 usb0: USB revision 1.0 uhub0: on usb0 uhub0: 2 ports with 2 removable, self powered uhci1: port 0x1140-0x115f irq 21 at device 26.1 on pci0 uhci1: [GIANT-LOCKED] uhci1: [ITHREAD] usb1: on uhci1 usb1: USB revision 1.0 uhub1: on usb1 uhub1: 2 ports with 2 removable, self powered uhci2: port 0x1160-0x117f irq 22 at device 26.2 on pci0 uhci2: [GIANT-LOCKED] uhci2: [ITHREAD] usb2: on uhci2 usb2: USB revision 1.0 uhub2: on usb2 uhub2: 2 ports with 2 removable, self powered ehci0: mem 0xf01a6000-0xf01a63ff irq 22 at device 26.7 on pci0 ehci0: [GIANT-LOCKED] ehci0: [ITHREAD] usb3: EHCI version 1.0 usb3: companion controllers, 2 ports each: usb0 usb1 usb2 usb3: on ehci0 usb3: USB revision 2.0 uhub3: on usb3 uhub3: 6 ports with 6 removable, self powered hdac0: mem 0xf01a-0xf01a3fff irq 21 at device 27.0 on pci0 hdac0: HDA Driver Revision: 20090329_0131 hdac0: [ITHREAD] pcib1: at device 28.0 on pci0 pci32: on pcib1 pcib2: irq 21 at device 28.1 on pci0 pci48: on pcib2 uhci3: port 0x1180-0x119f irq 20 at device 29.0 on pci0 uhci3: [GIANT-LOCKED] uhci3: [ITHREAD] usb4: on uhci3 usb4: USB revision 1.0 uhub4: on usb4 uhub4: 2 ports with 2 removable, self powered uhci4: port 0x11a0-0x11bf irq 21 at device 29.1 on pci0 uhci4: [GIANT-LOCKED] uhci4: [ITHREAD] usb5: on uhci4 usb5: USB revision 1.0 uhub5: on usb5 uhub5: 2 ports with 2 removable, self powered ehci1: mem 0xf01a6400-0xf01a67ff irq 20 at device 29.7 on pci0 ehci1: [GIANT-LOCKED] ehci1: [ITHREAD] usb6: EHCI version 1.0 usb6: companion controllers, 2 ports each: usb4 usb5 usb6: on ehci1 usb6: USB revision 2.0 uhub6: on usb6 uhub6: 4 ports with 4 removable, self powered pcib3: at device 30.0 on pci0 pci7: on pcib3 isab0: at device 31.0 on pci0 isa0: on isab0 atapci1: port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0x11f0-0x11ff,0x1200-0x120f irq 18 at device 31.2 on pci0 ata0: on atapci1 ata0: [ITHREAD] ata1: on atapci1 ata1: [ITHREAD] atapci2: port 0x1260-0x1267,0x1280-0x1283,0x1268-0x126f,0x1284-0x1287,0x1210-0x121f,0x1220-0x122f irq 18 at device 31.5 on p
