Re: agp driver locks up on resume.
On Thu, 2003-04-03 at 11:14, David Gilbert wrote: > I don't know the exact nature of the bug, but compiling in the agp > driver on my laptop locks up the unit on resume. Runing without agp > compiled in is fine. The lockup isn't every time ... and it isn't > solved by suspending and resuming with the console active. The > relavant probes are: > > apm0: on motherboard > apm0: found APM BIOS v1.2, connected at v1.2 > pcib0: on motherboard > pci0: on pcib0 > agp0: mem 0xf400-0xf7ff at > device 0.0 on pci0 > pcib1: at device 1.0 on pci0 > pci1: on pcib1 > pci1: at 0.0 irq 9 > > then: > > info: [drm] Checking PCI vendor=32902, device=9283 > info: [drm] Checking PCI vendor=4098, device=19782 > drm0: port 0x2000-0x20ff mem > 0xf000-0xf0003fff,0xf800-0xfbff irq 9 at device 0.0 on pci1 > info: [drm] AGP at 0xf400 64MB > info: [drm] Initialized r128 2.2.0 20010405 on minor 0 > info: [drm] 8192 13 12 > > This laptop otherwise suspend/resumes fine (ie: without agp). Could you retry suspend/resume with AGP compiled in but without the DRM (uninstall drm-kmod)? If having agp in the kernel is causing suspend/resume problems, then maybe it will be fixed by re-doing the initialization of the AGP after resume like linux does. Once I played with that on my laptop, which also has suspend/resume issues. It looked like AGP was still configured right after resume but before the machine hung, so I didn't try reconfiguring. Now I think I probably should have. -- Eric Anholt[EMAIL PROTECTED] http://people.freebsd.org/~anholt/ [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RE: agp driver locks up on resume
No, not at all. Disable DRI in your XF86Config file. One work around I have used with good success is to start up the server without DRI enabled (using one XF86Config)and then after that start up another server (with DRI) for JUST 3D work on another VT. This is easy enough to do from the command line (you can even do it from within the first X session if you like). That way, when I want to suspend I just shut down the DRI enabled session before suspending and then restart it after the suspend; I don't have to shut down all my NON-3D programs with this method. I used something like this to start the other (DRI enabled) server: startx -- :1 -xf86config XF86Config.DRI_enabled & I'm not at my machine at the moment, so I can't be sure this is it exactly (you might need one more ":1" before the "&", but I don't think so). Sean -Original Message- From: David Gilbert [mailto:[EMAIL PROTECTED] Sent: Thursday, April 03, 2003 2:40 PM To: Welch, Sean M. Cc: '[EMAIL PROTECTED]'; '[EMAIL PROTECTED]' Subject: Re:agp driver locks up on resume > "Sean" == Sean M Welch writes: Sean> I'm familiar with this one -- it isn't agp, it is DRI. DRI Sean> depends on AGP so you are disabling both when you disable AGP. Sean> This issue has to do with the DRI module "losing track" of what Sean> is going on in the usage of main memory (through AGP) when you Sean> do a suspend resume -- it gets stuck trying to flush a buffer... So ... this means that there's no hope ... just disable agp ... ? Dave. -- |David Gilbert, Velocet Communications. | Two things can only be | |Mail: [EMAIL PROTECTED] | equal if and only if they | |http://daveg.ca | are precisely opposite. | =GLO ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
