New issues in 2.6.35-rc{1,2}
in [Kernel]
|
From: Nico Schottelius on 14 Jun 2010 12:30 Hey devs! In both of these versions, the update of the carrier flag seems to be "different" than before (linux-2.6.34-08528-gb3f2f6c): wlan0 (iwlagn) does not recognize it's disconnected and eth0 (e1000e) does only react correctly after I restarted dhcpcd (isc): [11:20] kr:pm# dhcpcd eth0 dhcpcd: version 5.2.2 starting dhcpcd: eth0: waiting for carrier ^Cdhcpcd: received SIGINT, stopping dhcpcd: eth0: removing interface [11:20] kr:pm# dhcpcd eth0 dhcpcd: version 5.2.2 starting dhcpcd: eth0: broadcasting for a lease dhcpcd: eth0: offered 129.132.102.115 from 129.132.65.12 dhcpcd: eth0: ignoring offer of 129.132.102.115 from 129.132.57.97 dhcpcd: eth0: acknowledged 129.132.102.115 from 129.132.65.12 dhcpcd: eth0: checking for 129.132.102.115 dhcpcd: eth0: leased 129.132.102.115 for 86400 seconds dhcpcd: forking to background It's known that iwlagn has problems after suspend/resume, but new is that both nics do not notify dhcpcd that the link has gone. I'm not sure what / where broke here, just see that dhcpcd noticed it before and now doesn't anymore. Nico -- New PGP key: 7ED9 F7D3 6B10 81D7 0EC5 5C09 D7DC C8E4 3187 7DF0 Please resign, if you signed 9885188C or 8D0E27A4. Currently moving *.schottelius.org to http://www.nico.schottelius.org/ ...
From: Borislav Petkov on 14 Jun 2010 12:50 From: Nico Schottelius <nico-linux-20100614(a)schottelius.org> Date: Mon, Jun 14, 2010 at 06:19:04PM +0200 Ccing netdev. > Hey devs! > > In both of these versions, the update of the carrier flag seems > to be "different" than before (linux-2.6.34-08528-gb3f2f6c): > > wlan0 (iwlagn) does not recognize it's disconnected > and eth0 (e1000e) does only react correctly after I restarted > dhcpcd (isc): > > [11:20] kr:pm# dhcpcd eth0 > dhcpcd: version 5.2.2 starting > dhcpcd: eth0: waiting for carrier > ^Cdhcpcd: received SIGINT, stopping > dhcpcd: eth0: removing interface > [11:20] kr:pm# dhcpcd eth0 > dhcpcd: version 5.2.2 starting > dhcpcd: eth0: broadcasting for a lease > dhcpcd: eth0: offered 129.132.102.115 from 129.132.65.12 > dhcpcd: eth0: ignoring offer of 129.132.102.115 from 129.132.57.97 > dhcpcd: eth0: acknowledged 129.132.102.115 from 129.132.65.12 > dhcpcd: eth0: checking for 129.132.102.115 > dhcpcd: eth0: leased 129.132.102.115 for 86400 seconds > dhcpcd: forking to background > > It's known that iwlagn has problems after suspend/resume, > but new is that both nics do not notify dhcpcd that the link > has gone. I'm not sure what / where broke here, just see that > dhcpcd noticed it before and now doesn't anymore. Had the same dhcpcd issue here both with e1000e and bnx2 and definitely after the .35 merge window. dhclient doesn't seem affected. -- Regards/Gruss, Boris. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo(a)vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
From: Nico Schottelius on 15 Jun 2010 04:50 And another one: with 2.6.35-rc2 my system freezes after about 5 times suspend & resume. I'm now back on 2.6.34-08528-gb3f2f6c, it seems this kernel reliable suspends & resumes. Although this issue is an old one, it simply "disappeared", but has never been solved explicitly, see thread "2.6.33-2.6.34-rc5 suspend issues" on lkml, from 27 Apr 2010. Cheers, Nico -- New PGP key: 7ED9 F7D3 6B10 81D7 0EC5 5C09 D7DC C8E4 3187 7DF0 Please resign, if you signed 9885188C or 8D0E27A4. Currently moving *.schottelius.org to http://www.nico.schottelius.org/ ...
|
Pages: 1 Prev: iwlagn completely unusable with some AP since 2.6.31 Next: power: Add JZ4740 battery driver. |