From: andrew@lunn.ch (Andrew Lunn)
To: linux-arm-kernel@lists.infradead.org
Subject: [v2,1/1] ARM: orion5x: use mac_pton() helper
Date: Thu, 22 Feb 2018 22:42:37 +0100 [thread overview]
Message-ID: <20180222214237.GH28112@lunn.ch> (raw)
In-Reply-To: <099870d3-e2bd-aad9-d526-5438596bb575@the2masters.de>
On Thu, Feb 22, 2018 at 06:45:51PM +0100, Stefan Hellermann wrote:
> Hi!
>
> My QNAP TS-209 NAS Device is crashing with the following commit, which went
> in the kernel as commit 4904dbda41c860fd117b20f3c48adb2780eee37e
>
> I cannot provide a boot log, the device panics before enabling the serial
> console.
Hi Stefan
Did you try earlyprintk? You might need to recompile your kernel to
enable it.
Looking at the code, i don't see anything obviously wrong. So i think
i would start by looking how many times it goes through the loop in
qnap_tsx09_find_mac_addr() with this patch reverted, and what address
it finds the MAC address at.
Then see what happens with the current crashing code. Is it failing to
recognise the MAC address, and so keep looping around?
Thanks
Andrew
next prev parent reply other threads:[~2018-02-22 21:42 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-02 14:12 [PATCH v2 1/1] ARM: orion5x: use mac_pton() helper Andy Shevchenko
2015-10-13 11:27 ` Detlef Vollmann
2015-10-15 7:51 ` Gregory CLEMENT
2018-02-22 17:45 ` [v2,1/1] " Stefan Hellermann
2018-02-22 21:42 ` Andrew Lunn [this message]
2018-02-22 23:18 ` Stefan Hellermann
2018-02-22 23:34 ` Andrew Lunn
2018-02-23 10:09 ` Andy Shevchenko
2018-02-23 15:01 ` Andrew Lunn
2018-02-23 15:18 ` Andy Shevchenko
2018-02-23 15:51 ` Andrew Lunn
2018-02-23 16:36 ` Stefan Hellermann
2018-02-23 16:57 ` Andy Shevchenko
2018-02-23 17:23 ` Andrew Lunn
2018-02-23 18:20 ` Alexey Dobriyan
2018-02-23 20:17 ` [PATCH] net: Allow mac_pton() to work on non-NULL terminated strings Stefan Hellermann
2018-02-23 20:27 ` Andrew Lunn
2018-02-23 20:41 ` Alexey Dobriyan
2018-02-23 20:51 ` Andy Shevchenko
2018-02-26 18:37 ` David Miller
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=20180222214237.GH28112@lunn.ch \
--to=andrew@lunn.ch \
--cc=linux-arm-kernel@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;
as well as URLs for NNTP newsgroup(s).