From: joe@perches•com (Joe Perches)
To: linux-arm-kernel@lists•infradead.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 prev parent reply other threads:[~2015-01-21 16:05 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-16 11:00 [PATCH v3 1/3] dt-bindings: mfd: add lubbock-io binding Robert Jarzmik
2015-01-16 11:00 ` [PATCH v3 2/3] mfd: lubbock_io: add lubbock_io board Robert Jarzmik
2015-01-19 9:17 ` Lee Jones
2015-01-19 19:09 ` Robert Jarzmik
2015-01-20 10:29 ` Lee Jones
2015-01-20 11:56 ` Russell King - ARM Linux
2015-01-21 7:46 ` Robert Jarzmik
2015-01-21 8:16 ` Lee Jones
2015-01-21 8:27 ` Robert Jarzmik
2015-01-21 12:35 ` Lee Jones
2015-01-21 13:02 ` Russell King - ARM Linux
2015-01-21 13:36 ` robert.jarzmik at free.fr
2015-01-21 15:10 ` Lee Jones
2015-01-21 19:22 ` Robert Jarzmik
2015-01-21 9:47 ` Russell King - ARM Linux
2015-01-21 9:44 ` Russell King - ARM Linux
2015-01-21 16:05 ` Joe Perches [this message]
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
2015-01-16 11:00 ` [PATCH v3 3/3] ARM: pxa: lubbock: use new lubbock_io driver Robert Jarzmik
2015-01-19 8:35 ` [PATCH v3 1/3] dt-bindings: mfd: add lubbock-io binding Lee Jones
2015-01-19 19:29 ` Robert Jarzmik
2015-01-20 10:18 ` Lee Jones
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=linux-arm-kernel@lists$(echo .)infradead.org \
/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