From: Joe Perches <joe@perches•com>
To: Russell King - ARM Linux <linux@arm•linux.org.uk>,
netdev <netdev@vger•kernel.org>
Cc: Robert Jarzmik <robert.jarzmik@free•fr>,
Lee Jones <lee.jones@linaro•org>,
Mark Rutland <mark.rutland@arm•com>,
devicetree@vger•kernel.org, Samuel Ortiz <sameo@linux•intel.com>,
Pawel Moll <pawel.moll@arm•com>,
Ian Campbell <ijc+devicetree@hellion•org.uk>,
Dmitry Eremin-Solenikov <dbaryshkov@gmail•com>,
linux-kernel@vger•kernel.org,
Haojian Zhuang <haojian.zhuang@gmail•com>,
Rob Herring <robh+dt@kernel•org>, Arnd Bergmann <arnd@arndb•de>,
linux-arm-kernel@lists•infradead.org,
Kumar Gala <galak@codeaurora•org>,
Daniel Mack <daniel@zonque•org>
Subject: unclear ipv6 redirect message (was Re: [PATCH v3 2/3] mfd: lubbock_io: add lubbock_io board)
Date: Wed, 21 Jan 2015 08:05:21 -0800 [thread overview]
Message-ID: <1421856321.10574.13.camel@perches.com> (raw)
In-Reply-To: <20150121094453.GO26493@n2100.arm.linux.org.uk>
(adding netdev)
On Wed, 2015-01-21 at 09:44 +0000, Russell King - ARM Linux wrote:
> On Wed, Jan 21, 2015 at 08:46:29AM +0100, Robert Jarzmik wrote:
> > Russell King - ARM Linux <linux@arm•linux.org.uk> writes:
> >
> > > What I'd suggest (and always have done) is:
> > >
> > > dev_err(&pdev->dev, "couldn't request main irq%d: %d\n",
> > > irq, ret);
> > I like it, it's even more compact, I'll use it for next patch version.
>
> BTW, this is an example why I have the policy of always ensuring that
> the kernel messages print sufficient diagnostics. Right now, I have
> a problem - since I rebooted my firewall a few nights ago, I now get
> on one of my machines:
>
> rt6_redirect: source isn't a valid nexthop for redirect target
>
> and it spews that for a few minutes every 26 hours or so. No further
> information, and it leaves you wondering "well, what was the invalid
> next hop? What was the source?"
>
> Pretty much the only way to try and find out is to leave a tcpdump or
> wireshark running for 24 hours to try and get a dump - which is not
> that easy if you don't have lots of disk space. So, right now, I have
> no way to diagnose the above.
>
> If it printed that information, then I'd be able to see what the
> addresses were, and I'd probably be able to come up with a tcpdump
> filter which didn't involve logging all IPv6 traffic.
>
> Kernel messages need to be smart. If not, they might as well just be
> "The kernel encountered a problem. Abort, Retry or Fail?"
>
next parent reply other threads:[~2015-01-21 16:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1421406010-14851-1-git-send-email-robert.jarzmik@free.fr>
[not found] ` <1421406010-14851-2-git-send-email-robert.jarzmik@free.fr>
[not found] ` <20150119091705.GG21886@x1>
[not found] ` <87ppaah9k5.fsf@free.fr>
[not found] ` <20150120102919.GP5767@x1>
[not found] ` <20150120115658.GJ26493@n2100.arm.linux.org.uk>
[not found] ` <873874fuei.fsf@free.fr>
[not found] ` <20150121094453.GO26493@n2100.arm.linux.org.uk>
2015-01-21 16:05 ` Joe Perches [this message]
[not found] ` <1421856321.10574.13.camel-6d6DIl74uiNBDgjK7y7TUQ@public.gmane.org>
2015-01-21 16:11 ` unclear ipv6 redirect message (was Re: [PATCH v3 2/3] mfd: lubbock_io: add lubbock_io board) Russell King - ARM Linux
2015-01-21 16:40 ` Joe Perches
2015-01-21 16:46 ` Russell King - ARM Linux
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=1421856321.10574.13.camel@perches.com \
--to=joe@perches$(echo .)com \
--cc=arnd@arndb$(echo .)de \
--cc=daniel@zonque$(echo .)org \
--cc=dbaryshkov@gmail$(echo .)com \
--cc=devicetree@vger$(echo .)kernel.org \
--cc=galak@codeaurora$(echo .)org \
--cc=haojian.zhuang@gmail$(echo .)com \
--cc=ijc+devicetree@hellion$(echo .)org.uk \
--cc=lee.jones@linaro$(echo .)org \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux@arm$(echo .)linux.org.uk \
--cc=mark.rutland@arm$(echo .)com \
--cc=netdev@vger$(echo .)kernel.org \
--cc=pawel.moll@arm$(echo .)com \
--cc=robert.jarzmik@free$(echo .)fr \
--cc=robh+dt@kernel$(echo .)org \
--cc=sameo@linux$(echo .)intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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