[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <56D9DCD2.2090009@boundarydevices.com>
Date: Fri, 4 Mar 2016 12:06:58 -0700
From: Troy Kisky <troy.kisky@...ndarydevices.com>
To: Joe Perches <joe@...ches.com>, Fugang Duan <fugang.duan@....com>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
"davem@...emloft.net" <davem@...emloft.net>,
"b38611@...escale.com" <b38611@...escale.com>
Cc: "fabio.estevam@...escale.com" <fabio.estevam@...escale.com>,
"l.stach@...gutronix.de" <l.stach@...gutronix.de>,
"andrew@...n.ch" <andrew@...n.ch>,
"tremyfr@...il.com" <tremyfr@...il.com>,
"linux@....linux.org.uk" <linux@....linux.org.uk>,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>,
"laci@...ndarydevices.com" <laci@...ndarydevices.com>,
"shawnguo@...nel.org" <shawnguo@...nel.org>,
"johannes@...solutions.net" <johannes@...solutions.net>,
"stillcompiling@...il.com" <stillcompiling@...il.com>,
"sergei.shtylyov@...entembedded.com"
<sergei.shtylyov@...entembedded.com>,
"arnd@...db.de" <arnd@...db.de>
Subject: Re: [PATCH net-next V2 13/16] net: fec: print more debug info in
fec_timeout
On 3/4/2016 10:35 AM, Joe Perches wrote:
> On Fri, 2016-03-04 at 09:05 -0700, Troy Kisky wrote:
>> On 3/4/2016 3:06 AM, Fugang Duan wrote:
>>> From: Troy Kisky <troy.kisky@...ndarydevices.com> Sent: Thursday, February 25, 2016 8:37 AM
> []
>>>> Print the current interrupt flags and mask and the interrupt state during the last
>>>> interrupt in fec_timeout.
> []
>>>> diff --git a/drivers/net/ethernet/freescale/fec_main.c
> []
>>>> @@ -1107,6 +1107,9 @@ fec_timeout(struct net_device *ndev)
>>>> int i;
>>>> uint events = 0;
>>>>
>>>> + pr_err("%s: last=%x %x, mask %x\n", __func__, fep->last_ievents,
>>>> + readl(fep->hwp + FEC_IEVENT), readl(fep->hwp + FEC_IMASK));
>>>> +
>>> pr_err() -> netdev_err()
>> Sounds good
>
> This seems like debugging information rather than
> an error a user can do anything with and if there's
> a timeout, how likely is it that the hardware is
> hosed and this would repetitively and unnecessarily
> fill up logs?
>
> So maybe netdev_dbg and net_ratelimit() too.
>
> if (net_ratelimit()
> netdev_<level>(etc...)
>
>
This patch hasn't been helpful to me in quite a while. I'll just drop it.
I know where to get it if I need it again.
Thanks
Troy
Powered by blists - more mailing lists