Bug#766058: mesa-vdpau-drivers: vlc crash with Radeon 3850HD

2014-10-20 Thread Arthur Marsh 



Michel Dänzer wrote, on 21/10/14 12:57:


==13424== Invalid read of size 1
==13424==at 0x1A8789C0: r600_bind_blend_state_internal (in
/usr/lib/x86_64-linux-gnu/vdpau/libvdpau_r600.so.1.0.0)
==13424==by 0x1A6723C0: blitter_restore_fragment_states (in
/usr/lib/x86_64-linux-gnu/vdpau/libvdpau_r600.so.1.0.0)
==13424==by 0x1A675C47: util_blitter_clear_render_target (in
/usr/lib/x86_64-linux-gnu/vdpau/libvdpau_r600.so.1.0.0)
==13424==by 0x1A852985: r600_clear_render_target (in
/usr/lib/x86_64-linux-gnu/vdpau/libvdpau_r600.so.1.0.0)
==13424==by 0x1A69D9A9: vl_compositor_render (in
/usr/lib/x86_64-linux-gnu/vdpau/libvdpau_r600.so.1.0.0)
==13424==by 0x1A629E96: vlVdpPresentationQueueDisplay (in
/usr/lib/x86_64-linux-gnu/vdpau/libvdpau_r600.so.1.0.0)
==13424==by 0x1F2F80A3: Queue (in
/usr/lib/vlc/plugins/vdpau/libvdpau_display_plugin.so)
==13424==by 0x30D0E6DB48: ThreadDisplayPicture (in
/usr/lib/libvlccore.so.8.0.0)
==13424==by 0x30D0E6DEB2: Thread (in /usr/lib/libvlccore.so.8.0.0)
==13424==by 0x30022080A3: start_thread (pthread_create.c:309)
==13424==  Address 0xedfe51d is 61 bytes inside a block of size 64 free'd
==13424==at 0x4A08E90: free (vg_replace_malloc.c:473)
==13424==by 0x1A62C7DD: vlVdpOutputSurfaceRenderBitmapSurface (in
/usr/lib/x86_64-linux-gnu/vdpau/libvdpau_r600.so.1.0.0)
==13424==by 0x1F2F8200: Queue (in
/usr/lib/vlc/plugins/vdpau/libvdpau_display_plugin.so)
==13424==by 0x30D0E6DB48: ThreadDisplayPicture (in
/usr/lib/libvlccore.so.8.0.0)
==13424==by 0x30D0E6DEB2: Thread (in /usr/lib/libvlccore.so.8.0.0)
==13424==by 0x30022080A3: start_thread (pthread_create.c:309)


This looks like a use-after-free bug in the Mesa r600g driver. Can you
report this upstream at
https://bugs.freedesktop.org/enter_bug.cgi?product=Mesa , component
Drivers/Gallium/r600?


Done:

https://bugs.freedesktop.org/show_bug.cgi?id=85267





==13424== Invalid read of size 8
==13424==at 0x1A6A4291: destroy_video_buffer_private (in
/usr/lib/x86_64-linux-gnu/vdpau/libvdpau_r600.so.1.0.0)
==13424==by 0x1A6C0127: vl_video_buffer_destroy (in
/usr/lib/x86_64-linux-gnu/vdpau/libvdpau_r600.so.1.0.0)
==13424==by 0x1A627314: vlVdpVideoSurfaceDestroy (in
/usr/lib/x86_64-linux-gnu/vdpau/libvdpau_r600.so.1.0.0)
==13424==by 0x189B4092: SurfaceDestroy (in
/usr/lib/vlc/plugins/vdpau/libvdpau_avcodec_plugin.so)
==13424==by 0x30D0E8DCF4: picture_Release (in
/usr/lib/libvlccore.so.8.0.0)
==13424==by 0x30D0E6D095: ThreadDisplayPreparePicture (in
/usr/lib/libvlccore.so.8.0.0)
==13424==by 0x30D0E6D12B: ThreadDisplayPicture (in
/usr/lib/libvlccore.so.8.0.0)
==13424==by 0x30D0E6DEB2: Thread (in /usr/lib/libvlccore.so.8.0.0)
==13424==by 0x30022080A3: start_thread (pthread_create.c:309)
==13424==  Address 0x6780940 is 480 bytes inside a block of size
10,760 free'd
==13424==at 0x4A08E90: free (vg_replace_malloc.c:473)
==13424==by 0x1A6A44CA: vl_mpeg12_destroy (in
/usr/lib/x86_64-linux-gnu/vdpau/libvdpau_r600.so.1.0.0)
==13424==by 0x1A628489: vlVdpDecoderDestroy (in
/usr/lib/x86_64-linux-gnu/vdpau/libvdpau_r600.so.1.0.0)
==13424==by 0x189B370D: Close (in
/usr/lib/vlc/plugins/vdpau/libvdpau_avcodec_plugin.so)
==13424==by 0x30D0E9028E: vlc_module_unload (in
/usr/lib/libvlccore.so.8.0.0)
==13424==by 0x1715EE48: vlc_va_Delete (in
/usr/lib/vlc/plugins/codec/libavcodec_plugin.so)
==13424==by 0x1715AA59: ffmpeg_GetFormat (in
/usr/lib/vlc/plugins/codec/libavcodec_plugin.so)
==13424==by 0x306F7FD5E0: ff_get_format (in
/usr/lib/x86_64-linux-gnu/libavcodec.so.56.1.0)
==13424==by 0x306F6DDBC8: decode_chunks (in
/usr/lib/x86_64-linux-gnu/libavcodec.so.56.1.0)
==13424==by 0x306F6DF8C8: mpeg_decode_frame (in
/usr/lib/x86_64-linux-gnu/libavcodec.so.56.1.0)
==13424==by 0x306F7FBE1A: avcodec_decode_video2 (in
/usr/lib/x86_64-linux-gnu/libavcodec.so.56.1.0)
==13424==by 0x1715C18C: DecodeVideo (in
/usr/lib/vlc/plugins/codec/libavcodec_plugin.so)


Looks like VLC destroys the VDPAU surface after the VDPAU decoder, and
the Gallium VDPAU state tracker chokes on that. Can you report this
upstream at https://bugs.freedesktop.org/enter_bug.cgi?product=Mesa ,
component "Mesa core"?




Done,

https://bugs.freedesktop.org/show_bug.cgi?id=85268

Regards,

Arthur.


--
To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/5445cc8d.5050...@internode.on.net

Bug#766058: mesa-vdpau-drivers: vlc crash with Radeon 3850HD

2014-10-20 Thread Michel Dänzer 

On 20.10.2014 22:44, Arthur Marsh wrote:


==13424== Invalid write of size 1
==13424==at 0x315BA045B7: BOSA_ST_InitComponentLoader (in 
/usr/lib/libomxil-bellagio.so.0.0.0)
==13424==by 0x315BA055A7: OMX_Init (in /usr/lib/libomxil-bellagio.so.0.0.0)
==13424==by 0x16D4BADB: InitOmxCore (in 
/usr/lib/vlc/plugins/codec/libomxil_plugin.so)
==13424==by 0x16D4A99C: OpenGeneric (in 
/usr/lib/vlc/plugins/codec/libomxil_plugin.so)
==13424==by 0x16D4B6DF: OpenDecoder (in 
/usr/lib/vlc/plugins/codec/libomxil_plugin.so)
==13424==by 0x30D0E8F7E4: module_load (in /usr/lib/libvlccore.so.8.0.0)
==13424==by 0x30D0E8FD9D: vlc_module_load (in /usr/lib/libvlccore.so.8.0.0)
==13424==by 0x30D0E3F865: CreateDecoder (in /usr/lib/libvlccore.so.8.0.0)
==13424==by 0x30D0E42464: input_DecoderNew (in /usr/lib/libvlccore.so.8.0.0)
==13424==by 0x30D0E45595: EsCreateDecoder (in /usr/lib/libvlccore.so.8.0.0)
==13424==by 0x30D0E4641A: EsSelect (in /usr/lib/libvlccore.so.8.0.0)
==13424==by 0x30D0E469E2: EsOutSelect (in /usr/lib/libvlccore.so.8.0.0)
==13424==  Address 0x54331e0 is 0 bytes after a block of size 2,048 alloc'd
==13424==at 0x4A07C20: malloc (vg_replace_malloc.c:296)
==13424==by 0x315BA0452E: BOSA_ST_InitComponentLoader (in 
/usr/lib/libomxil-bellagio.so.0.0.0)
==13424==by 0x315BA055A7: OMX_Init (in /usr/lib/libomxil-bellagio.so.0.0.0)
==13424==by 0x16D4BADB: InitOmxCore (in 
/usr/lib/vlc/plugins/codec/libomxil_plugin.so)
==13424==by 0x16D4A99C: OpenGeneric (in 
/usr/lib/vlc/plugins/codec/libomxil_plugin.so)
==13424==by 0x16D4B6DF: OpenDecoder (in 
/usr/lib/vlc/plugins/codec/libomxil_plugin.so)
==13424==by 0x30D0E8F7E4: module_load (in /usr/lib/libvlccore.so.8.0.0)
==13424==by 0x30D0E8FD9D: vlc_module_load (in /usr/lib/libvlccore.so.8.0.0)
==13424==by 0x30D0E3F865: CreateDecoder (in /usr/lib/libvlccore.so.8.0.0)
==13424==by 0x30D0E42464: input_DecoderNew (in /usr/lib/libvlccore.so.8.0.0)
==13424==by 0x30D0E45595: EsCreateDecoder (in /usr/lib/libvlccore.so.8.0.0)
==13424==by 0x30D0E4641A: EsSelect (in /usr/lib/libvlccore.so.8.0.0)


This looks like a buffer overflow bug in 
/usr/lib/libomxil-bellagio.so.0.0.0.




==13424== Invalid read of size 1
==13424==at 0x1A8789C0: r600_bind_blend_state_internal (in 
/usr/lib/x86_64-linux-gnu/vdpau/libvdpau_r600.so.1.0.0)
==13424==by 0x1A6723C0: blitter_restore_fragment_states (in 
/usr/lib/x86_64-linux-gnu/vdpau/libvdpau_r600.so.1.0.0)
==13424==by 0x1A675C47: util_blitter_clear_render_target (in 
/usr/lib/x86_64-linux-gnu/vdpau/libvdpau_r600.so.1.0.0)
==13424==by 0x1A852985: r600_clear_render_target (in 
/usr/lib/x86_64-linux-gnu/vdpau/libvdpau_r600.so.1.0.0)
==13424==by 0x1A69D9A9: vl_compositor_render (in 
/usr/lib/x86_64-linux-gnu/vdpau/libvdpau_r600.so.1.0.0)
==13424==by 0x1A629E96: vlVdpPresentationQueueDisplay (in 
/usr/lib/x86_64-linux-gnu/vdpau/libvdpau_r600.so.1.0.0)
==13424==by 0x1F2F80A3: Queue (in 
/usr/lib/vlc/plugins/vdpau/libvdpau_display_plugin.so)
==13424==by 0x30D0E6DB48: ThreadDisplayPicture (in 
/usr/lib/libvlccore.so.8.0.0)
==13424==by 0x30D0E6DEB2: Thread (in /usr/lib/libvlccore.so.8.0.0)
==13424==by 0x30022080A3: start_thread (pthread_create.c:309)
==13424==  Address 0xedfe51d is 61 bytes inside a block of size 64 free'd
==13424==at 0x4A08E90: free (vg_replace_malloc.c:473)
==13424==by 0x1A62C7DD: vlVdpOutputSurfaceRenderBitmapSurface (in 
/usr/lib/x86_64-linux-gnu/vdpau/libvdpau_r600.so.1.0.0)
==13424==by 0x1F2F8200: Queue (in 
/usr/lib/vlc/plugins/vdpau/libvdpau_display_plugin.so)
==13424==by 0x30D0E6DB48: ThreadDisplayPicture (in 
/usr/lib/libvlccore.so.8.0.0)
==13424==by 0x30D0E6DEB2: Thread (in /usr/lib/libvlccore.so.8.0.0)
==13424==by 0x30022080A3: start_thread (pthread_create.c:309)


