Date: Wed, 22 Jul 2009 05:18:59 +0000 From: "b. f." <bf1783@googlemail.com> To: freebsd-current@FreeBSD.org Cc: sfourman@gmail.com, webmaster@doghouserepair.com Subject: Re: nfe problem on 8.0-BETA2 Message-ID: <d873d5be0907212218nde4167bw8e4e9951659b3729@mail.gmail.com>
next in thread | raw e-mail | index | archive | help
> Seeing that nfe apparently worked on June 1st, I headed to the FTP to see > which snapshots were available. =A0The earliest -CURRENT June snapshot wa= s > dated the 8th, so I grabbed that one. =A0The nics didn't work at all. > > So, there's a small window where something changed which broke nfe. Looki= ng > at the SVN commit logs for if_nfe.c, nothing really fits in that window. = =A0To > me, this looks like something about general network device handling chang= ed > which nfe nics can't cope with. =A0I have no idea what that could be thou= gh, > so I'm hoping that someone on this list would be able to point me in the > right direction. > > Ryan Well, you guys picked a helluva week (June 1-8) in which to narrow down problems. It would help if you gave the exact revisions of the snapshots you are using. And if you are going to hunt this down, I would recommend getting a local subversion repository of the sources, so that you can selectively revert changes and then rebuild to test. I have a MCP61-based NIC using nfe, and I haven't had any problems. Since you both have Marvell 88E1116-based chipsets, I'm going to guess that one of yongari@'s changesets from June 2 was the source of your problems: http://svn.freebsd.org/changeset/base/193289 http://svn.freebsd.org/changeset/base/193291 If you revert these and still can't get your NICs to work, then I think that probably the new ACPI import that began on June 5 with r193529 may be the next likely suspect. Regards, b.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?d873d5be0907212218nde4167bw8e4e9951659b3729>