From: Nico Schottelius <nico-linux-20100614@schottelius.org>
To: LKML <linux-kernel@vger.kernel.org>
Subject: New issues in 2.6.35-rc{1,2}
Date: Mon, 14 Jun 2010 18:19:04 +0200 [thread overview]
Message-ID: <20100614161904.GE31910@schottelius.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1309 bytes --]
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/ ...
[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]
next reply other threads:[~2010-06-14 16:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-14 16:19 Nico Schottelius [this message]
2010-06-14 16:43 ` New issues in 2.6.35-rc{1,2} Borislav Petkov
2010-06-15 8:43 ` Nico Schottelius
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=20100614161904.GE31910@schottelius.org \
--to=nico-linux-20100614@schottelius.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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