From: Dongpo Li <lidongpo@hisilicon.com>
To: Marty Plummer <netz.kernel@gmail.com>
Cc: <netdev@vger.kernel.org>, <yisen.zhuang@huawei.com>,
<salil.mehta@huawei.com>
Subject: Re: net: hix5hd2_gmac uninitialized net_device
Date: Mon, 13 Feb 2017 09:25:38 +0800 [thread overview]
Message-ID: <58A10B12.8050400@hisilicon.com> (raw)
In-Reply-To: <20170211005132.xdk2d7etb732scqo@tha-monstah.mydomain>
On 2017/2/11 8:51, Marty Plummer wrote:
> On Fri, Feb 10, 2017 at 06:21:35PM +0800, Dongpo Li wrote:
>> I think the error "No irq resource" happened for some other reason, has no relation with
>> the info "(unnamed net_device) (uninitialized):".
>> You can add more debug info to find bug.
> Do you have any particular suggestions as to what to check out, or is
> this just a general 'debug more' instruction?
I haven't encountered such a problem. So it needs you to debug what happens.
>> Yes, I agree with you that the ndev has not been initialized completely,
>> because the function "register_netdev" has not been called yet.
>> It's better to use the "dev_err" to replace the "netdev_err".
>>
> Ah, I see. So, prior to line 1266's call to register_netdev, it will
> always be uninitialized and unnamed, regardless of what is or isn't
> right elsewhere. Good to know. So, I could replace these netdev_err
> with dev_err for now, up until that point, so I can get a bit more info,
> yes?
Yes.
Regards,
Dongpo
.
next prev parent reply other threads:[~2017-02-13 1:25 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-10 7:41 Marty Plummer
2017-02-10 7:41 ` (unknown) Marty Plummer
2017-02-10 7:45 ` net: hix5hd2_gmac uninitialized net_device Marty Plummer
2017-02-10 10:21 ` Dongpo Li
2017-02-11 0:51 ` Marty Plummer
2017-02-13 1:25 ` Dongpo Li [this message]
2017-02-14 23:59 ` Marty Plummer
2017-02-15 6:18 ` Dongpo Li
2017-02-16 18:45 ` Marty Plummer
2017-02-17 1:32 ` Dongpo Li
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=58A10B12.8050400@hisilicon.com \
--to=lidongpo@hisilicon.com \
--cc=netdev@vger.kernel.org \
--cc=netz.kernel@gmail.com \
--cc=salil.mehta@huawei.com \
--cc=yisen.zhuang@huawei.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 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.