From: b32955@freescale.com (Huang Shijie)
To: linux-arm-kernel@lists.infradead.org
Subject: Bug in v7_coherent_kern_range() ?
Date: Fri, 6 Apr 2012 11:35:09 +0800 [thread overview]
Message-ID: <4F7E646D.6000302@freescale.com> (raw)
In-Reply-To: <20120402111240.GG19011@mudshark.cambridge.arm.com>
Hi Will:
> On Sun, Apr 01, 2012 at 04:21:10AM +0100, Huang Shijie wrote:
>> But in some unknown situation, cacheflush() failed and one threads
>> (assume A) may hung up in the following code:
> [...]
>
>> multiqueue0:src D 804cd678 0 7328 5963 0x00000001
>> [<804cd678>] (__schedule+0x228/0x760) from [<804d0564>]
>> (__down_read+0xa8/0xe0)
>> [<804d0564>] (__down_read+0xa8/0xe0) from [<800478c4>]
>> (do_page_fault+0xbc/0x480)
>> [<800478c4>] (do_page_fault+0xbc/0x480) from [<8003841c>]
>> (do_DataAbort+0x34/0x98)
>> [<8003841c>] (do_DataAbort+0x34/0x98) from [<8003df10>]
>> (__dabt_svc+0x70/0xa0)
>> Exception stack(0xbae37ea8 to 0xbae37ef0)
>> 7ea0: 31e05000 31e1d000 00000020 0000001f 31e05000 31e1d000
>> 7ec0: bfac86b8 31e05000 31e1d000 bae36000 08100075 31e056fc 31e08000
>> bae37ef0
>> 7ee0: 800424a8 8004a1fc 800f0013 ffffffff
>> [<8003df10>] (__dabt_svc+0x70/0xa0) from [<8004a1fc>]
>> (v7_coherent_kern_range+0x20/0x80)
>> [<8004a1fc>] (v7_coherent_kern_range+0x20/0x80) from [<800424a8>]
>> (arm_syscall+0x2a0/0x2c4)
>> [<800424a8>] (arm_syscall+0x2a0/0x2c4) from [<8003e500>]
>> (ret_fast_syscall+0x0/0x3c)
> Please can you try the patch posted here:?
>
> http://lists.arm.linux.org.uk/lurker/message/20111107.173344.f738392e.en.html
I tested this patch. It fixed this bug. This bug did not occur any more.
But my system still hung at futex. I think the futex issue is another
bug.(will this patch affect the futex?)
So :
Tested-by: Huang Shijie <b32955@freescale.com>
BR
Huang Shijie
> If it fixes your problem, please consider giving a tested-by.
>
> Will
>
next prev parent reply other threads:[~2012-04-06 3:35 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 [this message]
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
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=4F7E646D.6000302@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.