dri-devel June 2011

dri-devel@lists.freedesktop.org

101 participants
499 discussions

[Bug 33867] New: [bisected] Graphics corruption related to pageflip ioctl support in 2.6.38-rc*
by bugzilla-daemon＠freedesktop.org 22 Jul '12

22 Jul '12

https://bugs.freedesktop.org/show_bug.cgi?id=33867 Summary: [bisected] Graphics corruption related to pageflip ioctl support in 2.6.38-rc* Product: DRI Version: DRI CVS Platform: x86-64 (AMD64) OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium Component: DRM/Radeon AssignedTo: dri-devel(a)lists.freedesktop.org ReportedBy: dawitbro(a)sbcglobal.net Created an attachment (id=42887) --> (https://bugs.freedesktop.org/attachment.cgi?id=42887) Commits not present in 2.6.37 applied to local branch I am troubleshooting some graphics corruption I noticed when testing the post-2.6.37 commits from drm-airlied git (drm-fixes in this case). I was trying to produce a kernel as close as possible to the latest stable release (since 2.6.38 is very early in the rc stage) with all of the newest radeon-related features. This is a preliminary report, and may turn out to be invalid, because the kernel I am using is actually a local branch from v2.6.37 with only the commits from drm-airlied relevant to my hardware individually cherry-picked. I have bisected the problem down to a specific commit, but if I made any errors during the cherry-pick process then this report is useless. I plan to confirm that the problem is real tomorrow, by building directly from the drm-airlied/drm-fixes tree (which was the most up-to-date tree I could find today). As I will report below, there is some similarity with https://bugs.freedesktop.org/show_bug.cgi?id=33515 and that is the only reason I decided to report my findings before I am really sure there is a problem. Hopefully this will help Michel and other devs save some time and trouble if my guess (that my bug is related) turns out to be correct. ---------------------- OK, here is what I have done so far: 1. I made a local git branch based on v2.6.37. 2. I identified commits I wanted from drm-airlied/drm-fixes (Feb. 2, 2011) 3. Because of GPU lockups recently cured by Alex Deucher, I picked one particular commit first (1e644d6d, "drm/radeon/kms: re-emit full context state for evergreen blits"); without this, testing would be pointless since my GPU would just lock up when trying and 3D app. 4. I then cherry-picked the rest of the commits I had chosen, in order from oldest to newest (according to 'git log'). See attached file, 'applied-cherry-picks.txt', if interested in specifics. Everything actually seemed to be working fine; I only happened to notice a small glitch. I use a locally-built game called 'prboom-plus' with my original Ultimate DOOM WAD file to test Radeon support (in kernels, Mesa, xf86-video-ati, etc.). When a game begins, there is a melt-down animation which transitions into the new game; there is a similar (I would have guessed identical before) melting effect when the player is killed but hits the space bar to restart the game. In this second melting effect, after being killed, the "melted" part of the screen was all black, a clear regression. Before today's testing, I had been using a straight 2.6.37 kernel with the patch from Alex I mentioned in item 3 above. With that kernel, both melting effects work fine. That seems to rule out a problem with xorg-server, mesa, libdrm, or xf86-video-ati. I decided to try bisecting the issue. I built kernels from the first and last commits listed in the attached file: 1e644d6d and dca0d612. The former was "good" and the latter "bad". The bisect jumped to 204663c4 and 18007401 next -- both were "bad". The next jump, 65705962, caused 'prboom-plus' to hang during the second kind of melting; I was able to SSH into the machine and 'kill -9' the game. Since there was a series of TTM related changes in that series of commits, I used 'git bisect skip' until I was presented with a commit before or after the TTM series; I tested the kernels (all hung on the second melt), but told git to skip them; the ones I pretended to skip were eba67093, 95762c2b, and 702adba2. I was offered 147666fb, and it was "bad" but did not hang during the second kind of melt. Continuing, the bisect took me back to 2357cbe5, which hung X so that it could not be killed with 'kill -9'; I had to reboot via SSH. I skipped ecf7ace9 and 68c4fa31 without building kernels. The bisect then went to d6ea8886 and b6724405, which hung (so I pretended to skip them). I skipped 96726fe50 without building. The bisect moved to 3e4ea742, which hung, and 6f34be50, which also hung. Interestingly, f5a80209 was perfectly OK. This meant that the last commit I tested was the first bad commit. I had been skipping the commits causing hangs because I expected the hang to be a temporary problem resolved somewhere in the middle of the list; I believed this because of the fact the first and last commits in my list did _not_ produce hanging kernels. Of course, I was actually building most of the kernels that I "skipped", so I knew they were "bad" even if git did not. To sum up. the first three cherry-picks (applied to v2.6.37) were fine: 1e644d6dce366a7bae22484f60133b61ba322911 drm/radeon/kms: re-emit full context state for evergreen blits 27641c3f003e7f3b6585c01d8a788883603eb262 drm/vblank: Add support for precise vblank timestamping. f5a8020903932624cf020dc72455a10a3e005087 drm/kms/radeon: Add support for precise vblank timestamping. The commit which introduced the hangs -- and these happened entirely predictably and consistently: when the second kind of "melt" in 'prboom-plus' occurs -- was 6f34be50bd1bdd2ff3c955940e033a80d05f248a drm/radeon/kms: add pageflip ioctl support (v3) After a series of several TTM-related commits, the hanging was resolved and the second kind of melt would display in all black instead, beginning at this commit: 147666fb3b93b8c484f562da33a37f886ddff768 drm/radeon: Use the ttm execbuf utilities As I mentioned above, these results are preliminary; I will try builds directly from drm-airlied tomorrow since we are snowed-in here in Michigan, and I don't have to work tomorrow. My problems with hangs sound very similar to f.d.o. bug #33515. This may also be related to #33418, since that user (Erdem) is using 2.6.38-rc1. Hardware: Radeon HD 5750 (Evergreen JUNIPER) Software: kernel 2.6.37 + commits as described above libdrm 2.4.23 xorg-server 1.9.3.902 xf86-video-ati 6.13.99 (git commit 3dc28c86 of Jan. 27) mesa 7.11.0 (git commit 11b15c4d of Jan 30), r600g -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.

1 16

[Bug 35192] New: BUG() in radeon driver with ATI Technologies Inc RV515 [Radeon X1300]
by bugzilla-daemon＠bugzilla.kernel.org 13 Jun '12

13 Jun '12

https://bugzilla.kernel.org/show_bug.cgi?id=35192 URL: http://bugs.gentoo.org/show_bug.cgi?id=359281 Summary: BUG() in radeon driver with ATI Technologies Inc RV515 [Radeon X1300] Product: Drivers Version: 2.5 Kernel Version: 2.6.37 and 2.6.38 Platform: All OS/Version: Linux Tree: Mainline Status: NEW Severity: normal Priority: P1 Component: Video(DRI - non Intel) AssignedTo: drivers_video-dri(a)kernel-bugs.osdl.org ReportedBy: blueness(a)gentoo.org Regression: Yes A regression in kernels 2.6.37 up to 2.6.38.6 hits a BUG() in the radeon driver with the following hardware (as reported by lspci -kv) 02:00.0 VGA compatible controller: ATI Technologies Inc RV515 [Radeon X1300] (prog-if 00 [VGA controller]) Subsystem: ATI Technologies Inc All-in-Wonder 2006 PCI-E Edition Flags: bus master, fast devsel, latency 0, IRQ 40 Memory at e0000000 (64-bit, prefetchable) [size=256M] Memory at fd9f0000 (64-bit, non-prefetchable) [size=64K] I/O ports at ce00 [size=256] Expansion ROM at fd9c0000 [disabled] [size=128K] Capabilities: [50] Power Management version 2 Capabilities: [58] Express Endpoint, MSI 00 Capabilities: [80] MSI: Enable+ Count=1/1 Maskable- 64bit+ Kernel driver in use: radeon The BUG() is kernel tried to execute NX-protected page - exploit attempt? (uid: 0) BUG: unable to handle kernel paging request at ffffffff81c0e711 IP: [<ffffffff81c0e711>] platform_device_register_resndata+0x0/0x8c PGD 1ae5067 PUD 1ae9063 PMD 3c473063 PTE 8000000001c0e163 Oops: 0011 [#1] SMP last sysfs file: /sys/devices/system/cpu/cpu1/cache/index2/shared_cpu_map CPU 0 Pid: 1627, comm: X Tainted: G W 2.6.38.6 #1 HP Pavilion 061 ER900AA-ABA a1430n/NAGAMI RIP: 0010:[<ffffffff81c0e711>] [<ffffffff81c0e711>] platform_device_register_resndata+0x0/0x8c RSP: 0018:ffff88003a2b3d30 EFLAGS: 00010246 RAX: 0000000000000000 RBX: ffff88003cb81000 RCX: 0000000000000000 RDX: 0000000000000000 RSI: ffffffff81a41cbb RDI: 0000000000000000 RBP: ffff88003a2b3d88 R08: 0000000000000000 R09: 0000000000000000 R10: ffff88003a340000 R11: 00000000effff000 R12: 0000000000000000 R13: ffff88003cb80800 R14: ffff88003abeaa80 R15: 0000000000000001 FS: 00007f40b4c72880(0000) GS:ffff88003fc00000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: ffffffff81c0e711 CR3: 000000003a2a8000 CR4: 00000000000006f0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400 Process X (pid: 1627, threadinfo ffff88003a2b2000, task ffff88003d3ef1a0) Stack: ffffffff8133aa29 0000000000000000 0000000000000001 ffff88003a2b3de8 ffffffff811681fc ffff88003a2b3df8 ffff88003abeaa80 ffff88003cb80800 0000000000000040 0000000040786440 0000000000000078 ffff88003a2b3ea8 Call Trace: [<ffffffff8133aa29>] ? radeon_cp_init+0xd79/0x1180 [<ffffffff811681fc>] ? ext4_file_write+0x6c/0x2a0 [<ffffffff81317439>] drm_ioctl+0x389/0x4d0 [<ffffffff81339cb0>] ? radeon_cp_init+0x0/0x1180 [<ffffffff8110ddfb>] do_vfs_ioctl+0x9b/0x510 [<ffffffff8110e2bf>] sys_ioctl+0x4f/0x80 [<ffffffff81002e2b>] system_call_fastpath+0x16/0x1b Code: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 <00> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 RIP [<ffffffff81c0e711>] platform_device_register_resndata+0x0/0x8c RSP <ffff88003a2b3d30> CR2: ffffffff81c0e711 ---[ end trace f569524e57c84b79 ]--- More detail is avaiable in the following gentoo bug: http://bugs.gentoo.org/show_bug.cgi?id=359281 We're looking into doing the git-bisect now. -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching the assignee of the bug. ------------------------------------------------------------------------------ Achieve unprecedented app performance and reliability What every C/C++ and Fortran developer should know. Learn how Intel has extended the reach of its next-generation tools to help boost performance applications - inlcuding clusters. http://p.sf.net/sfu/intel-dev2devmay -- _______________________________________________ Dri-devel mailing list Dri-devel(a)lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel

1 9

[Bug 34102] New: radeon drm/kms driver: please use suspend/hibernate notifiers for allocating memory in suspend routines
by bugzilla-daemon＠bugzilla.kernel.org 13 Jun '12

13 Jun '12

https://bugzilla.kernel.org/show_bug.cgi?id=34102 Summary: radeon drm/kms driver: please use suspend/hibernate notifiers for allocating memory in suspend routines Product: Drivers Version: 2.5 Platform: All OS/Version: Linux Tree: Mainline Status: NEW Severity: normal Priority: P1 Component: Video(DRI - non Intel) AssignedTo: drivers_video-dri(a)kernel-bugs.osdl.org ReportedBy: Martin(a)Lichtvoll.de Regression: Yes I have the issue that since switching to Radeon KMS neither in-kernel-suspend nor TuxOnIce - that I do not use anymore currently - hibernation aborts due to lack of free memory when I have more than just 2-3 applications open although I have 2 GB of RAM in my ThinkPad T42. For further details please see: Bug #30482 - try harder to free enough memory / improve image size autotuning According to Rafael "The problem is a consequence of bugs in device drivers that shouldn't allocate memory in their suspend/resume routines _at_ _all_. So, a more fundamental fix would be to modify drivers so that they use suspend/hibernate notifiers for allocating memory. IOW, you should complain to the developers of the drivers that cause problems to happen." (see https://bugzilla.kernel.org/show_bug.cgi?id=30482#c7) While I am not completely sure that it is the Radeon DRM/KMS driver allocating memory additionally memory during hibernation cycle having this issue since switching to KMS points at that. Currently I am using 2.6.38.4 with gallium userspace: martin@shambhala:~> glxinfo | grep OpenGL OpenGL vendor string: X.Org R300 Project OpenGL renderer string: Gallium 0.4 on ATI RV350 OpenGL version string: 2.1 Mesa 7.10.2 OpenGL shading language version string: 1.20 OpenGL extensions: martin@shambhala:~> xdpyinfo | grep version version number: 11.0 X.Org version: 1.10.1 but this happened with earlier versions as well. -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching the assignee of the bug. ------------------------------------------------------------------------------ WhatsUp Gold - Download Free Network Management Software The most intuitive, comprehensive, and cost-effective network management toolset available today. Delivers lowest initial acquisition cost and overall TCO of any competing solution. http://p.sf.net/sfu/whatsupgold-sd -- _______________________________________________ Dri-devel mailing list Dri-devel(a)lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel

1 17

[Bug 34082] New: Incorrect / missing device id in radeon_atombios.c
by bugzilla-daemon＠bugzilla.kernel.org 13 Jun '12

13 Jun '12

https://bugzilla.kernel.org/show_bug.cgi?id=34082 Summary: Incorrect / missing device id in radeon_atombios.c Product: Drivers Version: 2.5 Kernel Version: 2.6.38+ Platform: All OS/Version: Linux Tree: Mainline Status: NEW Severity: normal Priority: P1 Component: Video(DRI - non Intel) AssignedTo: drivers_video-dri(a)kernel-bugs.osdl.org ReportedBy: zhamahn(a)gmail.com Regression: No I have an Acer TravelMate 5730, and the scenario described around line 434 in radeon_atombios.c applies to this model as well. The problem is that the 5730 has a different device id than 5730G (at least my machine has). Changing the relevant id from 0x95c4 to 0x9591 fixes everything for me. Without changing the id, HDMI output works only if I turn it off with xrandr and then use DVI (which this laptop doesn't have) and it doesn't even work that well then, I also get lots of invalid EDID spam in dmesg. ... Apr 28 23:00:26 localhost kernel: [ 3476.326407] [drm:radeon_dvi_detect] *ERROR* DVI-I-1: probed a monitor but no|invalid EDID Apr 28 23:02:19 localhost kernel: [ 3589.819736] [drm:radeon_dvi_detect] *ERROR* HDMI-A-1: probed a monitor but no|invalid EDID Apr 28 23:04:02 localhost kernel: [ 3692.619727] [drm:radeon_dvi_detect] *ERROR* DVI-I-1: probed a monitor but no|invalid EDID Apr 28 23:05:24 localhost kernel: [ 3774.783055] [drm:radeon_dvi_detect] *ERROR* HDMI-A-1: probed a monitor but no|invalid EDID ... This patch fixes the problems mentioned above. It just copies the entry for 5730G and changes the device id. diff --git a/drivers/gpu/drm/radeon/radeon_atombios.c b/drivers/gpu/drm/radeon/radeon_atombios.c index f5d12fb..d706df5 100644 --- a/drivers/gpu/drm/radeon/radeon_atombios.c +++ b/drivers/gpu/drm/radeon/radeon_atombios.c @@ -451,6 +451,18 @@ static bool radeon_atom_apply_quirks(struct drm_device *dev, } } + /* Same as above, but for Acer Travelmate 5730 */ + if ((dev->pdev->device == 0x9591) && + (dev->pdev->subsystem_vendor == 0x1025) && + (dev->pdev->subsystem_device == 0x013c)) { + if ((*connector_type == DRM_MODE_CONNECTOR_DVII) && + (supported_device == ATOM_DEVICE_DFP1_SUPPORT)) { + /* actually it's a DVI-D port not DVI-I */ + *connector_type = DRM_MODE_CONNECTOR_DVID; + return false; + } + } + /* XFX Pine Group device rv730 reports no VGA DDC lines * even though they are wired up to record 0x93 */ -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching the assignee of the bug. ------------------------------------------------------------------------------ WhatsUp Gold - Download Free Network Management Software The most intuitive, comprehensive, and cost-effective network management toolset available today. Delivers lowest initial acquisition cost and overall TCO of any competing solution. http://p.sf.net/sfu/whatsupgold-sd -- _______________________________________________ Dri-devel mailing list Dri-devel(a)lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel

1 5

[Bug 35622] New: [i915g] 6358e6371b31671acbfa7c00336673f62ee928c5 result in a black screen in the main menu of portal in wine
by bugzilla-daemon＠freedesktop.org 10 Jun '12

10 Jun '12

https://bugs.freedesktop.org/show_bug.cgi?id=35622 Summary: [i915g] 6358e6371b31671acbfa7c00336673f62ee928c5 result in a black screen in the main menu of portal in wine Product: Mesa Version: git Platform: x86 (IA32) OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium Component: Drivers/Gallium/i915g AssignedTo: dri-devel(a)lists.freedesktop.org ReportedBy: cme3000(a)gmail.com Created an attachment (id=44781) --> (https://bugs.freedesktop.org/attachment.cgi?id=44781) batchbuffer dumps of portal Commit 6358e6371b31671acbfa7c00336673f62ee928c5 breaks portal in wine. If you start it with -console -novid it fails to render the main menu (it's just black). With I915_USE_BLITTER=yes it's rendered correctly again. In the portal_batchbuffer.tar.gz is the dump of 'I915_DUMP_RAW_FILE=', good.batchbuffer with I915_USE_BLITTER=yes and bad.batchbuffer without. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.

1 7

[Bug 30383] New: r600c: GPU lockup / driver hang when playing ufoai
by bugzilla-daemon＠freedesktop.org 02 May '12

02 May '12

https://bugs.freedesktop.org/show_bug.cgi?id=30383 Summary: r600c: GPU lockup / driver hang when playing ufoai Product: Mesa Version: git Platform: Other OS/Version: All Status: NEW Severity: normal Priority: medium Component: Drivers/DRI/R600 AssignedTo: dri-devel(a)lists.freedesktop.org ReportedBy: edwintorok(a)gmail.com Kernel bug reported here: https://bugzilla.kernel.org/show_bug.cgi?id=19102 Trying to play this game: ufoai.ninex.info, as soon as you choose to enter a mission there is a GPU lockup and then the radeon driver hangs. It is impossible to switch to the console, or otherwise kill the game at this point. I can ssh in, but there is no way to get back X into a working state (or killing it either). Only a reboot helps. This happens using r600 classic driver from git mesa. Tried it twice: locked up system both times. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.

1 3

[Bug 34822] New: Blank display on Toshiba laptop C670D-10C using AMD E-240 Palm chip
by bugzilla-daemon＠bugzilla.kernel.org 29 Apr '12

29 Apr '12

