From: Andrew Morton <akpm@linux-foundation.org>
To: Robert Hancock <hancockr@shaw.ca>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
netdev@vger.kernel.org, Ayaz Abdulla <aabdulla@nvidia.com>
Subject: Re: forcedeth problems on 2.6.20-rc6-mm3
Date: Sun, 4 Feb 2007 21:36:03 -0800 [thread overview]
Message-ID: <20070204213603.a5bce839.akpm@linux-foundation.org> (raw)
In-Reply-To: <45C6BCE5.90103@shaw.ca>
On Sun, 04 Feb 2007 23:13:09 -0600 Robert Hancock <hancockr@shaw.ca> wrote:
> Something's busted with forcedeth in 2.6.20-rc6-mm3 for me relative to
> 2.6.20-rc6. There's no errors in dmesg, but it seems no packets ever get
> received and so the machine can't get an IP address. I tried reverting
> all the -mm changes to drivers/net/forcedeth.c, which didn't help. The
> network controller shares an IRQ with the USB OHCI controller which is
> receiving interrupts, so it doesn't seem like an interrupt routing
> problem, though I suppose something wierd could be happening there.
>
> This is on an Asus A8N-SLI Deluxe (CK804 chipset) on x86_64.
>
> Any suggestions on how to debug/what to try reverting to see what's
> causing this?
There are many forcedeth changes in git-netdev-all.patch. Can you
try reverting drivers/net/forcedeth.c back to the unpatched version
from 2.6.20-rc6?
Thanks.
next prev parent reply other threads:[~2007-02-05 5:36 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-05 5:13 forcedeth problems on 2.6.20-rc6-mm3 Robert Hancock
2007-02-05 5:36 ` Andrew Morton [this message]
2007-02-05 5:48 ` Robert Hancock
2007-02-05 6:17 ` Andrew Morton
[not found] ` <523e55a00702081326j43de05e3hdd8cf35e946eae9@mail.gmail.com>
2007-02-09 2:57 ` Ayaz Abdulla
2007-02-09 11:58 ` Tobias Diedrich
2007-02-09 12:07 ` Tobias Diedrich
2007-02-09 14:50 ` Jeff Garzik
2007-02-12 6:28 ` Tobias Diedrich
2007-02-16 14:54 ` Tobias Diedrich
2007-02-10 4:40 ` Robert Hancock
2007-02-05 6:34 ` Daniel Barkalow
2007-02-06 0:35 ` Robert Hancock
2007-02-06 0:52 ` Andrew Morton
2007-02-08 5:33 ` Andrew Morton
[not found] <fa.EU4/Dq38S7AbpiJstT7NwokqTWE@ifi.uio.no>
[not found] ` <fa.aMmqbeBS9CpIUWfPrgAtORtlXAQ@ifi.uio.no>
[not found] ` <fa.d8YTRl6o0OIk8Vvk1QLpyc+bxQU@ifi.uio.no>
[not found] ` <fa.XnyZ7qxKkAZ7Yhrg0DdiDmiy6wg@ifi.uio.no>
[not found] ` <fa.s8qbnOGnlEinPfyyhT0PZsqiwwE@ifi.uio.no>
[not found] ` <fa.6Uftu56OuKdbN+aI/fzLv4opZ/I@ifi.uio.no>
2007-02-20 0:39 ` Robert Hancock
2007-02-19 14:31 ` Ayaz Abdulla
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=20070204213603.a5bce839.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=aabdulla@nvidia.com \
--cc=hancockr@shaw.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@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;
as well as URLs for NNTP newsgroup(s).