Re: [PATCH] fix ACK processing after netlink_dump_start
On Tue, Oct 23, 2007 at 06:40:23PM +0400, Denis V. Lunev wrote: Revert to original netlink behavior. Do not reply with ACK if the netlink dump has bees successfully started. libnl has been broken by the cd40b7d3983c708aabe3d3008ec64ffce56d33b0 The following command reproduce the problem: /nl-route-get 192.168.1.1 Signed-off-by: Denis V. Lunev [EMAIL PROTECTED] Network Manager works correctly here with this patch applied against Linus's current -git. (Sorry for the lack of response before -- I think I forgot to ask to be CC'd on replies, and found the discussion of this in archives only this morning.) -- Joseph Fannin [EMAIL PROTECTED] - To unsubscribe from this list: send the line unsubscribe netdev in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Regression in current git - Network Manager fails (bisected)
Network Manager (the freedesktop.org one) fails to work with Linus's current git on a couple of different boxes I have here. All the boxes have different NIC types, with different drivers. I've bisected it down to cd40b7d3983c708aabe3d3008ec64ffce56d33b0 , [NET]: make netlink user - kernel interface synchronious. I've double checked this by testing the kernel as of the immediately previous commit; Network Manager works with that one, as it did on all my machines in 2.6.23-mm1. The netlink change seems to confuse N-M, and it somehow decides that there's no link beat, so doesn't try to bring up the interface. If I run ifconfig eth0 up, N-M will decide there's a carrier after all and takes over. Ethtool detects the link state correctly even with the interface down. If I down the interface again with ifconfig, N-M brings it right back up without a problem, but if I kill N-M, it'll down the interface before it exits, and fail in the same way as before when restarted. N-M also emits this error: -- Error: Invalid message: type=DONE length=20 flags=MULTI sequence-nr=1193012574 pid=1185943630 ...which it doesn't do on kernels where it works normally. strace'ing NetworkManager shows that it prints that message just after talking over a netlink socket. Networking otherwise works fine here with the latest git and N-M, if I use the ifconfig trick to get the link up. -- Joseph Fannin [EMAIL PROTECTED] - To unsubscribe from this list: send the line unsubscribe netdev in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: bcm43xx regression 2.6.19rc3 - rc5, rtnl_lock trouble?
On Wed, Nov 15, 2006 at 11:01:00AM -0800, Ray Lee wrote: I've come back to my laptop being mostly dead after hours of it being off on its own (twice now). Mostly dead meaning the keyboard is nearly non-responsive, but the mouse works great (I'm in X, of course). I say 'nearly dead' as sysrq-t,b works, so I'm sorta stumped there. (x-session seems to use netlink, so perhaps that's the connection? ctrl-alt-f[1-7] don't do anything, however.) This sounds like what my laptop was doing in -rc5, though mine didn't take hours to start acting up. I *think* it was the MSI troubles, causing interrupts to get lost forever. Anyway, it went away in -rc6. I don't have the broadcom hardware. -- Joseph Fannin [EMAIL PROTECTED] || [EMAIL PROTECTED] signature.asc Description: Digital signature
