From: b32955@freescale.com (Huang Shijie)
To: linux-arm-kernel@lists.infradead.org
Subject: Bug in v7_coherent_kern_range() ?
Date: Mon, 16 Apr 2012 13:48:41 +0800 [thread overview]
Message-ID: <4F8BB2B9.3050202@freescale.com> (raw)
In-Reply-To: <CAOMZO5A1hO8O1Zr5R2929bA2LYrcKM0RySM4aSu0PkLU-Cmr_w@mail.gmail.com>
? 2012?04?11? 19:02, Fabio Estevam ??:
> On Wed, Apr 11, 2012 at 7:24 AM, Will Deacon<will.deacon@arm.com> wrote:
>
>>> I wish i could find a more common test case to reproduce this bug. But, i can't.
>>> The only test case now is to run the gplay on our IMX6Q platform.
>> Ok, that makes it tricky since I don't have gplay or an IMX6Q platform.
> gplay is a C application that does the same thing as launching a
> simple Gstreamer pipeline like:
>
> gst-launch playbin2 uri=file:///home/file.mp4
>
> Huang,
>
> Does the problem also occur if you don?t use the VPU driver? I mean,
I do not test the case with the VPU disabled.
> does it also happen if you decode the file using software codecs. I
> would like to know if the issue you see is related to the VPU driver
Can the vpu affects the futex? I am debugging an uart bug now.
I will continue to debug this bug when i finish the uart bug.
Best Regards
Huang Shijie
> or not.
>
next prev parent reply other threads:[~2012-04-16 5:48 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-01 3:21 Bug in v7_coherent_kern_range() ? Huang Shijie
2012-04-01 6:10 ` Dirk Behme
2012-04-01 7:09 ` Huang Shijie
2012-04-01 8:01 ` Dirk Behme
2012-04-01 8:16 ` Huang Shijie
2012-04-01 8:50 ` Dirk Behme
2012-04-01 9:14 ` Huang Shijie
2012-04-01 8:57 ` Dirk Behme
2012-04-01 9:19 ` Huang Shijie
2012-04-01 9:19 ` Huang Shijie
2012-04-02 11:12 ` Will Deacon
2012-04-06 3:35 ` Huang Shijie
2012-04-10 9:22 ` Will Deacon
2012-04-10 10:30 ` Huang Shijie
2012-04-10 10:35 ` Will Deacon
[not found] ` <4F854992.9080601@freescale.com>
2012-04-11 10:24 ` Will Deacon
2012-04-11 11:02 ` Fabio Estevam
2012-04-16 5:48 ` Huang Shijie [this message]
2012-05-10 2:51 ` Huang Shijie
2012-05-10 8:38 ` Will Deacon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4F8BB2B9.3050202@freescale.com \
--to=b32955@freescale.com \
--cc=linux-arm-kernel@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.