From: Neil Armstrong <narmstrong@baylibre.com>
To: "zhangn1985@outlook.com" <zhangn1985@outlook.com>,
"linux-amlogic@lists.infradead.org"
<linux-amlogic@lists.infradead.org>
Subject: Re: S905x (VIM) ramdon crashes, maybe due to display driver.
Date: Mon, 5 Oct 2020 14:52:38 +0200 [thread overview]
Message-ID: <79305527-ca16-598f-2963-4b87c106892b@baylibre.com> (raw)
In-Reply-To: <SYCPR01MB37764A52D0614522A279AC76CD0C0@SYCPR01MB3776.ausprd01.prod.outlook.com>
Hi,
On 05/10/2020 14:42, zhangn1985@outlook.com wrote:
> 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.
Your report is extremely vague, could you be more precise about which patch causes the issue ?
Does it still occur on more recent stable kernels ?
Please catch the crash on the console, otherwise we couldn't help...
Neil
>
>
> [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
next prev parent reply other threads:[~2020-10-05 12:52 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 [this message]
[not found] ` <6d14a14f-d212-d2b3-794d-b52c60a68c0c@yandex.ru>
2020-10-05 13:45 ` 回复: " 张 宁
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=79305527-ca16-598f-2963-4b87c106892b@baylibre.com \
--to=narmstrong@baylibre.com \
--cc=linux-amlogic@lists.infradead.org \
--cc=zhangn1985@outlook.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
all inboxes | Powered by JetHome®