https://bugzilla.kernel.org/show_bug.cgi?id=34822 Summary: Blank display on Toshiba laptop C670D-10C using AMD E-240 Palm chip Product: Drivers Version: 2.5 Kernel Version: 2.6.39-rc7 Platform: All OS/Version: Linux Tree: Mainline Status: NEW Severity: normal Priority: P1 Component: Video(DRI - non Intel) AssignedTo: drivers_video-dri(a)kernel-bugs.osdl.org ReportedBy: anisse(a)astier.eu Regression: No Created an attachment (id=57132) --> (https://bugzilla.kernel.org/attachment.cgi?id=57132) dmesg using Linus' HEAD of May 10th 2011 On a Toshiba laptop using an AMD Fusion GPU (SoC: E-240), I am unable to have screen turn on with KMS. It stays blank, even when starting the X server. I tried with 2.6.38.5, Today's Linus tree, Yesterday's drm-2.6/drm-next, all to the same result. Here is the lspci: 00:00.0 Host bridge [0600]: Advanced Micro Devices [AMD] Device [1022:1510] 00:01.0 VGA compatible controller [0300]: ATI Technologies Inc Device [1002:9803] 00:11.0 SATA controller [0106]: ATI Technologies Inc SB700/SB800 SATA Controller [AHCI mode] [1002:4391] (rev 40) 00:12.0 USB Controller [0c03]: ATI Technologies Inc SB700/SB800 USB OHCI0 Controller [1002:4397] 00:12.2 USB Controller [0c03]: ATI Technologies Inc SB700/SB800 USB EHCI Controller [1002:4396] 00:13.0 USB Controller [0c03]: ATI Technologies Inc SB700/SB800 USB OHCI0 Controller [1002:4397] 00:13.2 USB Controller [0c03]: ATI Technologies Inc SB700/SB800 USB EHCI Controller [1002:4396] 00:14.0 SMBus [0c05]: ATI Technologies Inc SBx00 SMBus Controller [1002:4385] (rev 42) 00:14.1 IDE interface [0101]: ATI Technologies Inc SB700/SB800 IDE Controller [1002:439c] (rev 40) 00:14.2 Audio device [0403]: ATI Technologies Inc SBx00 Azalia (Intel HDA) [1002:4383] (rev 40) 00:14.3 ISA bridge [0601]: ATI Technologies Inc SB700/SB800 LPC host controller [1002:439d] (rev 40) 00:14.4 PCI bridge [0604]: ATI Technologies Inc SBx00 PCI to PCI Bridge [1002:4384] (rev 40) 00:15.0 PCI bridge [0604]: ATI Technologies Inc Device [1002:43a0] 00:15.1 PCI bridge [0604]: ATI Technologies Inc Device [1002:43a1] 00:15.2 PCI bridge [0604]: ATI Technologies Inc Device [1002:43a2] 00:16.0 USB Controller [0c03]: ATI Technologies Inc SB700/SB800 USB OHCI0 Controller [1002:4397] 00:16.2 USB Controller [0c03]: ATI Technologies Inc SB700/SB800 USB EHCI Controller [1002:4396] 00:18.0 Host bridge [0600]: Advanced Micro Devices [AMD] Device [1022:1700] (rev 43) 00:18.1 Host bridge [0600]: Advanced Micro Devices [AMD] Device [1022:1701] 00:18.2 Host bridge [0600]: Advanced Micro Devices [AMD] Device [1022:1702] 00:18.3 Host bridge [0600]: Advanced Micro Devices [AMD] Device [1022:1703] 00:18.4 Host bridge [0600]: Advanced Micro Devices [AMD] Device [1022:1704] 00:18.5 Host bridge [0600]: Advanced Micro Devices [AMD] Device [1022:1718] 00:18.6 Host bridge [0600]: Advanced Micro Devices [AMD] Device [1022:1716] 00:18.7 Host bridge [0600]: Advanced Micro Devices [AMD] Device [1022:1719] 03:00.0 Network controller [0280]: Realtek Semiconductor Co., Ltd. Device [10ec:8176] (rev 01) 04:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8101E/RTL8102E PCI Express Fast Ethernet controller [10ec:8136] (rev 05) -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching the assignee of the bug. ------------------------------------------------------------------------------ Achieve unprecedented app performance and reliability What every C/C++ and Fortran developer should know. Learn how Intel has extended the reach of its next-generation tools to help boost performance applications - inlcuding clusters. http://p.sf.net/sfu/intel-dev2devmay -- _______________________________________________ Dri-devel mailing list Dri-devel(a)lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel

1 21

[Bug 29412] New: fans running at full-speed after resume from suspend with radeon and KMS
by bugzilla-daemon＠bugzilla.kernel.org 16 Apr '12

16 Apr '12

https://bugzilla.kernel.org/show_bug.cgi?id=29412 Summary: fans running at full-speed after resume from suspend with radeon and KMS Product: Drivers Version: 2.5 Kernel Version: 2.6.38-rc5+ Platform: All OS/Version: Linux Tree: Mainline Status: NEW Severity: normal Priority: P1 Component: Video(DRI - non Intel) AssignedTo: drivers_video-dri(a)kernel-bugs.osdl.org ReportedBy: jon+bugzilla.kernel.org(a)alcopop.org Regression: No Hi, Originally reported against the wrong product, here: https://bugzilla.kernel.org/show_bug.cgi?id=18552 I have an ATI Radeon X850XT PCIE card plugged into an Intel DG35EC motherboard. With kernels since 2.6.32-rc1 and most recently tested with mainline commit 2a324ce7b79a3a90cc2d4ade5d5f960a99000caa (2.6.38-rc5+), if I attempt a suspend-to-ram, upon resume, the fan on my ATI card remains at full speed (loud), and does not throttle back to quiet (normal behaviour). Booting with 'radeon.modeset=0' prevents this. Please let me know what further information is needed. Thanks! -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching the assignee of the bug. ------------------------------------------------------------------------------ The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: Pinpoint memory and threading errors before they happen. Find and fix more than 250 security defects in the development cycle. Locate bottlenecks in serial and parallel code that limit performance. http://p.sf.net/sfu/intel-dev2devfeb -- _______________________________________________ Dri-devel mailing list Dri-devel(a)lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel

1 18

Re: 2.6.35-rc4 Graphics performance issue and freeing invalid memtype messages on boot.
by Andrew Morton 03 Apr '12

03 Apr '12

(Rafael, Maciej: two probably-separate post-2.6.34 regressions here) On Tue, 06 Jul 2010 22:22:17 +1000 Andrew Hendry <andrew.hendry(a)gmail.com> wrote: > > Some extra messages when booting with -rc4. Didn't get them in -rc3. > [ 1.387013] swapper:1 freeing invalid memtype bf788000-bf789000 > [ 1.387409] swapper:1 freeing invalid memtype bf789000-bf78a000 > [ 5.999675] modprobe:548 freeing invalid memtype d0000000-d0040000 > [ 6.068347] modprobe:548 freeing invalid memtype d0140000-d0150000 > [ 6.068647] modprobe:548 freeing invalid memtype d0150000-d0160000 > [ 6.069661] modprobe:548 freeing invalid memtype d0170000-d01f0000 > [ 6.085969] modprobe:548 freeing invalid memtype d01f0000-d0200000 > [ 6.087673] modprobe:548 freeing invalid memtype d0210000-d0220000 > [ 6.087900] modprobe:548 freeing invalid memtype d0220000-d0230000 > [ 6.088092] modprobe:548 freeing invalid memtype d0230000-d0240000 > [ 6.088317] modprobe:548 freeing invalid memtype d0240000-d0250000 hrmpf, one of those wonderful messages where neither it nor its source code give you any clue regarding what caused it nor how to fix it. please, apply this: --- a/arch/x86/mm/pat.c~a +++ a/arch/x86/mm/pat.c @@ -359,7 +359,7 @@ int free_memtype(u64 start, u64 end) entry = rbt_memtype_erase(start, end); spin_unlock(&memtype_lock); - if (!entry) { + if (WARN_ON(!entry)) { printk(KERN_INFO "%s:%d freeing invalid memtype %Lx-%Lx\n", current->comm, current->pid, start, end); return -EINVAL; and let's at least see where it's coming from. > Not sure if its related, but also have a noticeable performance issue with graphics under rc4. > Dragging and resizing windows, screen updates, and jumpy cursor are all slow. > Playing a full screen video under vlc gets only 1-2 frames per second, but plays fine under rc3. > Tested a kernel compile, it was roughly the same. > Userspace is ubunutu 10.04 64bit. > > Any hints? Otherwise will start a bisect tomorrow night. > > Config attached, lspci, rc3 and rc4 boot messages below: What graphics hardware are you using?

3 3

[Bug 36421] New: RV710: GPU lockup running portal2 in wine.
by bugzilla-daemon＠freedesktop.org 23 Mar '12

23 Mar '12

https://bugs.freedesktop.org/show_bug.cgi?id=36421 Summary: RV710: GPU lockup running portal2 in wine. Product: Mesa Version: git Platform: x86-64 (AMD64) OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium Component: Drivers/Gallium/r600 AssignedTo: dri-devel(a)lists.freedesktop.org ReportedBy: NightNord(a)gmail.com Created an attachment (id=45860) --> (https://bugs.freedesktop.org/attachment.cgi?id=45860) kernel traces for GPU lockup OpenGL renderer string: Gallium 0.4 on AMD RV710 OpenGL version string: 2.1 Mesa 7.11-devel (git-c98fa6b) After finishing loading any level game shows black screen (like monitor goes off), than screen goes back to live filled with some flickering garbage. netconsole on other hosts reports GPU lockup traces from kernel. Leaving game in this state for a while leads to complete kernel hangup. I failed to reproduce this on any other non-native 3d-application (read: game), neither on any native (still, I don't have access to much of them). Changing various in-game settings to lowest possible doesn't help, nor switching dxlevel (they seems to disable this feature). Attaching traces log from netconsole. I may also attach wine output, as it contains information about GL calls, but maybe it will be better to post wine bug for this? If there is any way to get some error-state (like one from intel cards in similar bugs here) or opengl calls trace - I'll happily provide them. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.

1 9

← Newer
1
...
19
20
21
22
23
24
25
...
50
Older →

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

dri-devel June 2011