This looks like a use-after-free bug in the Mesa r600g driver. Can you 
report this upstream at 
https://bugs.freedesktop.org/enter_bug.cgi?product=Mesa , component 
Drivers/Gallium/r600?




==13424== Invalid read of size 8
==13424==at 0x1A6A4291: destroy_video_buffer_private (in 
/usr/lib/x86_64-linux-gnu/vdpau/libvdpau_r600.so.1.0.0)
==13424==by 0x1A6C0127: vl_video_buffer_destroy (in 
/usr/lib/x86_64-linux-gnu/vdpau/libvdpau_r600.so.1.0.0)
==13424==by 0x1A627314: vlVdpVideoSurfaceDestroy (in 
/usr/lib/x86_64-linux-gnu/vdpau/libvdpau_r600.so.1.0.0)
==13424==by 0x189B4092: SurfaceDestroy (in 
/usr/lib/vlc/plugins/vdpau/libvdpau_avcodec_plugin.so)
==13424==by 0x30D0E8DCF4: picture_Release (in /usr/lib/libvlccore.so.8.0.0)
==13424==by 0x30D0E6D095: ThreadDisplayPreparePicture (in 
/usr/lib/libvlccore.so.8.0.0)
==13424==by 0x30D0E6D12B: ThreadDisplayPicture (in 
/usr/lib/libvlccore.so.8.0.0)
==13424==by 0x30D0E6DEB2: Thread (in /usr/lib/libvlccore.so.8.0.0)
==13424==by 0x30022080A3: start_thread (pthread_create.c:309)
==13424==  Address 0x6780940 is 480 bytes inside a block of size 10,760 f

Bug#740953: [xserver-xorg-video-nouveau]: No devices detected. (anymore)

2014-10-20 Thread Viktor Malyarchuk 
Fixed in kernel 3.16.5 (unstable) and 3.17 (experimental).

Relevant commit is:
https://git.kernel.org/cgit/linux/kernel/git/stable/linux-stable.git/commit/?id=7babfd7f066dae02c63d9ccac886419ccfb80cfd

Cheers!
Viktor

On Wed, Mar 26, 2014 at 5:27 PM, Sven Joachim  wrote:

