linux-kernel - Re: [GIT] Networking

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <1367883316.22645.2.camel@dcbw.foobar.com>
Date:	Mon, 06 May 2013 18:35:16 -0500
From:	Dan Williams <dcbw@...hat.com>
To:	Linus Torvalds <torvalds@...ux-foundation.org>
Cc:	David Miller <davem@...emloft.net>,
	hayeswang <hayeswang@...ltek.com>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Network Development <netdev@...r.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [GIT] Networking

On Thu, 2013-05-02 at 15:22 -0500, Dan Williams wrote:
> On Thu, 2013-05-02 at 14:17 -0500, Dan Williams wrote:
> > On Thu, 2013-05-02 at 11:53 -0700, Linus Torvalds wrote:
> > > On Thu, May 2, 2013 at 11:52 AM, Linus Torvalds
> > > <torvalds@...ux-foundation.org> wrote:
> > > >
> > > > but for some reason in the bad case NM just doesn't react past the
> > > > "carrier now ON" part.
> > > 
> > > Grr. That was much more readable while editing, then gmail ended up
> > > doing its "smart line wrap" thing and my nice long lines became a
> > > mess. I think you can still figure it out,
> > 
> > Yeah, the dump is good, and it seems to point to a problem in NM for
> > now.  I'm investigating.
> 
> If you don't mind helping me confirm/reject a theory, would you mind:
> 
> 1) drop "level=debug" into the [logging] section
> of /etc/NetworkManager/NetworkManager.conf (create the section if it
> doesn't exist)
> 
> 2) reboot (or just rmmod/modprobe r8169 if that's enough to trigger it)
> 
> 3) grab syslog and send it to me (privately if you wish)

Spent a while trying to reproduce this on a tg3 today, twiddling the
carrier from the code, but failed to do so...  if you're at all able to
get the debug logs here as mentioned here, that would help greatly.

Contrary to the suggestion above, changing the log level in
NetworkManager.conf does not immediately start logging in that level,
you do need to restart NM.  So with that in mind, I'd suggest a full
reboot of the system just to make sure we have the exact same situation
as when you experience the problem.

(I'm still mystified how the netdev features thing "fixes" this
though...)

Thanks!
Dan

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/