Re: [Dri-users] X hangs when starting glxgears on r350

[Bellido N. <nb...@sk...>]

On Wednesday 27 July 2005 19:04, Aapo Tahkola wrote:
> On Wed, 27 Jul 2005 12:25:27 +0200
>
> Bellido Nicolas <nb...@sk...> wrote:
> > On Wednesday 27 July 2005 08:44, Aapo Tahkola wrote:
> > > On Tue, 26 Jul 2005 14:18:10 +0200
> > >
> > > You dont have two cards hooked up by any chance? :)
> >
> > No, no handmade mobo with 2 agp slots :)
> >
> > > Does Xorg.0.log get the card right?
> >RADEON_PARAM_GART_BUFFER_OFFSET
> > Apparently yes, it does.
> >
> > > You probably want to check if microcode_version actually has any sane
> > > value at radeon_cp_cmdbuf. Try something like:
> > > printk("microcode_version %d\n", dev_priv->microcode_version);
> > > return DRM_ERR(EINVAL);
> >
> > Yeah, I was planning to do smthg like that.
> >
> > But, how do you explain:
> >
> >  [drm:drm_ioctl] pid=9733, cmd=0x40106450, nr=0x50, dev 0xe200, auth=1
>
> DRM_COMMAND_BASE + DRM_RADEON_CMDBUF == 0x50
>
> >  [drm:radeon_cp_cmdbuf] RADEON_CMD_SCALARS2
>
> cmd type 7 equals to R300_CMD_WAIT(from r300DoEmitState)
>
> >  [drm:rRADEON_PARAM_GART_BUFFER_OFFSETadeon_cp_cmdbuf] *ERROR* bad 
cmd_type 0 at e08fa024
>
> This is random bits of memory already as cmd length of previous wasnt
> right.

I meant I don't understand why there is a RADEON_CMD_SCALAR2 followed by the 
*ERROR* message, without a drm_ioctl notice in between...

Possibly because the PID is different than for the other calls ?