Summary: | [r300g] [bisected] hard locks with polling enabled in 2.6.35 | ||
---|---|---|---|
Product: | Mesa | Reporter: | Giacomo Perale <ghepeu> |
Component: | Drivers/Gallium/r300 | Assignee: | Default DRI bug account <dri-devel> |
Status: | RESOLVED FIXED | QA Contact: | |
Severity: | normal | ||
Priority: | medium | CC: | bugzi11.fdo.tormod, hicham.haouari, xeros |
Version: | git | ||
Hardware: | Other | ||
OS: | All | ||
Whiteboard: | |||
i915 platform: | i915 features: | ||
Attachments: |
git-bisect.log
add parameter to disable polling patch to disable polling DACs dmesg 2.6.36-rc7 with disabled polling DACs patch, rv380 |
Description
Giacomo Perale
2010-08-03 14:17:16 UTC
Created attachment 37981 [details] [review] add parameter to disable polling I came back from vacation and found a patch from Chris Wilson in dri-devel who added a parameter to disable polling; since my bisection run pointed to the commit who enabled polling as the origin of my problem, I quickly adapted the patch to vanilla 2.6.35 to do some tests. The patch is attached to this comment; to try it patch the kernel and boot with drm_kms_helper.poll=0; be careful, without this parameter sometime X refused to start here. Since this was only a test I didn't look too hard, I think it's related to the slow work->workqueues conversion. Anyway, with polling disabled I was able to play with openarena for about 15 minutes, while with polling (without the patch) I had a hardlock in 30-60s. Since this could be important, I have a VGA/DVI card and I'm using the DVI port, with nothing connected to the VGA port. I can confirm this problem. With polling disabled my computer does not lock up anymore. *** Bug 28474 has been marked as a duplicate of this bug. *** can you attach a dmesg for the rv370 card? and also what connectors you have monitors connected to. Created attachment 39604 [details] [review] patch to disable polling DACs does this patch help when booting with polling enabled? I reported the same bug (I think) over here: https://bugzilla.kernel.org/show_bug.cgi?id=20042 Your latest patch disabling polling DACs works for my, I applied it to 2.6.36-rc7 and then ran Penumbra Overture without any problem. I'm using rv380, not rv370 (according to dmesg). I've included dmesg output as an attachment. Thanks very much for this patch! Created attachment 39745 [details]
dmesg 2.6.36-rc7 with disabled polling DACs patch, rv380
I have radeon module compilation errors with this patch applied on 2.6.35: make: Entering directory `/usr/src/linux-headers-2.6.35-22-generic' CC [M] /usr/src/linux-source-2.6.35/linux-source-2.6.35/drivers/gpu/drm/radeon/radeon_drv.o CC [M] /usr/src/linux-source-2.6.35/linux-source-2.6.35/drivers/gpu/drm/radeon/radeon_cp.o CC [M] /usr/src/linux-source-2.6.35/linux-source-2.6.35/drivers/gpu/drm/radeon/radeon_state.o CC [M] /usr/src/linux-source-2.6.35/linux-source-2.6.35/drivers/gpu/drm/radeon/radeon_mem.o CC [M] /usr/src/linux-source-2.6.35/linux-source-2.6.35/drivers/gpu/drm/radeon/radeon_irq.o CC [M] /usr/src/linux-source-2.6.35/linux-source-2.6.35/drivers/gpu/drm/radeon/r300_cmdbuf.o CC [M] /usr/src/linux-source-2.6.35/linux-source-2.6.35/drivers/gpu/drm/radeon/r600_cp.o CC [M] /usr/src/linux-source-2.6.35/linux-source-2.6.35/drivers/gpu/drm/radeon/radeon_device.o CC [M] /usr/src/linux-source-2.6.35/linux-source-2.6.35/drivers/gpu/drm/radeon/radeon_asic.o CC [M] /usr/src/linux-source-2.6.35/linux-source-2.6.35/drivers/gpu/drm/radeon/radeon_kms.o CC [M] /usr/src/linux-source-2.6.35/linux-source-2.6.35/drivers/gpu/drm/radeon/radeon_atombios.o /usr/src/linux-source-2.6.35/linux-source-2.6.35/drivers/gpu/drm/radeon/radeon_atombios.c: In function ‘radeon_atom_get_hpd_info_from_gpio’: /usr/src/linux-source-2.6.35/linux-source-2.6.35/drivers/gpu/drm/radeon/radeon_atombios.c:199: warning: ‘hpd.plugged_state’ is used uninitialized in CC [M] /usr/src/linux-source-2.6.35/linux-source-2.6.35/drivers/gpu/drm/radeon/radeon_agp.o CC [M] /usr/src/linux-source-2.6.35/linux-source-2.6.35/drivers/gpu/drm/radeon/atombios_crtc.o CC [M] /usr/src/linux-source-2.6.35/linux-source-2.6.35/drivers/gpu/drm/radeon/radeon_combios.o CC [M] /usr/src/linux-source-2.6.35/linux-source-2.6.35/drivers/gpu/drm/radeon/atom.o CC [M] /usr/src/linux-source-2.6.35/linux-source-2.6.35/drivers/gpu/drm/radeon/radeon_fence.o CC [M] /usr/src/linux-source-2.6.35/linux-source-2.6.35/drivers/gpu/drm/radeon/radeon_ttm.o CC [M] /usr/src/linux-source-2.6.35/linux-source-2.6.35/drivers/gpu/drm/radeon/radeon_object.o CC [M] /usr/src/linux-source-2.6.35/linux-source-2.6.35/drivers/gpu/drm/radeon/radeon_gart.o CC [M] /usr/src/linux-source-2.6.35/linux-source-2.6.35/drivers/gpu/drm/radeon/radeon_legacy_crtc.o CC [M] /usr/src/linux-source-2.6.35/linux-source-2.6.35/drivers/gpu/drm/radeon/radeon_legacy_encoders.o CC [M] /usr/src/linux-source-2.6.35/linux-source-2.6.35/drivers/gpu/drm/radeon/radeon_connectors.o /usr/src/linux-source-2.6.35/linux-source-2.6.35/drivers/gpu/drm/radeon/radeon_connectors.c: In function ‘radeon_vga_detect’: /usr/src/linux-source-2.6.35/linux-source-2.6.35/drivers/gpu/drm/radeon/radeon_connectors.c:626: error: ‘force’ undeclared (first use in this functio /usr/src/linux-source-2.6.35/linux-source-2.6.35/drivers/gpu/drm/radeon/radeon_connectors.c:626: error: (Each undeclared identifier is reported only /usr/src/linux-source-2.6.35/linux-source-2.6.35/drivers/gpu/drm/radeon/radeon_connectors.c:626: error: for each function it appears in.) /usr/src/linux-source-2.6.35/linux-source-2.6.35/drivers/gpu/drm/radeon/radeon_connectors.c: In function ‘radeon_dvi_detect’: /usr/src/linux-source-2.6.35/linux-source-2.6.35/drivers/gpu/drm/radeon/radeon_connectors.c:814: error: ‘force’ undeclared (first use in this functio make[1]: *** [/usr/src/linux-source-2.6.35/linux-source-2.6.35/drivers/gpu/drm/radeon/radeon_connectors.o] Błąd 1 make[1]: *** Oczekiwanie na niezakończone zadania.... make: *** [_module_/usr/src/linux-source-2.6.35/linux-source-2.6.35/drivers/gpu/drm/radeon] Error 2 make: Leaving directory `/usr/src/linux-headers-2.6.35-22-generic' *** Bug 30575 has been marked as a duplicate of this bug. *** This bug have been fixed in upstream kernel (.37-rc1 IIRC), so I think this bug can be safely closed. FWIW, it has been fixed in fedora stock kernel 2.6.35-51.fc14 also. Thank you Dave Thanks for feedback, closing.. |
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.