The following reply was made to PR kernel/6632; it has been noted by GNATS.

From: Bryan Linton <[email protected]>
To: Owain Ainsworth <[email protected]>
Cc: [email protected]
Subject: Re: kernel/6632: Reproduceable hard crash in new snap, Xorg/radeon 
related
Date: Sun, 19 Jun 2011 09:21:11 -0700

 On 2011-06-19 12:53:58, Owain Ainsworth <[email protected]> wrote:
 > On Mon, Jun 13, 2011 at 07:49:11PM -0700, Bryan Linton wrote:
 >> >Number:         6632
 >> >Category:       kernel
 >> >Synopsis:       Reproduceable hard crash in new snap, Xorg/radeon related
 >> 
 >> [snip]
 >>
 >> After updating from a May 13th snap to the June 9th snap I
 >> experience a reproduceable hard crash after running startx.  The
 >> monitor immediately blanks and goes into stand-by mode and the
 >> machine does not respond to <ctrl>+<alt>+{<bksp>,<esc>,<del>,<f#>} or
 >> network connections (keyboard LEDs still toggle however).
 >> 
 >> I have not been able to get a trace or any kind of log
 >> information, however, after reverting this commit on May 30th:
 >>     http://marc.info/?l=openbsd-cvs&m=130679235018645&w=2
 >> the machine no longer crashes and functions normally.
 >> 
 >> I am not using an xorg.conf file.
 >> 
 >> The Xorg.0.log attached is from a kernel with the above commit reverted.
 >> If I can provide any further information, please let me know.
 > 
 > can you try this kernel diff, please?
 > 
 > 
 > diff --git dev/pci/drm/radeon_irq.c dev/pci/drm/radeon_irq.c
 > index 92c4811..95dad83 100644
 > --- dev/pci/drm/radeon_irq.c
 > +++ dev/pci/drm/radeon_irq.c
 > @@ -197,9 +197,6 @@ radeondrm_intr(void *arg)
 >      drm_radeon_private_t    *dev_priv = dev->dev_private;
 >      u_int32_t                stat, r500_disp_int;
 >  
 > -    if (dev_priv->cp_running == 0)
 > -            return (0);
 > -    /* XXX wtf? */
 >      if ((dev_priv->flags & RADEON_FAMILY_MASK) >= CHIP_R600)
 >              return (0);
 >  
 
 I'm happy to report that the above diff does indeed resolve the
 issue I was seeing.  Thank you very much for the fix.  :)
 
 -- 
 Bryan

Reply via email to