[Bug 55692] [KMS][Cayman] Garbled screen and oops with 6950 with linus git from 20121006 (3.7-rc0)
https://bugs.freedesktop.org/show_bug.cgi?id=55692 --- Comment #39 from Alexandre Demers --- (In reply to comment #36) > (In reply to comment #35) > > I've been playing a bit (booting and restarting with kernel 3.7-rc1) and > > strangely, what I see is very similar to what I was observing in bug 43655. > > It was then merged with bug 42373. At the time, attachment 64759 [details] > > [review] > > [review] was proposed and a similar patch ended up being commited that fixed > > bug 43655 for me (but it never fixed bug 42373 on NI CAICOS). > > > > I'll try the workaround used at the time to see if it is really related to > > bug 43655 (comments 8 and 10) and I'll begin bisecting kernel right after. > > I think what you really want for your caicos is this patch: > http://git.kernel.org/?p=linux/kernel/git/torvalds/linux.git;a=commit; > h=62444b7462a2b98bc78d68736c03a7c4e66ba7e2 You misunderstood me. I'm using a 6950 (not CAICOS) and it was working great with commit http://git.kernel.org/?p=linux/kernel/git/torvalds/linux.git;a=commitdiff;h=81ee8fb6b52ec69eeed37fe7943446af1dccecc5 for my Cayman (but not for CAICOS according to reporter of bug 42373) included in kernel 3.6. What I'm saying is that the symptoms I'm now seeing with 3.7-rc1 are similar to what I was seeing at the time, but it was fixed in 3.6. Now, about the patch you propose, it is already included in kernel 3.7-rc1 according to commit history. Since I'm experiencing bug 55692 with 3.7-rc1, the proposed patch can't be the cure. I'm bisecting right now between kernel 3.6 and 3.7-rc1. If it appears to be a different bug than 55692, I'll open a new one. -- You are receiving this mail because: You are the assignee for the bug. -- next part -- An HTML attachment was scrubbed... URL: <http://lists.freedesktop.org/archives/dri-devel/attachments/20121017/9095963f/attachment-0001.html>
Linux 3.x: Flickering when logging into GNOME Shell or Unity
Am Mittwoch, den 17.10.2012, 16:25 -0400 schrieb Alex Deucher: > On Wed, Oct 17, 2012 at 11:26 AM, Paul Menzel wrote: > > Am Mittwoch, den 17.10.2012, 16:49 +0200 schrieb Paul Menzel: > > > >> setting up an ASUS M2A-VM after some months with > >> > >> [3.178337] [drm] initializing kernel modesetting (RS690 > >> 0x1002:0x791E 0x1043:0x826D). > >> > >> logging in into GNOME Shell (GNOME 3) or for testing with Ubuntu 12.04 > >> and Unity, the image flickers for a second and then works normally. > >> > >> Turning on debugging > >> > >> /sys/module/drm/parameters$ echo "0x06" | sudo tee debug > >> sudo: unable to resolve host granit > >> 0x06 > >> > >> before logging in, the following is logged. Looking at the source code, > >> I do not see that this is supposed to be a problem. But maybe you can > >> figure out more. > >> > >> [ 454.896408] [drm:drm_mode_addfb], [FB:41] > >> [ 454.896427] [drm:radeon_crtc_page_flip], flip-ioctl() cur_fbo = > >> 880072438400, cur_bbo = 880037072400 > > > > trying Linux 3.5 > > > > $ dpkg -l linux-image-3.5* | grep ii | tr -s ' ' | cut -d ' ' -f 2-4 > > linux-image-3.5-trunk-amd64 3.5.5-1~experimental.1 amd64 > > > > the flickering is still there. > > I don't see anything wrong in the log. Does the flicker occur at > regular intervals or just at start up? As far as I see, one second after hitting enter in the graphical login manager (LightDM in this case). > I suspect the flicker may be due to your desktop environment probing > for monitors at startup Hmm. Only a VGA monitor is detected and I do not see that issue on different system where I tested GNOME Shell to reproduce this. I have test Unity too again. Though the probing should be in the logs somehow? But there are not during the time of login. > which causes a flicker if nothing is attached to the analog ports > (VGA, s-video) as that results in a load detection operation to probe > for old monitors without EDIDs or analog TVs. Any hint on how to rule that out? Disable some outputs on the command line or so? Thanks, Paul -- next part -- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: This is a digitally signed message part URL: <http://lists.freedesktop.org/archives/dri-devel/attachments/20121017/a156c930/attachment.pgp>
[Bug 55692] [KMS][Cayman] Garbled screen and oops with 6950 with linus git from 20121006 (3.7-rc0)
https://bugs.freedesktop.org/show_bug.cgi?id=55692 --- Comment #38 from Serkan Hosca --- Using the same linus git kernel with test patch and mesa git, I've reverted gnome to 3.4, kept slim as login manager, logged in to gnome, it worked fine, no errors in dmesg. I stopped slim, installed gdm and started it and logged in without any errors. I disabled slim and enabled gdm instead and rebooted the computer. Gdm login came up, i logged in and it worked fine. -- You are receiving this mail because: You are the assignee for the bug. -- next part -- An HTML attachment was scrubbed... URL: <http://lists.freedesktop.org/archives/dri-devel/attachments/20121017/17da6f10/attachment.html>
[Bug 56038] "r100_ring_test] *ERROR*" messages sometimes on boot with ati radeon 9000 AGP ( r200 driver, dri2 KMS enabled )
https://bugs.freedesktop.org/show_bug.cgi?id=56038 --- Comment #4 from Barto --- (In reply to comment #2) > If I set the "radeon.agpmode" to "-1" I get low video performance and > sometimes the error message ( ring test *error* ), in fact it's not the same error with "radeon.agpmode=-1", "ring test is ok" but there is a different error : 12.013412] [drm:radeon_ib_ring_tests] *ERROR* radeon: failed testing IB on GFX ring (-35). [ 12.013458] [drm:radeon_device_init] *ERROR* ib ring test failed (-35). [ 12.016565] [drm] Panel ID String: 1024x768 [ 12.016571] [drm] Panel Size 1024x768 you can see the attachement for more details ( dmesg output ) -- You are receiving this mail because: You are the assignee for the bug. -- next part -- An HTML attachment was scrubbed... URL: <http://lists.freedesktop.org/archives/dri-devel/attachments/20121017/32c37d3e/attachment.html>
[Bug 55692] [KMS][Cayman] Garbled screen and oops with 6950 with linus git from 20121006 (3.7-rc0)
https://bugs.freedesktop.org/show_bug.cgi?id=55692 --- Comment #37 from Serkan Hosca --- Created attachment 68728 --> https://bugs.freedesktop.org/attachment.cgi?id=68728&action=edit dmesg.3.7-rc1 with testpatch with mesa-git I removed gdm and installed slim as login manager. Also installed cinnamon as a replacement for gnome and it works fine the first round with linus git with the test patch and mesa git. Restarted slim and logged in again and there were some font corruptions, i restarted cinnamon and they were gone. I tried google maps with webgl enabled and it was working fine. After that i edited my .xinitrc to startup gnome, restarted slim and logged in but it failed and got the error window saying oh no something has gone wrong and a log out button. I checked dmesg at that point and saw the ttm gart memory error. i switched back to cinnamon logged in and got the same font corruptions, restarting cinnamon fixed them. -- You are receiving this mail because: You are the assignee for the bug. -- next part -- An HTML attachment was scrubbed... URL: <http://lists.freedesktop.org/archives/dri-devel/attachments/20121017/313be987/attachment.html>
[Bug 56038] "r100_ring_test] *ERROR*" messages sometimes on boot with ati radeon 9000 AGP ( r200 driver, dri2 KMS enabled )
https://bugs.freedesktop.org/show_bug.cgi?id=56038 --- Comment #3 from Barto --- Created attachment 68727 --> https://bugs.freedesktop.org/attachment.cgi?id=68727&action=edit dmesg error with radeon.agpmode=-1 -- You are receiving this mail because: You are the assignee for the bug. -- next part -- An HTML attachment was scrubbed... URL: <http://lists.freedesktop.org/archives/dri-devel/attachments/20121017/c4036477/attachment.html>
[Bug 55692] [KMS][Cayman] Garbled screen and oops with 6950 with linus git from 20121006 (3.7-rc0)
https://bugs.freedesktop.org/show_bug.cgi?id=55692 --- Comment #36 from Alex Deucher --- (In reply to comment #35) > I've been playing a bit (booting and restarting with kernel 3.7-rc1) and > strangely, what I see is very similar to what I was observing in bug 43655. > It was then merged with bug 42373. At the time, attachment 64759 [details] > [review] was proposed and a similar patch ended up being commited that fixed > bug 43655 for me (but it never fixed bug 42373 on NI CAICOS). > > I'll try the workaround used at the time to see if it is really related to > bug 43655 (comments 8 and 10) and I'll begin bisecting kernel right after. I think what you really want for your caicos is this patch: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux.git;a=commit;h=62444b7462a2b98bc78d68736c03a7c4e66ba7e2 -- You are receiving this mail because: You are the assignee for the bug. -- next part -- An HTML attachment was scrubbed... URL: <http://lists.freedesktop.org/archives/dri-devel/attachments/20121017/e084c1bf/attachment.html>
[Bug 55692] [KMS][Cayman] Garbled screen and oops with 6950 with linus git from 20121006 (3.7-rc0)
https://bugs.freedesktop.org/show_bug.cgi?id=55692 --- Comment #35 from Alexandre Demers --- I've been playing a bit (booting and restarting with kernel 3.7-rc1) and strangely, what I see is very similar to what I was observing in bug 43655. It was then merged with bug 42373. At the time, attachment 64759 was proposed and a similar patch ended up being commited that fixed bug 43655 for me (but it never fixed bug 42373 on NI CAICOS). I'll try the workaround used at the time to see if it is really related to bug 43655 (comments 8 and 10) and I'll begin bisecting kernel right after. -- You are receiving this mail because: You are the assignee for the bug. -- next part -- An HTML attachment was scrubbed... URL: <http://lists.freedesktop.org/archives/dri-devel/attachments/20121017/249c471a/attachment-0001.html>
[Bug 56038] "r100_ring_test] *ERROR*" messages sometimes on boot with ati radeon 9000 AGP ( r200 driver, dri2 KMS enabled )
https://bugs.freedesktop.org/show_bug.cgi?id=56038 --- Comment #2 from Barto --- (In reply to comment #1) > Does radeon.agpmode=-1 (or not passing radeon.agpmode on the kernel command > line in the first place) prevent it from happening? > If I set the "radeon.agpmode" to "-1" I get low video performance and sometimes the error message ( ring test *error* ), If I remove the "radeon.agmode" setting I have no problem, the agp setting is set automatically to 4x ( according to the dmesg output ), but as the bug occurs randomly ( 10% of the time ) I don't know if removing the "radeon.agmode" setting can fix the problem > After the cascaded failure shown in the attached dmesg output, there is no > 3D or even 2D hardware acceleration... yes you are right, when I type glxinfo I can see that dri2 is not used when the bug occurs -- You are receiving this mail because: You are the assignee for the bug. -- next part -- An HTML attachment was scrubbed... URL: <http://lists.freedesktop.org/archives/dri-devel/attachments/20121017/934f3864/attachment.html>
[Bug 48941] Error creating '/sys/class/backlight/radeon_bl' in radeon_atom_backlight_init()
https://bugzilla.kernel.org/show_bug.cgi?id=48941 --- Comment #5 from Alex Deucher 2012-10-17 21:24:04 --- Created an attachment (id=83751) --> (https://bugzilla.kernel.org/attachment.cgi?id=83751) give each radeon_bl a unique name This patch should fix the issue, however, you'll have to use the appropriate bl device depending on which gpu is active. -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are watching the assignee of the bug.
[Linaro-mm-sig] [PATCH] dma-buf: Use EXPORT_SYMBOL
> From the fact this patch keeps getting resubmitted despite repeated
> objection I deduce they are in fact of the view it does matter and that
> therefore it is a licensing change and they are scared of the
> consequences of ignoring it.
>
No I think they just want to have to write a pointless hack lie in
their kernel module.
There is no nice way for nvidia developers to say our lawyers don't
think this is a license issues without doing
MODULE_LICENSE("GPL\0 OH NOT WE DIDNT OUR LAWYESR ARE OKAY");
I don't think I'd be going quite into how illegal it is.
The thing is I can't base a useful userspace interface on this, and
since the nvidia driver exists everwhere despite what we'd wish, I'd
rather let the users have some hope of a sane architecture, instead of
nvidia having to replace even more userspace code and kernel code with
their own insane shit.
Dave.
[Linaro-mm-sig] [PATCH] dma-buf: Use EXPORT_SYMBOL
On Wed, Oct 17, 2012 at 8:25 PM, Alan Cox wrote: >> > Please go and discuss estoppel, wilful infringement and re-licensing with >> > your corporate attorneys. If you want to relicense components of the code >> > then please take the matter up with the corporate attorneys of the rights >> > holders concerned. >> >> Alan please stick with the facts. This isn't a relicense of anything. > > In your opinion. Are you a qualified IP attorney - NO. Are you my lawyer > - NO. Does my laywer disagree with you - YES. Okay then we should remove this code from the kernel forthwith, as I showed it was illegally relicensed previously in your lawyers opinion. Dave.
[Linaro-mm-sig] [PATCH] dma-buf: Use EXPORT_SYMBOL
b>> >> Alan please stick with the facts. This isn't a relicense of anything. >> EXPORT_SYMBOL_GPL isn't a license its nothing like a license. Its a >> totally pointless thing, it should be >> EXPORT_SYMBOL_USERS_MIGHT_BE_DERIVED_CONSULT_YOUR_LAWYER, but it >> really should be EXPORT_SYMBOL, and really consult your lawyers >> anyways. >> > > Also we should look at this > http://lists.linaro.org/pipermail/linaro-mm-sig/2011-September/000616.html > > original code posting had no EXPORT_SYMBOL, so the original author's > intents were quite clear. Yeah so a history research shows this didn't change until v3 of the code base, and I don't think any lawyers were consulted about changing the exports then, so I don't see why we should need any now. If we do need some now, then we needed some then thus making the original change of the exports a problem. Now how do I withdraw a Signed-off-by and have dma-buf removed from the kernel? (not I'm just spouting bullshit here which has as much value as Alan's, as I said before unless someone grows a pair and sues someone its all just IANAL and humble opinions.) Dave.
[Linaro-mm-sig] [PATCH] dma-buf: Use EXPORT_SYMBOL
>> Please go and discuss estoppel, wilful infringement and re-licensing with >> your corporate attorneys. If you want to relicense components of the code >> then please take the matter up with the corporate attorneys of the rights >> holders concerned. > > Alan please stick with the facts. This isn't a relicense of anything. > EXPORT_SYMBOL_GPL isn't a license its nothing like a license. Its a > totally pointless thing, it should be > EXPORT_SYMBOL_USERS_MIGHT_BE_DERIVED_CONSULT_YOUR_LAWYER, but it > really should be EXPORT_SYMBOL, and really consult your lawyers > anyways. > Also we should look at this http://lists.linaro.org/pipermail/linaro-mm-sig/2011-September/000616.html original code posting had no EXPORT_SYMBOL, so the original author's intents were quite clear. Dave.
[Bug 48941] Error creating '/sys/class/backlight/radeon_bl' in radeon_atom_backlight_init()
https://bugzilla.kernel.org/show_bug.cgi?id=48941 --- Comment #4 from Alex Deucher 2012-10-17 20:05:42 --- The acpi backlight control should still work. -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are watching the assignee of the bug.
[Linaro-mm-sig] [PATCH] dma-buf: Use EXPORT_SYMBOL
On Wed, Oct 17, 2012 at 7:53 PM, Alan Cox wrote: >> I believe that the developers and maintainers of dma-buf have provided >> the needed signoff, both in person and in this thread. If there are any >> objections from that group, I'm happy to discuss any changes necessary to get >> this merged. > > You need the permission of the owners of all the dependant code that > forms the work. The rules and licence are quite clear, as I think are the > views of several of the rights holders on both the interpretation and > intent of the licensing of their code. > > Please go and discuss estoppel, wilful infringement and re-licensing with > your corporate attorneys. If you want to relicense components of the code > then please take the matter up with the corporate attorneys of the rights > holders concerned. Alan please stick with the facts. This isn't a relicense of anything. EXPORT_SYMBOL_GPL isn't a license its nothing like a license. Its a totally pointless thing, it should be EXPORT_SYMBOL_USERS_MIGHT_BE_DERIVED_CONSULT_YOUR_LAWYER, but it really should be EXPORT_SYMBOL, and really consult your lawyers anyways. Dave.
[Bug 55692] [KMS][Cayman] Garbled screen and oops with 6950 with linus git from 20121006 (3.7-rc0)
https://bugs.freedesktop.org/show_bug.cgi?id=55692 --- Comment #34 from Alexandre Demers --- If Serkan and I are experiencing the same problem as I suspect, I would say this is improbably related to Gnome 3.6 because I'm still using 3.4 (with both kernel 3.6 and 3.7-rc1). We have the same GPU and we are not using plymouth. We are experiencing similar visual problem (can't confirm with a remote connection for now) when moving to kernel 3.7-rcX, but not with 3.6. I'll bisect kernel tonight and when I'm done. I'll keep you updated. -- You are receiving this mail because: You are the assignee for the bug. -- next part -- An HTML attachment was scrubbed... URL: <http://lists.freedesktop.org/archives/dri-devel/attachments/20121017/d95a9e3c/attachment.html>
[Bug 56111] EDID not read, results in flickering monitor
https://bugs.freedesktop.org/show_bug.cgi?id=56111 --- Comment #1 from Darxus --- Created attachment 68742 --> https://bugs.freedesktop.org/attachment.cgi?id=68742&action=edit Debian dmesg output, which does have this problem -- You are receiving this mail because: You are the assignee for the bug. ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 56111] New: EDID not read, results in flickering monitor
https://bugs.freedesktop.org/show_bug.cgi?id=56111 Priority: medium Bug ID: 56111 Assignee: dri-devel@lists.freedesktop.org Summary: EDID not read, results in flickering monitor Severity: normal Classification: Unclassified OS: All Reporter: dar...@chaosreigns.com Hardware: Other Status: NEW Version: unspecified Component: General Product: DRI Created attachment 68741 --> https://bugs.freedesktop.org/attachment.cgi?id=68741&action=edit Ubuntu Oneric dmesg output, not having this problem Debian bug: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=690794 Ubuntu bug, possibly the same, fixed, but I don't know how: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/958439 Installed Debian Wheezy, then installed package linux-image-3.5-trunk-amd64 from Experimental, which I guess is an unmodified mainline kernel: $ uname -a Linux dancer 3.5-trunk-amd64 #1 SMP Debian 3.5.5-1~experimental.1 x86_64 GNU/Linux EDID is not read properly, resulting in (CRT) monitor flickering (looks like 60hz). gnome-control-center says the display is "Unknown". xrandr --verbose does not mention the EDID. I previously had these problems on Ubuntu, reported in the above Ubuntu bug. It persisted when I changed video cards from Nvidia to AMD Radeon. It went away with a kernel upgrade. Not sure what the change was. "xrandr --verbose" output: - xrandr: Failed to get size of gamma for output default Screen 0: minimum 640 x 400, current 1600 x 1200, maximum 1920 x 1440 default connected 1600x1200+0+0 (0x13b) normal (normal) 0mm x 0mm Identifier: 0x137 Timestamp: 40607 Subpixel: no subpixels Clones: CRTC: 0 CRTCs: 0 Transform: 1.00 0.00 0.00 0.00 1.00 0.00 0.00 0.00 1.00 filter: 1920x1440 (0x138)0.0MHz h: width 1920 start0 end0 total 1920 skew0 clock0.0KHz v: height 1440 start0 end0 total 1440 clock0.0Hz 1856x1392 (0x139)0.0MHz h: width 1856 start0 end0 total 1856 skew0 clock0.0KHz v: height 1392 start0 end0 total 1392 clock0.0Hz 1792x1344 (0x13a)0.0MHz h: width 1792 start0 end0 total 1792 skew0 clock0.0KHz v: height 1344 start0 end0 total 1344 clock0.0Hz 1600x1200 (0x13b)0.0MHz *current h: width 1600 start0 end0 total 1600 skew0 clock0.0KHz v: height 1200 start0 end0 total 1200 clock0.0Hz 1280x1024 (0x13c)0.0MHz h: width 1280 start0 end0 total 1280 skew0 clock0.0KHz v: height 1024 start0 end0 total 1024 clock0.0Hz 1152x864 (0x13d)0.0MHz h: width 1152 start0 end0 total 1152 skew0 clock0.0KHz v: height 864 start0 end0 total 864 clock0.0Hz 1024x768 (0x13e)0.0MHz h: width 1024 start0 end0 total 1024 skew0 clock0.0KHz v: height 768 start0 end0 total 768 clock0.0Hz 800x600 (0x13f)0.0MHz h: width 800 start0 end0 total 800 skew0 clock0.0KHz v: height 600 start0 end0 total 600 clock0.0Hz 640x480 (0x140)0.0MHz h: width 640 start0 end0 total 640 skew0 clock0.0KHz v: height 480 start0 end0 total 480 clock0.0Hz 720x400 (0x141)0.0MHz h: width 720 start0 end0 total 720 skew0 clock0.0KHz v: height 400 start0 end0 total 400 clock0.0Hz - "get-edid 2>&1 | parse-edid > get-parse-edid.txt 2>&1" output: - parse-edid: parse-edid version 2.0.0 parse-edid: EDID checksum failed - data is corrupt. Continuing anyway. parse-edid: first bytes don't match EDID version 1 header parse-edid: do not trust output (if any). # EDID version 32 revision 118 Section "Monitor" Identifier "NQ@:6765" VendorName "NQ@" ModelName "NQ@:6765" # DPMS capabilities: Active off:yes Suspend:yes Standby:no Mode"1110x1568" # vfreq 17.559Hz, hfreq 33.766kHz DotClock82.93 HTimings1110 1218 1326 2456 VTimings1568 1600 1626 1923 EndMode Mode"884x888" # vfreq 335.422Hz, hfreq 314.290kHz DotClock287.89 HTimings884 916 1029 916
[Bug 55692] [KMS][Cayman] Garbled screen and oops with 6950 with linus git from 20121006 (3.7-rc0)
https://bugs.freedesktop.org/show_bug.cgi?id=55692 --- Comment #33 from Serkan Hosca --- (In reply to comment #32) > Other explanation might be that the gdm admin queue a bunch of animation in > form of big bo and thus fill up the gart before the first gpu lockup had a > chance to be detected. I'll try lightdm or straight startx from console too -- You are receiving this mail because: You are the assignee for the bug. -- next part -- An HTML attachment was scrubbed... URL: <http://lists.freedesktop.org/archives/dri-devel/attachments/20121017/6a1b4f0d/attachment.html>
[Bug 55692] [KMS][Cayman] Garbled screen and oops with 6950 with linus git from 20121006 (3.7-rc0)
https://bugs.freedesktop.org/show_bug.cgi?id=55692 --- Comment #32 from Jerome Glisse --- Other explanation might be that the gdm admin queue a bunch of animation in form of big bo and thus fill up the gart before the first gpu lockup had a chance to be detected. -- You are receiving this mail because: You are the assignee for the bug. -- next part -- An HTML attachment was scrubbed... URL: <http://lists.freedesktop.org/archives/dri-devel/attachments/20121017/aa415a0a/attachment.html>
Linux 3.x: Flickering when logging into GNOME Shell or Unity
s], [CONNECTOR:16:SVIDEO-1] disconnected [ 259.316036] [drm:drm_mode_getconnector], [CONNECTOR:16:?] [ 259.316039] [drm:drm_helper_probe_single_connector_modes], [CONNECTOR:16:SVIDEO-1] [ 259.404020] [drm:radeon_atom_dac_detect], Bios 0 scratch 2 0005 [ 259.404025] [drm:radeon_atombios_connected_scratch_regs], TV1 disconnected [ 259.404028] [drm:drm_helper_probe_single_connector_modes], [CONNECTOR:16:SVIDEO-1] disconnected [ 259.404064] [drm:drm_mode_getconnector], [CONNECTOR:17:?] [ 259.404068] [drm:drm_helper_probe_single_connector_modes], [CONNECTOR:17:HDMI-A-1] [ 259.406332] [drm:radeon_atombios_connected_scratch_regs], DFP2 disconnected [ 259.406335] [drm:drm_helper_probe_single_connector_modes], [CONNECTOR:17:HDMI-A-1] disconnected [ 259.406339] [drm:drm_mode_getconnector], [CONNECTOR:17:?] [ 259.406342] [drm:drm_helper_probe_single_connector_modes], [CONNECTOR:17:HDMI-A-1] [ 259.408618] [drm:radeon_atombios_connected_scratch_regs], DFP2 disconnected [ 259.408621] [drm:drm_helper_probe_single_connector_modes], [CONNECTOR:17:HDMI-A-1] disconnected [ 259.408639] [drm:drm_mode_getconnector], [CONNECTOR:18:?] [ 259.408643] [drm:drm_helper_probe_single_connector_modes], [CONNECTOR:18:DVI-D-1] [ 259.409648] [drm:radeon_atombios_connected_scratch_regs], DFP3 disconnected [ 259.409651] [drm:drm_helper_probe_single_connector_modes], [CONNECTOR:18:DVI-D-1] disconnected [ 259.409655] [drm:drm_mode_getconnector], [CONNECTOR:18:?] [ 259.409658] [drm:drm_helper_probe_single_connector_modes], [CONNECTOR:18:DVI-D-1] [ 259.410660] [drm:radeon_atombios_connected_scratch_regs], DFP3 disconnected [ 259.410663] [drm:drm_helper_probe_single_connector_modes], [CONNECTOR:18:DVI-D-1] disconnected [ 259.412135] [drm:radeon_encoder_set_active_device], setting active device to 0001 from 0005 0001 for encoder 4 [ 259.412145] [drm:drm_crtc_helper_set_mode], [CRTC:10] [ 259.412159] [drm:radeon_atom_encoder_dpms], encoder dpms 25 to mode 3, devices 0080, active_devices [ 259.412169] [drm:radeon_atom_encoder_dpms], encoder dpms 15 to mode 3, devices 0200, active_devices [ 259.423804] [drm:radeon_compute_pll_avivo], 10799, pll dividers - fb: 181.0 ref: 3, post 8 [ 259.423843] [drm:drm_crtc_helper_set_mode], [ENCODER:12:TV-12] set [MODE:22:1280x1024] [ 259.423846] [drm:radeon_atom_encoder_dpms], encoder dpms 21 to mode 3, devices 0005, active_devices 0001 [ 259.423896] [drm:avivo_crtc_load_lut], 0 [ 259.423908] [drm:radeon_atom_encoder_dpms], encoder dpms 21 to mode 0, devices 0005, active_devices 0001 [ 259.441037] [drm:drm_mode_addfb], [FB:45] [ 259.441091] [drm:avivo_crtc_load_lut], 0 [ 259.441107] [drm:drm_mode_setcrtc], [CRTC:10] [ 259.441113] [drm:drm_mode_setcrtc], [CONNECTOR:15:VGA-1] [ 259.441117] [drm:drm_crtc_helper_set_config], [ 259.441119] [drm:drm_crtc_helper_set_config], [CRTC:10] [FB:45] #connectors=1 (x y) (0 0) [ 259.441141] [drm:drm_crtc_helper_set_config], [CONNECTOR:15:VGA-1] to [CRTC:10] [ 259.441165] [drm:drm_mode_setcrtc], [CRTC:11] [ 259.441168] [drm:drm_crtc_helper_set_config], [ 259.441170] [drm:drm_crtc_helper_set_config], [CRTC:11] [NOFB] [ 259.441175] [drm:radeon_atom_encoder_dpms], encoder dpms 25 to mode 3, devices 0080, active_devices [ 259.441195] [drm:radeon_atom_encoder_dpms], encoder dpms 15 to mode 3, devices 0200, active_devices [ 263.426373] [drm:radeon_atombios_connected_scratch_regs], DFP2 disconnected [ 263.426388] [drm:output_poll_execute], [CONNECTOR:17:HDMI-A-1] status updated from 2 to 2 -- next part -- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: This is a digitally signed message part URL: <http://lists.freedesktop.org/archives/dri-devel/attachments/20121017/3a80897e/attachment-0001.pgp>
[PATCH] drm/radeon: give each backlight a unique id
From: Alex Deucher
In cases where we have multiple radeons with backlight controls.
Should fix:
https://bugzilla.kernel.org/show_bug.cgi?id=48941
Signed-off-by: Alex Deucher
---
drivers/gpu/drm/radeon/atombios_encoders.c |5 -
drivers/gpu/drm/radeon/radeon_legacy_encoders.c |5 -
2 files changed, 8 insertions(+), 2 deletions(-)
diff --git a/drivers/gpu/drm/radeon/atombios_encoders.c
b/drivers/gpu/drm/radeon/atombios_encoders.c
index 806cbcc..a9a059c 100644
--- a/drivers/gpu/drm/radeon/atombios_encoders.c
+++ b/drivers/gpu/drm/radeon/atombios_encoders.c
@@ -184,6 +184,7 @@ void radeon_atom_backlight_init(struct radeon_encoder
*radeon_encoder,
struct radeon_backlight_privdata *pdata;
struct radeon_encoder_atom_dig *dig;
u8 backlight_level;
+ char bl_name[16];
if (!radeon_encoder->enc_priv)
return;
@@ -203,7 +204,9 @@ void radeon_atom_backlight_init(struct radeon_encoder
*radeon_encoder,
memset(&props, 0, sizeof(props));
props.max_brightness = RADEON_MAX_BL_LEVEL;
props.type = BACKLIGHT_RAW;
- bd = backlight_device_register("radeon_bl", &drm_connector->kdev,
+ snprintf(bl_name, sizeof(bl_name),
+"radeon_bl%d", dev->primary->index);
+ bd = backlight_device_register(bl_name, &drm_connector->kdev,
pdata, &radeon_atom_backlight_ops,
&props);
if (IS_ERR(bd)) {
DRM_ERROR("Backlight registration failed\n");
diff --git a/drivers/gpu/drm/radeon/radeon_legacy_encoders.c
b/drivers/gpu/drm/radeon/radeon_legacy_encoders.c
index 8ad9c5f..687b07c 100644
--- a/drivers/gpu/drm/radeon/radeon_legacy_encoders.c
+++ b/drivers/gpu/drm/radeon/radeon_legacy_encoders.c
@@ -370,6 +370,7 @@ void radeon_legacy_backlight_init(struct radeon_encoder
*radeon_encoder,
struct backlight_properties props;
struct radeon_backlight_privdata *pdata;
uint8_t backlight_level;
+ char bl_name[16];
if (!radeon_encoder->enc_priv)
return;
@@ -389,7 +390,9 @@ void radeon_legacy_backlight_init(struct radeon_encoder
*radeon_encoder,
memset(&props, 0, sizeof(props));
props.max_brightness = RADEON_MAX_BL_LEVEL;
props.type = BACKLIGHT_RAW;
- bd = backlight_device_register("radeon_bl", &drm_connector->kdev,
+ snprintf(bl_name, sizeof(bl_name),
+"radeon_bl%d", dev->primary->index);
+ bd = backlight_device_register(bl_name, &drm_connector->kdev,
pdata, &radeon_backlight_ops, &props);
if (IS_ERR(bd)) {
DRM_ERROR("Backlight registration failed\n");
--
1.7.7.5
Linux 3.2.23: Flickering when logging into GNOME Shell or Unity
[FB:39] [ 598.278263] [drm:radeon_crtc_page_flip], flip-ioctl() cur_fbo = 880037072400, cur_bbo = 880072438400 [ 598.362396] [drm:drm_mode_addfb], [FB:41] [ 598.362411] [drm:radeon_crtc_page_flip], flip-ioctl() cur_fbo = 880072438400, cur_bbo = 880037072400 [ 598.445414] [drm:drm_mode_addfb], [FB:39] [ 598.445425] [drm:radeon_crtc_page_flip], flip-ioctl() cur_fbo = 880037072400, cur_bbo = 880072438400 [ 598.56] [drm:drm_mode_addfb], [FB:41] [ 598.66] [drm:radeon_crtc_page_flip], flip-ioctl() cur_fbo = 880072438400, cur_bbo = 880037072400 [ 598.634372] [drm:drm_mode_addfb], [FB:39] [ 598.634382] [drm:radeon_crtc_page_flip], flip-ioctl() cur_fbo = 880037072400, cur_bbo = 880072438400 [ 598.733480] [drm:drm_mode_addfb], [FB:41] [ 598.733505] [drm:radeon_crtc_page_flip], flip-ioctl() cur_fbo = 880072438400, cur_bbo = 880037072400 [ 598.829357] [drm:drm_mode_addfb], [FB:39] [ 598.829376] [drm:radeon_crtc_page_flip], flip-ioctl() cur_fbo = 880037072400, cur_bbo = 880072438400 [ 599.334381] [drm:drm_mode_addfb], [FB:41] [ 599.334395] [drm:radeon_crtc_page_flip], flip-ioctl() cur_fbo = 880072438400, cur_bbo = 880037072400 [ 599.358253] [drm:drm_mode_addfb], [FB:39] [ 599.358263] [drm:radeon_crtc_page_flip], flip-ioctl() cur_fbo = 880037072400, cur_bbo = 880072438400 [ 599.445212] [drm:drm_mode_addfb], [FB:41] [ 599.445233] [drm:radeon_crtc_page_flip], flip-ioctl() cur_fbo = 880072438400, cur_bbo = 880037072400 [ 599.528856] [drm:drm_mode_addfb], [FB:39] [ 599.528872] [drm:radeon_crtc_page_flip], flip-ioctl() cur_fbo = 880037072400, cur_bbo = 880072438400 [ 599.614464] [drm:drm_mode_addfb], [FB:41] [ 599.614476] [drm:radeon_crtc_page_flip], flip-ioctl() cur_fbo = 880072438400, cur_bbo = 880037072400 [ 599.660903] [drm:drm_mode_addfb], [FB:39] [ 599.660908] [drm:radeon_crtc_page_flip], flip-ioctl() cur_fbo = 880037072400, cur_bbo = 880072438400 [ 599.707962] [drm:drm_mode_addfb], [FB:41] [ 599.707969] [drm:radeon_crtc_page_flip], flip-ioctl() cur_fbo = 880072438400, cur_bbo = 880037072400 [ 599.760402] [drm:drm_mode_addfb], [FB:39] [ 599.760421] [drm:radeon_crtc_page_flip], flip-ioctl() cur_fbo = 880037072400, cur_bbo = 880072438400 [ 599.844680] [drm:drm_mode_addfb], [FB:41] [ 599.844692] [drm:radeon_crtc_page_flip], flip-ioctl() cur_fbo = 880072438400, cur_bbo = 880037072400 [ 599.941692] [drm:drm_mode_addfb], [FB:39] [ 599.941709] [drm:radeon_crtc_page_flip], flip-ioctl() cur_fbo = 880037072400, cur_bbo = 880072438400 [ 600.225493] [drm:drm_mode_addfb], [FB:41] [ 600.225508] [drm:radeon_crtc_page_flip], flip-ioctl() cur_fbo = 880072438400, cur_bbo = 880037072400 [ 600.271707] [drm:drm_mode_addfb], [FB:39] [ 600.271720] [drm:radeon_crtc_page_flip], flip-ioctl() cur_fbo = 880037072400, cur_bbo = 880072438400 [ 600.324875] [drm:drm_mode_addfb], [FB:41] [ 600.324881] [drm:radeon_crtc_page_flip], flip-ioctl() cur_fbo = 880072438400, cur_bbo = 880037072400 [ 600.377399] [drm:drm_mode_addfb], [FB:39] [ 600.377409] [drm:radeon_crtc_page_flip], flip-ioctl() cur_fbo = 880037072400, cur_bbo = 880072438400 [ 600.461278] [drm:drm_mode_addfb], [FB:41] [ 600.461288] [drm:radeon_crtc_page_flip], flip-ioctl() cur_fbo = 880072438400, cur_bbo = 880037072400 [ 600.558208] [drm:drm_mode_addfb], [FB:39] [ 600.558230] [drm:radeon_crtc_page_flip], flip-ioctl() cur_fbo = 880037072400, cur_bbo = 880072438400 -- next part -- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: This is a digitally signed message part URL: <http://lists.freedesktop.org/archives/dri-devel/attachments/20121017/0467bff1/attachment-0001.pgp>
[Bug 48941] Error creating '/sys/class/backlight/radeon_bl' in radeon_atom_backlight_init()
https://bugzilla.kernel.org/show_bug.cgi?id=48941 --- Comment #3 from Igor Murzov 2012-10-17 16:44:02 --- Can I help somehow with this and other issue with hybrid systems with a mux? Looks like not much people have such configuration and linux becomes more and more buggy with regard to gpus on my laptop. I can help testing patches or may be bisect some regression for you or even inspect some code :] -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are watching the assignee of the bug.
Linux 3.x: Flickering when logging into GNOME Shell or Unity
On Wed, Oct 17, 2012 at 11:26 AM, Paul Menzel wrote: > Dear Linux folks, > > > > Am Mittwoch, den 17.10.2012, 16:49 +0200 schrieb Paul Menzel: > >> setting up an ASUS M2A-VM after some months with >> >> [3.178337] [drm] initializing kernel modesetting (RS690 >> 0x1002:0x791E 0x1043:0x826D). >> >> logging in into GNOME Shell (GNOME 3) or for testing with Ubuntu 12.04 >> and Unity, the image flickers for a second and then works normally. >> >> Turning on debugging >> >> /sys/module/drm/parameters$ echo "0x06" | sudo tee debug >> sudo: unable to resolve host granit >> 0x06 >> >> before logging in, the following is logged. Looking at the source code, >> I do not see that this is supposed to be a problem. But maybe you can >> figure out more. >> >> [ 454.896408] [drm:drm_mode_addfb], [FB:41] >> [ 454.896427] [drm:radeon_crtc_page_flip], flip-ioctl() cur_fbo = >> 880072438400, cur_bbo = 880037072400 > > trying Linux 3.5 > > $ dpkg -l linux-image-3.5* | grep ii | tr -s ' ' | cut -d ' ' -f 2-4 > linux-image-3.5-trunk-amd64 3.5.5-1~experimental.1 amd64 > > the flickering is still there. I don't see anything wrong in the log. Does the flicker occur at regular intervals or just at start up? I suspect the flicker may be due to your desktop environment probing for monitors at startup which causes a flicker if nothing is attached to the analog ports (VGA, s-video) as that results in a load detection operation to probe for old monitors without EDIDs or analog TVs. Alex
[Bug 55692] [KMS][Cayman] Garbled screen and oops with 6950 with linus git from 20121006 (3.7-rc0)
https://bugs.freedesktop.org/show_bug.cgi?id=55692 --- Comment #31 from Serkan Hosca --- (In reply to comment #29) > I haven't had time to dig it, but just to let you know I'm pretty much in > the same situation as Serkan with a very similar config. I don't think it > has to do with something using too much memory, but more about not > releasing/attributing it correctly in the first place. Otherwise, why would > it work with kernel 3.6 and not 3.7 if only kernel version is in the balance? > > I should have time to look at it tonight. I think the gart memory issue is because of my recent update to gnome 3.6, i didn't see that with gdm 3.4. The machine also boots very fast now after the systemd upgrade, from grub to gdm i would say its about 5~7 seconds. Also when grub starts, the screen stays at console login prompt with the mouse cursor available and it takes about 2~3 seconds till gdm starts doing its fading thing to login prompt. I will try to revert it back and test it again when i get home. -- You are receiving this mail because: You are the assignee for the bug. -- next part -- An HTML attachment was scrubbed... URL: <http://lists.freedesktop.org/archives/dri-devel/attachments/20121017/e7552db4/attachment.html>
[Bug 55692] [KMS][Cayman] Garbled screen and oops with 6950 with linus git from 20121006 (3.7-rc0)
https://bugs.freedesktop.org/show_bug.cgi?id=55692 --- Comment #30 from Jerome Glisse --- Well log for comment #25 shows out of memory. Which should not happen. It looks like it's the framebuffer that try to go into gtt but that doesn't make sense (16M is fb size according to log). -- You are receiving this mail because: You are the assignee for the bug. -- next part -- An HTML attachment was scrubbed... URL: <http://lists.freedesktop.org/archives/dri-devel/attachments/20121017/919c5678/attachment.html>
[Bug 55692] [KMS][Cayman] Garbled screen and oops with 6950 with linus git from 20121006 (3.7-rc0)
https://bugs.freedesktop.org/show_bug.cgi?id=55692 --- Comment #39 from Alexandre Demers --- (In reply to comment #36) > (In reply to comment #35) > > I've been playing a bit (booting and restarting with kernel 3.7-rc1) and > > strangely, what I see is very similar to what I was observing in bug 43655. > > It was then merged with bug 42373. At the time, attachment 64759 [details] > > [review] > > [review] was proposed and a similar patch ended up being commited that fixed > > bug 43655 for me (but it never fixed bug 42373 on NI CAICOS). > > > > I'll try the workaround used at the time to see if it is really related to > > bug 43655 (comments 8 and 10) and I'll begin bisecting kernel right after. > > I think what you really want for your caicos is this patch: > http://git.kernel.org/?p=linux/kernel/git/torvalds/linux.git;a=commit; > h=62444b7462a2b98bc78d68736c03a7c4e66ba7e2 You misunderstood me. I'm using a 6950 (not CAICOS) and it was working great with commit http://git.kernel.org/?p=linux/kernel/git/torvalds/linux.git;a=commitdiff;h=81ee8fb6b52ec69eeed37fe7943446af1dccecc5 for my Cayman (but not for CAICOS according to reporter of bug 42373) included in kernel 3.6. What I'm saying is that the symptoms I'm now seeing with 3.7-rc1 are similar to what I was seeing at the time, but it was fixed in 3.6. Now, about the patch you propose, it is already included in kernel 3.7-rc1 according to commit history. Since I'm experiencing bug 55692 with 3.7-rc1, the proposed patch can't be the cure. I'm bisecting right now between kernel 3.6 and 3.7-rc1. If it appears to be a different bug than 55692, I'll open a new one. -- You are receiving this mail because: You are the assignee for the bug. ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 55692] [KMS][Cayman] Garbled screen and oops with 6950 with linus git from 20121006 (3.7-rc0)
https://bugs.freedesktop.org/show_bug.cgi?id=55692 --- Comment #38 from Serkan Hosca --- Using the same linus git kernel with test patch and mesa git, I've reverted gnome to 3.4, kept slim as login manager, logged in to gnome, it worked fine, no errors in dmesg. I stopped slim, installed gdm and started it and logged in without any errors. I disabled slim and enabled gdm instead and rebooted the computer. Gdm login came up, i logged in and it worked fine. -- You are receiving this mail because: You are the assignee for the bug. ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 55692] [KMS][Cayman] Garbled screen and oops with 6950 with linus git from 20121006 (3.7-rc0)
https://bugs.freedesktop.org/show_bug.cgi?id=55692 --- Comment #29 from Alexandre Demers --- I haven't had time to dig it, but just to let you know I'm pretty much in the same situation as Serkan with a very similar config. I don't think it has to do with something using too much memory, but more about not releasing/attributing it correctly in the first place. Otherwise, why would it work with kernel 3.6 and not 3.7 if only kernel version is in the balance? I should have time to look at it tonight. -- You are receiving this mail because: You are the assignee for the bug. -- next part -- An HTML attachment was scrubbed... URL: <http://lists.freedesktop.org/archives/dri-devel/attachments/20121017/8185ab7e/attachment.html>
[Bug 56038] "r100_ring_test] *ERROR*" messages sometimes on boot with ati radeon 9000 AGP ( r200 driver, dri2 KMS enabled )
https://bugs.freedesktop.org/show_bug.cgi?id=56038 --- Comment #1 from Michel D?nzer --- (In reply to comment #1) > randomly ( it's very rare, 90% of the time I don't have this error message ) > I can see these error messages on boot : Does radeon.agpmode=-1 (or not passing radeon.agpmode on the kernel command line in the first place) prevent it from happening? > but the boot process continues and I see no problem on KDE4.9.2 and 3d games, After the cascaded failure shown in the attached dmesg output, there is no 3D or even 2D hardware acceleration... -- You are receiving this mail because: You are the assignee for the bug. -- next part -- An HTML attachment was scrubbed... URL: <http://lists.freedesktop.org/archives/dri-devel/attachments/20121017/aa73e632/attachment.html>
[Bug 56038] "r100_ring_test] *ERROR*" messages sometimes on boot with ati radeon 9000 AGP ( r200 driver, dri2 KMS enabled )
https://bugs.freedesktop.org/show_bug.cgi?id=56038 --- Comment #4 from Barto --- (In reply to comment #2) > If I set the "radeon.agpmode" to "-1" I get low video performance and > sometimes the error message ( ring test *error* ), in fact it's not the same error with "radeon.agpmode=-1", "ring test is ok" but there is a different error : 12.013412] [drm:radeon_ib_ring_tests] *ERROR* radeon: failed testing IB on GFX ring (-35). [ 12.013458] [drm:radeon_device_init] *ERROR* ib ring test failed (-35). [ 12.016565] [drm] Panel ID String: 1024x768 [ 12.016571] [drm] Panel Size 1024x768 you can see the attachement for more details ( dmesg output ) -- You are receiving this mail because: You are the assignee for the bug. ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 55692] [KMS][Cayman] Garbled screen and oops with 6950 with linus git from 20121006 (3.7-rc0)
https://bugs.freedesktop.org/show_bug.cgi?id=55692 --- Comment #37 from Serkan Hosca --- Created attachment 68728 --> https://bugs.freedesktop.org/attachment.cgi?id=68728&action=edit dmesg.3.7-rc1 with testpatch with mesa-git I removed gdm and installed slim as login manager. Also installed cinnamon as a replacement for gnome and it works fine the first round with linus git with the test patch and mesa git. Restarted slim and logged in again and there were some font corruptions, i restarted cinnamon and they were gone. I tried google maps with webgl enabled and it was working fine. After that i edited my .xinitrc to startup gnome, restarted slim and logged in but it failed and got the error window saying oh no something has gone wrong and a log out button. I checked dmesg at that point and saw the ttm gart memory error. i switched back to cinnamon logged in and got the same font corruptions, restarting cinnamon fixed them. -- You are receiving this mail because: You are the assignee for the bug. ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 56038] "r100_ring_test] *ERROR*" messages sometimes on boot with ati radeon 9000 AGP ( r200 driver, dri2 KMS enabled )
https://bugs.freedesktop.org/show_bug.cgi?id=56038 --- Comment #3 from Barto --- Created attachment 68727 --> https://bugs.freedesktop.org/attachment.cgi?id=68727&action=edit dmesg error with radeon.agpmode=-1 -- You are receiving this mail because: You are the assignee for the bug. ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 55692] [KMS][Cayman] Garbled screen and oops with 6950 with linus git from 20121006 (3.7-rc0)
https://bugs.freedesktop.org/show_bug.cgi?id=55692 --- Comment #36 from Alex Deucher --- (In reply to comment #35) > I've been playing a bit (booting and restarting with kernel 3.7-rc1) and > strangely, what I see is very similar to what I was observing in bug 43655. > It was then merged with bug 42373. At the time, attachment 64759 [details] > [review] was proposed and a similar patch ended up being commited that fixed > bug 43655 for me (but it never fixed bug 42373 on NI CAICOS). > > I'll try the workaround used at the time to see if it is really related to > bug 43655 (comments 8 and 10) and I'll begin bisecting kernel right after. I think what you really want for your caicos is this patch: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux.git;a=commit;h=62444b7462a2b98bc78d68736c03a7c4e66ba7e2 -- You are receiving this mail because: You are the assignee for the bug. ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 55692] [KMS][Cayman] Garbled screen and oops with 6950 with linus git from 20121006 (3.7-rc0)
https://bugs.freedesktop.org/show_bug.cgi?id=55692 --- Comment #35 from Alexandre Demers --- I've been playing a bit (booting and restarting with kernel 3.7-rc1) and strangely, what I see is very similar to what I was observing in bug 43655. It was then merged with bug 42373. At the time, attachment 64759 was proposed and a similar patch ended up being commited that fixed bug 43655 for me (but it never fixed bug 42373 on NI CAICOS). I'll try the workaround used at the time to see if it is really related to bug 43655 (comments 8 and 10) and I'll begin bisecting kernel right after. -- You are receiving this mail because: You are the assignee for the bug. ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 56038] "r100_ring_test] *ERROR*" messages sometimes on boot with ati radeon 9000 AGP ( r200 driver, dri2 KMS enabled )
https://bugs.freedesktop.org/show_bug.cgi?id=56038 --- Comment #2 from Barto --- (In reply to comment #1) > Does radeon.agpmode=-1 (or not passing radeon.agpmode on the kernel command > line in the first place) prevent it from happening? > If I set the "radeon.agpmode" to "-1" I get low video performance and sometimes the error message ( ring test *error* ), If I remove the "radeon.agmode" setting I have no problem, the agp setting is set automatically to 4x ( according to the dmesg output ), but as the bug occurs randomly ( 10% of the time ) I don't know if removing the "radeon.agmode" setting can fix the problem > After the cascaded failure shown in the attached dmesg output, there is no > 3D or even 2D hardware acceleration... yes you are right, when I type glxinfo I can see that dri2 is not used when the bug occurs -- You are receiving this mail because: You are the assignee for the bug. ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 56081] (SUMO2) Black screen on X Launch, corrupted VTs when using KMS
https://bugs.freedesktop.org/show_bug.cgi?id=56081 Tony Thomas changed: What|Removed |Added Attachment #68714|0 |1 is obsolete|| --- Comment #6 from Tony Thomas --- Created attachment 68717 --> https://bugs.freedesktop.org/attachment.cgi?id=68717&action=edit 3.7.0-rc1 dmesg (drm.debug=6) -- You are receiving this mail because: You are the assignee for the bug. -- next part -- An HTML attachment was scrubbed... URL: <http://lists.freedesktop.org/archives/dri-devel/attachments/20121017/cab3eccd/attachment.html>
[Bug 56081] (SUMO2) Black screen on X Launch, corrupted VTs when using KMS
https://bugs.freedesktop.org/show_bug.cgi?id=56081 --- Comment #5 from Tony Thomas --- Created attachment 68714 --> https://bugs.freedesktop.org/attachment.cgi?id=68714&action=edit 3.7.0-rc1 dmesg (no debug) -- You are receiving this mail because: You are the assignee for the bug. -- next part -- An HTML attachment was scrubbed... URL: <http://lists.freedesktop.org/archives/dri-devel/attachments/20121017/c4e9b20d/attachment.html>
[Bug 56081] (SUMO2) Black screen on X Launch, corrupted VTs when using KMS
https://bugs.freedesktop.org/show_bug.cgi?id=56081 Tony Thomas changed: What|Removed |Added Attachment #68683|0 |1 is obsolete|| --- Comment #4 from Tony Thomas --- Created attachment 68713 --> https://bugs.freedesktop.org/attachment.cgi?id=68713&action=edit Ubuntu updated Xorg.0.log -- You are receiving this mail because: You are the assignee for the bug. -- next part -- An HTML attachment was scrubbed... URL: <http://lists.freedesktop.org/archives/dri-devel/attachments/20121017/69651de1/attachment.html>
[Bug 56081] (SUMO2) Black screen on X Launch, corrupted VTs when using KMS
https://bugs.freedesktop.org/show_bug.cgi?id=56081 --- Comment #3 from Tony Thomas --- (In reply to comment #2) > Can your try kernel 3.7? There were some fixes that went in that may help. Still the same. Upgraded xorg on Ubuntu (from xorg-edgers ppa), added 3.7.0-rc1 mainline kernel from Ubuntu kernel team. -- You are receiving this mail because: You are the assignee for the bug. -- next part -- An HTML attachment was scrubbed... URL: <http://lists.freedesktop.org/archives/dri-devel/attachments/20121017/846aadb6/attachment.html>
[PATCH] drm/radeon: give each backlight a unique id
From: Alex Deucher
In cases where we have multiple radeons with backlight controls.
Should fix:
https://bugzilla.kernel.org/show_bug.cgi?id=48941
Signed-off-by: Alex Deucher
---
drivers/gpu/drm/radeon/atombios_encoders.c |5 -
drivers/gpu/drm/radeon/radeon_legacy_encoders.c |5 -
2 files changed, 8 insertions(+), 2 deletions(-)
diff --git a/drivers/gpu/drm/radeon/atombios_encoders.c
b/drivers/gpu/drm/radeon/atombios_encoders.c
index 806cbcc..a9a059c 100644
--- a/drivers/gpu/drm/radeon/atombios_encoders.c
+++ b/drivers/gpu/drm/radeon/atombios_encoders.c
@@ -184,6 +184,7 @@ void radeon_atom_backlight_init(struct radeon_encoder
*radeon_encoder,
struct radeon_backlight_privdata *pdata;
struct radeon_encoder_atom_dig *dig;
u8 backlight_level;
+ char bl_name[16];
if (!radeon_encoder->enc_priv)
return;
@@ -203,7 +204,9 @@ void radeon_atom_backlight_init(struct radeon_encoder
*radeon_encoder,
memset(&props, 0, sizeof(props));
props.max_brightness = RADEON_MAX_BL_LEVEL;
props.type = BACKLIGHT_RAW;
- bd = backlight_device_register("radeon_bl", &drm_connector->kdev,
+ snprintf(bl_name, sizeof(bl_name),
+"radeon_bl%d", dev->primary->index);
+ bd = backlight_device_register(bl_name, &drm_connector->kdev,
pdata, &radeon_atom_backlight_ops,
&props);
if (IS_ERR(bd)) {
DRM_ERROR("Backlight registration failed\n");
diff --git a/drivers/gpu/drm/radeon/radeon_legacy_encoders.c
b/drivers/gpu/drm/radeon/radeon_legacy_encoders.c
index 8ad9c5f..687b07c 100644
--- a/drivers/gpu/drm/radeon/radeon_legacy_encoders.c
+++ b/drivers/gpu/drm/radeon/radeon_legacy_encoders.c
@@ -370,6 +370,7 @@ void radeon_legacy_backlight_init(struct radeon_encoder
*radeon_encoder,
struct backlight_properties props;
struct radeon_backlight_privdata *pdata;
uint8_t backlight_level;
+ char bl_name[16];
if (!radeon_encoder->enc_priv)
return;
@@ -389,7 +390,9 @@ void radeon_legacy_backlight_init(struct radeon_encoder
*radeon_encoder,
memset(&props, 0, sizeof(props));
props.max_brightness = RADEON_MAX_BL_LEVEL;
props.type = BACKLIGHT_RAW;
- bd = backlight_device_register("radeon_bl", &drm_connector->kdev,
+ snprintf(bl_name, sizeof(bl_name),
+"radeon_bl%d", dev->primary->index);
+ bd = backlight_device_register(bl_name, &drm_connector->kdev,
pdata, &radeon_backlight_ops, &props);
if (IS_ERR(bd)) {
DRM_ERROR("Backlight registration failed\n");
--
1.7.7.5
___
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 48941] Error creating '/sys/class/backlight/radeon_bl' in radeon_atom_backlight_init()
https://bugzilla.kernel.org/show_bug.cgi?id=48941 --- Comment #5 from Alex Deucher 2012-10-17 21:24:04 --- Created an attachment (id=83751) --> (https://bugzilla.kernel.org/attachment.cgi?id=83751) give each radeon_bl a unique name This patch should fix the issue, however, you'll have to use the appropriate bl device depending on which gpu is active. -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are watching the assignee of the bug. ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 55692] [KMS][Cayman] Garbled screen and oops with 6950 with linus git from 20121006 (3.7-rc0)
https://bugs.freedesktop.org/show_bug.cgi?id=55692 --- Comment #28 from Serkan Hosca --- (In reply to comment #27) > Well that's interesting, according to the logs you are running out of GART > memory (which is 512MB in size) just 7 seconds after boot, and that is > really odd. > > Could you please tell me what the heck you're doing to run out of memory? Is > there some kind of animated splash screen running or something like that? > > I think that this problem shows up when you're tight on memory AND try to > use VM at the same time. Probably we're missing some return value check or > something like this. > > Anyway, as Alexandre Demers pointed out simply disabling VM should also help. > > In the meantime I will try to test the VM implementation under memory > pressure, maybe that will yield some results. > > Cheers, > Christian. I don't have anything graphical running during boot. I have radeon in mkinitcpio MODULES, no plymouth or anything just console, that sets up the mode then straight to gdm. -- You are receiving this mail because: You are the assignee for the bug. -- next part -- An HTML attachment was scrubbed... URL: <http://lists.freedesktop.org/archives/dri-devel/attachments/20121017/231f9122/attachment.html>
[Bug 55692] [KMS][Cayman] Garbled screen and oops with 6950 with linus git from 20121006 (3.7-rc0)
https://bugs.freedesktop.org/show_bug.cgi?id=55692 --- Comment #27 from Christian K?nig --- Well that's interesting, according to the logs you are running out of GART memory (which is 512MB in size) just 7 seconds after boot, and that is really odd. Could you please tell me what the heck you're doing to run out of memory? Is there some kind of animated splash screen running or something like that? I think that this problem shows up when you're tight on memory AND try to use VM at the same time. Probably we're missing some return value check or something like this. Anyway, as Alexandre Demers pointed out simply disabling VM should also help. In the meantime I will try to test the VM implementation under memory pressure, maybe that will yield some results. Cheers, Christian. -- You are receiving this mail because: You are the assignee for the bug. -- next part -- An HTML attachment was scrubbed... URL: <http://lists.freedesktop.org/archives/dri-devel/attachments/20121017/a82ea15d/attachment.html>
[Bug 56081] (SUMO2) Black screen on X Launch, corrupted VTs when using KMS
https://bugs.freedesktop.org/show_bug.cgi?id=56081 --- Comment #2 from Alex Deucher --- Can your try kernel 3.7? There were some fixes that went in that may help. -- You are receiving this mail because: You are the assignee for the bug. -- next part -- An HTML attachment was scrubbed... URL: <http://lists.freedesktop.org/archives/dri-devel/attachments/20121017/8ad8a539/attachment.html>
[Bug 48941] Error creating '/sys/class/backlight/radeon_bl' in radeon_atom_backlight_init()
https://bugzilla.kernel.org/show_bug.cgi?id=48941 Alex Deucher changed: What|Removed |Added CC||alexdeucher at gmail.com --- Comment #2 from Alex Deucher 2012-10-17 14:01:08 --- You have a hybrid laptop with with a mux to switch between the two GPUs. I suppose ideally we'd only create one bl device and switch control of it when the mux is switched. I'm not sure of the best way to do that off hand at the moment. -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are watching the assignee of the bug.
Re: Linux 3.x: Flickering when logging into GNOME Shell or Unity
Am Mittwoch, den 17.10.2012, 16:25 -0400 schrieb Alex Deucher: > On Wed, Oct 17, 2012 at 11:26 AM, Paul Menzel wrote: > > Am Mittwoch, den 17.10.2012, 16:49 +0200 schrieb Paul Menzel: > > > >> setting up an ASUS M2A-VM after some months with > >> > >> [3.178337] [drm] initializing kernel modesetting (RS690 > >> 0x1002:0x791E 0x1043:0x826D). > >> > >> logging in into GNOME Shell (GNOME 3) or for testing with Ubuntu 12.04 > >> and Unity, the image flickers for a second and then works normally. > >> > >> Turning on debugging > >> > >> /sys/module/drm/parameters$ echo "0x06" | sudo tee debug > >> sudo: unable to resolve host granit > >> 0x06 > >> > >> before logging in, the following is logged. Looking at the source code, > >> I do not see that this is supposed to be a problem. But maybe you can > >> figure out more. > >> > >> [ 454.896408] [drm:drm_mode_addfb], [FB:41] > >> [ 454.896427] [drm:radeon_crtc_page_flip], flip-ioctl() cur_fbo = > >> 880072438400, cur_bbo = 880037072400 > > > > trying Linux 3.5 > > > > $ dpkg -l linux-image-3.5* | grep ii | tr -s ' ' | cut -d ' ' -f 2-4 > > linux-image-3.5-trunk-amd64 3.5.5-1~experimental.1 amd64 > > > > the flickering is still there. > > I don't see anything wrong in the log. Does the flicker occur at > regular intervals or just at start up? As far as I see, one second after hitting enter in the graphical login manager (LightDM in this case). > I suspect the flicker may be due to your desktop environment probing > for monitors at startup Hmm. Only a VGA monitor is detected and I do not see that issue on different system where I tested GNOME Shell to reproduce this. I have test Unity too again. Though the probing should be in the logs somehow? But there are not during the time of login. > which causes a flicker if nothing is attached to the analog ports > (VGA, s-video) as that results in a load detection operation to probe > for old monitors without EDIDs or analog TVs. Any hint on how to rule that out? Disable some outputs on the command line or so? Thanks, Paul signature.asc Description: This is a digitally signed message part ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
Re: Linux 3.x: Flickering when logging into GNOME Shell or Unity
On Wed, Oct 17, 2012 at 11:26 AM, Paul Menzel wrote: > Dear Linux folks, > > > > Am Mittwoch, den 17.10.2012, 16:49 +0200 schrieb Paul Menzel: > >> setting up an ASUS M2A-VM after some months with >> >> [3.178337] [drm] initializing kernel modesetting (RS690 >> 0x1002:0x791E 0x1043:0x826D). >> >> logging in into GNOME Shell (GNOME 3) or for testing with Ubuntu 12.04 >> and Unity, the image flickers for a second and then works normally. >> >> Turning on debugging >> >> /sys/module/drm/parameters$ echo "0x06" | sudo tee debug >> sudo: unable to resolve host granit >> 0x06 >> >> before logging in, the following is logged. Looking at the source code, >> I do not see that this is supposed to be a problem. But maybe you can >> figure out more. >> >> [ 454.896408] [drm:drm_mode_addfb], [FB:41] >> [ 454.896427] [drm:radeon_crtc_page_flip], flip-ioctl() cur_fbo = >> 880072438400, cur_bbo = 880037072400 > > trying Linux 3.5 > > $ dpkg -l linux-image-3.5* | grep ii | tr -s ' ' | cut -d ' ' -f 2-4 > linux-image-3.5-trunk-amd64 3.5.5-1~experimental.1 amd64 > > the flickering is still there. I don't see anything wrong in the log. Does the flicker occur at regular intervals or just at start up? I suspect the flicker may be due to your desktop environment probing for monitors at startup which causes a flicker if nothing is attached to the analog ports (VGA, s-video) as that results in a load detection operation to probe for old monitors without EDIDs or analog TVs. Alex ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 48941] Error creating '/sys/class/backlight/radeon_bl' in radeon_atom_backlight_init()
https://bugzilla.kernel.org/show_bug.cgi?id=48941 --- Comment #4 from Alex Deucher 2012-10-17 20:05:42 --- The acpi backlight control should still work. -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are watching the assignee of the bug. ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
[PATCH 0/9] cleanup: remove legacy connector property functions
Hi Rob, Thanks for the patches. They look good to me, except for the empty commit messages and the odd alignment. For instance, I would have replaced - drm_connector_property_set_value(connector, + drm_object_property_set_value(&connector->base, dpms_property, DRM_MODE_DPMS_ON); with - drm_connector_property_set_value(connector, -dpms_property, -DRM_MODE_DPMS_ON); + drm_object_property_set_value(&connector->base, + dpms_property, + DRM_MODE_DPMS_ON); Feel free to ignore the alignment issue if you wish. Other than that, Reviewed-by: Laurent Pinchart and Acked-by: Laurent Pinchart for the shmob patch. On Thursday 11 October 2012 21:05:53 Rob Clark wrote: > From: Rob Clark > > It was suggested by Laurent Pinchart to clean up the legacy connector > property functions, as they are no longer needed. This patchset > replaces references to and remove the connector property fxns, which > have been superseded with the more general object property fxns: > > + drm_connector_attach_property -> drm_object_attach_property > + drm_connector_property_set_value -> drm_object_property_set_value > + drm_connector_property_get_value -> drm_object_property_get_value > > Rob Clark (9): > drm/i915: drm_connector_property -> drm_object_property > drm/gma500: drm_connector_property -> drm_object_property > drm/nouveau: drm_connector_property -> drm_object_property > drm/radeon: drm_connector_property -> drm_object_property > drm/shmob: drm_connector_property -> drm_object_property > drm/udl: drm_connector_property -> drm_object_property > drm/vmwgfx: drm_connector_property -> drm_object_property > drm/i2c: drm_connector_property -> drm_object_property > drm: remove legacy drm_connector_property fxns > > drivers/gpu/drm/drm_crtc.c | 31 +++-- > drivers/gpu/drm/drm_fb_helper.c |2 +- > drivers/gpu/drm/drm_sysfs.c |6 +-- > drivers/gpu/drm/gma500/cdv_device.c |4 +- > drivers/gpu/drm/gma500/cdv_intel_dp.c|2 +- > drivers/gpu/drm/gma500/cdv_intel_hdmi.c |6 +-- > drivers/gpu/drm/gma500/cdv_intel_lvds.c | 10 ++--- > drivers/gpu/drm/gma500/mdfld_dsi_output.c| 10 ++--- > drivers/gpu/drm/gma500/mdfld_intel_display.c |2 +- > drivers/gpu/drm/gma500/oaktrail_crtc.c |2 +- > drivers/gpu/drm/gma500/oaktrail_lvds.c |8 ++-- > drivers/gpu/drm/gma500/psb_intel_lvds.c | 10 ++--- > drivers/gpu/drm/gma500/psb_intel_sdvo.c | 24 +- > drivers/gpu/drm/i2c/ch7006_drv.c | 20 - > drivers/gpu/drm/i915/intel_display.c |2 +- > drivers/gpu/drm/i915/intel_dp.c |2 +- > drivers/gpu/drm/i915/intel_hdmi.c|2 +- > drivers/gpu/drm/i915/intel_lvds.c|2 +- > drivers/gpu/drm/i915/intel_modes.c |4 +- > drivers/gpu/drm/i915/intel_sdvo.c| 24 +- > drivers/gpu/drm/i915/intel_tv.c | 14 +++--- > drivers/gpu/drm/nouveau/nouveau_connector.c | 22 - > drivers/gpu/drm/nouveau/nv17_tv.c| 16 +++ > drivers/gpu/drm/radeon/radeon_connectors.c | 62 +++ > drivers/gpu/drm/shmobile/shmob_drm_crtc.c|2 +- > drivers/gpu/drm/udl/udl_connector.c |2 +- > drivers/gpu/drm/vmwgfx/vmwgfx_ldu.c |2 +- > drivers/gpu/drm/vmwgfx/vmwgfx_scrn.c |2 +- > include/drm/drm_crtc.h |8 > 29 files changed, 137 insertions(+), 166 deletions(-) -- Regards, Laurent Pinchart
[Bug 55692] [KMS][Cayman] Garbled screen and oops with 6950 with linus git from 20121006 (3.7-rc0)
https://bugs.freedesktop.org/show_bug.cgi?id=55692 --- Comment #34 from Alexandre Demers --- If Serkan and I are experiencing the same problem as I suspect, I would say this is improbably related to Gnome 3.6 because I'm still using 3.4 (with both kernel 3.6 and 3.7-rc1). We have the same GPU and we are not using plymouth. We are experiencing similar visual problem (can't confirm with a remote connection for now) when moving to kernel 3.7-rcX, but not with 3.6. I'll bisect kernel tonight and when I'm done. I'll keep you updated. -- You are receiving this mail because: You are the assignee for the bug. ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
[Linaro-mm-sig] [PATCH] dma-buf: Use EXPORT_SYMBOL
On Wed, 17 Oct 2012 20:22:04 +1000 Dave Airlie wrote: > On Wed, Oct 17, 2012 at 8:25 PM, Alan Cox wrote: > >> > Please go and discuss estoppel, wilful infringement and re-licensing with > >> > your corporate attorneys. If you want to relicense components of the code > >> > then please take the matter up with the corporate attorneys of the rights > >> > holders concerned. > >> > >> Alan please stick with the facts. This isn't a relicense of anything. > > > > In your opinion. Are you a qualified IP attorney - NO. Are you my lawyer > > - NO. Does my laywer disagree with you - YES. > > Okay then we should remove this code from the kernel forthwith, as I > showed it was illegally relicensed previously in your lawyers opinion. That would not be the same question I asked my lawyer. Anyway I refer you to the Developer's Certificate of Origin 1.1. Anything Signed off was submitted under the GPL and so is usable as part of a GPL derived work, but not as part of a non GPL derived work. Thus Nouveau can happily use it for example. Simples. And as I said before if Nvidia believe the _GPL makes no difference and their work is not derivative then it's clearly within their power to just ignore it, at which point *they* take the risk on their own.
[Linaro-mm-sig] [PATCH] dma-buf: Use EXPORT_SYMBOL
> > Please go and discuss estoppel, wilful infringement and re-licensing with > > your corporate attorneys. If you want to relicense components of the code > > then please take the matter up with the corporate attorneys of the rights > > holders concerned. > > Alan please stick with the facts. This isn't a relicense of anything. In your opinion. Are you a qualified IP attorney - NO. Are you my lawyer - NO. Does my laywer disagree with you - YES. > EXPORT_SYMBOL_GPL isn't a license its nothing like a license. Its a > totally pointless thing, In your personal viewpoint. I disagree. I'm a rights holder too. Several rights holders have made it clear the change is not wanted. It's over, done, buried. If you want it can go as far as Linus and then he can get a copy of all the discussion and say that same as he did in the classic video. Should I start submitting all the Intel non-free user space X drivers at this point as there seems to be a dramatic policy change going on here ? Alan
[Bug 55692] [KMS][Cayman] Garbled screen and oops with 6950 with linus git from 20121006 (3.7-rc0)
https://bugs.freedesktop.org/show_bug.cgi?id=55692 --- Comment #33 from Serkan Hosca --- (In reply to comment #32) > Other explanation might be that the gdm admin queue a bunch of animation in > form of big bo and thus fill up the gart before the first gpu lockup had a > chance to be detected. I'll try lightdm or straight startx from console too -- You are receiving this mail because: You are the assignee for the bug. ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 56081] (SUMO2) Black screen on X Launch, corrupted VTs when using KMS
https://bugs.freedesktop.org/show_bug.cgi?id=56081 --- Comment #1 from Tony Thomas --- Created attachment 68684 --> https://bugs.freedesktop.org/attachment.cgi?id=68684&action=edit dmesg, booted drm.debug=6 -- You are receiving this mail because: You are the assignee for the bug. -- next part -- An HTML attachment was scrubbed... URL: <http://lists.freedesktop.org/archives/dri-devel/attachments/20121017/0f935431/attachment.html>
[Bug 56081] New: (SUMO2) Black screen on X Launch, corrupted VTs when using KMS
https://bugs.freedesktop.org/show_bug.cgi?id=56081 Priority: medium Bug ID: 56081 Assignee: dri-devel at lists.freedesktop.org Summary: (SUMO2) Black screen on X Launch, corrupted VTs when using KMS Severity: major Classification: Unclassified OS: Linux (All) Reporter: autonymous at gmail.com Hardware: x86-64 (AMD64) Status: NEW Version: git Component: Drivers/DRI/R600 Product: Mesa Created attachment 68683 --> https://bugs.freedesktop.org/attachment.cgi?id=68683&action=edit Xorg.0.log Using AMD A4-3420M APU, have NOT been able to use the R600 driver on either Suse (12.x, factory), Arch Linux (latest built, or git xorg/mesa/dri build), or Ubuntu (12.04, 12.10b2). ALL various combinations of xorg 1.12/1.13, xorg-video-ati, mesa, and kernel 3.5-3.6 give the same black screen after startup, transition to Xorg corrupts all VT's. KMS for Single user or non-X sessions works fine. Grub boot with "radeon.audio=0" does alleviate some corruption on VT7 (but not enough to be usable). Changing accel options or even disabling accel has no effect. Appears there is something specific to the A4-3420M(6410D, chipID 0x9644, identified by system as a Sumo2) that is affected by this. -- You are receiving this mail because: You are the assignee for the bug. -- next part -- An HTML attachment was scrubbed... URL: <http://lists.freedesktop.org/archives/dri-devel/attachments/20121017/35b7c203/attachment.html>
[Bug 55692] [KMS][Cayman] Garbled screen and oops with 6950 with linus git from 20121006 (3.7-rc0)
https://bugs.freedesktop.org/show_bug.cgi?id=55692 --- Comment #32 from Jerome Glisse --- Other explanation might be that the gdm admin queue a bunch of animation in form of big bo and thus fill up the gart before the first gpu lockup had a chance to be detected. -- You are receiving this mail because: You are the assignee for the bug. ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
[PATCH] dma-buf: Use EXPORT_SYMBOL
> I believe that the developers and maintainers of dma-buf have provided > the needed signoff, both in person and in this thread. If there are any > objections from that group, I'm happy to discuss any changes necessary to get > this merged. You need the permission of the owners of all the dependant code that forms the work. The rules and licence are quite clear, as I think are the views of several of the rights holders on both the interpretation and intent of the licensing of their code. Please go and discuss estoppel, wilful infringement and re-licensing with your corporate attorneys. If you want to relicense components of the code then please take the matter up with the corporate attorneys of the rights holders concerned. Alan
[Bug 48941] Error creating '/sys/class/backlight/radeon_bl' in radeon_atom_backlight_init()
https://bugzilla.kernel.org/show_bug.cgi?id=48941 --- Comment #3 from Igor Murzov 2012-10-17 16:44:02 --- Can I help somehow with this and other issue with hybrid systems with a mux? Looks like not much people have such configuration and linux becomes more and more buggy with regard to gpus on my laptop. I can help testing patches or may be bisect some regression for you or even inspect some code :] -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are watching the assignee of the bug. ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 55692] [KMS][Cayman] Garbled screen and oops with 6950 with linus git from 20121006 (3.7-rc0)
https://bugs.freedesktop.org/show_bug.cgi?id=55692 --- Comment #31 from Serkan Hosca --- (In reply to comment #29) > I haven't had time to dig it, but just to let you know I'm pretty much in > the same situation as Serkan with a very similar config. I don't think it > has to do with something using too much memory, but more about not > releasing/attributing it correctly in the first place. Otherwise, why would > it work with kernel 3.6 and not 3.7 if only kernel version is in the balance? > > I should have time to look at it tonight. I think the gart memory issue is because of my recent update to gnome 3.6, i didn't see that with gdm 3.4. The machine also boots very fast now after the systemd upgrade, from grub to gdm i would say its about 5~7 seconds. Also when grub starts, the screen stays at console login prompt with the mouse cursor available and it takes about 2~3 seconds till gdm starts doing its fading thing to login prompt. I will try to revert it back and test it again when i get home. -- You are receiving this mail because: You are the assignee for the bug. ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 55692] [KMS][Cayman] Garbled screen and oops with 6950 with linus git from 20121006 (3.7-rc0)
https://bugs.freedesktop.org/show_bug.cgi?id=55692 --- Comment #30 from Jerome Glisse --- Well log for comment #25 shows out of memory. Which should not happen. It looks like it's the framebuffer that try to go into gtt but that doesn't make sense (16M is fb size according to log). -- You are receiving this mail because: You are the assignee for the bug. ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 26294] [Regression] Resolution for external TV/monitor Philips 32PFL5404H not set correctly
https://bugs.freedesktop.org/show_bug.cgi?id=26294 --- Comment #26 from Paul Menzel --- (In reply to comment #0) [?] > connecting a Philips 32PFL5404H [1] to the ASUS EeePC 701 4G worked with > version 2.8 and maybe even 2.9.0 of the Intel driver. With 2.9.1 it does not > work anymore and I get a similar picture as in [2] (different monitor). In #intel-gfx on irc.freenode.net ajax suggested, to test it with VESA. Unfortunately I could not test that yet, because I had forgotten to install `xserver-xorg-video-vesa`. But KMS seems to be the culprit indeed. Checking the Debian changelog around the time this issue started to appear [3], KMS was enabled by installing `/etc/modprobe.d/i915-kms.conf` enabling KMS. xserver-xorg-video-intel (2:2.9.1-2) unstable; urgency=low * Upload to unstable. -- Julien Cristau Thu, 07 Jan 2010 20:53:45 + xserver-xorg-video-intel (2:2.9.1-1+exp1) experimental; urgency=low [ Julien Cristau ] * Enable kernel mode setting by default on linux (closes: #555906). [ Brice Goglin ] * Build against xserver 1.7. -- Brice Goglin Wed, 02 Dec 2009 15:50:17 +0100 [?] [3] http://packages.debian.org/changelogs/pool/main/x/xserver-xorg-video-intel/xserver-xorg-video-intel_2.20.5-1/changelog.html#version2:2.9.1-2 -- You are receiving this mail because: You are the assignee for the bug. -- next part -- An HTML attachment was scrubbed... URL: <http://lists.freedesktop.org/archives/dri-devel/attachments/20121017/d2a32c8b/attachment.html>
[Bug 55692] [KMS][Cayman] Garbled screen and oops with 6950 with linus git from 20121006 (3.7-rc0)
https://bugs.freedesktop.org/show_bug.cgi?id=55692 --- Comment #29 from Alexandre Demers --- I haven't had time to dig it, but just to let you know I'm pretty much in the same situation as Serkan with a very similar config. I don't think it has to do with something using too much memory, but more about not releasing/attributing it correctly in the first place. Otherwise, why would it work with kernel 3.6 and not 3.7 if only kernel version is in the balance? I should have time to look at it tonight. -- You are receiving this mail because: You are the assignee for the bug. ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
Re: Linux 3.x: Flickering when logging into GNOME Shell or Unity
Dear Linux folks, Am Mittwoch, den 17.10.2012, 16:49 +0200 schrieb Paul Menzel: > setting up an ASUS M2A-VM after some months with > > [3.178337] [drm] initializing kernel modesetting (RS690 > 0x1002:0x791E 0x1043:0x826D). > > logging in into GNOME Shell (GNOME 3) or for testing with Ubuntu 12.04 > and Unity, the image flickers for a second and then works normally. > > Turning on debugging > > /sys/module/drm/parameters$ echo "0x06" | sudo tee debug > sudo: unable to resolve host granit > 0x06 > > before logging in, the following is logged. Looking at the source code, > I do not see that this is supposed to be a problem. But maybe you can > figure out more. > > [ 454.896408] [drm:drm_mode_addfb], [FB:41] > [ 454.896427] [drm:radeon_crtc_page_flip], flip-ioctl() cur_fbo = > 880072438400, cur_bbo = 880037072400 trying Linux 3.5 $ dpkg -l linux-image-3.5* | grep ii | tr -s ' ' | cut -d ' ' -f 2-4 linux-image-3.5-trunk-amd64 3.5.5-1~experimental.1 amd64 the flickering is still there. Thanks, Paul PS: Here are the drm message from `/var/log/syslog` (with polling enabled). $ grep drm syslog | cut -d ' ' -f 6- [2.658753] calling drm_core_init+0x0/0x1000 [drm] @ 414 [2.658796] [drm] Initialized drm 1.1.0 20060810 [2.658812] initcall drm_core_init+0x0/0x1000 [drm] returned 0 after 35 usecs [2.708907] [drm] radeon kernel modesetting enabled. [2.709340] [drm] initializing kernel modesetting (RS690 0x1002:0x791E 0x1043:0x826D). [2.709365] [drm] register mmio base: 0xFDBF [2.709367] [drm] register mmio size: 65536 [2.711361] [drm] Supports vblank timestamp caching Rev 1 (10.10.2010). [2.711363] [drm] Driver supports precise vblank timestamp query. [2.711377] [drm] radeon: irq initialized. [2.711735] [drm] Detected VRAM RAM=128M, BAR=128M [2.711740] [drm] RAM width 128bits DDR [2.723553] [drm] radeon: 128M of VRAM memory ready [2.723556] [drm] radeon: 512M of GTT memory ready. [2.723580] [drm] GART: num cpu pages 131072, num gpu pages 131072 [2.768652] [drm] radeon: 1 quad pipes, 1 z pipes initialized. [2.776211] [drm] PCIE GART of 512M enabled (table at 0x7468). [2.777651] [drm] Loading RS690/RS740 Microcode [2.836298] [drm] radeon: ring at 0x80001000 [2.836322] [drm] ring test succeeded in 1 usecs [2.836449] [drm] ib test succeeded in 0 usecs [2.836816] [drm] Radeon Display Connectors [2.836818] [drm] Connector 0: [2.836820] [drm] VGA-1 [2.836822] [drm] DDC: 0x7e50 0x7e40 0x7e54 0x7e44 0x7e58 0x7e48 0x7e5c 0x7e4c [2.836824] [drm] Encoders: [2.836825] [drm] CRT1: INTERNAL_KLDSCP_DAC1 [2.836827] [drm] Connector 1: [2.836829] [drm] SVIDEO-1 [2.836830] [drm] Encoders: [2.836831] [drm] TV1: INTERNAL_KLDSCP_DAC1 [2.836832] [drm] Connector 2: [2.836834] [drm] HDMI-A-1 [2.836835] [drm] HPD2 [2.836838] [drm] DDC: 0x7e40 0x7e60 0x7e44 0x7e64 0x7e48 0x7e68 0x7e4c 0x7e6c [2.836839] [drm] Encoders: [2.836840] [drm] DFP2: INTERNAL_DDI [2.836842] [drm] Connector 3: [2.836843] [drm] DVI-D-1 [2.836845] [drm] DDC: 0x7e40 0x7e50 0x7e44 0x7e54 0x7e48 0x7e58 0x7e4c 0x7e5c [2.836847] [drm] Encoders: [2.836848] [drm] DFP3: INTERNAL_LVTM1 [2.968511] [drm] fb mappable at 0xF004 [2.968515] [drm] vram apper at 0xF000 [2.968516] [drm] size 5242880 [2.968518] [drm] fb depth is 24 [2.968519] [drm]pitch is 5120 [2.968866] fbcon: radeondrmfb (fb0) is primary device [3.017489] fb0: radeondrmfb frame buffer device [3.017493] drm: registered panic notifier [3.017507] [drm] Initialized radeon 2.18.0 20080528 for :01:05.0 on minor 0 [ 213.346406] [drm:radeon_atombios_connected_scratch_regs], DFP2 disconnected [ 213.346422] [drm:output_poll_execute], [CONNECTOR:17:HDMI-A-1] status updated from 2 to 2 [ 213.347452] [drm:radeon_atombios_connected_scratch_regs], DFP3 disconnected [ 213.347457] [drm:output_poll_execute], [CONNECTOR:18:DVI-D-1] status updated from 2 to 2 [ 223.362380] [drm:radeon_atombios_connected_scratch_regs], DFP2 disconnected [ 223.362394] [drm:output_poll_execute], [CONNECTOR:17:HDMI-A-1] status updated from 2 to 2 [ 223.363429] [drm:radeon_atombios_connected_scratch_regs], DFP3 disconnected [ 223.363434] [drm:output_poll_execute], [CONNECTOR:18:DVI-D-1] status updated from 2 to 2 [ 233.378399] [drm:radeon_atombios_connected_scratch_regs], DFP2 disconnected [ 233.378414] [drm:output_poll_execute], [CONNECTOR:17:HDMI-A-1] status updated from 2 to 2 [ 233.379447] [drm:radeon_atombios_connected_scratch_regs], DFP3 disconnected [ 233.379452] [drm:output_poll_execute], [CONNECTOR:18:DVI-D-1] status updated from 2 to 2 [ 243.394342] [drm:radeon_atombios_connected_scratch_regs], DFP2 disconnected [ 243.394360] [drm:output_poll_execute]
[Bug 56038] "r100_ring_test] *ERROR*" messages sometimes on boot with ati radeon 9000 AGP ( r200 driver, dri2 KMS enabled )
https://bugs.freedesktop.org/show_bug.cgi?id=56038 --- Comment #1 from Michel Dänzer --- (In reply to comment #1) > randomly ( it's very rare, 90% of the time I don't have this error message ) > I can see these error messages on boot : Does radeon.agpmode=-1 (or not passing radeon.agpmode on the kernel command line in the first place) prevent it from happening? > but the boot process continues and I see no problem on KDE4.9.2 and 3d games, After the cascaded failure shown in the attached dmesg output, there is no 3D or even 2D hardware acceleration... -- You are receiving this mail because: You are the assignee for the bug. ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 56081] (SUMO2) Black screen on X Launch, corrupted VTs when using KMS
https://bugs.freedesktop.org/show_bug.cgi?id=56081 Tony Thomas changed: What|Removed |Added Attachment #68714|0 |1 is obsolete|| --- Comment #6 from Tony Thomas --- Created attachment 68717 --> https://bugs.freedesktop.org/attachment.cgi?id=68717&action=edit 3.7.0-rc1 dmesg (drm.debug=6) -- You are receiving this mail because: You are the assignee for the bug. ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 56081] (SUMO2) Black screen on X Launch, corrupted VTs when using KMS
https://bugs.freedesktop.org/show_bug.cgi?id=56081 --- Comment #5 from Tony Thomas --- Created attachment 68714 --> https://bugs.freedesktop.org/attachment.cgi?id=68714&action=edit 3.7.0-rc1 dmesg (no debug) -- You are receiving this mail because: You are the assignee for the bug. ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
Linux 3.2.23: Flickering when logging into GNOME Shell or Unity
Dear Linux folks, setting up an ASUS M2A-VM after some months with [3.178337] [drm] initializing kernel modesetting (RS690 0x1002:0x791E 0x1043:0x826D). logging in into GNOME Shell (GNOME 3) or for testing with Ubuntu 12.04 and Unity, the image flickers for a second and then works normally. Turning on debugging /sys/module/drm/parameters$ echo "0x06" | sudo tee debug sudo: unable to resolve host granit 0x06 before logging in, the following is logged. Looking at the source code, I do not see that this is supposed to be a problem. But maybe you can figure out more. [ 454.896408] [drm:drm_mode_addfb], [FB:41] [ 454.896427] [drm:radeon_crtc_page_flip], flip-ioctl() cur_fbo = 880072438400, cur_bbo = 880037072400 Thanks, Paul PS: Here is some more information. linux-image-3.2.0-3-amd64 3.2.23-1 xserver-xorg-video-radeon 1:6.14.4-5 $ grep drm syslog | cut -d ' ' -f 6- [3.293377] calling drm_core_init+0x0/0x1000 [drm] @ 458 [3.293415] [drm] Initialized drm 1.1.0 20060810 [3.293430] initcall drm_core_init+0x0/0x1000 [drm] returned 0 after 34 usecs [3.378937] [drm] radeon kernel modesetting enabled. [3.393594] [drm] initializing kernel modesetting (RS690 0x1002:0x791E 0x1043:0x826D). [3.393620] [drm] register mmio base: 0xFDCF [3.393622] [drm] register mmio size: 65536 [3.395571] [drm] Supports vblank timestamp caching Rev 1 (10.10.2010). [3.395573] [drm] Driver supports precise vblank timestamp query. [3.395590] [drm] radeon: irq initialized. [3.396186] [drm] Detected VRAM RAM=128M, BAR=128M [3.396191] [drm] RAM width 128bits DDR [3.410542] [drm] radeon: 128M of VRAM memory ready [3.410545] [drm] radeon: 512M of GTT memory ready. [3.410573] [drm] GART: num cpu pages 131072, num gpu pages 131072 [3.423571] [drm] radeon: 1 quad pipes, 1 z pipes initialized. [3.434449] [drm] PCIE GART of 512M enabled (table at 0x7440). [3.445695] [drm] Loading RS690/RS740 Microcode [3.467505] [drm] radeon: ring at 0x80001000 [3.467525] [drm] ring test succeeded in 1 usecs [3.467677] [drm] radeon: ib pool ready. [3.467751] [drm] ib test succeeded in 0 usecs [3.468125] [drm] Radeon Display Connectors [3.468127] [drm] Connector 0: [3.468129] [drm] VGA [3.468131] [drm] DDC: 0x7e50 0x7e40 0x7e54 0x7e44 0x7e58 0x7e48 0x7e5c 0x7e4c [3.468134] [drm] Encoders: [3.468135] [drm] CRT1: INTERNAL_KLDSCP_DAC1 [3.468137] [drm] Connector 1: [3.468139] [drm] S-video [3.468140] [drm] Encoders: [3.468142] [drm] TV1: INTERNAL_KLDSCP_DAC1 [3.468143] [drm] Connector 2: [3.468145] [drm] HDMI-A [3.468146] [drm] HPD2 [3.468149] [drm] DDC: 0x7e40 0x7e60 0x7e44 0x7e64 0x7e48 0x7e68 0x7e4c 0x7e6c [3.468151] [drm] Encoders: [3.468153] [drm] DFP2: INTERNAL_DDI [3.468154] [drm] Connector 3: [3.468156] [drm] DVI-D [3.468158] [drm] DDC: 0x7e40 0x7e50 0x7e44 0x7e54 0x7e48 0x7e58 0x7e4c 0x7e5c [3.468160] [drm] Encoders: [3.468162] [drm] DFP3: INTERNAL_LVTM1 [3.640470] [drm] fb mappable at 0xF004 [3.640476] [drm] vram apper at 0xF000 [3.640480] [drm] size 5242880 [3.640484] [drm] fb depth is 24 [3.640488] [drm]pitch is 5120 [3.640686] fbcon: radeondrmfb (fb0) is primary device [3.691068] fb0: radeondrmfb frame buffer device [3.691072] drm: registered panic notifier [3.691087] [drm] Initialized radeon 2.12.0 20080528 for :01:05.0 on minor 0 [ 450.145497] [drm:drm_mode_getconnector], [CONNECTOR:15:?] [ 450.145513] [drm:drm_helper_probe_single_connector_modes], [CONNECTOR:15:VGA-1] [ 450.201692] [drm:radeon_atombios_connected_scratch_regs], CRT1 connected [ 450.201789] [drm:drm_helper_probe_single_connector_modes], [CONNECTOR:15:VGA-1] probed modes : [ 450.201797] [drm:drm_mode_debug_printmodeline], Modeline 20:"1280x1024" 60 108000 1280 1328 1440 1688 1024 1025 1028 1066 0x48 0x5 [ 450.201810] [drm:drm_mode_debug_printmodeline], Modeline 30:"1280x1024" 75 135000 1280 1296 1440 1688 1024 1025 1028 1066 0x40 0x5 [ 450.201822] [drm:drm_mode_debug_printmodeline], Modeline 21:"1280x960" 60 108000 1280 1376 1488 1800 960 961 964 1000 0x40 0x5 [ 450.201834] [drm:drm_mode_debug_printmodeline], Modeline 37:"1152x864" 75 108000 1152 1216 1344 1600 864 865 868 900 0x40 0x5 [ 450.201846] [drm:drm_mode_debug_printmodeline], Modeline 31:"1024x768" 75 78800 1024 1040 1136 1312 768 769 772 800 0x40 0x5 [ 450.201857] [drm:drm_mode_debug_printmodeline], Modeline 32:"1024x768" 70 75000 1024 1048 1184 1328 768 771 777 806 0x40 0xa [ 450.201869] [drm:drm_mode_debug_printmodeline], Modeline 33:"1024x768" 60 65000 1024 1048 1184 1344 768 771 777 806 0x40 0xa [ 450.201881] [drm:drm_mode_debug_printmodeline], Modeline 34:"832x624" 75 57284 832 864 928 1152 624 625 628 667 0x40 0xa [ 450.201892] [drm:d
[Bug 56081] (SUMO2) Black screen on X Launch, corrupted VTs when using KMS
https://bugs.freedesktop.org/show_bug.cgi?id=56081 Tony Thomas changed: What|Removed |Added Attachment #68683|0 |1 is obsolete|| --- Comment #4 from Tony Thomas --- Created attachment 68713 --> https://bugs.freedesktop.org/attachment.cgi?id=68713&action=edit Ubuntu updated Xorg.0.log -- You are receiving this mail because: You are the assignee for the bug. ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 56081] (SUMO2) Black screen on X Launch, corrupted VTs when using KMS
https://bugs.freedesktop.org/show_bug.cgi?id=56081 --- Comment #3 from Tony Thomas --- (In reply to comment #2) > Can your try kernel 3.7? There were some fixes that went in that may help. Still the same. Upgraded xorg on Ubuntu (from xorg-edgers ppa), added 3.7.0-rc1 mainline kernel from Ubuntu kernel team. -- You are receiving this mail because: You are the assignee for the bug. ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 55692] [KMS][Cayman] Garbled screen and oops with 6950 with linus git from 20121006 (3.7-rc0)
https://bugs.freedesktop.org/show_bug.cgi?id=55692 --- Comment #28 from Serkan Hosca --- (In reply to comment #27) > Well that's interesting, according to the logs you are running out of GART > memory (which is 512MB in size) just 7 seconds after boot, and that is > really odd. > > Could you please tell me what the heck you're doing to run out of memory? Is > there some kind of animated splash screen running or something like that? > > I think that this problem shows up when you're tight on memory AND try to > use VM at the same time. Probably we're missing some return value check or > something like this. > > Anyway, as Alexandre Demers pointed out simply disabling VM should also help. > > In the meantime I will try to test the VM implementation under memory > pressure, maybe that will yield some results. > > Cheers, > Christian. I don't have anything graphical running during boot. I have radeon in mkinitcpio MODULES, no plymouth or anything just console, that sets up the mode then straight to gdm. -- You are receiving this mail because: You are the assignee for the bug. ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 55692] [KMS][Cayman] Garbled screen and oops with 6950 with linus git from 20121006 (3.7-rc0)
https://bugs.freedesktop.org/show_bug.cgi?id=55692 --- Comment #27 from Christian König --- Well that's interesting, according to the logs you are running out of GART memory (which is 512MB in size) just 7 seconds after boot, and that is really odd. Could you please tell me what the heck you're doing to run out of memory? Is there some kind of animated splash screen running or something like that? I think that this problem shows up when you're tight on memory AND try to use VM at the same time. Probably we're missing some return value check or something like this. Anyway, as Alexandre Demers pointed out simply disabling VM should also help. In the meantime I will try to test the VM implementation under memory pressure, maybe that will yield some results. Cheers, Christian. -- You are receiving this mail because: You are the assignee for the bug. ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 56081] (SUMO2) Black screen on X Launch, corrupted VTs when using KMS
https://bugs.freedesktop.org/show_bug.cgi?id=56081 --- Comment #2 from Alex Deucher --- Can your try kernel 3.7? There were some fixes that went in that may help. -- You are receiving this mail because: You are the assignee for the bug. ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 48941] Error creating '/sys/class/backlight/radeon_bl' in radeon_atom_backlight_init()
https://bugzilla.kernel.org/show_bug.cgi?id=48941 Alex Deucher changed: What|Removed |Added CC||alexdeuc...@gmail.com --- Comment #2 from Alex Deucher 2012-10-17 14:01:08 --- You have a hybrid laptop with with a mux to switch between the two GPUs. I suppose ideally we'd only create one bl device and switch control of it when the mux is switched. I'm not sure of the best way to do that off hand at the moment. -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are watching the assignee of the bug. ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 56081] (SUMO2) Black screen on X Launch, corrupted VTs when using KMS
https://bugs.freedesktop.org/show_bug.cgi?id=56081 --- Comment #1 from Tony Thomas --- Created attachment 68684 --> https://bugs.freedesktop.org/attachment.cgi?id=68684&action=edit dmesg, booted drm.debug=6 -- You are receiving this mail because: You are the assignee for the bug. ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 56081] New: (SUMO2) Black screen on X Launch, corrupted VTs when using KMS
https://bugs.freedesktop.org/show_bug.cgi?id=56081 Priority: medium Bug ID: 56081 Assignee: dri-devel@lists.freedesktop.org Summary: (SUMO2) Black screen on X Launch, corrupted VTs when using KMS Severity: major Classification: Unclassified OS: Linux (All) Reporter: autonym...@gmail.com Hardware: x86-64 (AMD64) Status: NEW Version: git Component: Drivers/DRI/R600 Product: Mesa Created attachment 68683 --> https://bugs.freedesktop.org/attachment.cgi?id=68683&action=edit Xorg.0.log Using AMD A4-3420M APU, have NOT been able to use the R600 driver on either Suse (12.x, factory), Arch Linux (latest built, or git xorg/mesa/dri build), or Ubuntu (12.04, 12.10b2). ALL various combinations of xorg 1.12/1.13, xorg-video-ati, mesa, and kernel 3.5-3.6 give the same black screen after startup, transition to Xorg corrupts all VT's. KMS for Single user or non-X sessions works fine. Grub boot with "radeon.audio=0" does alleviate some corruption on VT7 (but not enough to be usable). Changing accel options or even disabling accel has no effect. Appears there is something specific to the A4-3420M(6410D, chipID 0x9644, identified by system as a Sumo2) that is affected by this. -- You are receiving this mail because: You are the assignee for the bug. ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
Re: [PATCH 0/9] cleanup: remove legacy connector property functions
Hi Rob, Thanks for the patches. They look good to me, except for the empty commit messages and the odd alignment. For instance, I would have replaced - drm_connector_property_set_value(connector, + drm_object_property_set_value(&connector->base, dpms_property, DRM_MODE_DPMS_ON); with - drm_connector_property_set_value(connector, -dpms_property, -DRM_MODE_DPMS_ON); + drm_object_property_set_value(&connector->base, + dpms_property, + DRM_MODE_DPMS_ON); Feel free to ignore the alignment issue if you wish. Other than that, Reviewed-by: Laurent Pinchart and Acked-by: Laurent Pinchart for the shmob patch. On Thursday 11 October 2012 21:05:53 Rob Clark wrote: > From: Rob Clark > > It was suggested by Laurent Pinchart to clean up the legacy connector > property functions, as they are no longer needed. This patchset > replaces references to and remove the connector property fxns, which > have been superseded with the more general object property fxns: > > + drm_connector_attach_property -> drm_object_attach_property > + drm_connector_property_set_value -> drm_object_property_set_value > + drm_connector_property_get_value -> drm_object_property_get_value > > Rob Clark (9): > drm/i915: drm_connector_property -> drm_object_property > drm/gma500: drm_connector_property -> drm_object_property > drm/nouveau: drm_connector_property -> drm_object_property > drm/radeon: drm_connector_property -> drm_object_property > drm/shmob: drm_connector_property -> drm_object_property > drm/udl: drm_connector_property -> drm_object_property > drm/vmwgfx: drm_connector_property -> drm_object_property > drm/i2c: drm_connector_property -> drm_object_property > drm: remove legacy drm_connector_property fxns > > drivers/gpu/drm/drm_crtc.c | 31 +++-- > drivers/gpu/drm/drm_fb_helper.c |2 +- > drivers/gpu/drm/drm_sysfs.c |6 +-- > drivers/gpu/drm/gma500/cdv_device.c |4 +- > drivers/gpu/drm/gma500/cdv_intel_dp.c|2 +- > drivers/gpu/drm/gma500/cdv_intel_hdmi.c |6 +-- > drivers/gpu/drm/gma500/cdv_intel_lvds.c | 10 ++--- > drivers/gpu/drm/gma500/mdfld_dsi_output.c| 10 ++--- > drivers/gpu/drm/gma500/mdfld_intel_display.c |2 +- > drivers/gpu/drm/gma500/oaktrail_crtc.c |2 +- > drivers/gpu/drm/gma500/oaktrail_lvds.c |8 ++-- > drivers/gpu/drm/gma500/psb_intel_lvds.c | 10 ++--- > drivers/gpu/drm/gma500/psb_intel_sdvo.c | 24 +- > drivers/gpu/drm/i2c/ch7006_drv.c | 20 - > drivers/gpu/drm/i915/intel_display.c |2 +- > drivers/gpu/drm/i915/intel_dp.c |2 +- > drivers/gpu/drm/i915/intel_hdmi.c|2 +- > drivers/gpu/drm/i915/intel_lvds.c|2 +- > drivers/gpu/drm/i915/intel_modes.c |4 +- > drivers/gpu/drm/i915/intel_sdvo.c| 24 +- > drivers/gpu/drm/i915/intel_tv.c | 14 +++--- > drivers/gpu/drm/nouveau/nouveau_connector.c | 22 - > drivers/gpu/drm/nouveau/nv17_tv.c| 16 +++ > drivers/gpu/drm/radeon/radeon_connectors.c | 62 +++ > drivers/gpu/drm/shmobile/shmob_drm_crtc.c|2 +- > drivers/gpu/drm/udl/udl_connector.c |2 +- > drivers/gpu/drm/vmwgfx/vmwgfx_ldu.c |2 +- > drivers/gpu/drm/vmwgfx/vmwgfx_scrn.c |2 +- > include/drm/drm_crtc.h |8 > 29 files changed, 137 insertions(+), 166 deletions(-) -- Regards, Laurent Pinchart ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 55692] [KMS][Cayman] Garbled screen and oops with 6950 with linus git from 20121006 (3.7-rc0)
https://bugs.freedesktop.org/show_bug.cgi?id=55692 --- Comment #26 from Alexandre Demers --- (In reply to comment #23) > Created attachment 68623 [details] [review] > Test patch. > > VM is definitely enabled, otherwise you won't got that error in the first > place. > > Ok let's try to narrow down that bug a bit more, please apply the attached > test patch and see what happens. > > If the GPU hang vanished we indeed have a syncing issue, but not the PFP > sync. It is and it is not. What I mean is concerning comment 17 "So i did a git log --graph --oneline --all and started to git checkout between those two commits, starting from 2d2f1fd to de92b7a are bad and with commit "ef557ea winsys/radeon: disable virtual memory on Cayman" it started working." If the variable "RADEON_VA" is not set or doesn't exist, from the point commit "ef557ea" kicks in, VM gets disabled. Before that commit, VM is always enabled; from that point, we must be careful. If we want to test after commit "ef557ea" with VM enabled, "RADEON_VA" MUST be set, otherwise it will be disable and will hide the bug. -- You are receiving this mail because: You are the assignee for the bug. -- next part -- An HTML attachment was scrubbed... URL: <http://lists.freedesktop.org/archives/dri-devel/attachments/20121017/4f6c694c/attachment.html>
Re: [Linaro-mm-sig] [PATCH] dma-buf: Use EXPORT_SYMBOL
> From the fact this patch keeps getting resubmitted despite repeated
> objection I deduce they are in fact of the view it does matter and that
> therefore it is a licensing change and they are scared of the
> consequences of ignoring it.
>
No I think they just want to have to write a pointless hack lie in
their kernel module.
There is no nice way for nvidia developers to say our lawyers don't
think this is a license issues without doing
MODULE_LICENSE("GPL\0 OH NOT WE DIDNT OUR LAWYESR ARE OKAY");
I don't think I'd be going quite into how illegal it is.
The thing is I can't base a useful userspace interface on this, and
since the nvidia driver exists everwhere despite what we'd wish, I'd
rather let the users have some hope of a sane architecture, instead of
nvidia having to replace even more userspace code and kernel code with
their own insane shit.
Dave.
___
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
Re: [Linaro-mm-sig] [PATCH] dma-buf: Use EXPORT_SYMBOL
On Wed, 17 Oct 2012 20:22:04 +1000 Dave Airlie wrote: > On Wed, Oct 17, 2012 at 8:25 PM, Alan Cox wrote: > >> > Please go and discuss estoppel, wilful infringement and re-licensing with > >> > your corporate attorneys. If you want to relicense components of the code > >> > then please take the matter up with the corporate attorneys of the rights > >> > holders concerned. > >> > >> Alan please stick with the facts. This isn't a relicense of anything. > > > > In your opinion. Are you a qualified IP attorney - NO. Are you my lawyer > > - NO. Does my laywer disagree with you - YES. > > Okay then we should remove this code from the kernel forthwith, as I > showed it was illegally relicensed previously in your lawyers opinion. That would not be the same question I asked my lawyer. Anyway I refer you to the Developer's Certificate of Origin 1.1. Anything Signed off was submitted under the GPL and so is usable as part of a GPL derived work, but not as part of a non GPL derived work. Thus Nouveau can happily use it for example. Simples. And as I said before if Nvidia believe the _GPL makes no difference and their work is not derivative then it's clearly within their power to just ignore it, at which point *they* take the risk on their own. >From the fact this patch keeps getting resubmitted despite repeated objection I deduce they are in fact of the view it does matter and that therefore it is a licensing change and they are scared of the consequences of ignoring it. Alan ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
Re: [Linaro-mm-sig] [PATCH] dma-buf: Use EXPORT_SYMBOL
On Wed, Oct 17, 2012 at 8:25 PM, Alan Cox wrote: >> > Please go and discuss estoppel, wilful infringement and re-licensing with >> > your corporate attorneys. If you want to relicense components of the code >> > then please take the matter up with the corporate attorneys of the rights >> > holders concerned. >> >> Alan please stick with the facts. This isn't a relicense of anything. > > In your opinion. Are you a qualified IP attorney - NO. Are you my lawyer > - NO. Does my laywer disagree with you - YES. Okay then we should remove this code from the kernel forthwith, as I showed it was illegally relicensed previously in your lawyers opinion. Dave. ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
Re: [Linaro-mm-sig] [PATCH] dma-buf: Use EXPORT_SYMBOL
> > Please go and discuss estoppel, wilful infringement and re-licensing with > > your corporate attorneys. If you want to relicense components of the code > > then please take the matter up with the corporate attorneys of the rights > > holders concerned. > > Alan please stick with the facts. This isn't a relicense of anything. In your opinion. Are you a qualified IP attorney - NO. Are you my lawyer - NO. Does my laywer disagree with you - YES. > EXPORT_SYMBOL_GPL isn't a license its nothing like a license. Its a > totally pointless thing, In your personal viewpoint. I disagree. I'm a rights holder too. Several rights holders have made it clear the change is not wanted. It's over, done, buried. If you want it can go as far as Linus and then he can get a copy of all the discussion and say that same as he did in the classic video. Should I start submitting all the Intel non-free user space X drivers at this point as there seems to be a dramatic policy change going on here ? Alan ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
Re: [Linaro-mm-sig] [PATCH] dma-buf: Use EXPORT_SYMBOL
b>> >> Alan please stick with the facts. This isn't a relicense of anything. >> EXPORT_SYMBOL_GPL isn't a license its nothing like a license. Its a >> totally pointless thing, it should be >> EXPORT_SYMBOL_USERS_MIGHT_BE_DERIVED_CONSULT_YOUR_LAWYER, but it >> really should be EXPORT_SYMBOL, and really consult your lawyers >> anyways. >> > > Also we should look at this > http://lists.linaro.org/pipermail/linaro-mm-sig/2011-September/000616.html > > original code posting had no EXPORT_SYMBOL, so the original author's > intents were quite clear. Yeah so a history research shows this didn't change until v3 of the code base, and I don't think any lawyers were consulted about changing the exports then, so I don't see why we should need any now. If we do need some now, then we needed some then thus making the original change of the exports a problem. Now how do I withdraw a Signed-off-by and have dma-buf removed from the kernel? (not I'm just spouting bullshit here which has as much value as Alan's, as I said before unless someone grows a pair and sues someone its all just IANAL and humble opinions.) Dave. ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
Re: [Linaro-mm-sig] [PATCH] dma-buf: Use EXPORT_SYMBOL
>> Please go and discuss estoppel, wilful infringement and re-licensing with >> your corporate attorneys. If you want to relicense components of the code >> then please take the matter up with the corporate attorneys of the rights >> holders concerned. > > Alan please stick with the facts. This isn't a relicense of anything. > EXPORT_SYMBOL_GPL isn't a license its nothing like a license. Its a > totally pointless thing, it should be > EXPORT_SYMBOL_USERS_MIGHT_BE_DERIVED_CONSULT_YOUR_LAWYER, but it > really should be EXPORT_SYMBOL, and really consult your lawyers > anyways. > Also we should look at this http://lists.linaro.org/pipermail/linaro-mm-sig/2011-September/000616.html original code posting had no EXPORT_SYMBOL, so the original author's intents were quite clear. Dave. ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
Re: [Linaro-mm-sig] [PATCH] dma-buf: Use EXPORT_SYMBOL
On Wed, Oct 17, 2012 at 7:53 PM, Alan Cox wrote: >> I believe that the developers and maintainers of dma-buf have provided >> the needed signoff, both in person and in this thread. If there are any >> objections from that group, I'm happy to discuss any changes necessary to get >> this merged. > > You need the permission of the owners of all the dependant code that > forms the work. The rules and licence are quite clear, as I think are the > views of several of the rights holders on both the interpretation and > intent of the licensing of their code. > > Please go and discuss estoppel, wilful infringement and re-licensing with > your corporate attorneys. If you want to relicense components of the code > then please take the matter up with the corporate attorneys of the rights > holders concerned. Alan please stick with the facts. This isn't a relicense of anything. EXPORT_SYMBOL_GPL isn't a license its nothing like a license. Its a totally pointless thing, it should be EXPORT_SYMBOL_USERS_MIGHT_BE_DERIVED_CONSULT_YOUR_LAWYER, but it really should be EXPORT_SYMBOL, and really consult your lawyers anyways. Dave. ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
Re: [PATCH] dma-buf: Use EXPORT_SYMBOL
> I believe that the developers and maintainers of dma-buf have provided > the needed signoff, both in person and in this thread. If there are any > objections from that group, I'm happy to discuss any changes necessary to get > this merged. You need the permission of the owners of all the dependant code that forms the work. The rules and licence are quite clear, as I think are the views of several of the rights holders on both the interpretation and intent of the licensing of their code. Please go and discuss estoppel, wilful infringement and re-licensing with your corporate attorneys. If you want to relicense components of the code then please take the matter up with the corporate attorneys of the rights holders concerned. Alan ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 26294] [Regression] Resolution for external TV/monitor Philips 32PFL5404H not set correctly
https://bugs.freedesktop.org/show_bug.cgi?id=26294 --- Comment #26 from Paul Menzel --- (In reply to comment #0) […] > connecting a Philips 32PFL5404H [1] to the ASUS EeePC 701 4G worked with > version 2.8 and maybe even 2.9.0 of the Intel driver. With 2.9.1 it does not > work anymore and I get a similar picture as in [2] (different monitor). In #intel-gfx on irc.freenode.net ajax suggested, to test it with VESA. Unfortunately I could not test that yet, because I had forgotten to install `xserver-xorg-video-vesa`. But KMS seems to be the culprit indeed. Checking the Debian changelog around the time this issue started to appear [3], KMS was enabled by installing `/etc/modprobe.d/i915-kms.conf` enabling KMS. xserver-xorg-video-intel (2:2.9.1-2) unstable; urgency=low * Upload to unstable. -- Julien Cristau Thu, 07 Jan 2010 20:53:45 + xserver-xorg-video-intel (2:2.9.1-1+exp1) experimental; urgency=low [ Julien Cristau ] * Enable kernel mode setting by default on linux (closes: #555906). [ Brice Goglin ] * Build against xserver 1.7. -- Brice Goglin Wed, 02 Dec 2009 15:50:17 +0100 […] [3] http://packages.debian.org/changelogs/pool/main/x/xserver-xorg-video-intel/xserver-xorg-video-intel_2.20.5-1/changelog.html#version2:2.9.1-2 -- You are receiving this mail because: You are the assignee for the bug. ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
[PATCH] drm/omap: Remove cpu_is_omapXXXX usage in DMM
Removed usage of the cpu_is_omap in the DMM driver. This is no
longer necessary as we can key off of the omap_dmm pointer that is
only non-NULL if the device has been probed successfully.
Signed-off-by: Andy Gross
---
drivers/staging/omapdrm/omap_dmm_tiler.c |2 +-
drivers/staging/omapdrm/omap_dmm_tiler.h |7 +--
drivers/staging/omapdrm/omap_gem.c |2 +-
3 files changed, 3 insertions(+), 8 deletions(-)
diff --git a/drivers/staging/omapdrm/omap_dmm_tiler.c
b/drivers/staging/omapdrm/omap_dmm_tiler.c
index e2f1e37..6376e17 100644
--- a/drivers/staging/omapdrm/omap_dmm_tiler.c
+++ b/drivers/staging/omapdrm/omap_dmm_tiler.c
@@ -487,7 +487,7 @@ size_t tiler_vsize(enum tiler_fmt fmt, uint16_t w, uint16_t
h)
return round_up(geom[fmt].cpp * w, PAGE_SIZE) * h;
}
-bool dmm_is_initialized(void)
+bool dmm_is_available(void)
{
return omap_dmm ? true : false;
}
diff --git a/drivers/staging/omapdrm/omap_dmm_tiler.h
b/drivers/staging/omapdrm/omap_dmm_tiler.h
index 7b1052a..8c1fe5c 100644
--- a/drivers/staging/omapdrm/omap_dmm_tiler.h
+++ b/drivers/staging/omapdrm/omap_dmm_tiler.h
@@ -94,7 +94,7 @@ uint32_t tiler_stride(enum tiler_fmt fmt);
size_t tiler_size(enum tiler_fmt fmt, uint16_t w, uint16_t h);
size_t tiler_vsize(enum tiler_fmt fmt, uint16_t w, uint16_t h);
void tiler_align(enum tiler_fmt fmt, uint16_t *w, uint16_t *h);
-bool dmm_is_initialized(void);
+bool dmm_is_available(void);
extern struct platform_driver omap_dmm_driver;
@@ -126,9 +126,4 @@ static inline bool validfmt(enum tiler_fmt fmt)
}
}
-static inline int dmm_is_available(void)
-{
- return cpu_is_omap44xx();
-}
-
#endif
diff --git a/drivers/staging/omapdrm/omap_gem.c
b/drivers/staging/omapdrm/omap_gem.c
index b740adc..33faa32 100644
--- a/drivers/staging/omapdrm/omap_gem.c
+++ b/drivers/staging/omapdrm/omap_gem.c
@@ -1408,7 +1408,7 @@ void omap_gem_init(struct drm_device *dev)
};
int i, j;
- if (!dmm_is_initialized()) {
+ if (!dmm_is_available()) {
/* DMM only supported on OMAP4 and later, so this isn't fatal */
dev_warn(dev->dev, "DMM not available, disable DMM support\n");
return;
--
1.7.5.4
___
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
Re: [PATCH 1/2] uapi: update includes for drm content when no kernel API exists
Luis R. Rodriguez wrote: > >> The include_next trick can work as well but that'd mean synching the UAPI > >> files regularly into compat. I'd much prefer to have code intact when > >> possible when backporting so the option I stuck with then was to patch > >> the code directly and then as part of compat-drivers to always copy > >> that day's linux-next UAPI headers into the current directory for > >> compilation. I see no other driver code using the uapi path explicitly > >> though, is that by design? > > > > As far as I understand that's by design, yes. Kernel code isn't expected to > > reference uapi/ headers directly. > > Did the design consider the case where no respective kernel API header > file would ever exist? I didn't particularly design it such that kernel .c files couldn't access uapi .h files directly. I did, however, design it so that my scripts wouldn't have to touch any .c files where possible, and certainly I didn't want to have to double up all #includes that refer to KAPI/UAPI split headers. Ideally, I'd've used #include_next in the KAPI file to refer to the UAPI file where both exist, but some people have strong objections to that, so I ended up having to do #include instead. I also didn't want to rename the asm/, linux/, etc. prefixes as that would mandate changing pretty much every #include in the kernel. For the case where no respective KAPI file exists, it was considered and it is handled. This is done by adding extra -I flags, for example: -I include -I include/uapi so looking for linux/foo.h, say, will look first for include/linux/foo.h and then for include/uapi/linux/foo.h. David ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 55692] [KMS][Cayman] Garbled screen and oops with 6950 with linus git from 20121006 (3.7-rc0)
https://bugs.freedesktop.org/show_bug.cgi?id=55692 --- Comment #26 from Alexandre Demers --- (In reply to comment #23) > Created attachment 68623 [details] [review] > Test patch. > > VM is definitely enabled, otherwise you won't got that error in the first > place. > > Ok let's try to narrow down that bug a bit more, please apply the attached > test patch and see what happens. > > If the GPU hang vanished we indeed have a syncing issue, but not the PFP > sync. It is and it is not. What I mean is concerning comment 17 "So i did a git log --graph --oneline --all and started to git checkout between those two commits, starting from 2d2f1fd to de92b7a are bad and with commit "ef557ea winsys/radeon: disable virtual memory on Cayman" it started working." If the variable "RADEON_VA" is not set or doesn't exist, from the point commit "ef557ea" kicks in, VM gets disabled. Before that commit, VM is always enabled; from that point, we must be careful. If we want to test after commit "ef557ea" with VM enabled, "RADEON_VA" MUST be set, otherwise it will be disable and will hide the bug. -- You are receiving this mail because: You are the assignee for the bug. ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 48941] Error creating '/sys/class/backlight/radeon_bl' in radeon_atom_backlight_init()
https://bugzilla.kernel.org/show_bug.cgi?id=48941 --- Comment #1 from Igor Murzov 2012-10-17 00:35:56 --- Created an attachment (id=83701) --> (https://bugzilla.kernel.org/attachment.cgi?id=83701) lspci -vvv -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are watching the assignee of the bug.
[Bug 48941] New: Error creating '/sys/class/backlight/radeon_bl' in radeon_atom_backlight_init()
https://bugzilla.kernel.org/show_bug.cgi?id=48941 Summary: Error creating '/sys/class/backlight/radeon_bl' in radeon_atom_backlight_init() Product: Drivers Version: 2.5 Kernel Version: 3.7.0-rc1 Platform: All OS/Version: Linux Tree: Mainline Status: NEW Severity: normal Priority: P1 Component: Video(DRI - non Intel) AssignedTo: drivers_video-dri at kernel-bugs.osdl.org ReportedBy: e-mail at date.by Regression: No Created an attachment (id=83691) --> (https://bugzilla.kernel.org/attachment.cgi?id=83691) dmesg There is an error in my dmesg: sysfs: cannot create duplicate filename '/class/backlight/radeon_bl' and there is no '/sys/class/backlight/radeon_bl' after system boot. -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are watching the assignee of the bug.
[PATCH] drm/omap: Remove cpu_is_omapXXXX usage in DMM
Removed usage of the cpu_is_omap in the DMM driver. This is no
longer necessary as we can key off of the omap_dmm pointer that is
only non-NULL if the device has been probed successfully.
Signed-off-by: Andy Gross
---
drivers/staging/omapdrm/omap_dmm_tiler.c |2 +-
drivers/staging/omapdrm/omap_dmm_tiler.h |7 +--
drivers/staging/omapdrm/omap_gem.c |2 +-
3 files changed, 3 insertions(+), 8 deletions(-)
diff --git a/drivers/staging/omapdrm/omap_dmm_tiler.c
b/drivers/staging/omapdrm/omap_dmm_tiler.c
index e2f1e37..6376e17 100644
--- a/drivers/staging/omapdrm/omap_dmm_tiler.c
+++ b/drivers/staging/omapdrm/omap_dmm_tiler.c
@@ -487,7 +487,7 @@ size_t tiler_vsize(enum tiler_fmt fmt, uint16_t w, uint16_t
h)
return round_up(geom[fmt].cpp * w, PAGE_SIZE) * h;
}
-bool dmm_is_initialized(void)
+bool dmm_is_available(void)
{
return omap_dmm ? true : false;
}
diff --git a/drivers/staging/omapdrm/omap_dmm_tiler.h
b/drivers/staging/omapdrm/omap_dmm_tiler.h
index 7b1052a..8c1fe5c 100644
--- a/drivers/staging/omapdrm/omap_dmm_tiler.h
+++ b/drivers/staging/omapdrm/omap_dmm_tiler.h
@@ -94,7 +94,7 @@ uint32_t tiler_stride(enum tiler_fmt fmt);
size_t tiler_size(enum tiler_fmt fmt, uint16_t w, uint16_t h);
size_t tiler_vsize(enum tiler_fmt fmt, uint16_t w, uint16_t h);
void tiler_align(enum tiler_fmt fmt, uint16_t *w, uint16_t *h);
-bool dmm_is_initialized(void);
+bool dmm_is_available(void);
extern struct platform_driver omap_dmm_driver;
@@ -126,9 +126,4 @@ static inline bool validfmt(enum tiler_fmt fmt)
}
}
-static inline int dmm_is_available(void)
-{
- return cpu_is_omap44xx();
-}
-
#endif
diff --git a/drivers/staging/omapdrm/omap_gem.c
b/drivers/staging/omapdrm/omap_gem.c
index b740adc..33faa32 100644
--- a/drivers/staging/omapdrm/omap_gem.c
+++ b/drivers/staging/omapdrm/omap_gem.c
@@ -1408,7 +1408,7 @@ void omap_gem_init(struct drm_device *dev)
};
int i, j;
- if (!dmm_is_initialized()) {
+ if (!dmm_is_available()) {
/* DMM only supported on OMAP4 and later, so this isn't fatal */
dev_warn(dev->dev, "DMM not available, disable DMM support\n");
return;
--
1.7.5.4
[PATCH 1/2] uapi: update includes for drm content when no kernel API exists
Luis R. Rodriguez wrote: > >> The include_next trick can work as well but that'd mean synching the UAPI > >> files regularly into compat. I'd much prefer to have code intact when > >> possible when backporting so the option I stuck with then was to patch > >> the code directly and then as part of compat-drivers to always copy > >> that day's linux-next UAPI headers into the current directory for > >> compilation. I see no other driver code using the uapi path explicitly > >> though, is that by design? > > > > As far as I understand that's by design, yes. Kernel code isn't expected to > > reference uapi/ headers directly. > > Did the design consider the case where no respective kernel API header > file would ever exist? I didn't particularly design it such that kernel .c files couldn't access uapi .h files directly. I did, however, design it so that my scripts wouldn't have to touch any .c files where possible, and certainly I didn't want to have to double up all #includes that refer to KAPI/UAPI split headers. Ideally, I'd've used #include_next in the KAPI file to refer to the UAPI file where both exist, but some people have strong objections to that, so I ended up having to do #include instead. I also didn't want to rename the asm/, linux/, etc. prefixes as that would mandate changing pretty much every #include in the kernel. For the case where no respective KAPI file exists, it was considered and it is handled. This is done by adding extra -I flags, for example: -I include -I include/uapi so looking for linux/foo.h, say, will look first for include/linux/foo.h and then for include/uapi/linux/foo.h. David
