mirror of https://lore.kernel.org/linux-amlogic/
 help / color / mirror / Atom feed
From: "张 宁" <zhangn1985@outlook.com>
To: Oleg <balbes-150@yandex.ru>,
	"linux-amlogic@lists.infradead.org"
	<linux-amlogic@lists.infradead.org>
Subject: 回复: S905x (VIM) ramdon crashes, maybe due to display driver.
Date: Mon, 5 Oct 2020 13:45:10 +0000	[thread overview]
Message-ID: <SYCPR01MB3776EFAD4209225E2F4FBE31CD0C0@SYCPR01MB3776.ausprd01.prod.outlook.com> (raw)
In-Reply-To: <6d14a14f-d212-d2b3-794d-b52c60a68c0c@yandex.ru>

@Oleg

I build it on VIM, natively build kernel, code in NFS, about 12MB/s access bindwidth, using WIFI, and on board 100Mbps ethernet even slower. 
 
And I use debian’s kernel build scripts to build, fully build binary-arch target will take about 18h, mostly due to network, because thermal is about 40, with fun.

may be use usb storage will be faster.

@Neil
after review the patches I applied to 5.9-rc7, no display related patches.  and 5.9-rc7 still has this issue.

I understand report issue this way which is no help for debug.
I will try to narrow down to find out the patches between 5.6~5.7,  use chroot-arm64-with-qemu on powerful x86_64 build server, this will take 6h on i7-4770K, with local code storage, for 1 build.

BR.
Ning.

 



发件人: Oleg <balbes-150@yandex.ru>
发送时间: 2020年10月5日 13:06
收件人: zhangn1985@outlook.com <zhangn1985@outlook.com>
主题: Re: S905x (VIM) ramdon crashes, maybe due to display driver. 
 
Hi
Did I understand correctly that it takes 3 days to build the kernel directly on the device itself (ARM)?????


hi,

I observed VIM ramdon crashes from 5.7 kernel with WIP patches[1] from this mail list. 

I have tried to find better power supply,  remove case,   install cooling fun, disable Xserver. VIM still ramdon crashes.

Thus I think this maybe VIM is broken, maybe due to thermal.

I don't have a chance to get the log, even no log print to console, when crash happens.

these days, I made it an arm64 build server, without connect a HDMI display. it runs very well, build kernel 3 days without any crash.

from the phenomenon I think some hidden issues may in display driver.


[1]: https://github.com/zhangn1985/linux/commits/master/debian/patches/khadas

BR.

_______________________________________________
linux-amlogic mailing list
linux-amlogic@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-amlogic

_______________________________________________
linux-amlogic mailing list
linux-amlogic@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-amlogic

      parent reply	other threads:[~2020-10-05 17:36 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-05 12:42 zhangn1985
2020-10-05 12:52 ` Neil Armstrong
     [not found] ` <6d14a14f-d212-d2b3-794d-b52c60a68c0c@yandex.ru>
2020-10-05 13:45   ` 张 宁 [this message]

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=SYCPR01MB3776EFAD4209225E2F4FBE31CD0C0@SYCPR01MB3776.ausprd01.prod.outlook.com \
    --to=zhangn1985@outlook.com \
    --cc=balbes-150@yandex.ru \
    --cc=linux-amlogic@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®