Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 05 May 2009 14:51:16 +0100
From:      Gavin Atkinson <gavin@FreeBSD.org>
To:        Kostik Belousov <kostikbel@gmail.com>
Cc:        freebsd-stable@FreeBSD.org, Guido Falsi <mad@madpilot.net>, jhb@FreeBSD.org
Subject:   Re: [PANIC] recent 7.2-STABLE when probing drm
Message-ID:  <1241531476.47323.8.camel@buffy.york.ac.uk>
In-Reply-To: <1241526927.47323.5.camel@buffy.york.ac.uk>
References:  <20090505110624.GA83487@megatron.madpilot.net> <1241521951.47323.3.camel@buffy.york.ac.uk> <20090505121247.GN1948@deviant.kiev.zoral.com.ua> <1241526927.47323.5.camel@buffy.york.ac.uk>

next in thread | previous in thread | raw e-mail | index | archive | help
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: <Intel i945GM> 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,ffffffff,1,4) at 0xc045a2d1 = pci_alloc_resource+0x581
> > bus_alloc_resource(c2d00c80,3,c2d2a1fc,0,ffffffff,...) at 0xc04f0a8c = bus_alloc_resource+0x7c
> > vga_pci_alloc_resource(c2d00c80,c2cfa080,3,c2d2a1fc,0,ffffffff,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



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1241531476.47323.8.camel>