> On 2014-03-26 22:57 +0100, Viktor Malyarchuk wrote:
>
> > On Sun, Mar 23, 2014 at 3:48 AM, Sven Joachim  wrote:
> >
> >> When the nouveau kernel module is loaded, any conflicting framebuffer
> >> drivers are (supposed to be) removed.  Check your dmesg if that is the
> >> case for you.
>
> > Conflicting framebuffer drivers are different. Here are relevant dmesg
> > lines:
> >
> >
> > a) CONFIG_X86_SYSFB=y (dmesg.3.13-1-amd64 and Xorg.0.log.3.13-1-amd64 in
> > attachment)
> > ---
> > [   10.591133] fb: conflicting fb hw usage nouveaufb vs simple - removing
> > generic driver
> > ...
> > [   10.983470] nouveau  [ DRM] allocated 2560x1440 fb: 0x8, bo
> > 880265d15000
> > [   11.01] nouveau :01:00.0: fb0: nouveaufb frame buffer device
> > ---
> >
> > b) # CONFIG_X86_SYSFB is not set (dmesg.3.13.7+ and Xorg.0.log.3.13.7+ in
> > attachment)
> > ---
> > [   11.666121] fb: conflicting fb hw usage nouveaufb vs EFI VGA -
> removing
> > generic driver
> > ...
> > [   12.040732] nouveau  [ DRM] allocated 2560x1440 fb: 0x8, bo
> > 880262dc8400
> > [   12.040790] fbcon: nouveaufb (fb0) is primary device
> > [   12.121273] nouveau :01:00.0: fb0: nouveaufb frame buffer device
> > ---
>
> That's how it is supposed to be in both cases, so we can rule that out.
> Now why X fails in the first case but not in the second, I don't know.
>
> I think you're best off reporting the bug upstream, please see
> http://nouveau.freedesktop.org/wiki/Bugs/ for instructions.
>
> > [   10.800256] wl: module license 'MIXED/Proprietary' taints kernel.
>
> You might want to disable the wl module temporarily, kernel developers
> refuse to help when the kernel is tainted.
>
> Cheers,
>Sven
>

Processed: [bts-link] source package x11-xkb-utils

2014-10-20 Thread Debian Bug Tracking System 
Processing commands for cont...@bugs.debian.org:

> #
> # bts-link upstream status pull for source package x11-xkb-utils
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> #
> user bts-link-upstr...@lists.alioth.debian.org
Setting user to bts-link-upstr...@lists.alioth.debian.org (was 
bts-link-de...@lists.alioth.debian.org).
> # remote status report for #673035 (http://bugs.debian.org/673035)
> # Bug title: useless "No symbols defined for" warnings
> #  * https://bugs.freedesktop.org/show_bug.cgi?id=66344
> #  * remote status changed: RESOLVED -> REOPENED
> #  * remote resolution changed: FIXED -> (?)
> #  * reopen upstream
> tags 673035 - fixed-upstream
Bug #673035 [x11-xkb-utils] useless "No symbols defined for" warnings
Removed tag(s) fixed-upstream.
> usertags 673035 - status-RESOLVED resolution-FIXED
Usertags were: status-RESOLVED resolution-FIXED.
Usertags are now: .
> usertags 673035 + status-REOPENED
There were no usertags set.
Usertags are now: status-REOPENED.
> # remote status report for #673035 (http://bugs.debian.org/673035)
> # Bug title: useless "No symbols defined for" warnings
> #  * https://bugs.freedesktop.org/show_bug.cgi?id=66344
> #  * remote status changed: RESOLVED -> REOPENED
> #  * remote resolution changed: FIXED -> (?)
> #  * reopen upstream
> tags 673035 - fixed-upstream
Bug #673035 [x11-xkb-utils] useless "No symbols defined for" warnings
Ignoring request to alter tags of bug #673035 to the same tags previously set
> usertags 673035 - status-RESOLVED resolution-FIXED
Usertags were: status-REOPENED.
Usertags are now: status-REOPENED.
> usertags 673035 + status-REOPENED
Usertags were: status-REOPENED.
Usertags are now: status-REOPENED.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
673035: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=673035
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems


--
To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/handler.s.c.141382286223053.transcr...@bugs.debian.org

Processed: Re: Bug#766049: xserver-xorg-core: Blank primary screen when seocndary attached

2014-10-20 Thread Debian Bug Tracking System 
Processing control commands:

> severity -1 normal
Bug #766049 [xserver-xorg-core] xserver-xorg-core: Blank primary screen when 
seocndary attached
Severity set to 'normal' from 'grave'
> tag -1 moreinfo
Bug #766049 [xserver-xorg-core] xserver-xorg-core: Blank primary screen when 
seocndary attached
Added tag(s) moreinfo.

-- 
766049: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=766049
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems


--
To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/handler.s.b766049.141381896622604.transcr...@bugs.debian.org

xserver-xorg-video-intel: Changes to 'ubuntu-trusty'

