On 10/10/05, Dave Airlie <[EMAIL PROTECTED]> wrote: > > > > Thanks! I downloaded and compiled xorg and mesa from cvs today. Now if > > I try to start X with dri active the computer locks up, and it's a > > hard lock-up -- I can't ssh into the machine. Nothing special appears > > in the syslog, and the xorg log does still say that dri is disabled > > for some reason (no, not a pebkac, I rebooted into recovery mode and > > copied the log to my home dir; I didn't reboot into X). Other than > > that, I can't see anything wrong in the log. I've uploaded it to > > http://eulex.0nyx.com/Xorg.0.log.x300.2 . Are there any other way of > > debugging it? > > DRI is enabled in the log you just sent... this is the same card as I have > with more memory,... it looks to be getting things correct... can you > maybe switch on drm debugging before starting X and see if you can get any > information out of it ..??
Yes it is. That's what happens when you stay up far too long at night :) > insmod drm debug=1 > insmod radeon > then start X Most times I just get this: Oct 11 16:58:22 localhost kernel: [drm] Initialized drm 1.0.0 20040925 Oct 11 16:58:37 localhost kernel: [drm:drm_init] Oct 11 16:58:37 localhost kernel: PCI: Unable to reserve mem region #1:[EMAIL PROTECTED] for device 0000:01:00.0 Oct 11 16:58:37 localhost kernel: [drm:drm_get_dev] Oct 11 16:58:37 localhost kernel: [drm:radeon_driver_load] PCIE card detected Oct 11 16:58:37 localhost kernel: [drm:drm_ctxbitmap_next] drm_ctxbitmap_next bit : 0 Oct 11 16:58:37 localhost kernel: [drm:drm_ctxbitmap_init] drm_ctxbitmap_init : 0 Oct 11 16:58:37 localhost kernel: [drm:drm_get_head] Oct 11 16:58:37 localhost kernel: [drm:drm_get_head] new minor assigned 0 Oct 11 16:58:37 localhost kernel: [drm] Initialized radeon 1.19.0 20050911 on minor 0: ATI Technologies Inc M22 [Radeon Mobility M300] Oct 11 16:58:37 localhost kernel: [drm] Used old pci detect: framebuffer loaded and then nothing more. However, once, I got the following, which seems to contain a lot of nifty info for you: http://eulex.0nyx.com/drmlog.txt An interesting thing is that those things that didn't happen before, happens almost 4 minutes after the things that always happens. And I know that those things don't happen every time -- I did let it run for more than 10 minutes several times after it had hung. May just be that I was lucky and got a flush() at the right time :) Anyway, those IRQ errors at the end look interesting to me. Though it may just be some random thing that was messed up when X hung... > It really needs to machines to debug these types of hard hang.. Yeah, that's what I was thinking, that there was probably need for testing on more of these cards, that's why I posted to the dev list in the first place. X300's are quite rare. > How much RAM to you have? 128mb. Regards, Alexander Toresson ------------------------------------------------------- This SF.Net email is sponsored by: Power Architecture Resource Center: Free content, downloads, discussions, and more. http://solutions.newsforge.com/ibmarch.tmpl -- _______________________________________________ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
