On Po, 2002-02-18 at 12:56, Michel Dänzer wrote: > > This log doesn't even show the radeon_freelist_get error; the X server > waits in vain for the CP to go idle.
Yes, the radeon_freelist_get error is probably another thing. > I don't see anything bad leading up > to that, but I don't know the radeon driver well yet. Let's hope Keith > will spot something. :) What seems weird to me is the sequence: Feb 11 14:13:50 whale kernel: [drm:radeon_lock] 1 (pid 2715) requests lock (0x00000003), flags = 0x00000000 Feb 11 14:13:50 whale kernel: [drm:radeon_lock] 1 has lock Feb 11 14:13:50 whale kernel: [drm:radeon_ioctl] pid=2715, cmd=0x6444, nr=0x44, dev 0xe200, auth=1 Feb 11 14:13:50 whale kernel: [drm:radeon_cp_idle] radeon_cp_idle Feb 11 14:13:50 whale kernel: [drm:radeon_do_cp_idle] radeon_do_cp_idle Feb 11 14:13:50 whale kernel: [drm:radeon_ioctl] pid=2715, cmd=0x6444, nr=0x44, dev 0xe200, auth=1 <-- repeating idle, stripped ---> Feb 11 14:13:50 whale kernel: [drm:radeon_cp_idle] radeon_cp_idle Feb 11 14:13:50 whale kernel: [drm:radeon_do_cp_idle] radeon_do_cp_idle Feb 11 14:13:50 whale kernel: [drm:radeon_ioctl] pid=3719, cmd=0x4008642a, nr=0x2a, dev 0xe200, auth=1 Feb 11 14:13:50 whale kernel: [drm:radeon_lock] 3 (pid 3719) requests lock (0x80000001), flags = 0x00000000 Feb 11 14:13:50 whale kernel: [drm:radeon_ioctl] pid=2715, cmd=0x6444, nr=0x44, dev 0xe200, auth=1 Feb 11 14:13:50 whale kernel: [drm:radeon_cp_idle] radeon_cp_idle Feb 11 14:13:50 whale kernel: [drm:radeon_do_cp_idle] radeon_do_cp_idle Feb 11 14:13:50 whale kernel: [drm:radeon_ioctl] pid=2715, cmd=0x6444, nr=0x44, dev 0xe200, auth=1 and nothing happens anymore - it seems much as deadlock to me. It would also explain why is the bug harder to encounter with full logging. Side note: to eliminate a hw problem I've updated to lastest BIOS (mobo Asus a7v133). It was quite suprising that the stability increased substantialy - the mean time of lockup increased from 4 minutes to about 1.5 hour [even though only Athlon XP support and no bugfixes were declared]. But all problems I described before still exist but it's more bearable now ;) > > > The situation was: X start, quake3 demo, < 5 min if playing, hangup to blank > > screen. > > 'Blank screen' sounds like the chip went into a bad state... > > > -- > Earthling Michel Dänzer (MrCooper)/ Debian GNU/Linux (powerpc) developer > XFree86 and DRI project member / CS student, Free Software enthusiast > > -- Kamil Toman _______________________________________________ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
