System freezes with radeon 9100 graphics card

[Glenn Johnson]

On Sat, Aug 23, 2003 at 09:40:55PM -0700, Scott M. Likens wrote:

> On Sat, 2003-08-23 at 20:38, Glenn Johnson wrote:
>
> > On Sat, Aug 23, 2003 at 02:11:15PM -0500, Glenn Johnson wrote:
> >
> > > I have had an ongoing problem with -current freezing during a
> > > restart of the X serer.  The graphics card is an ATI Radeon 9100.
> > > I am pretty sure this is related to DRI as I have not had it
> > > happen with DRI disabled.
> > >
> > > I am not sure if the problem is with the radeon kernel module,    
> > > with XFree86-Server, or something else.  The freezes totally lock 
> > > up the machine, no ssh access is possible, no crash dumps are     
> > > produced, I have to hit the reset button and run fsck in single   
> > > user mode.                                                        
> > >
> > > Is anyone else seeing this with a radeon card?  Any options I can
> > > set to alleviate the problem?  I going to turn on DRM_DEBUG and
> > > see what that yields.
> > >
> > > Thanks.
> >
> > Some more info:
> >
> > I get the following error messages when the X server starts:
> > 
> > drm0: <ATI Radeon QM R200 9100> port 0x9000-0x90ff mem 0xf9000000-0xf900ffff,0xe0000000-0xefffffff irq 2 at device 0.0 on pci1
> > info: [drm] Initialized radeon 1.9.0 20020828 on minor 0
> > error: [drm:radeon_cp_init] *ERROR* radeon_cp_init called without lock held
> > error: [drm:radeon_unlock] *ERROR* Process 579 using kernel context 0
> > error: [drm:radeon_cp_init] *ERROR* radeon_cp_init called without lock held
> > error: [drm:radeon_unlock] *ERROR* Process 738 using kernel context 0
> > error: [drm:radeon_cp_init] *ERROR* radeon_cp_init called without lock held
> > error: [drm:radeon_unlock] *ERROR* Process 865 using kernel context 0
> 
> I might suggest to you that you try the DRI lists... see
> http://dri.sf.net or email anholt at freebsd.org

I have, to the first.

> Also please teach your email client to word wrap.  That's nasty.

My e-mail client "knows" how to word wrap.  The unwrapped part above
was from command output, which should *not* be wrapped, to maintain
integrity of the output.  If you saw more than one line that was not
wrapped then I submit that there is something wrong with your e-mail
client.

-- 
Glenn Johnson
glennpj at charter.net