From: "Bradley M. Kuhn" <bkuhn@ebb•org>
To: Andrew Morton <akpm@linux-foundation•org>
Cc: bugme-daemon@bugzilla•kernel.org, netdev@vger•kernel.org
Subject: Re: [Bugme-new] [Bug 10682] New: (net 8139too) dual ethernet system, any reasonable network causes: NETDEV WATCHDOG: ethN: transmit timed out
Date: Sun, 18 May 2008 22:05:02 -0400 [thread overview]
Message-ID: <87d4njnj5d.fsf@ebb.org> (raw)
In-Reply-To: <20080512151142.067b98d2.akpm@linux-foundation.org> (Andrew Morton's message of "Mon, 12 May 2008 15:11:42 -0700")
I wrote:
>> 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
>> > > KernelVersion: 2.6.25.3
>> Andrew Morton replied:
> I think [trying] an early 2.6 would be a good place to start -
> 2.6.5. 2.6.9, etc.
I had trouble getting 2.6.5 onto the machine with the distribution it
had. I have installed a different distribution, and now have 2.6.15
running, and it produces the same error.
So, we know the bug was present in 2.6.15.
Now that I have an older distribution, I should be able to try 2.6.5 and
2.6.9 shortly. Do you expect it will produce substantially different
results from 2.6.15?
> 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 ;))
I'm absolutely inclinded to do so. What can I do to get you more
information, other than the above?
--
-- bkuhn
prev parent reply other threads:[~2008-05-19 2:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-10682-10286@http.bugzilla.kernel.org/>
2008-05-12 4:10 ` [Bugme-new] [Bug 10682] New: (net 8139too) dual ethernet system, any reasonable network causes: NETDEV WATCHDOG: ethN: transmit timed out Andrew Morton
[not found] ` <20080512214014.GB27236@ebb.org>
2008-05-12 22:11 ` Andrew Morton
2008-05-13 14:35 ` Bradley M. Kuhn
2008-05-19 2:05 ` Bradley M. Kuhn [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=87d4njnj5d.fsf@ebb.org \
--to=bkuhn@ebb$(echo .)org \
--cc=akpm@linux-foundation$(echo .)org \
--cc=bugme-daemon@bugzilla$(echo .)kernel.org \
--cc=netdev@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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