| Summary: | FireGL Mobility T2: WebGL under firefox16 freezes system | ||||||
|---|---|---|---|---|---|---|---|
| Product: | DRI | Reporter: | miri | ||||
| Component: | DRM/Radeon | Assignee: | Default DRI bug account <dri-devel> | ||||
| Status: | RESOLVED MOVED | QA Contact: | |||||
| Severity: | normal | ||||||
| Priority: | medium | ||||||
| Version: | XOrg git | ||||||
| Hardware: | x86 (IA32) | ||||||
| OS: | Linux (All) | ||||||
| Whiteboard: | |||||||
| i915 platform: | i915 features: | ||||||
| Attachments: |
|
||||||
|
Description
miri
2012-11-08 14:17:17 UTC
Does changing the agp mode help? Set radeon.agpmode=x where x=-1,1,2,4,8. -1 disables agp and uses the gpu's gart instead. That is a kernel boot parameter and not a X config, isn't it? correct. e.g., add: radeon.agpmode=-1 to the kernel command line in grub. If I read dmesg correctly, it defaults to agp mode 2 but the bug still appears with radeon.agpmode=1. Using radeon.agpmode=-1 avoids the freeze, though. agpmode=-1 will be slower than the default, won't it? Anything else I can do to help with fixing this bug? (In reply to comment #4) > If I read dmesg correctly, it defaults to agp mode 2 but the bug still > appears with radeon.agpmode=1. Using radeon.agpmode=-1 avoids the freeze, > though. > agpmode=-1 will be slower than the default, won't it? Anything else I can do > to help with fixing this bug? does agpmode=4 or 8 help? agpmode=-1 may be slower, depends on the system and what you are doing. AGP is old and was kind of broken by design so I don't think anyone is going to put much effort into making it work better at this point. agpmode=4 didn't help either. So are you saying that no one will fix this bug and everyone with this configuration remains at risk that the system freezes? (In reply to comment #6) > agpmode=4 didn't help either. So are you saying that no one will fix this > bug and everyone with this configuration remains at risk that the system > freezes? With AGP it depends on the motherboard, the card, the AGP mode, and the phase of the moon. Some combinations are stable, others are not. The computer used to work quite nicely for a lot of OpenGL programs back then when I could still use fglrx, so I find it hard to believe that buggy hardware is at fault here. (In reply to comment #8) > The computer used to work quite nicely for a lot of OpenGL programs back > then when I could still use fglrx, so I find it hard to believe that buggy > hardware is at fault here. There are probably ways to make your system work better, but due to the nature of AGP and the fact that the hw is so old, I'm just saying it's not likely anyone is going to put much time into it at this point. Anything I can do to help? More info or enabling some debug output? -- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/drm/amd/issues/313. |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.