[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <063D6719AE5E284EB5DD2968C1650D6D17276F36@AcuExch.aculab.com>
Date: Thu, 17 Jul 2014 15:27:55 +0000
From: David Laight <David.Laight@...LAB.COM>
To: 'Tom Gundersen' <teg@...m.no>
CC: Veaceslav Falico <vfalico@...il.com>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
"David S. Miller" <davem@...emloft.net>,
"Jason Baron" <jbaron@...mai.com>,
Eric Dumazet <edumazet@...gle.com>,
Vlad Yasevich <vyasevic@...hat.com>,
stephen hemminger <stephen@...workplumber.org>,
"Jerry Chu" <hkchu@...gle.com>,
Ben Hutchings <bhutchings@...arflare.com>
Subject: RE: [PATCH v2 net-next 0/2] net: print net_device name/state more
often
From: Tom Gundersen
> On Thu, Jul 17, 2014 at 4:48 PM, David Laight <David.Laight@...lab.com> wrote:
...
> > While you've got this code out on the operating table what about:
> > 1) Tracing the renames into the kernel message buffer.
>
> udev will log to dmesg what renames it does.
Not on the systems I'm looking at (ubuntu 13.10 server).
Possibly the trace level is such that they get dropped.
David
Powered by blists - more mailing lists