2014-10-20 Thread Timo Aaltonen 
 debian/changelog |5 
 debian/patches/fix-no-backlight.diff |   38 +++
 debian/patches/series|1 
 3 files changed, 44 insertions(+)

New commits:
commit 9d237d1aa2a2d7561ce4ceaf49e06296b1d6bfd0
Author: Timo Aaltonen 
Date:   Mon Oct 20 10:29:28 2014 +0300

fix-no-backlight.diff: Don't let backlight switch off when cycling through 
display modes. (LP: #1373776)

diff --git a/debian/changelog b/debian/changelog
index 7fa7a26..1440041 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,7 +1,12 @@
 xserver-xorg-video-intel (2:2.99.910-0ubuntu1.2) UNRELEASED; urgency=low
 
+  [ Maarten Lankhorst ]
   * Fix black screen with SNA. (LP: #1365695)
 
+  [ Timo Aaltonen ]
+  * fix-no-backlight.diff: Don't let backlight switch off when cycling
+through display modes. (LP: #1373776)
+
  -- Maarten Lankhorst   Mon, 22 Sep 2014 
11:26:22 +0200
 
 xserver-xorg-video-intel (2:2.99.910-0ubuntu1.1) trusty; urgency=medium
diff --git a/debian/patches/fix-no-backlight.diff 
b/debian/patches/fix-no-backlight.diff
new file mode 100644
index 000..0a73239
--- /dev/null
+++ b/debian/patches/fix-no-backlight.diff
@@ -0,0 +1,38 @@
+Index: xserver-xorg-video-intel-2.99.910/src/sna/sna_display.c
+===
+--- xserver-xorg-video-intel-2.99.910.orig/src/sna/sna_display.c   
2014-09-26 16:19:42.420356000 +0800
 xserver-xorg-video-intel-2.99.910/src/sna/sna_display.c2014-09-26 
16:20:00.001464561 +0800
+@@ -2386,8 +2386,12 @@
+  
sna_output->backlight_active_level);
+   } else {
+   /* Only save the current backlight value if we're going from on 
to off. */
+-  if (oldmode == DPMSModeOn)
+-  sna_output->backlight_active_level = 
sna_output_backlight_get(output);
++  if (oldmode == DPMSModeOn) {
++  int brightness = sna_output_backlight_get(output);
++  if (brightness > 0) {
++  sna_output->backlight_active_level = brightness;
++  }
++  }
+   sna_output_backlight_set(output, 0);
+   }
+ }
+diff --git a/src/uxa/intel_display.c b/src/uxa/intel_display.c
+index 39d8507..51727a5 100644
+--- a/src/uxa/intel_display.c
 b/src/uxa/intel_display.c
+@@ -1095,8 +1095,12 @@ intel_output_dpms_backlight(xf86OutputPtr output, int 
oldmode, int mode)
+  
intel_output->backlight_active_level);
+   } else {
+   /* Only save the current backlight value if we're going from on 
to off. */
+-  if (oldmode == DPMSModeOn)
+-  intel_output->backlight_active_level = 
intel_output_backlight_get(output);
++  if (oldmode == DPMSModeOn) {
++  int brightness = intel_output_backlight_get(output);
++  if (brightness > 0) {
++  intel_output->backlight_active_level = brightness;
++  }
++  }
+   intel_output_backlight_set(output, 0);
+   }
+ }
diff --git a/debian/patches/series b/debian/patches/series
index f6330ab..1ddb42c 100644
--- a/debian/patches/series
+++ b/debian/patches/series
@@ -9,3 +9,4 @@ add-names-brw.diff
 
 sna-freescreen.diff
 disable-outputs-when-slaved.patch
+fix-no-backlight.diff


-- 
To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/e1xg7pk-0001ug...@moszumanska.debian.org

Re: Bug#761165: vlc: segmentation fault with VDPAU

