Re: Flash 11.2 content displays in shades of green and purple only, and in a horizontally compressed space

2013-10-05 Thread John Hupp

On 10/4/2013 9:44 AM, Dieter Nützel wrote:

Am 02.10.2013 21:20, schrieb John Hupp:

On 9/30/2013 7:36 AM, Daniel Vetter wrote:

On Sat, Sep 28, 2013 at 12:49:24PM -0400, John Hupp wrote:

[I emailed the list with this same material on 9/13, but it has
received no response and someone on the Ubuntu kernel team suggested
that I change the email Subject from "Re: Moving a bug upstream per
downstream request, emailing the maintainers" to the more
descriptive one above.]

When I emailed the maintainers with the report below on 8/15 (and
archived at 
http://lists.freedesktop.org/archives/dri-devel/2013-August/043876.html),

a response came on 8/16:

"It's a flash bug. They ignore the format of the Window that they
PutImage to. (Worse, they create an image of the right depth or else X
would reject the PutImage with a BadMatch and then render incorrect
pixel data into it.)"

Despite that, someone on the Ubuntu kernel team asserted "at a
minimum a non-flash regression exists going from Quantal to Raring,"
and urged me to proceed with upstream kernel bisection.

I finally finished that, and arrived at the result:
Still a flash bug. This commit simply enables rgb555 in the kernel, 
which

sna likes to use on gen2/3. Flash is just too dense and always presumes
xrgb. Adding

Section "Screen"
 Identifier "igd"
 DefaultDepth 24
EndSection

to your xorg.conf will work around.
-Daniel


*Thanks!  That successfully works around the Flash problem with the
Intel driver/chipsets that I reported on.  We have at least 4 of those
machines here.*


Hello John,

which 'special' Flash version are you running?
I see that you have an Celeron so YOU can use the SSE2 enabled 
version, which I can't 'cause a have old Athlon/Duron without SSE2.


Do you have to fiddle with

/etc/vdpau_wrapper.cfg
enable_flash_uv_swap=1
disable_flash_pq_bg_color=1
?

I can't get around the green and purple colors, but NO line distortion 
on my RV730 AGP, here.


Any hints, Christian?

Thank you for your insistence, John!

-Dieter


I'm just using the current 11.2.x Flash installed by 
flashplugin-installer from the standard Ubuntu repos.


I don't have to fiddle with anything you mentioned there.

On the face of it, though our cases share a symptom, your case varies 
from mine in both the graphics driver (my Intel chipsets, your ATI 
Radeon) and processor support.  I don't know enough about these things 
to assess whether the same bug and work-around apply.






57779d06367a915ee03e6cb918d7575f0a46e419 is the first bad commit
commit 57779d06367a915ee03e6cb918d7575f0a46e419
Author: Ville Syrjälä 
Date: Wed Oct 31 17:50:14 2012 +0200

 drm/i915: Fix display pixel format handling

 Fix support for all RGB/BGR pixel formats (except the
16:16:16:16 float
 format).

 Fix intel_init_framebuffer() to match hardware and driver 
limitations:

 * RGB332 is not supported at all
 * CI8 is supported
 * XRGB1555 & co. are supported on Gen3 and earlier
 * XRGB210101010 & co. are supported from Gen4 onwards
 * BGR formats are supported from Gen4 onwards
 * YUV formats are supported from Gen5 onwards (driver limitation)

 Signed-off-by: Ville Syrjälä 
 Reviewed-by: Jesse Barnes 
 Signed-off-by: Daniel Vetter 

:04 04 334e1536b3513d0c329a8bb6360593d12065b71d
bf0996ec13cbee07156c5e9f98dcdee30200e658 M drivers

-

The git bisect log:

git bisect start
# good: [29594404d7fe73cd80eaa4ee8c43dcc53970c60e] Linux 3.7
git bisect good 29594404d7fe73cd80eaa4ee8c43dcc53970c60e
# bad: [9931faca02c604c22335f5a935a501bb2ace6e20] Linux 3.8-rc3
git bisect bad 9931faca02c604c22335f5a935a501bb2ace6e20
# good: [db5b0ae00712b5176d7405e7a1dd2bfd6e8f5070] Merge tag 'dt' of
git://git.kernel.org/pub/scm/linux/kernel/git/arm/arm-soc
git bisect good db5b0ae00712b5176d7405e7a1dd2bfd6e8f5070
# bad: [3c2e81ef344a90bb0a39d84af6878b4aeff568a2] Merge branch
'drm-next' of git://people.freedesktop.org/~airlied/linux
git bisect bad 3c2e81ef344a90bb0a39d84af6878b4aeff568a2
# good: [d8c532c40721f7507896d202b8cae3b3642d2b0d] Merge branch
'v4l_for_linus' of
git://git.kernel.org/pub/scm/linux/kernel/git/mchehab/linux-media
git bisect good d8c532c40721f7507896d202b8cae3b3642d2b0d
# good: [2a74dbb9a86e8102dcd07d284135b4530a84826e] Merge branch
'for-linus' of
git://git.kernel.org/pub/scm/linux/kernel/git/jmorris/linux-security
git bisect good 2a74dbb9a86e8102dcd07d284135b4530a84826e
# bad: [124ea297c8f0e0a3a567af0894fdbe05caaf80ec] drm/nouveau: unpin
pushbuffer bo before destroying it
git bisect bad 124ea297c8f0e0a3a567af0894fdbe05caaf80ec
# bad: [12f3382bc0262e981a2e58aca900cbbdbbe66825] drm/i915:
implement WaDisablePSDDualDispatchEnable on IVB & VLV
git bisect bad 12f3382bc0262e981a2e58aca900cbbdbbe66825
# good: [20474e90c948545c51

Re: Flash 11.2 content displays in shades of green and purple only, and in a horizontally compressed space

2013-10-03 Thread John Hupp

On 9/30/2013 7:36 AM, Daniel Vetter wrote:

On Sat, Sep 28, 2013 at 12:49:24PM -0400, John Hupp wrote:

[I emailed the list with this same material on 9/13, but it has
received no response and someone on the Ubuntu kernel team suggested
that I change the email Subject from "Re: Moving a bug upstream per
downstream request, emailing the maintainers" to the more
descriptive one above.]

When I emailed the maintainers with the report below on 8/15 (and
archived at 
http://lists.freedesktop.org/archives/dri-devel/2013-August/043876.html),
a response came on 8/16:

"It's a flash bug. They ignore the format of the Window that they
PutImage to. (Worse, they create an image of the right depth or else X
would reject the PutImage with a BadMatch and then render incorrect
pixel data into it.)"

Despite that, someone on the Ubuntu kernel team asserted "at a
minimum a non-flash regression exists going from Quantal to Raring,"
and urged me to proceed with upstream kernel bisection.

I finally finished that, and arrived at the result:

Still a flash bug. This commit simply enables rgb555 in the kernel, which
sna likes to use on gen2/3. Flash is just too dense and always presumes
xrgb. Adding

Section "Screen"
 Identifier "igd"
 DefaultDepth 24
EndSection

to your xorg.conf will work around.
-Daniel


*Thanks!  That successfully works around the Flash problem with the 
Intel driver/chipsets that I reported on.  We have at least 4 of those 
machines here.*



57779d06367a915ee03e6cb918d7575f0a46e419 is the first bad commit
commit 57779d06367a915ee03e6cb918d7575f0a46e419
Author: Ville Syrjälä 
Date: Wed Oct 31 17:50:14 2012 +0200

 drm/i915: Fix display pixel format handling

 Fix support for all RGB/BGR pixel formats (except the
16:16:16:16 float
 format).

 Fix intel_init_framebuffer() to match hardware and driver limitations:
 * RGB332 is not supported at all
 * CI8 is supported
 * XRGB1555 & co. are supported on Gen3 and earlier
 * XRGB210101010 & co. are supported from Gen4 onwards
 * BGR formats are supported from Gen4 onwards
 * YUV formats are supported from Gen5 onwards (driver limitation)

 Signed-off-by: Ville Syrjälä 
 Reviewed-by: Jesse Barnes 
 Signed-off-by: Daniel Vetter 

:04 04 334e1536b3513d0c329a8bb6360593d12065b71d
bf0996ec13cbee07156c5e9f98dcdee30200e658 M drivers

-

The git bisect log:

git bisect start
# good: [29594404d7fe73cd80eaa4ee8c43dcc53970c60e] Linux 3.7
git bisect good 29594404d7fe73cd80eaa4ee8c43dcc53970c60e
# bad: [9931faca02c604c22335f5a935a501bb2ace6e20] Linux 3.8-rc3
git bisect bad 9931faca02c604c22335f5a935a501bb2ace6e20
# good: [db5b0ae00712b5176d7405e7a1dd2bfd6e8f5070] Merge tag 'dt' of
git://git.kernel.org/pub/scm/linux/kernel/git/arm/arm-soc
git bisect good db5b0ae00712b5176d7405e7a1dd2bfd6e8f5070
# bad: [3c2e81ef344a90bb0a39d84af6878b4aeff568a2] Merge branch
'drm-next' of git://people.freedesktop.org/~airlied/linux
git bisect bad 3c2e81ef344a90bb0a39d84af6878b4aeff568a2
# good: [d8c532c40721f7507896d202b8cae3b3642d2b0d] Merge branch
'v4l_for_linus' of
git://git.kernel.org/pub/scm/linux/kernel/git/mchehab/linux-media
git bisect good d8c532c40721f7507896d202b8cae3b3642d2b0d
# good: [2a74dbb9a86e8102dcd07d284135b4530a84826e] Merge branch
'for-linus' of
git://git.kernel.org/pub/scm/linux/kernel/git/jmorris/linux-security
git bisect good 2a74dbb9a86e8102dcd07d284135b4530a84826e
# bad: [124ea297c8f0e0a3a567af0894fdbe05caaf80ec] drm/nouveau: unpin
pushbuffer bo before destroying it
git bisect bad 124ea297c8f0e0a3a567af0894fdbe05caaf80ec
# bad: [12f3382bc0262e981a2e58aca900cbbdbbe66825] drm/i915:
implement WaDisablePSDDualDispatchEnable on IVB & VLV
git bisect bad 12f3382bc0262e981a2e58aca900cbbdbbe66825
# good: [20474e90c948545c51da95689b8342a4f3bbaeb6] drm/i915: fix
checks inside ironlake_crtc_{enable, disable}
git bisect good 20474e90c948545c51da95689b8342a4f3bbaeb6
# good: [00c09d70df6b30c980f20facc1db3def3f5a637e] drm/i915: create
the DDI encoder
git bisect good 00c09d70df6b30c980f20facc1db3def3f5a637e
# bad: [a35f267946947b3798827a783d82d3d2aa55697d] drm/i915: remove
IBX code from lpt_enable_pch_transcoder
git bisect bad a35f267946947b3798827a783d82d3d2aa55697d
# bad: [9256aa195d3badd009bf4addee6c3ae39879b8a6] drm/i915: move
encoder->mode_set calls to crtc_mode_set
git bisect bad 9256aa195d3badd009bf4addee6c3ae39879b8a6
# good: [e7210c3c4f0d05e318b854bbd545fe335930c5cc] drm/i915: move
more pte encoding to pte encode
git bisect good e7210c3c4f0d05e318b854bbd545fe335930c5cc
# bad: [90f9a336f56318d4f21a29e8ef063cb70fe7dd11] drm/i915: Check
the framebuffer offset
git bisect bad 90f9a336f56318d4f21a29e8ef063cb70fe7dd11
# bad: [5d7bd705ddb362d5bd8ef2f3b294cd8f9d93c39e] drm/i915: Check
framebuffer stride more thoroughly
git bisect bad 5d7bd705ddb362d5bd8ef2f3

Flash 11.2 content displays in shades of green and purple only, and in a horizontally compressed space

2013-09-28 Thread John Hupp
[I emailed the list with this same material on 9/13, but it has received 
no response and someone on the Ubuntu kernel team suggested that I 
change the email Subject from "Re: Moving a bug upstream per downstream 
request, emailing the maintainers" to the more descriptive one above.]

When I emailed the maintainers with the report below on 8/15 (and 
archived at 
http://lists.freedesktop.org/archives/dri-devel/2013-August/043876.html), a 
response came on 8/16:

"It's a flash bug. They ignore the format of the Window that they
PutImage to. (Worse, they create an image of the right depth or else X
would reject the PutImage with a BadMatch and then render incorrect
pixel data into it.)"

Despite that, someone on the Ubuntu kernel team asserted "at a minimum a 
non-flash regression exists going from Quantal to Raring," and urged me 
to proceed with upstream kernel bisection.

I finally finished that, and arrived at the result:

57779d06367a915ee03e6cb918d7575f0a46e419 is the first bad commit
commit 57779d06367a915ee03e6cb918d7575f0a46e419
Author: Ville Syrj??l?? 
Date: Wed Oct 31 17:50:14 2012 +0200

 drm/i915: Fix display pixel format handling

 Fix support for all RGB/BGR pixel formats (except the 16:16:16:16 
float
 format).

 Fix intel_init_framebuffer() to match hardware and driver limitations:
 * RGB332 is not supported at all
 * CI8 is supported
 * XRGB1555 & co. are supported on Gen3 and earlier
 * XRGB210101010 & co. are supported from Gen4 onwards
 * BGR formats are supported from Gen4 onwards
 * YUV formats are supported from Gen5 onwards (driver limitation)

 Signed-off-by: Ville Syrj??l?? 
 Reviewed-by: Jesse Barnes 
 Signed-off-by: Daniel Vetter 

:04 04 334e1536b3513d0c329a8bb6360593d12065b71d 
bf0996ec13cbee07156c5e9f98dcdee30200e658 M drivers

-

The git bisect log:

git bisect start
# good: [29594404d7fe73cd80eaa4ee8c43dcc53970c60e] Linux 3.7
git bisect good 29594404d7fe73cd80eaa4ee8c43dcc53970c60e
# bad: [9931faca02c604c22335f5a935a501bb2ace6e20] Linux 3.8-rc3
git bisect bad 9931faca02c604c22335f5a935a501bb2ace6e20
# good: [db5b0ae00712b5176d7405e7a1dd2bfd6e8f5070] Merge tag 'dt' of 
git://git.kernel.org/pub/scm/linux/kernel/git/arm/arm-soc
git bisect good db5b0ae00712b5176d7405e7a1dd2bfd6e8f5070
# bad: [3c2e81ef344a90bb0a39d84af6878b4aeff568a2] Merge branch 
'drm-next' of git://people.freedesktop.org/~airlied/linux
git bisect bad 3c2e81ef344a90bb0a39d84af6878b4aeff568a2
# good: [d8c532c40721f7507896d202b8cae3b3642d2b0d] Merge branch 
'v4l_for_linus' of 
git://git.kernel.org/pub/scm/linux/kernel/git/mchehab/linux-media
git bisect good d8c532c40721f7507896d202b8cae3b3642d2b0d
# good: [2a74dbb9a86e8102dcd07d284135b4530a84826e] Merge branch 
'for-linus' of 
git://git.kernel.org/pub/scm/linux/kernel/git/jmorris/linux-security
git bisect good 2a74dbb9a86e8102dcd07d284135b4530a84826e
# bad: [124ea297c8f0e0a3a567af0894fdbe05caaf80ec] drm/nouveau: unpin 
pushbuffer bo before destroying it
git bisect bad 124ea297c8f0e0a3a567af0894fdbe05caaf80ec
# bad: [12f3382bc0262e981a2e58aca900cbbdbbe66825] drm/i915: implement 
WaDisablePSDDualDispatchEnable on IVB & VLV
git bisect bad 12f3382bc0262e981a2e58aca900cbbdbbe66825
# good: [20474e90c948545c51da95689b8342a4f3bbaeb6] drm/i915: fix checks 
inside ironlake_crtc_{enable, disable}
git bisect good 20474e90c948545c51da95689b8342a4f3bbaeb6
# good: [00c09d70df6b30c980f20facc1db3def3f5a637e] drm/i915: create the 
DDI encoder
git bisect good 00c09d70df6b30c980f20facc1db3def3f5a637e
# bad: [a35f267946947b3798827a783d82d3d2aa55697d] drm/i915: remove IBX 
code from lpt_enable_pch_transcoder
git bisect bad a35f267946947b3798827a783d82d3d2aa55697d
# bad: [9256aa195d3badd009bf4addee6c3ae39879b8a6] drm/i915: move 
encoder->mode_set calls to crtc_mode_set
git bisect bad 9256aa195d3badd009bf4addee6c3ae39879b8a6
# good: [e7210c3c4f0d05e318b854bbd545fe335930c5cc] drm/i915: move more 
pte encoding to pte encode
git bisect good e7210c3c4f0d05e318b854bbd545fe335930c5cc
# bad: [90f9a336f56318d4f21a29e8ef063cb70fe7dd11] drm/i915: Check the 
framebuffer offset
git bisect bad 90f9a336f56318d4f21a29e8ef063cb70fe7dd11
# bad: [5d7bd705ddb362d5bd8ef2f3b294cd8f9d93c39e] drm/i915: Check 
framebuffer stride more thoroughly
git bisect bad 5d7bd705ddb362d5bd8ef2f3b294cd8f9d93c39e
# bad: [57779d06367a915ee03e6cb918d7575f0a46e419] drm/i915: Fix display 
pixel format handling
git bisect bad 57779d06367a915ee03e6cb918d7575f0a46e419

-

After finishing the kernel bisection, I also tested the new latest 
mainline kernel (3.11.0-031100-generic, modified 9-2-13) and found that 
it still suffers from the bug.

Software Update also offered an updated version of the 
Flashplugin-Installer (updating 11.2.202.297 to 11.2.202.310), but that 
did not fix the problem either.

-
THE ORIGINAL REPORT:

[1.] One line summary of the problem:
Fla

Re: Moving a bug upstream per downstream request, emailing the maintainers

2013-09-15 Thread John Hupp
When I emailed the maintainers with the report below on 8/15 (and 
archived at 
http://lists.freedesktop.org/archives/dri-devel/2013-August/043876.html), a 
response came on 8/16:


"It's a flash bug. They ignore the format of the Window that they
PutImage to. (Worse, they create an image of the right depth or else X
would reject the PutImage with a BadMatch and then render incorrect
pixel data into it.)"

Despite that, someone on the Ubuntu kernel team asserted "at a minimum a 
non-flash regression exists going from Quantal to Raring," and urged me 
to proceed with upstream kernel bisection.


I finally finished that, and arrived at the result:

57779d06367a915ee03e6cb918d7575f0a46e419 is the first bad commit
commit 57779d06367a915ee03e6cb918d7575f0a46e419
Author: Ville Syrjälä 
Date: Wed Oct 31 17:50:14 2012 +0200

drm/i915: Fix display pixel format handling

Fix support for all RGB/BGR pixel formats (except the 16:16:16:16 float
format).

Fix intel_init_framebuffer() to match hardware and driver limitations:
* RGB332 is not supported at all
* CI8 is supported
* XRGB1555 & co. are supported on Gen3 and earlier
* XRGB210101010 & co. are supported from Gen4 onwards
* BGR formats are supported from Gen4 onwards
* YUV formats are supported from Gen5 onwards (driver limitation)

Signed-off-by: Ville Syrjälä 
Reviewed-by: Jesse Barnes 
Signed-off-by: Daniel Vetter 

:04 04 334e1536b3513d0c329a8bb6360593d12065b71d 
bf0996ec13cbee07156c5e9f98dcdee30200e658 M drivers


-

The git bisect log:

git bisect start
# good: [29594404d7fe73cd80eaa4ee8c43dcc53970c60e] Linux 3.7
git bisect good 29594404d7fe73cd80eaa4ee8c43dcc53970c60e
# bad: [9931faca02c604c22335f5a935a501bb2ace6e20] Linux 3.8-rc3
git bisect bad 9931faca02c604c22335f5a935a501bb2ace6e20
# good: [db5b0ae00712b5176d7405e7a1dd2bfd6e8f5070] Merge tag 'dt' of 
git://git.kernel.org/pub/scm/linux/kernel/git/arm/arm-soc

git bisect good db5b0ae00712b5176d7405e7a1dd2bfd6e8f5070
# bad: [3c2e81ef344a90bb0a39d84af6878b4aeff568a2] Merge branch 
'drm-next' of git://people.freedesktop.org/~airlied/linux

git bisect bad 3c2e81ef344a90bb0a39d84af6878b4aeff568a2
# good: [d8c532c40721f7507896d202b8cae3b3642d2b0d] Merge branch 
'v4l_for_linus' of 
git://git.kernel.org/pub/scm/linux/kernel/git/mchehab/linux-media

git bisect good d8c532c40721f7507896d202b8cae3b3642d2b0d
# good: [2a74dbb9a86e8102dcd07d284135b4530a84826e] Merge branch 
'for-linus' of 
git://git.kernel.org/pub/scm/linux/kernel/git/jmorris/linux-security

git bisect good 2a74dbb9a86e8102dcd07d284135b4530a84826e
# bad: [124ea297c8f0e0a3a567af0894fdbe05caaf80ec] drm/nouveau: unpin 
pushbuffer bo before destroying it

git bisect bad 124ea297c8f0e0a3a567af0894fdbe05caaf80ec
# bad: [12f3382bc0262e981a2e58aca900cbbdbbe66825] drm/i915: implement 
WaDisablePSDDualDispatchEnable on IVB & VLV

git bisect bad 12f3382bc0262e981a2e58aca900cbbdbbe66825
# good: [20474e90c948545c51da95689b8342a4f3bbaeb6] drm/i915: fix checks 
inside ironlake_crtc_{enable, disable}

git bisect good 20474e90c948545c51da95689b8342a4f3bbaeb6
# good: [00c09d70df6b30c980f20facc1db3def3f5a637e] drm/i915: create the 
DDI encoder

git bisect good 00c09d70df6b30c980f20facc1db3def3f5a637e
# bad: [a35f267946947b3798827a783d82d3d2aa55697d] drm/i915: remove IBX 
code from lpt_enable_pch_transcoder

git bisect bad a35f267946947b3798827a783d82d3d2aa55697d
# bad: [9256aa195d3badd009bf4addee6c3ae39879b8a6] drm/i915: move 
encoder->mode_set calls to crtc_mode_set

git bisect bad 9256aa195d3badd009bf4addee6c3ae39879b8a6
# good: [e7210c3c4f0d05e318b854bbd545fe335930c5cc] drm/i915: move more 
pte encoding to pte encode

git bisect good e7210c3c4f0d05e318b854bbd545fe335930c5cc
# bad: [90f9a336f56318d4f21a29e8ef063cb70fe7dd11] drm/i915: Check the 
framebuffer offset

git bisect bad 90f9a336f56318d4f21a29e8ef063cb70fe7dd11
# bad: [5d7bd705ddb362d5bd8ef2f3b294cd8f9d93c39e] drm/i915: Check 
framebuffer stride more thoroughly

git bisect bad 5d7bd705ddb362d5bd8ef2f3b294cd8f9d93c39e
# bad: [57779d06367a915ee03e6cb918d7575f0a46e419] drm/i915: Fix display 
pixel format handling

git bisect bad 57779d06367a915ee03e6cb918d7575f0a46e419

-

After finishing the kernel bisection, I also tested the new latest 
mainline kernel (3.11.0-031100-generic, modified 9-2-13) and found that 
it still suffers from the bug.


Software Update also offered an updated version of the 
Flashplugin-Installer (updating 11.2.202.297 to 11.2.202.310), but that 
did not fix the problem either.


-
THE ORIGINAL REPORT:

[1.] One line summary of the problem:
Flash 11.2 content displays in shades of green and purple only, and in a
horizontally compressed space

[2.] Full description of the problem/report:
The full downstream bug report is at
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1212455 , but my
description from there:

In m

Re: Moving a bug upstream per downstream request, emailing the maintainers

2013-08-18 Thread John Hupp

On 8/16/2013 3:43 AM, Chris Wilson wrote:

On Thu, Aug 15, 2013 at 03:28:53PM -0400, John Hupp wrote:

[1.] One line summary of the problem:
Flash 11.2 content displays in shades of green and purple only, and
in a horizontally compressed space

[2.] Full description of the problem/report:
The full downstream bug report is at
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1212455 , but
my description from there:

In my testing with the Intel driver using its default acceleration:
- Flash 11.2 works on Quantal with the 3.5 kernel
- Flash 11.2 works on Raring with the 3.5.0-17 kernel (though it
boots to a low-res desktop with a frozen pointer)
- Flash 11.2 works on Raring also with the 3.6.11-030611 or
3.7.10-030710 mainline kernels
- Flash 11.8 works on Raring with the 3.8 kernel (in Chrome)
- Flash 11.2 fails on Raring with the 3.8 kernel
- Flash 11.2 fails on Raring with the latest mainline kernel,
3.11.0-031100rc5
- Flash 11.2 fails on Saucy alpha 2 with its default kernel

It's a flash bug. They ignore the format of the Window that they
PutImage to. (Worse, they create an image of the right depth or else X
would reject the PutImage with a BadMatch and then render incorrect
pixel data into it.)
-Chris



OK, thanks for identifying the problem.
___
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel


Moving a bug upstream per downstream request, emailing the maintainers

2013-08-16 Thread John Hupp
On 8/16/2013 3:43 AM, Chris Wilson wrote:
> On Thu, Aug 15, 2013 at 03:28:53PM -0400, John Hupp wrote:
>> [1.] One line summary of the problem:
>> Flash 11.2 content displays in shades of green and purple only, and
>> in a horizontally compressed space
>>
>> [2.] Full description of the problem/report:
>> The full downstream bug report is at
>> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1212455 , but
>> my description from there:
>>
>> In my testing with the Intel driver using its default acceleration:
>> - Flash 11.2 works on Quantal with the 3.5 kernel
>> - Flash 11.2 works on Raring with the 3.5.0-17 kernel (though it
>> boots to a low-res desktop with a frozen pointer)
>> - Flash 11.2 works on Raring also with the 3.6.11-030611 or
>> 3.7.10-030710 mainline kernels
>> - Flash 11.8 works on Raring with the 3.8 kernel (in Chrome)
>> - Flash 11.2 fails on Raring with the 3.8 kernel
>> - Flash 11.2 fails on Raring with the latest mainline kernel,
>> 3.11.0-031100rc5
>> - Flash 11.2 fails on Saucy alpha 2 with its default kernel
> It's a flash bug. They ignore the format of the Window that they
> PutImage to. (Worse, they create an image of the right depth or else X
> would reject the PutImage with a BadMatch and then render incorrect
> pixel data into it.)
> -Chris
>

OK, thanks for identifying the problem.


Moving a bug upstream per downstream request, emailing the maintainers

2013-08-15 Thread John Hupp

[1.] One line summary of the problem:
Flash 11.2 content displays in shades of green and purple only, and in a 
horizontally compressed space


[2.] Full description of the problem/report:
The full downstream bug report is at 
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1212455 , but my 
description from there:


In my testing with the Intel driver using its default acceleration:
- Flash 11.2 works on Quantal with the 3.5 kernel
- Flash 11.2 works on Raring with the 3.5.0-17 kernel (though it boots 
to a low-res desktop with a frozen pointer)
- Flash 11.2 works on Raring also with the 3.6.11-030611 or 
3.7.10-030710 mainline kernels

- Flash 11.8 works on Raring with the 3.8 kernel (in Chrome)
- Flash 11.2 fails on Raring with the 3.8 kernel
- Flash 11.2 fails on Raring with the latest mainline kernel, 
3.11.0-031100rc5

- Flash 11.2 fails on Saucy alpha 2 with its default kernel

Disabling Flash *hardware* acceleration altogether (via R-click in the 
Flash display window: Settings: General tab) did not fix the problem.


WORKAROUND: Setting the Intel driver's acceleration method to UXA rather 
than its default SNA *always* fixes the Flash problem, but causes a 
garbled login screen under LightDM that so far has no workaround.


I also tried one possible fix for the default Intel SNA acceleration 
using the TearFree option. I created /etc/X11/xorg.conf.d/20-intel.conf 
with contents:

Section "Device"
   Identifier "Intel Graphics"
   Driver "intel"
   Option "AccelMethod" "sna"
   Option "TearFree" "true"
EndSection
But this had no effect.

[3.] Keywords (i.e., modules, networking, kernel):
I'm a newbie hanging on by my fingernails here -- I have no idea about 
appropriate keywords.


[4.] Kernel version (from /proc/version):
Linux version 3.11.0-031100rc5-generic (apw@gomeisa) (gcc version 4.6.3 
(Ubuntu/Linaro 4.6.3-1ubuntu5) ) #201308112135 SMP Mon Aug 12 01:44:44 
UTC 2013


[5.] Output of Oops.. message (if applicable) with symbolic information 
resolved (see Documentation/oops-tracing.txt)


[6.] A small shell script or example program which triggers the problem 
(if possible)


[7.] Environment
Description:Ubuntu 13.04
Release:13.04

[7.1.] Software (add the output of the ver_linux script here)
If some fields are empty or look unusual you may have an old version.
Compare to the current minimal requirements in Documentation/Changes.

Linux Dimension 3.11.0-031100rc5-generic #201308112135 SMP Mon Aug 12 
01:44:44 UTC 2013 i686 i686 i686 GNU/Linux


Gnu C /usr/src/linux-headers-3.11.0-031100rc5-generic/scripts/ver_linux:
binutils
util-linux 2.20.1
mount  support
module-init-tools  9
e2fsprogs  1.42.5
PPP2.4.5
Linux C Library2.17
Dynamic linker (ldd)   2.17
Procps 3.3.3
Net-tools  1.60
Kbd1.15.5
Sh-utils   8.20
wireless-tools 30
Modules Loaded nls_iso8859_1 usb_storage snd_intel8x0 
snd_ac97_codec ac97_bus bnep snd_pcm rfcomm bluetooth ppdev 
snd_page_alloc gpio_ich snd_seq_midi snd_seq_midi_event snd_rawmidi 
snd_seq dcdbas snd_seq_device i915 snd_timer video snd psmouse 
drm_kms_helper serio_raw soundcore drm i2c_algo_bit parport_pc lpc_ich 
shpchp lp mac_hid parport b44 ssb mii floppy


[7.2.] Processor information (from /proc/cpuinfo):
processor: 0
vendor_id: GenuineIntel
cpu family: 15
model: 2
model name: Intel(R) Celeron(R) CPU 2.40GHz
stepping: 9
microcode: 0x17
cpu MHz: 2392.420
cache size: 128 KB
fdiv_bug: no
f00f_bug: no
coma_bug: no
fpu: yes
fpu_exception: yes
cpuid level: 2
wp: yes
flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca 
cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe pebs bts 
cid xtpr

bogomips: 4784.84
clflush size: 64
cache_alignment: 128
address sizes: 36 bits physical, 32 bits virtual
power management:

[7.3.] Module information (from /proc/modules):
nls_iso8859_1 12617 1 - Live 0x
usb_storage 48631 1 - Live 0x
snd_intel8x0 33458 1 - Live 0x
snd_ac97_codec 110295 1 snd_intel8x0, Live 0x
ac97_bus 12642 1 snd_ac97_codec, Live 0x
bnep 19143 2 - Live 0x
snd_pcm 94597 2 snd_intel8x0,snd_ac97_codec, Live 0x
rfcomm 58965 0 - Live 0x
bluetooth 337841 10 bnep,rfcomm, Live 0x
ppdev 17423 0 - Live 0x
snd_page_alloc 18398 2 snd_intel8x0,snd_pcm, Live 0x
gpio_ich 13278 0 - Live 0x
snd_seq_midi 13132 0 - Live 0x
snd_seq_midi_event 14475 1 snd_seq_midi, Live 0x
snd_rawmidi 25157 1 snd_seq_midi, Live 0x
snd_seq 55716 2 snd_seq_midi,snd_seq_midi_event, Live 0x
dcdbas 14456 0 - Live 0x
snd_seq_device 14137 3 snd_seq_midi,snd_rawmidi,snd_seq, Live 0x
i915 606994 2 - Live 0x
snd_timer 28930 2 snd_pcm,snd_seq, Live 0x
v

Moving a bug upstream per downstream request, emailing the maintainers

2013-08-15 Thread John Hupp
[1.] One line summary of the problem:
Flash 11.2 content displays in shades of green and purple only, and in a 
horizontally compressed space

[2.] Full description of the problem/report:
The full downstream bug report is at 
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1212455 , but my 
description from there:

In my testing with the Intel driver using its default acceleration:
- Flash 11.2 works on Quantal with the 3.5 kernel
- Flash 11.2 works on Raring with the 3.5.0-17 kernel (though it boots 
to a low-res desktop with a frozen pointer)
- Flash 11.2 works on Raring also with the 3.6.11-030611 or 
3.7.10-030710 mainline kernels
- Flash 11.8 works on Raring with the 3.8 kernel (in Chrome)
- Flash 11.2 fails on Raring with the 3.8 kernel
- Flash 11.2 fails on Raring with the latest mainline kernel, 
3.11.0-031100rc5
- Flash 11.2 fails on Saucy alpha 2 with its default kernel

Disabling Flash *hardware* acceleration altogether (via R-click in the 
Flash display window: Settings: General tab) did not fix the problem.

WORKAROUND: Setting the Intel driver's acceleration method to UXA rather 
than its default SNA *always* fixes the Flash problem, but causes a 
garbled login screen under LightDM that so far has no workaround.

I also tried one possible fix for the default Intel SNA acceleration 
using the TearFree option. I created /etc/X11/xorg.conf.d/20-intel.conf 
with contents:
 Section "Device"
Identifier "Intel Graphics"
Driver "intel"
Option "AccelMethod" "sna"
Option "TearFree" "true"
 EndSection
But this had no effect.

[3.] Keywords (i.e., modules, networking, kernel):
I'm a newbie hanging on by my fingernails here -- I have no idea about 
appropriate keywords.

[4.] Kernel version (from /proc/version):
Linux version 3.11.0-031100rc5-generic (apw at gomeisa) (gcc version 4.6.3 
(Ubuntu/Linaro 4.6.3-1ubuntu5) ) #201308112135 SMP Mon Aug 12 01:44:44 
UTC 2013

[5.] Output of Oops.. message (if applicable) with symbolic information 
resolved (see Documentation/oops-tracing.txt)

[6.] A small shell script or example program which triggers the problem 
(if possible)

[7.] Environment
Description:Ubuntu 13.04
Release:13.04

[7.1.] Software (add the output of the ver_linux script here)
If some fields are empty or look unusual you may have an old version.
Compare to the current minimal requirements in Documentation/Changes.

Linux Dimension 3.11.0-031100rc5-generic #201308112135 SMP Mon Aug 12 
01:44:44 UTC 2013 i686 i686 i686 GNU/Linux

Gnu C /usr/src/linux-headers-3.11.0-031100rc5-generic/scripts/ver_linux:
binutils
util-linux 2.20.1
mount  support
module-init-tools  9
e2fsprogs  1.42.5
PPP2.4.5
Linux C Library2.17
Dynamic linker (ldd)   2.17
Procps 3.3.3
Net-tools  1.60
Kbd1.15.5
Sh-utils   8.20
wireless-tools 30
Modules Loaded nls_iso8859_1 usb_storage snd_intel8x0 
snd_ac97_codec ac97_bus bnep snd_pcm rfcomm bluetooth ppdev 
snd_page_alloc gpio_ich snd_seq_midi snd_seq_midi_event snd_rawmidi 
snd_seq dcdbas snd_seq_device i915 snd_timer video snd psmouse 
drm_kms_helper serio_raw soundcore drm i2c_algo_bit parport_pc lpc_ich 
shpchp lp mac_hid parport b44 ssb mii floppy

[7.2.] Processor information (from /proc/cpuinfo):
processor: 0
vendor_id: GenuineIntel
cpu family: 15
model: 2
model name: Intel(R) Celeron(R) CPU 2.40GHz
stepping: 9
microcode: 0x17
cpu MHz: 2392.420
cache size: 128 KB
fdiv_bug: no
f00f_bug: no
coma_bug: no
fpu: yes
fpu_exception: yes
cpuid level: 2
wp: yes
flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca 
cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe pebs bts 
cid xtpr
bogomips: 4784.84
clflush size: 64
cache_alignment: 128
address sizes: 36 bits physical, 32 bits virtual
power management:

[7.3.] Module information (from /proc/modules):
nls_iso8859_1 12617 1 - Live 0x
usb_storage 48631 1 - Live 0x
snd_intel8x0 33458 1 - Live 0x
snd_ac97_codec 110295 1 snd_intel8x0, Live 0x
ac97_bus 12642 1 snd_ac97_codec, Live 0x
bnep 19143 2 - Live 0x
snd_pcm 94597 2 snd_intel8x0,snd_ac97_codec, Live 0x
rfcomm 58965 0 - Live 0x
bluetooth 337841 10 bnep,rfcomm, Live 0x
ppdev 17423 0 - Live 0x
snd_page_alloc 18398 2 snd_intel8x0,snd_pcm, Live 0x
gpio_ich 13278 0 - Live 0x
snd_seq_midi 13132 0 - Live 0x
snd_seq_midi_event 14475 1 snd_seq_midi, Live 0x
snd_rawmidi 25157 1 snd_seq_midi, Live 0x
snd_seq 55716 2 snd_seq_midi,snd_seq_midi_event, Live 0x
dcdbas 14456 0 - Live 0x
snd_seq_device 14137 3 snd_seq_midi,snd_rawmidi,snd_seq, Live 0x
i915 606994 2 - Live 0x
snd_timer 28930 2 snd_pcm,snd_seq, Live 0x
video 1