From: "Huang, Tao" <huangtao@rock-chips.com>
To: "Paweł Jarosz" <paweljarosz3691@gmail.com>,
heiko@sntech.de, linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org
Subject: Re: [PATCH] ARM: dts: rockchip: Reserve unusable memory region on rk3066
Date: Thu, 13 Oct 2016 15:12:38 +0800 [thread overview]
Message-ID: <e3746f9a-084e-163e-a412-1a1fc66926d5@rock-chips.com> (raw)
In-Reply-To: <149df5ee-3478-6d15-bb76-47becac146e9@gmail.com>
Hi, Paweł:
On 2016年10月10日 17:11, Paweł Jarosz wrote:
> W dniu 10.10.2016 o 09:18, Huang, Tao pisze:
>> Our IC guy need us tell them which master can not access such area, DMA
>> or EMMC Controller or GPU, etc? Could you tell me how to reproduce such
>> issue?
>> And we can confirm CPU core can access this memory through /dev/mem and
>> the test board is 1GB too. Personally, I don't think RK3066 has such
>> limit because when we verify this chip, we don't found such limit at all.
>>
>> Thanks,
>> Huang, Tao
> I'm getting this on Ubuntu 16.04 with mainline kernel.
> My board always freezes when i type: "memtester 800M"
>
We try run memtest 800M with Linux kernel 4.8, which killed by OOM.
But if we run:
# memtester -p 0x9F000000 16K 1
memtester version 4.3.0 (32-bit)
Copyright (C) 2001-2012 Charles Cazabon.
Licensed under the GNU General Public License version 2 (only).
pagesize is 4096
pagesizemask is 0xfffff000
want 0MB (16384 bytes)
Loop 1/1:
Stuck Address : ok
Random Value : ok
Compare XOR : ok
Compare SUB : ok
Compare MUL : ok
Compare DIV : ok
Compare OR : ok
Compare AND : ok
Sequential Increment: ok
Solid Bits : ok
Block Sequential : ok
Checkerboard : ok
Bit Spread : ok
Bit Flip : ok
Walking Ones : ok
Walking Zeroes : ok
8-bit Writes : ok
16-bit Writes : ok
So these memory should be fine to CPU core. Maybe your system just
freeze because out of memory.
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2016-10-13 7:12 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-01 14:09 [PATCH] ARM: dts: rockchip: Reserve unusable memory region on rk3066 =?UTF-8?q?Pawe=C5=82=20Jarosz?=
2016-10-01 18:17 ` Mark Rutland
2016-10-01 19:18 ` Heiko Stuebner
2016-10-01 19:59 ` Paweł Jarosz
2016-10-03 10:20 ` Mark Rutland
2016-10-03 10:54 ` Heiko Stuebner
2016-10-04 11:56 ` Paweł Jarosz
[not found] ` <81d1fb8b-ee0e-35a7-77db-5e15c3f46449-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2016-10-04 18:56 ` Heiko Stübner
2016-10-05 2:27 ` Huang, Tao
[not found] ` <6239b970-09d3-f7ee-e6f5-c019eaedb725-TNX95d0MmH7DzftRWevZcw@public.gmane.org>
2016-10-05 6:09 ` Paweł Jarosz
[not found] ` <f8aba48d-6c69-b246-4cb2-48a2770c80e4-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2016-10-10 7:18 ` Huang, Tao
[not found] ` <67831fd0-76af-a793-0b2f-958e45633fe8-TNX95d0MmH7DzftRWevZcw@public.gmane.org>
2016-10-10 9:11 ` Paweł Jarosz
2016-10-13 7:12 ` Huang, Tao [this message]
[not found] ` <e3746f9a-084e-163e-a412-1a1fc66926d5-TNX95d0MmH7DzftRWevZcw@public.gmane.org>
2016-10-13 8:55 ` Paweł Jarosz
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=e3746f9a-084e-163e-a412-1a1fc66926d5@rock-chips.com \
--to=huangtao@rock-chips.com \
--cc=heiko@sntech.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=paweljarosz3691@gmail.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox