6.0-BETA2 DRM/witness panic: Assertion j < 1000 failed at
kris at obsecurity.org
Thu Sep 29 09:35:48 PDT 2005
On Thu, Sep 29, 2005 at 05:32:03PM +0100, Gavin Atkinson wrote:
> On Thu, 2005-09-29 at 17:24 +0100, Gavin Atkinson wrote:
> > On Thu, 2005-09-29 at 12:10 -0400, John Baldwin wrote:
> > > On Tuesday 09 August 2005 12:02 pm, Gavin Atkinson wrote:
> > > > On Tue, 2005-08-09 at 10:50 -0400, John Baldwin wrote:
> > > > > On Tuesday 09 August 2005 07:57 am, Gavin Atkinson wrote:
> > > > > > Hi,
> > > > > >
> > > > > > I have a regular panic (3 times a day) on a system running 6.0-BETA2
> > > > > > which was very stable under 5.4. dmesg available at
> > > > > > http://www.devrandom.co.uk/freebsd/dmesg-buffy-20050809 . The panic
> > > > > > seems to relate to DRM, I have a ATI Radeon QY RV100 7000/VE card.
> > > > >
> > > > > Do a 'show witness', it looks like witness has a cycle somehow. Normally
> > > > > these can only occur if there is a cycle in the static lock order.
> > > >
> > > > http://www.devrandom.co.uk/freebsd/sh-witness-buffy-20050809
> > > >
> > > > Gavin
> > >
> > > Do you still get this panic on more recent 6.0?
> > I do with BETA3 from Sept 6th. I'll update again (after re-adding
> > WITNESS etc to GENERIC) and test it again.
> I should have said that I also stepped back in time several times, and
> was still getting the panic with kernel from sources dated April 15th,
> ruling out the major DRM upgrade in July. I couldn't get any of the
> screensavers that easily provoke the panic to run on a pre-April 15th
> system, even after recompiling all ports.
You're not using modules, right? Or at least, you're remembering to
recompile them all each time you update your kernel?
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 187 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-current/attachments/20050929/f15d56e5/attachment.bin
More information about the freebsd-current