From: Ben Hutchings <ben@decadent.org.uk>
To: Oliver Neukum <oliver@neukum.name>
Cc: netdev@vger.kernel.org, bugzilla-daemon@bugzilla.kernel.org,
bugme-daemon@bugzilla.kernel.org, speedyboyinovator@hotmail.com,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [Bugme-new] [Bug 14791] New: Something has been broken in the network stack this week
Date: Thu, 17 Dec 2009 00:03:31 +0000 [thread overview]
Message-ID: <1261008211.2284.16.camel@localhost> (raw)
In-Reply-To: <20091216154018.e3baaed6.akpm@linux-foundation.org>
[-- Attachment #1: Type: text/plain, Size: 1976 bytes --]
speedyboyinovator@hotmail.com wrote (via Bugzilla):
> > Apparently something has been broken in the network stack this week
> >
> > Hi. This is my first bug/issue report, so understand any mistake or n00b thing
> > I make here. And sorry for the bad english ;)
> >
> > It looks like that from the 2.6.32 release, to the git commit
> > 2.6.32-05254-g3067e02 (i've compiled it in Dec 10 11:39:26 (Brazilian TZ)
> > 2009), something weird happened ;)
> >
> > I've used the USB_NET_CDCETHER for 2 years now, and it always worked.
> > But when I rebooted to my new kernel 2.6.32-05254-g3067e02, from the 2.6.32, it
> > just dont get connected.
> >
> > [ 16.683465] ADDRCONF(NETDEV_UP): eth1: link is not ready
> > [ 94.854539] ADDRCONF(NETDEV_UP): eth1: link is not ready
> >
> > There's no symptom of anything wrong. And even restarting the modem and then
> > reconnecting the USB cable, it does'nt work.
> >
> > Then I reboot to the 2.6.32 one, and it takes just one dhclient command and 1
> > second to be online again.
This may well be due to this change, which sets the initial assumed link
state to be down, not up:
commit 37e8273cd30592d3a82bcb70cbb1bdc4eaeb6b71
Author: Ben Hutchings <ben@decadent.org.uk>
Date: Wed Nov 4 15:29:52 2009 +0000
usbnet: Set link down initially for drivers that update link state
Some usbnet drivers update link state while others do not due to
hardware limitations. Add a flag to distinguish those that do, and
set the link down initially for their devices.
This is intended to fix this bug: http://bugs.debian.org/444043
Signed-off-by: Ben Hutchings <ben@decadent.org.uk>
Signed-off-by: David S. Miller <davem@davemloft.net>
Perhaps cdc_ether should poll the hardware to get the initial link
state?
Ben.
--
Ben Hutchings
Hoare's Law of Large Problems:
Inside every large problem is a small problem struggling to get out.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
prev parent reply other threads:[~2009-12-17 0:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-14791-10286@http.bugzilla.kernel.org/>
2009-12-16 23:40 ` [Bugme-new] [Bug 14791] New: Something has been broken in the network stack this week Andrew Morton
2009-12-17 0:03 ` Ben Hutchings [this message]
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=1261008211.2284.16.camel@localhost \
--to=ben@decadent.org.uk \
--cc=akpm@linux-foundation.org \
--cc=bugme-daemon@bugzilla.kernel.org \
--cc=bugzilla-daemon@bugzilla.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=oliver@neukum.name \
--cc=speedyboyinovator@hotmail.com \
/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;
as well as URLs for NNTP newsgroup(s).