2014-10-20 Thread Bálint Réczey 
2014-10-20 18:43 GMT+02:00 Rémi Denis-Courmont :
> Le mardi 21 octobre 2014, 02:13:00 Arthur Marsh a écrit :
>> Package: vlc
>> Version: 2.2.0~pre4-1+b1
>> Followup-For: Bug #761165
>>
>> Dear Maintainer,
>>
>> *** Reporter, please consider answering these questions, where appropriate
>> ***
>>
>> See also bug report 766058.
>>
>> After running vlc under valgrind both with default options and with
>> helgrind, I found the video terminated at the 9 second mark with default
>> options but continued playing back very slowly with the helgrind option,
>> which someone in #radeon in IRC suggested was a thread race condition in
>> vlc.
>
> The helgrind log there suggests a race condition in the Mesa VDPAU´s internal
> buffer object management to me.
>
> And please don´t use VLC with Bellagio. The only tested software decoder is
> libav(codec).
There is an other bug for XBMC which also looks like to be triggered
by a race condition related toVDPAU:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=742896#201

CC-ing mesa maintainers.

Cheers,
Balint


--
To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/cak0odpzo24ub1iquwvat-kzzgzaw3t5btnmp3gnxt+tmu45...@mail.gmail.com

Bug#766049: xserver-xorg-core: Blank primary screen when seocndary attached

2014-10-20 Thread Julien Cristau 
Control: severity -1 normal
Control: tag -1 moreinfo

On Mon, Oct 20, 2014 at 23:18:14 +1100, Takis Diakoumis wrote:

> Package: xserver-xorg-core
> Version: 2:1.16.1-1
> Severity: grave
> 
> Dear Maintainer,
> 
> [ issues with reportbug #758619 prevented me from using it completely
> to send this report so I generated using reportbug --template ]
> 
> Since upgrading from 2.:1.16.0.901-1 to the above version I have been
> unable to use a second screen attached to my laptop. During this
> update, I also went from linux-image-amd64 (3.14+59) to 3.16+61 – not
> sure if its relevant.
> 
Actually this seems more likely to be a kernel issue than an X one.

> I have Debian Jessie on a Thinkpad T440s.
> 
> I normally boot with the second monitor attached and it boots fine
> into gdm. Since the update, booting with the monitor attached blanks
> the laptop screen (primary screen) as X starts. The second screen
> works fine as a second screen – as in the primary display is off but
> it behaves as if it is there. The only way out here is to ctrl-alt-f1
> to a terminal and reboot.
> 
Is the screen actually dead, or does it "just" reset the brightness to
minimum?  I.e. do the brightness keys or poking
/sys/class/backlight/*/brightness work?

Cheers,
Julien


signature.asc
Description: Digital signature

Bug#766049: xserver-xorg-core: Blank primary screen when seocndary attached

2014-10-20 Thread Takis Diakoumis 
Package: xserver-xorg-core
Version: 2:1.16.1-1
Severity: grave

Dear Maintainer,

[ issues with reportbug #758619 prevented me from using it completely
to send this report so I generated using reportbug --template ]

Since upgrading from 2.:1.16.0.901-1 to the above version I have been
unable to use a second screen attached to my laptop. During this
update, I also went from linux-image-amd64 (3.14+59) to 3.16+61 – not
sure if its relevant.

I have Debian Jessie on a Thinkpad T440s.

I normally boot with the second monitor attached and it boots fine
into gdm. Since the update, booting with the monitor attached blanks
the laptop screen (primary screen) as X starts. The second screen
works fine as a second screen – as in the primary display is off but
it behaves as if it is there. The only way out here is to ctrl-alt-f1
to a terminal and reboot.

Booting with the second screen unplugged works fine for the primary
laptop screen. Attaching the second screen when logged into gnome
causes the primary laptop screen to blank again. From here if I
ctrl-alt-f1 and then ctrl-alt-f7 back into X I sometimes get them both
working as expected. Sometimes this too doesn't work and I have to
reboot again.

This worked fine until the update noted above. I have fiddled with
various display options to no avail.

The segmentation fault at the address shown in Xorg.0.log happens consistently.

Please let me know if there is any further info I can provide.

Thanks
Takis


-- Package-specific info:
X server symlink status:

lrwxrwxrwx 1 root root 13 May  3 16:00 /etc/X11/X -> /usr/bin/Xorg
-rwxr-xr-x 1 root root 2397280 Sep 23 07:49 /usr/bin/Xorg

VGA-compatible devices on PCI bus:
--
00:02.0 VGA compatible controller [0300]: Intel Corporation
Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 0b)

/etc/X11/xorg.conf does not exist.

Contents of /etc/X11/xorg.conf.d:
-
total 4
-rw-r--r-- 1 root root 1455 May  3 16:08 01-synaptics.conf

/etc/modprobe.d contains no KMS configuration files.

Kernel version (/proc/version):
---
Linux version 3.16-2-amd64 (debian-ker...@lists.debian.org) (gcc
version 4.8.3 (Debian 4.8.3-11) ) #1 SMP Debian 3.16.3-2 (2014-09-20)

Xorg X server log files on system:
--
-rw-r--r-- 1 root root 59701 Oct  1 20:55 /var/log/Xorg.0.log

Contents of most recent Xorg X server log file (/var/log/Xorg.0.log):
-
[   308.365]
X.Org X Server 1.16.1
Release Date: 2014-09-21
[   308.365] X Protocol Version 11, Revision 0
[   308.365] Build Operating System: Linux 3.2.0-4-amd64 x86_64 Debian
[   308.365] Current Operating System: Linux fitter 3.16-2-amd64 #1
SMP Debian 3.16.3-2 (2014-09-20) x86_64
[   308.365] Kernel command line:
BOOT_IMAGE=/boot/vmlinuz-3.16-2-amd64
root=UUID=cfca3780-efcd-4272-a268-648b0d9ffdf1 ro quiet
[   308.365] Build Date: 22 September 2014  09:45:37PM
[   308.365] xorg-server 2:1.16.1-1 (http://www.debian.org/support)
[   308.365] Current version of pixman: 0.32.6
[   308.366] Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[   308.366] Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[   308.366] (==) Log file: "/var/log/Xorg.0.log", Time: Wed Oct  1
20:38:26 2014
[   308.366] (==) Using config directory: "/etc/X11/xorg.conf.d"
[   308.366] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[   308.366] (==) No Layout section.  Using the first Screen section.
[   308.366] (==) No screen section available. Using defaults.
[   308.366] (**) |-->Screen "Default Screen Section" (0)
[   308.366] (**) |   |-->Monitor ""
[   308.366] (==) No monitor specified for screen "Default Screen Section".
Using a default monitor configuration.
[   308.366] (==) Automatically adding devices
[   308.366] (==) Automatically enabling devices
[   308.366] (==) Automatically adding GPU devices
[   308.366] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist.
[   308.366] Entry deleted from font path.
[   308.366] (==) FontPath set to:
/usr/share/fonts/X11/misc,
/usr/share/fonts/X11/100dpi/:unscaled,
/usr/share/fonts/X11/75dpi/:unscaled,
/usr/share/fonts/X11/Type1,
/usr/share/fonts/X11/100dpi,
/usr/share/fonts/X11/75dpi,
built-ins
[   308.366] (==) ModulePath set to "/usr/lib/xorg/modules"
[   308.366] (II) The server relies on udev to provide the list of
input devices.
If no devices become available, reconfigure udev or disable AutoAddDevices.
[   308.366] (II) Loader magic: 0x7fe9264d8d80
[   308.366] (II) Module ABI versions:
[   308.366] X.Org ANSI C Emulation: 0.4
[   308.366] X.Org Video Driver: 18.0
[   308.366] X.Org XInput driver : 21.0
[   308.366] X.Org Server Extension : 8.0
[