From: Peter Hurley <peter@hurleysoftware.com>
To: Matthias Schiffer <mschiffer@universe-factory.net>
Cc: Ralf Baechle <ralf@linux-mips.org>,
gregkh@linuxfoundation.org, jslaby@suse.com,
linux-mips@linux-mips.org, linux-serial@vger.kernel.org,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: Nonterministic hang during bootconsole/console handover on ath79
Date: Tue, 22 Mar 2016 08:38:48 -0700 [thread overview]
Message-ID: <56F16708.4020109@hurleysoftware.com> (raw)
In-Reply-To: <56F143A8.6020601@universe-factory.net>
On 03/22/2016 06:07 AM, Matthias Schiffer wrote:
> I've tried your patch and I can't reproduce the issue anymore with it; I
> have no idea if this actually has to do something with the issue, or the
> change of the code path just hid the bug again.
>
> Regarding your other mail: with "small change", I was not talking about
> adding an additional printk; as mentioned, even changing the numbers in
> UTS_VERSION can hide the issue. I diffed a working and a broken kernel
> image, and the UTS_VERSION is really the only difference. I have no idea
> how to explain this.
If _any_ change may hide the problem, that will make it impossible
to determine if any attempted fix actually works, regardless of what
debugging method you use.
FWIW, you could still use the boot console to debug the problem by
disabling the regular command-line console.
Regards,
Peter Hurley
> (OpenWrt uses an LZMA-compressed kernel image, so
> after compression, the differences are much greater; but how these
> differences would affect the kernel after decompression eludes me)
>
> I'll continue searching for a board with accessible JTAG which exhibits
> this issue. Given the heisenbuggy nature of the issue, getting to the root
> cause is probably impossible without JTAG unless someone has an obvious
> explanation...
>
> Thanks,
> Matthias
>
next prev parent reply other threads:[~2016-03-22 15:39 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-21 23:02 Nonterministic hang during bootconsole/console handover on ath79 Matthias Schiffer
2016-03-21 23:08 ` Greg KH
2016-03-22 0:52 ` Matthias Schiffer
2016-03-22 2:51 ` Peter Hurley
2016-03-22 2:44 ` Peter Hurley
2016-03-22 13:07 ` Matthias Schiffer
2016-03-22 15:38 ` Peter Hurley [this message]
2016-03-23 17:40 ` Matthias Schiffer
2016-03-24 0:44 ` Peter Hurley
2016-03-24 2:09 ` Matthias Schiffer
2016-03-24 3:17 ` Peter Hurley
2016-03-25 12:59 ` Gabor Juhos
2016-03-25 15:24 ` Peter Hurley
2016-03-22 5:40 ` Antony Pavlov
2016-03-22 9:50 ` Matthias Schiffer
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=56F16708.4020109@hurleysoftware.com \
--to=peter@hurleysoftware.com \
--cc=gregkh@linuxfoundation.org \
--cc=jslaby@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=linux-serial@vger.kernel.org \
--cc=mschiffer@universe-factory.net \
--cc=ralf@linux-mips.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.