netdev - Re: [Bugme-new] [Bug 10682] New: (net 8139too) dual ethernet system, any reasonable network causes: NETDEV WATCHDOG: ethN: transmit timed out

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <20080512151142.067b98d2.akpm@linux-foundation.org>
Date:	Mon, 12 May 2008 15:11:42 -0700
From:	Andrew Morton <akpm@...ux-foundation.org>
To:	"Bradley M. Kuhn" <bkuhn@....org>
Cc:	bugme-daemon@...zilla.kernel.org, netdev@...r.kernel.org
Subject: Re: [Bugme-new] [Bug 10682] New: (net 8139too) dual ethernet 
 system, any reasonable network causes: NETDEV WATCHDOG: ethN: transmit 
 timed out

On Mon, 12 May 2008 17:40:14 -0400
"Bradley M. Kuhn" <bkuhn@....org> wrote:

> Andrew, thanks so much for your quick reply!
> 
> I reported this bug:
> > > http://bugzilla.kernel.org/show_bug.cgi?id=10682
> > >
> > >            Summary: (net 8139too) dual ethernet system, any reasonable
> > >                     network causes: NETDEV WATCHDOG: ethN: transmit timed
> > >                     out
> > >            Product: Drivers
> > >            Version: 2.5
> > >      KernelVersion: 2.6.25.3
> > >           Platform: All
> > >         OS/Version: Linux
> > >               Tree: Mainline
> > >          Component: Network
> > >         AssignedTo: jgarzik@...ox.com
> > >         ReportedBy: bkuhn@....org
> 
> Andrew Morton replied:
> 
> > I really dont' know where to begin with this, sorry.  It's _probably_
> > some platform-related IRQ delivery problem.  But then again it might be
> > something else :(
> 
> I understand.  FWIW, I tried every BIOS change imaginable to make sure it
> wasn't some weird BIOS interaction.
> 
> > It would certainly be valuable to try some older kernels.
> 
> What are you suggestions regarding "how old"?  My plan *was* to install a
> 2.4 based distribution next, but if there are specific 2.6.x versions you
> think are worth trying, I'm happy to give a try.  I'd rather try the
> 2.6.x's you suggest first, of course.

I think an early 2.6 would be a good place to start - 2.6.5. 2.6.9, etc.

If that doesn't help then we can probably safely assume that it's
always been busted.  If that kernel works OK then we can drill in more
cloesly, if you're so inclined (which we hope you are ;))
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html