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: <APM BIOS> on motherboard
> apm0: found APM BIOS v1.2, connected at v1.2
> pcib0: <Host to PCI bridge> on motherboard
> pci0: <PCI bus> on pcib0
> agp0: <Intel 82815 (i815 GMCH) host to PCI bridge> mem
0xf4000000-0xf7ffffff at device 0.0 on pci0
> pcib1: <Intel 82801BA/BAM (ICH2) PCI-PCI (AGP) bridge> at device 1.0
on pci0
> pci1: <PCI bus> on pcib1
> pci1: <ATI model 4d46 graphics accelerator> at 0.0 irq 9
>
> then:
>
> info: [drm] Checking PCI vendor=32902, device=9283
> info: [drm] Checking PCI vendor=4098, device=19782
> drm0: <ATI Rage 128 Mobility MF (AGP 4x)> port 0x2000-0x20ff mem
0xf0000000-0xf0003fff,0xf8000000-0xfbffffff irq 9 at device 0.0 on pci1
> info: [drm] AGP at 0xf4000000 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 eta@lclark.edu
http://people.freebsd.org/~anholt/ anholt@FreeBSD.org