Re: Lockup with radeon.ko from r300 when the server starts

[Tino K. <tin...@gm...>]

On Mon, Jul 04, 2005 at 14:29:54 +0200, Jerome Glisse wrote:
> On 7/4/05, Tino Keitel <tin...@gm...> wrote:
> > On Mon, Jul 04, 2005 at 14:01:12 +0200, Jerome Glisse wrote:
> > > Is this a hard lockup or not ? ie could you ssh in the box ?
> > 
> > Yes, it's a hard lockup.
> > 
> > > If you can ssh to the box, could you provide Xorg log (in /var/log/)
> > > & revealent part of syslog or whatever is the ouput of radeon module
> > > when you try to start Xserver with it.
> > >
> > > Maybe you could try to first load radeon module & then Xserver,
> > > if you don't already try this.
> > 
> > When I load the radeon module on the command line everything works. The
> > lockup occurs when the server starts.
> > 
> > >
> > > Btw a "depmod -a " shouldn't hurt, and do a find /lib/modules -name radeon.ko
> > > to see if there isn't two copy of it in different places.
> > 
> > $ /sbin/modprobe -l | grep radeon
> > /lib/modules/2.6.12/kernel/drivers/char/drm/radeon.ko
> > 
> 
> Hhhmmm there must be a difference somewhere in your system.
> Somethings which have changed between first start & your last
> reboot.
> 
> Is there any things in your kernel message after loading radeon.ko
> (without starting x) ?

ACPI: PCI Interrupt 0000:02:00.0[A] -> Link [APC4] -> GSI 19 (level, high) -> IRQ 19
mtrr: 0xc0000000,0x10000000 overlaps existing 0xc0000000,0x8000000
[drm] Initialized radeon 1.15.0 20050208 on minor 0: ATI Technologies Inc RV350 AP [Radeon 9600]

> 
> Recompiling everythings from CVS should fix that (use Mesa CVS
> too).

IMHO Mesa only provides libGL, and libGL isn't used during the server
startup. Or am I wrong here?

Regards,
Tino