On Tue, 24 Aug 2010 22:38:39 -0700 (PDT) David Brownell <david-b@xxxxxxxxxxx> wrote: > > > --- On Tue, 8/24/10, Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx> wrote: > > > From: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx> > > Subject: Re: [Bugme-new] [Bug 16821] New: g ether no carrier while it is > > To: netdev@xxxxxxxxxxxxxxx, linux-usb@xxxxxxxxxxxxxxx > > Cc: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx, bugme-daemon@xxxxxxxxxxxxxxxxxxx, "Greg KH" <greg@xxxxxxxxx>, "David Brownell" <david-b@xxxxxxxxxxx>, public.avatar@xxxxxxxxx > > Date: Tuesday, August 24, 2010, 4:40 PM > > > > (switched to email. Please respond via emailed > > reply-to-all, not via the > > bugzilla web interface). > > > > On Mon, 23 Aug 2010 06:24:16 GMT > > bugzilla-daemon@xxxxxxxxxxxxxxxxxxx > > wrote: > > > > > https://bugzilla.kernel.org/show bug.cgi?id=16821 > > > > > > Summary: > > g ether no carrier while it is > > > Product: > > Networking > > > Version: 2.5 > > > Kernel Version: 2.6.3(2 - ok, > > 3?, 4-6 - fail) > > > Platform: > > All > > > OS/Version: > > Linux > > > > > Tree: Mainline > > > > > Status: NEW > > > Severity: > > blocking > > > Priority: > > P1 > > > Component: Other > > > AssignedTo: acme@xxxxxxxxxxxxxxxxxx > > > ReportedBy: public.avatar@xxxxxxxxx > > > Regression: Yes > > > > > > > > > After successfully loaded g ether module (with > > use eem=0) usb device appears. > > > If I configure it at host as ifconfig usb0 blah bah, > > than network present, all > > > ok. > > > In windows (with RNDIS config), and in linux with > > bridge it looks to CARRIER > > > state. I get in ip addr state DOWN, NO-CARRIER. That's > > why g ether usb device > > > in bridge and windows don't work at all. > > > > So g ether broke after 2.6.32? > > > > Nobody really seems to do much with that USB driver. > > That's changed then. There used to be boxes that > relied on it for their network connectivity... I meant not much development happens there. > Adding EEM support was something... I think the > issue might be driver changes since last it was > seriously tested in bridge configs (for which > the link state, such as carrier, matters LOTS.) Thanks. Let's cc Brian. > > > I wonder if some > > changes in core networking could have triggered this? > > Wouldn't be my first thought; but might be. > > ISTR getting link/carrier state to behave in > the first place (with just CDC and RNDIS) was > complex. If it wasn't carefully re-tested after > EEM was added, breakage may have been overlooked. > > - Dave > -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
