From: Liang Yang <liang.yang@amlogic.com>
To: Martin Blumenstingl <martin.blumenstingl@googlemail.com>
Cc: Matthew Wilcox <willy@infradead.org>, <mhocko@suse.com>,
<linux@armlinux.org.uk>, <linux-kernel@vger.kernel.org>,
<rppt@linux.ibm.com>, <linux-mm@kvack.org>,
<linux-mtd@lists.infradead.org>,
<linux-amlogic@lists.infradead.org>, <akpm@linux-foundation.org>,
<linux-arm-kernel@lists.infradead.org>
Subject: Re: 32-bit Amlogic (ARM) SoC: kernel BUG in kfree()
Date: Fri, 29 Mar 2019 15:44:30 +0800 [thread overview]
Message-ID: <79b81748-8508-414f-c08a-c99cb4ae4b2a@amlogic.com> (raw)
In-Reply-To: <CAFBinCDHmuNZxuDf3pe2ij6m8aX2fho7L+B9ZMaMOo28tPZ62Q@mail.gmail.com>
Hi Martin,
On 2019/3/29 2:03, Martin Blumenstingl wrote:
> Hi Liang,
[......]
>> I don't think it is caused by a different NAND type, but i have followed
>> the some test on my GXL platform. we can see the result from the
>> attachment. By the way, i don't find any information about this on meson
>> NFC datasheet, so i will ask our VLSI.
>> Martin, May you reproduce it with the new patch on meson8b platform ? I
>> need a more clear and easier compared log like gxl.txt. Thanks.
> your gxl.txt is great, finally I can also compare my own results with
> something that works for you!
> in my results (see attachment) the "DATA_IN [256 B, force 8-bit]"
> instructions result in a different info buffer output.
> does this make any sense to you?
>
I have asked our VLSI designer for explanation or simulation result by
an e-mail. Thanks.
next prev parent reply other threads:[~2019-03-29 7:44 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-21 20:17 Martin Blumenstingl
2019-03-21 21:44 ` Matthew Wilcox
2019-03-22 21:07 ` Martin Blumenstingl
2019-03-25 10:04 ` Liang Yang
2019-03-25 18:31 ` Martin Blumenstingl
2019-03-27 8:53 ` Liang Yang
2019-03-28 18:03 ` Martin Blumenstingl
2019-03-29 7:44 ` Liang Yang [this message]
2019-04-05 4:30 ` Martin Blumenstingl
2019-04-10 11:08 ` Liang Yang
2019-04-10 17:54 ` Martin Blumenstingl
2019-04-11 3:00 ` Liang Yang
2019-06-08 20:00 ` Martin Blumenstingl
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=79b81748-8508-414f-c08a-c99cb4ae4b2a@amlogic.com \
--to=liang.yang@amlogic.com \
--cc=akpm@linux-foundation.org \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-mtd@lists.infradead.org \
--cc=linux@armlinux.org.uk \
--cc=martin.blumenstingl@googlemail.com \
--cc=mhocko@suse.com \
--cc=rppt@linux.ibm.com \
--cc=willy@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox