Re: [Nouveau] [Discussion] User controls for PowerManagement
Adding dri-devel@ to CC. On Thu, 7 Jan 2010 22:44:24 +0100 r.spl...@umail.leidenuniv.nl wrote: With some progress in PowerManagement support (there's a patch nearly done for reading the P-tables, written mostly by xexaxo, derived from thunderbirds nvclock, with 0x40 adjustments from myself) in my opinion it's time to think about the user aspect of this. My personal idea for GPU scaling was similar to that of CPU scaling in appearance eventually. When you look at the cpufreq-applet for Gnome, you see the choice between every supported CPU speed, and an option for Automatic scaling. To make an application like this possible nouveau needs to communicate with users. I was thinking a procfs or sysfs node for outputting a readable table with possible modes like: 03: CPU=135MHz,Shdr=135MHz,Mem=135MHz,Vlt=0.8V,Fan=80%; ... the node name would be something like pm_supported. Another node named pm_current could output the current mode (for instance 03), and be writable to set the desired mode. Mode numbers will be the identifier given by pm_supported, found in the powermode table. A third node would then be required to set auto scaling on or off (called pm_auto ?). All those nodes could eventually be placed in a separate subdirectory (pm?) 1. joi pointed out that procfs is deprecated, and I should use sysfs instead. There are two reasons to use procfs: - DRM has a pointer to the right DRM subfolder (/proc/drm/card number) which can be obtained by drm_device.control-proc_root. numberOfcourse, if there's something similar for sysfs available, then there's no problem. Otherwise procfs simply saves a lot of hassle as long as DRM still promotes procfs to the device drivers. - sysfs was designed for one value per node. The output of the pm_supported node would be an entire table. Is this on par with the design of sysfs? So: procfs or sysfs? 2. It sounds sensible to me to have one scaling algorithm (whatever that may become... first things first). When you can scale you can have the maximum performance as soon as you need it... so the aim should be maximum powersaving at all time, without sacrificing on performance. Agreed, or should there be several auto modes for different situations? I recall someone (you?) saying this is only for testing for now, and the proper user interface can be done later. In any case, I'd like to suggest discussing it on dri-devel@, since there are other drivers wanting to expose similar features. Hopefully people working on power management interfaces on intel and radeon can comment on this, like is there an agreed user interface design yet. btw. I think max powersaving and no performance loss are mutually exclusive, since changing power modes is not free nor instantenous. Or is it? How much of the card you need to stop to change clocks and volts? Do you need to sync to vblank to prevent visual glitches? -- Pekka Paalanen http://www.iki.fi/pq/ -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
[Bug 25142] touhou 11/12 run very slow in wine
http://bugs.freedesktop.org/show_bug.cgi?id=25142 --- Comment #23 from Allen Walker walkerallen...@googlemail.com 2010-01-10 03:06:40 PST --- (In reply to comment #22) The r300-blit branch is now merged in mesa master (7.8-dev), however it's currently enabled only without KMS. Sorry, only *with* KMS Thank you. I finally got around trying it out. Tried it out with kernel 2.6.33-rc3 and libdrm/mesa/xf86-video-ati from yesterday. The game now runs at full speed but the ingame graphic isn't visible (all black). Before, it was garbled with KMS enabled (see old screenshot for this bugreport) so I think it has something to do with 32bit libs compiled for the old API and indirect rendering which uses the 64bit libraries with the new API. But I don't know yet if I can recompile the 32bit libraries without introducing errors to check my theory so I will leave it at this for now. Thank you for your great work. -- Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
[Bug 25142] touhou 11/12 run very slow in wine
http://bugs.freedesktop.org/show_bug.cgi?id=25142 --- Comment #24 from Allen Walker walkerallen...@googlemail.com 2010-01-10 03:08:37 PST --- (In reply to comment #23) (In reply to comment #22) But I don't know yet if I can recompile the 32bit libraries without introducing errors to check my theory so I will leave it at this for now. I meant 'recompile at all'. Archlinux isn't multilib and misses lots of necessary libraries for 32bit on 64bit (udev?). -- Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Nouveau] [Discussion] User controls for PowerManagement
On Sun, 10 Jan 2010 12:43:02 +0200 Alexey Dobriyan adobri...@gmail.com wrote: On Thu, 7 Jan 2010 22:44:24 +0100 r.spl...@umail.leidenuniv.nl wrote: 1. joi pointed out that procfs is deprecated, and I should use sysfs instead. /proc is not deprecated per se, you simply shouldn't expose everything you know to userspace, because it will be impossible to remove later. I think adding random crap to procfs is frowned upon nowadays, that's probably what he meant. Attributes should be in sysfs. What to expose is another question, you are right. If the interface is just temporary, it should probably go into debugfs. That way one can have the code in the kernel proper, not fear about freezing it, and prevent people from finding it by accident. And it should be guarded by an EXPERIMENTAL, DANGEROUS Kconfig option in any case. -- Pekka Paalanen http://www.iki.fi/pq/ -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
[Bug 15030] New: screen connected to displayport is not detected - kms radeon
http://bugzilla.kernel.org/show_bug.cgi?id=15030 Summary: screen connected to displayport is not detected - kms radeon Product: Drivers Version: 2.5 Kernel Version: 2.6.33-rc3 2c1f1895ef2aa8f0e5497893eff71304aef332e1 Platform: All OS/Version: Linux Tree: Mainline Status: NEW Severity: normal Priority: P1 Component: Video(DRI - non Intel) AssignedTo: drivers_video-...@kernel-bugs.osdl.org ReportedBy: pl4nk...@googlemail.com Regression: No arch amd64 01:00.0 VGA compatible controller: ATI Technologies Inc RV770 [Radeon HD 4870] dual screen DVI-D + Displayport Without kms DP operates as expected. DP + DVI-D, kms [0.528230] [drm] Initialized drm 1.1.0 20060810 [0.528274] [drm] radeon defaulting to kernel modesetting. [0.528275] [drm] radeon kernel modesetting enabled. [0.528326] radeon :01:00.0: PCI INT A - GSI 18 (level, low) - IRQ 18 [0.528331] radeon :01:00.0: setting latency timer to 64 [0.531137] [drm] radeon: Initializing kernel modesetting. [0.531215] [drm] register mmio base: 0xFEAF [0.531216] [drm] register mmio size: 65536 [0.531728] ATOM BIOS: ATI [0.531751] [drm] Clocks initialized ! [0.532135] [drm] Detected VRAM RAM=256M, BAR=256M [0.532139] [drm] RAM width 256bits DDR [0.532213] [TTM] Zone kernel: Available graphics memory: 1544004 kiB. [0.532229] [drm] radeon: 256M of VRAM memory ready [0.532231] [drm] radeon: 512M of GTT memory ready. [0.532277] radeon :01:00.0: irq 27 for MSI/MSI-X [0.532281] [drm] radeon: using MSI. [0.532301] [drm] radeon: irq initialized. [0.532304] [drm] GART: num cpu pages 131072, num gpu pages 131072 [0.533240] [drm] Loading RV770 Microcode [0.533243] platform radeon_cp.0: firmware: using built-in firmware radeon/RV770_pfp.bin [0.533246] platform radeon_cp.0: firmware: using built-in firmware radeon/RV770_me.bin [0.533249] platform radeon_cp.0: firmware: using built-in firmware radeon/R700_rlc.bin [0.581022] [drm] ring test succeeded in 1 usecs [0.581091] [drm] radeon: ib pool ready. [0.581160] [drm] ib test succeeded in 0 usecs [0.640444] [drm] Radeon Display Connectors [0.640446] [drm] Connector 0: [0.640447] [drm] HDMI-A [0.640448] [drm] HPD1 [0.640450] [drm] DDC: 0x7e40 0x7e40 0x7e44 0x7e44 0x7e48 0x7e48 0x7e4c 0x7e4c [0.640452] [drm] Encoders: [0.640453] [drm] DFP1: INTERNAL_UNIPHY [0.640455] [drm] Connector 1: [0.640456] [drm] DisplayPort [0.640457] [drm] HPD3 [0.640459] [drm] DDC: 0x7e60 0x7e60 0x7e64 0x7e64 0x7e68 0x7e68 0x7e6c 0x7e6c [0.640460] [drm] Encoders: [0.640462] [drm] DFP2: INTERNAL_UNIPHY [0.640463] [drm] Connector 2: [0.640464] [drm] DVI-I [0.640465] [drm] HPD2 [0.640467] [drm] DDC: 0x7e20 0x7e20 0x7e24 0x7e24 0x7e28 0x7e28 0x7e2c 0x7e2c [0.640468] [drm] Encoders: [0.640470] [drm] CRT1: INTERNAL_KLDSCP_DAC1 [0.640471] [drm] DFP3: INTERNAL_KLDSCP_LVTMA [0.640473] [drm] Connector 3: [0.640474] [drm] VGA [0.640476] [drm] DDC: 0x7e50 0x7e50 0x7e54 0x7e54 0x7e58 0x7e58 0x7e5c 0x7e5c [0.640478] [drm] Encoders: [0.640479] [drm] CRT2: INTERNAL_KLDSCP_DAC2 [1.081853] [drm] fb mappable at 0xD0141000 [1.081855] [drm] vram apper at 0xD000 [1.081856] [drm] size 5242880 [1.081857] [drm] fb depth is 24 [1.081858] [drm]pitch is 5120 [1.082924] executing set pll [1.130033] executing set crtc timing [1.130066] [drm] TMDS-14: set mode 1280x1024 18 [1.170259] Console: switching to colour frame buffer device 160x64 [1.174985] fb0: radeondrmfb frame buffer device [1.174987] registered panic notifier [1.174990] [drm] Initialized radeon 2.0.0 20080528 for :01:00.0 on minor 0 [ 11.640943] [drm:r600_irq_process] *ERROR* Unhandled interrupt: 21 5 [ 14.160031] executing set pll [ 14.160046] executing set crtc timing [ 14.160079] [drm] TMDS-14: set mode 1280x1024 18 Only DP, kms [0.528244] [drm] Initialized drm 1.1.0 20060810 [0.528288] [drm] radeon defaulting to kernel modesetting. [0.528289] [drm] radeon kernel modesetting enabled. [0.528340] radeon :01:00.0: PCI INT A - GSI 18 (level, low) - IRQ 18 [0.528344] radeon :01:00.0: setting latency timer to 64 [0.531151] [drm] radeon: Initializing kernel modesetting. [0.531230] [drm] register mmio base: 0xFEAF [0.531231] [drm] register mmio size: 65536 [0.531743] ATOM BIOS: ATI [0.531766] [drm] Clocks initialized ! [0.532150] [drm] Detected VRAM RAM=256M, BAR=256M [0.532154] [drm] RAM width 256bits DDR [0.532227] [TTM] Zone kernel: Available graphics memory: 1544004 kiB. [0.532244] [drm] radeon: 256M of VRAM memory ready [0.532245] [drm] radeon: 512M of GTT memory
[Bug 25982] New: Update 7.4 - 7.6.1 disables DRI
http://bugs.freedesktop.org/show_bug.cgi?id=25982 Summary: Update 7.4 - 7.6.1 disables DRI Product: Mesa Version: 7.6 Platform: x86-64 (AMD64) OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium Component: Drivers/DRI/r300 AssignedTo: dri-devel@lists.sourceforge.net ReportedBy: cur...@operamail.com Created an attachment (id=32563) -- (http://bugs.freedesktop.org/attachment.cgi?id=32563) dmesg Updating only Mesa from 7.4.4 to 7.6.1 disables DRI for me. Radeon X1300 Pro, pci-e Initial specs: linux 2.6.30.10, Xorg 7.4, ati 6.12.4 Just to be sure, I also updated the kernel to 2.6.32.3 and Xorg to 7.5, but still no direct rendering. Current specs: linux 2.6.32.3, Xorg 7.5, ati 6.12.99 (today's git master). Also tried Mesa 7.7, bug is still present. dmesg | grep drm: [drm] Initialized drm 1.1.0 20060810 [drm] radeon defaulting to userspace modesetting. [drm] Initialized radeon 1.31.0 20080528 for :01:00.0 on minor 0 grep drm Xorg.0.log (II) [KMS] drm report modesetting isn't supported. drmOpenDevice: node name is /dev/dri/card0 drmOpenByBusid: Searching for BusID pci::01:00.0 drmOpenDevice: node name is /dev/dri/card0 drmOpenByBusid: drmOpenMinor returns -1 drmOpenDevice: node name is /dev/dri/card1 drmOpenByBusid: drmOpenMinor returns -1 ... etc until card15 -- Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
[Bug 25982] Update 7.4 - 7.6.1 disables DRI
http://bugs.freedesktop.org/show_bug.cgi?id=25982 --- Comment #1 from Lauri Kasanen cur...@operamail.com 2010-01-10 11:58:57 PST --- Created an attachment (id=32564) -- (http://bugs.freedesktop.org/attachment.cgi?id=32564) lspci -vvnn -- Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
[Bug 25982] Update 7.4 - 7.6.1 disables DRI
http://bugs.freedesktop.org/show_bug.cgi?id=25982 --- Comment #2 from Lauri Kasanen cur...@operamail.com 2010-01-10 11:59:11 PST --- Created an attachment (id=32565) -- (http://bugs.freedesktop.org/attachment.cgi?id=32565) Xorg.0.log -- Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
[Bug 15035] BUG: unable to handle kernel paging request in rs600_gart_set_page()
http://bugzilla.kernel.org/show_bug.cgi?id=15035 Rafael J. Wysocki r...@sisk.pl changed: What|Removed |Added Blocks||7216 -- Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are watching the assignee of the bug. -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
[Bug 15035] New: BUG: unable to handle kernel paging request in rs600_gart_set_page()
http://bugzilla.kernel.org/show_bug.cgi?id=15035 Summary: BUG: unable to handle kernel paging request in rs600_gart_set_page() Product: Drivers Version: 2.5 Kernel Version: 2.6.33-rc2 Platform: All OS/Version: Linux Tree: Mainline Status: NEW Severity: normal Priority: P1 Component: Video(DRI - non Intel) AssignedTo: drivers_video-...@kernel-bugs.osdl.org ReportedBy: r...@sisk.pl Blocks: 14885 Regression: Yes Subject: BUG: unable to handle kernel paging request on 2.6.33-rc2 Submitter : Xiaotian Feng df...@redhat.com Date : 2010-01-05 19:10 References : http://lkml.org/lkml/2010/1/5/95 This entry is being used for tracking a regression from 2.6.32. Please don't close it until the problem is fixed in the mainline. -- Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are watching the assignee of the bug. -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
2.6.33-rc3-git3: Reported regressions from 2.6.32
This message contains a list of some regressions from 2.6.32, for which there are no fixes in the mainline I know of. If any of them have been fixed already, please let me know. If you know of any other unresolved regressions from 2.6.32, please let me know either and I'll add them to the list. Also, please let me know if any of the entries below are invalid. Each entry from the list will be sent additionally in an automatic reply to this message with CCs to the people involved in reporting and handling the issue. Listed regressions statistics: Date Total Pending Unresolved 2010-01-10 55 33 21 2009-12-29 36 34 27 Unresolved regressions -- Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=15043 Subject : Display goes off with i915.powersave=1 Submitter : Soeren Sonnenburg so...@debian.org Date: 2010-01-10 20:09 (1 days old) References : http://marc.info/?l=linux-kernelm=126315457519505w=4 Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=15041 Subject : Pagemap endless read loop with LTP Submitter : Andi Kleen a...@firstfloor.org Date: 2010-01-10 2:09 (1 days old) References : http://marc.info/?l=linux-kernelm=126308941423848w=4 Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=15038 Subject : drm/ksm: fbdev blanking regression Submitter : Johan Hovold jhov...@gmail.com Date: 2010-01-06 17:00 (5 days old) First-Bad-Commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=731b5a15a3b1474a41c2ca29b4c32b0f21bc852e References : http://marc.info/?l=linux-kernelm=126279726418748w=4 Handled-By : James Simmons jsimm...@infradead.org Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=15036 Subject : soft lockup in dmesg after suspend/resume Submitter : ykzhao yakui.z...@intel.com Date: 2010-01-04 5:36 (7 days old) References : http://marc.info/?l=linux-kernelm=126258356202722w=4 Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=15035 Subject : BUG: unable to handle kernel paging request in rs600_gart_set_page() Submitter : Xiaotian Feng df...@redhat.com Date: 2010-01-05 19:10 (6 days old) References : http://lkml.org/lkml/2010/1/5/95 Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=15033 Subject : drm: gem_object_free without struct_mutex Submitter : Hugh Dickins hugh.dick...@tiscali.co.uk Date: 2009-12-30 19:45 (12 days old) References : http://marc.info/?l=linux-kernelm=126220236201529w=4 Handled-By : Jesse Barnes jbar...@virtuousgeek.org Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=15032 Subject : Oops in uart_resume_port() on resume Submitter : Zdenek Kabelac zdenek.kabe...@gmail.com Date: 2010-01-04 15:47 (7 days old) First-Bad-Commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=ba15ab0e8de0d4439a91342ad52d55ca9e313f3d References : http://marc.info/?l=linux-kernelm=126262008815689w=4 Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=14976 Subject : No sound on snd_hda_codec_via in 2.6.33-rc2 Submitter : Mark Rosenstand rosenst...@gmail.com Date: 2010-01-02 08:27 (9 days old) Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=14954 Subject : warning from alloc_pages_nodemask on boot -- caused by commit 78f1699659963fff97975df44db6d5dbe7218e55 Submitter : Stephen Hemminger shemmin...@linux-foundation.org Date: 2009-12-29 19:57 (13 days old) First-Bad-Commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=78f1699659963fff97975df44db6d5dbe7218e55 Handled-By : Alex Chiang achi...@hp.com Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=14950 Subject : tbench regression with 2.6.33-rc1 Submitter : Lin Ming ming.m@intel.com Date: 2009-12-25 11:11 (17 days old) References : http://marc.info/?l=linux-kernelm=126174044213172w=4 Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=14949 Subject : drm_vm.c:drm_mmap: possible circular locking dependency detected Submitter : Borislav Petkov petko...@googlemail.com Date: 2009-12-26 9:45 (16 days old) References : http://marc.info/?l=linux-kernelm=126182073616279w=4 Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=14948 Subject : EHCI resume sysfs duplicates Submitter : Borislav Petkov petko...@googlemail.com Date: 2009-12-26 9:36 (16 days old) References : http://marc.info/?l=linux-kernelm=126182020615709w=4 Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=14946 Subject : All kernels after 2.6.32-git10
[Bug #14949] drm_vm.c:drm_mmap: possible circular locking dependency detected
This message has been generated automatically as a part of a report of recent regressions. The following bug entry is on the current list of known regressions from 2.6.32. Please verify if it still should be listed and let me know (either way). Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=14949 Subject : drm_vm.c:drm_mmap: possible circular locking dependency detected Submitter : Borislav Petkov petko...@googlemail.com Date: 2009-12-26 9:45 (16 days old) References : http://marc.info/?l=linux-kernelm=126182073616279w=4 -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
2.6.33-rc3-git3: Reported regressions 2.6.31 - 2.6.32
This message contains a list of some regressions introduced between 2.6.31 and 2.6.32, for which there are no fixes in the mainline I know of. If any of them have been fixed already, please let me know. If you know of any other unresolved regressions introduced between 2.6.31 and 2.6.32, please let me know either and I'll add them to the list. Also, please let me know if any of the entries below are invalid. Each entry from the list will be sent additionally in an automatic reply to this message with CCs to the people involved in reporting and handling the issue. Listed regressions statistics: Date Total Pending Unresolved 2010-01-10 130 44 40 2009-12-29 124 60 57 2009-11-21 86 29 25 2009-11-16 84 46 41 2009-10-26 66 42 37 2009-10-12 48 31 27 2009-10-02 22 15 9 Unresolved regressions -- Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=15042 Subject : socket(PF_INET6 hangs when ipv6 not yet initialized Submitter : Marc Haber mh+linux-ker...@zugschlus.de Date: 2010-01-10 14:28 (1 days old) References : http://marc.info/?l=linux-kernelm=126313553029280w=4 Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=14970 Subject : IBM Trackpoint Device changed - Scrolling doesn't work Submitter : Victor Hooi victorh...@yahoo.com Date: 2010-01-01 21:53 (10 days old) Handled-By : Dmitry Torokhov dmitry.torok...@gmail.com Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=14943 Subject : nfs regression? Submitter : Nikola Ciprich extmaill...@linuxbox.cz Date: 2009-12-28 12:10 (14 days old) References : http://marc.info/?l=linux-kernelm=126200276223524w=4 Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=14939 Subject : drm: random hang with i915 Submitter : Arnd Bergmann a...@arndb.de Date: 2009-12-07 17:30 (35 days old) References : http://marc.info/?l=linux-kernelm=126020704125723w=4 Handled-By : Jesse Barnes jbar...@virtuousgeek.org Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=14933 Subject : OOM killer unexpectedly called Submitter : A. Boulan arnaud.bou...@libertysurf.fr Date: 2009-12-24 23:42 (18 days old) References : http://marc.info/?l=linux-kernelm=126169821317492w=4 Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=14922 Subject : 2.6.32 seemed to have broken nVidia MCP7A sata controller Submitter : Mike Cui cui...@gmail.com Date: 2009-12-19 6:13 (23 days old) References : http://marc.info/?l=linux-idem=126120323407742w=4 Handled-By : Jeff Garzik j...@garzik.org Robert Hancock hancock...@gmail.com Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=14903 Subject : Kernel panic - not syncing: Attempted to kill init! Submitter : Zhiyong Wu zwu.ker...@gmail.com Date: 2009-12-18 4:08 (24 days old) References : http://marc.info/?l=linux-kernelm=126110931124738w=4 Handled-By : Américo Wang xiyou.wangc...@gmail.com Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=14898 Subject : ksoftirqd problem Submitter : Nico segfau...@hotmail.com Date: 2009-12-13 19:05 (29 days old) References : http://marc.info/?l=linux-kernelm=126073114325690w=4 Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=14897 Subject : i915: Commit 0e442c60 causes flickering Submitter : David John david...@xenontk.org Date: 2009-12-09 17:26 (33 days old) First-Bad-Commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=0e442c60dd39ac6924b11a20497734bd2303744c References : http://marc.info/?l=linux-kernelm=126037889600769w=4 Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=14895 Subject : BUG in kernel 2.6.32 when using luks encrypted root and RAID0.. Submitter : r4 m...@centrum.cz Date: 2009-12-03 18:24 (39 days old) References : http://marc.info/?l=linux-kernelm=125986664904751w=4 Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=14894 Subject : pohmelfs: NULL pointer dereference Submitter : Alexander Beregalov a.berega...@gmail.com Date: 2009-12-02 1:11 (40 days old) References : http://marc.info/?l=linux-kernelm=125971633107940w=4 Handled-By : Evgeniy Polyakov z...@ioremap.net Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=14892 Subject : intel, KMS, suspend2ram resume, screen black Submitter : Norbert Preining prein...@logic.at Date: 2009-11-24 4:35 (48 days old) References :
[Bug 23993] OpenGL app crashes randomly with 'drmRadeonCmdBuffer: -12'
http://bugs.freedesktop.org/show_bug.cgi?id=23993 --- Comment #7 from Dennis Nezic denn...@dennisn.dyndns.org 2010-01-10 15:14:16 PST --- With 2.6.33-rc3, the problem still exists but the crash error is slightly more descriptive :s.. drmRadeonCmdBuffer: -12. Kernel failed to parse or rejected command stream. See dmesg for more info. (P.S. If I run the offending program from an xterm, for example, by the way, it also crashes the xterm window and I have to kill it.) -- Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [TTM] general protection fault in ttm_tt_swapout, to_virtual looks screwed up
On Sun, Jan 10, 2010 at 8:10 PM, Thomas Hellstrom tho...@shipmail.org wrote: I've seen something similar with openchrome, but I think I traced that down to the DMA engines causing memory corruption. Corruption outside the memory it was supposed to affect? Shouldn't that lead to massive problems? Also, i don't think a dma engine can affect random memory pages (that would imply crappy memory protection). Note that IIRC kmap_atomic may return page_address(page) for a lowmem page. Any idea what may cause kmap_atomic to behave in this way? I think it's pretty normal for it to return page_address on x86_64, since that doesn't have or need PAE or anything like that. /Thomas Maarten Maathuis wrote: I've been noticing for a while that i've been getting general protection faults in ttm_to_swapout, this time i was printk'ing the virtual addresses. In case it's not obvious, the result of kmap_atomic() is wrong. This is nouveau/linux-2.6 which is somewhere after 2.6.32. I was wondering if anyone has ever seen anything like this? from_virtual 88003088b000 to_virtual 88003100f000 from_virtual 88003088c000 to_virtual 880031018000 from_virtual 88003088d000 to_virtual 880031019000 from_virtual 88003088e000 to_virtual 88003101a000 from_virtual 88003088f000 to_virtual 88003101b000 from_virtual 88003089 to_virtual 880031016000 from_virtual 880030891000 to_virtual 880031017000 from_virtual 880030892000 to_virtual 88003101c000 from_virtual 880030893000 to_virtual 88003101d000 from_virtual 880030894000 to_virtual 88003101e000 from_virtual 880030895000 to_virtual 88003101f000 from_virtual 880030896000 to_virtual 88001c626000 from_virtual 880030897000 to_virtual 88001c627000 from_virtual 880030898000 to_virtual 88001c752000 from_virtual 880030899000 to_virtual 88001c66d000 from_virtual 88003089a000 to_virtual 88001c642000 from_virtual 8800308db000 to_virtual 0005d12492492000 general protection fault: [#1] PREEMPT last sysfs file: /sys/devices/pci:00/:00:08.0/host3/uevent CPU 0 Modules linked in: nouveau snd_ice1724 snd_rawmidi wm8775 tuner ttm drm_kms_helper usbhid snd_ice17xx_ak4xxx snd_ac97_codec ac97_bus snd_ak4xxx_adda snd_ak4114 cx25840 snd_pcm ivtv drm snd_timer snd_page_alloc snd_pt2258 snd_i2c cx2341x agpgart ehci_hcd i2c_algo_bit i2c_nforce2 tveeprom snd soundcore ohci_hcd Pid: 1501, comm: ttm_swap Not tainted 2.6.32-00848-gedc4439-dirty #172 System Product Name RIP: 0010:[a017c3fb] [a017c3fb] ttm_tt_swapout+0x135/0x1db [ttm] RSP: :88003749fce0 EFLAGS: 00010282 RAX: 0040 RBX: 0005d12492492000 RCX: 0400 RDX: RSI: 8800308db000 RDI: 0005d12492492000 RBP: 88003749fd30 R08: 00be8bfa R09: 88003749fb30 R10: 000f R11: 0020 R12: 8800308db000 R13: 880030a7a4e0 R14: fff4 R15: 880037795a00 FS: 7fa003a78700() GS:814d8000() knlGS:f5a256d0 CS: 0010 DS: 0018 ES: 0018 CR0: 8005003b CR2: 7fcac3873f80 CR3: 3ecfd000 CR4: 06f0 DR0: DR1: DR2: DR3: DR6: 0ff0 DR7: 0400 Process ttm_swap (pid: 1501, threadinfo 88003749e000, task 88003d2ae360) Stack: 88003e00b910 88003749ffd8 880037795a00 8800377918b8 0 1f4be800 88001f4be870 88001f4be800 0 88001f4be844 88003edb95d8 88003749fdb0 a017d550 Call Trace: [a017d550] ttm_bo_swapout+0x1df/0x222 [ttm] [a017b38d] ttm_shrink+0x9b/0xc0 [ttm] [a017b3c6] ttm_shrink_work+0x14/0x16 [ttm] [810489c7] worker_thread+0x1b7/0x25e [a017b3b2] ? ttm_shrink_work+0x0/0x16 [ttm] [8104bd8a] ? autoremove_wake_function+0x0/0x38 [81048810] ? worker_thread+0x0/0x25e [8104ba75] kthread+0x7c/0x84 [8100bd6a] child_rip+0xa/0x20 [a01d776e] ? nouveau_mem_init_heap+0x5d/0xfd [nouveau] [8104b9f9] ? kthread+0x0/0x84 [8100bd60] ? child_rip+0x0/0x20 Code: 04 00 00 00 e8 97 f7 ff ff 4c 89 e6 48 89 c2 48 89 c3 48 c7 c7 92 1f 18 a0 31 c0 e8 ca ad 19 e1 48 89 df 4c 89 e6 b9 00 04 00 00 f3 a5 e8 ba f7 ff ff e8 b5 f7 ff ff bf 01 00 00 00 e8 c4 f0 19 RIP [a017c3fb] ttm_tt_swapout+0x135/0x1db [ttm] RSP 88003749fce0 ---[ end trace 8724ec5cfdbfe4ce ]--- note: ttm_swap[1501] exited with preempt_count 3 -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions
[Bug 25733] Latest drm-radeon-testing fails to suspend
http://bugs.freedesktop.org/show_bug.cgi?id=25733 --- Comment #2 from Chistopher Krakowiak krzysztof.krakow...@gmail.com 2010-01-10 16:49:03 PST --- I dont have 32bit userspace, so cannot tell how it works there, but got identical problem with T60p/FireGL V5200(r520) and drm-radeon-testing. s2ram works w/o kms, with kms always fails(w/o xorg too). I made patch for r520 yesterday with manny printk's, but not sure how to catch them. http://carme.pld-linux.org/~evil/radeon/drm-s2ram_r500_printk.patch -- Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
[git pull] drm
Hi Linus, Please pull the 'drm-linus' branch from ssh://master.kernel.org/pub/scm/linux/kernel/git/airlied/drm-2.6.git drm-linus This contains 3 trees: core: two KMS fixes, one for a regression I found with Fedora's plymouth on my r100 laptop with an 8-bpp console, the other for unwanted outputs lighting up on resume. radeon kms: a regression fix since we added host data flushing support some users reported r300s dying under load, this change fixes that, along with better s/r support for gpus with sideport RAM, along with eDP support (needed for new imacs to display anything). Also we sync'ed the whitespace in ObjectID.h with all the other copies to make syncing them with AMD's master copy easier, its not kernel compliant but it is a lot easier to work with for AMD. nouveau: scattering of fixes from the nouveau upstream tree. Dave. drivers/gpu/drm/drm_crtc.c |1 + drivers/gpu/drm/drm_crtc_helper.c | 26 +- drivers/gpu/drm/drm_fb_helper.c|9 +- drivers/gpu/drm/drm_irq.c |5 +- drivers/gpu/drm/nouveau/Kconfig|5 +- drivers/gpu/drm/nouveau/nouveau_bo.c | 243 ++--- drivers/gpu/drm/nouveau/nouveau_channel.c | 47 +-- drivers/gpu/drm/nouveau/nouveau_dma.c | 34 +- drivers/gpu/drm/nouveau/nouveau_dma.h | 10 +- drivers/gpu/drm/nouveau/nouveau_drv.h | 72 ++- drivers/gpu/drm/nouveau/nouveau_fbcon.c| 19 +- drivers/gpu/drm/nouveau/nouveau_fbcon.h|1 + drivers/gpu/drm/nouveau/nouveau_fence.c|2 +- drivers/gpu/drm/nouveau/nouveau_gem.c | 33 +- drivers/gpu/drm/nouveau/nouveau_irq.c |1 + drivers/gpu/drm/nouveau/nouveau_mem.c | 87 +++ drivers/gpu/drm/nouveau/nouveau_object.c |2 +- drivers/gpu/drm/nouveau/nouveau_reg.h | 16 +- drivers/gpu/drm/nouveau/nouveau_state.c| 27 +- drivers/gpu/drm/nouveau/nouveau_ttm.c | 30 +- drivers/gpu/drm/nouveau/nv04_dac.c | 35 +- drivers/gpu/drm/nouveau/nv04_fbcon.c | 41 +- drivers/gpu/drm/nouveau/nv04_fifo.c| 34 ++ drivers/gpu/drm/nouveau/nv04_graph.c | 159 +++--- drivers/gpu/drm/nouveau/nv10_fb.c | 32 +- drivers/gpu/drm/nouveau/nv10_graph.c | 28 +- drivers/gpu/drm/nouveau/nv17_tv.c | 115 - drivers/gpu/drm/nouveau/nv20_graph.c | 61 +-- drivers/gpu/drm/nouveau/nv40_fb.c | 53 ++- drivers/gpu/drm/nouveau/nv40_graph.c | 116 ++--- drivers/gpu/drm/nouveau/nv50_display.c | 17 + drivers/gpu/drm/nouveau/nv50_fbcon.c | 23 +- drivers/gpu/drm/nouveau/nv50_fifo.c|6 +- drivers/gpu/drm/radeon/Makefile|5 + drivers/gpu/drm/radeon/ObjectID.h | 801 +++- drivers/gpu/drm/radeon/atombios_dp.c |6 +- drivers/gpu/drm/radeon/mkregtable.c|4 +- drivers/gpu/drm/radeon/r100.c | 23 +- drivers/gpu/drm/radeon/r300.c | 17 +- drivers/gpu/drm/radeon/r420.c | 41 ++- drivers/gpu/drm/radeon/r520.c |1 + drivers/gpu/drm/radeon/r600.c | 21 +- drivers/gpu/drm/radeon/r600_blit_kms.c |4 +- drivers/gpu/drm/radeon/radeon.h|9 +- drivers/gpu/drm/radeon/radeon_agp.c|6 +- drivers/gpu/drm/radeon/radeon_asic.h | 12 - drivers/gpu/drm/radeon/radeon_atombios.c | 41 ++- drivers/gpu/drm/radeon/radeon_combios.c| 14 + drivers/gpu/drm/radeon/radeon_connectors.c | 23 +- drivers/gpu/drm/radeon/radeon_display.c|7 +- drivers/gpu/drm/radeon/radeon_encoders.c | 14 +- drivers/gpu/drm/radeon/radeon_gem.c|2 - drivers/gpu/drm/radeon/radeon_irq_kms.c| 10 +- drivers/gpu/drm/radeon/radeon_legacy_tv.c | 14 +- drivers/gpu/drm/radeon/radeon_mode.h | 26 - drivers/gpu/drm/radeon/radeon_object.c |5 +- drivers/gpu/drm/radeon/reg_srcs/r420 | 795 +++ drivers/gpu/drm/radeon/reg_srcs/rs600 | 68 +++- drivers/gpu/drm/radeon/reg_srcs/rv515 |6 + drivers/gpu/drm/radeon/rs400.c |2 + drivers/gpu/drm/radeon/rs600.c | 10 +- drivers/gpu/drm/radeon/rs690.c |2 + drivers/gpu/drm/radeon/rv515.c |1 + drivers/gpu/drm/radeon/rv770.c |3 +- include/drm/drm_mode.h |1 + 65 files changed, 2411 insertions(+), 973 deletions(-) create mode 100644 drivers/gpu/drm/radeon/reg_srcs/r420 commit f22d6ddaeb8126623d62c828a4d4a96dfc4cbc5c Merge: 0c9d2c4 40c2298 Author: Dave Airlie airl...@redhat.com Date: Mon Jan 11 14:43:16 2010 +1000 Merge branch 'for-airlied' of /ssd/git/drm-nouveau-next into drm-linus * 'for-airlied' of /ssd/git/drm-nouveau-next: (28 commits) drm/nv04: Fix set_operation software method. drm/nouveau: initialise DMA tracking parameters earlier drm/nouveau: use dma.max rather than pushbuf size
[PATCH RESEND] drm/radeon/kms: Fix crash getting TV info with no BIOS.
From: Michel Dänzer daen...@vmware.com
Signed-off-by: Michel Dänzer daen...@vmware.com
---
Looks like this simple fix got lost last time...
drivers/gpu/drm/radeon/radeon_combios.c |3 +++
1 files changed, 3 insertions(+), 0 deletions(-)
diff --git a/drivers/gpu/drm/radeon/radeon_combios.c
b/drivers/gpu/drm/radeon/radeon_combios.c
index 58f3426..fa91e42 100644
--- a/drivers/gpu/drm/radeon/radeon_combios.c
+++ b/drivers/gpu/drm/radeon/radeon_combios.c
@@ -673,6 +673,9 @@ radeon_combios_get_tv_info(struct radeon_device *rdev)
uint16_t tv_info;
enum radeon_tv_std tv_std = TV_STD_NTSC;
+ if (rdev-bios == NULL)
+ return tv_std;
+
tv_info = combios_get_table_offset(dev, COMBIOS_TV_INFO_TABLE);
if (tv_info) {
if (RBIOS8(tv_info + 6) == 'T') {
--
1.6.5.7
--
This SF.Net email is sponsored by the Verizon Developer Community
Take advantage of Verizon's best-in-class app development support
A streamlined, 14 day to market process makes app distribution fast and easy
Join now and get one step closer to millions of Verizon customers
http://p.sf.net/sfu/verizon-dev2dev
--
___
Dri-devel mailing list
Dri-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dri-devel
