From: Casey Dahlin <cjdahlin@ncsu.edu>
To: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [BUG:] forcedeth: MCP55 not allowing DHCP
Date: Mon, 17 Sep 2007 21:59:32 -0400 [thread overview]
Message-ID: <46EF3104.8080805@ncsu.edu> (raw)
In-Reply-To: <46E7111B.2050303@ncsu.edu>
Casey Dahlin wrote:
> I have an Asus Striker Extreme motherboard with two built in MCP55
> GigE interfaces. When I build with the original Fedora 7 release
> kernel (
> ftp://ftp.belnet.be/linux/fedora/linux/releases/7/Fedora/i386/os/Fedora/kernel-2.6.21-1.3194.fc7.i686.rpm
> ) everything works fine. However, when I boot with any updated kernels
> or any other kernel (have tried building from several points in the
> linus git tree between 2.6.20 and .23-rc3, and 2.6.21.2 in -stable) I
> cannot get an IP address via dhcp. There is no error in dmesg. The
> card shows a link and otherwise appears to be working, but it is as if
> the dhcp server has been removed from the network.
>
> On a running system there is no indication that this is a kernel bug
> at all, however by varying only the kernel the bug appears and
> disappears. I've run all these tests repeatedly with no intervening
> updates of any other packages.
>
> As I said I attempted to build 2.6.21.2 ( the point of divergence
> between the Fedora kernel in question and -stable ) and still the card
> did not work. I will next attempt to manually build the rpm for the
> release kernel. If this works I will try experimenting with the
> included patches to narrow it down, but at this point I'm at a
> complete loss.
>
> -Casey Dahlin
>
Is there any feedback to be had on this? I've gotten no reply whatsoever
from several sources now.
next prev parent reply other threads:[~2007-09-18 1:59 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-08 20:05 [RFC][Intel-IOMMU] Fix for IOMMU early crash Keshavamurthy, Anil S
2007-09-09 11:16 ` Muli Ben-Yehuda
2007-09-10 15:43 ` Keshavamurthy, Anil S
2007-09-09 17:51 ` Muli Ben-Yehuda
2007-09-11 17:22 ` Keshavamurthy, Anil S
2007-09-09 17:37 ` Paul Mackerras
2007-09-11 17:42 ` Keshavamurthy, Anil S
2007-09-10 20:25 ` Muli Ben-Yehuda
2007-09-11 20:43 ` Keshavamurthy, Anil S
2007-09-12 19:28 ` [patch][Intel-IOMMU] " Keshavamurthy, Anil S
2007-09-11 19:48 ` Paul Mackerras
2007-09-12 21:55 ` Keshavamurthy, Anil S
2007-09-11 22:05 ` [BUG:] forcedeth: MCP55 not allowing DHCP Casey Dahlin
2007-09-18 1:59 ` Casey Dahlin [this message]
2007-09-13 1:29 ` [patch][Intel-IOMMU] Fix for IOMMU early crash Keshavamurthy, Anil S
2007-09-14 16:30 ` Paul Mackerras
2007-09-25 17:07 ` Keshavamurthy, Anil S
2007-10-03 21:13 ` [patch take 2][Intel-IOMMU] " Keshavamurthy, Anil S
2007-10-04 1:19 ` Benjamin Herrenschmidt
2007-10-04 1:36 ` Keshavamurthy, Anil S
2007-10-04 3:39 ` Benjamin Herrenschmidt
2007-10-04 19:20 ` Keshavamurthy, Anil S
2007-10-05 3:08 ` Benjamin Herrenschmidt
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=46EF3104.8080805@ncsu.edu \
--to=cjdahlin@ncsu.edu \
--cc=linux-kernel@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