Date: Tue, 9 Oct 2007 11:09:23 -0700 From: "Jack Vogel" <jfvogel@gmail.com> To: "Mike Tancsa" <mike@sentex.net> Cc: FreeBSD Stable List <freebsd-stable@freebsd.org> Subject: Re: Heads UP - MFC for em coming shortly Message-ID: <2a41acea0710091109o79ebf0d1q988449565f8e345d@mail.gmail.com> In-Reply-To: <200710091649.l99Gnfk4048093@lava.sentex.ca> References: <2a41acea0710051328hdc0e49fr829b5ea35c95a413@mail.gmail.com> <200710082009.l98K9mCs042466@lava.sentex.ca> <2a41acea0710081336n11a36303ta70efc94c6f2d236@mail.gmail.com> <200710082111.l98LBGRa042719@lava.sentex.ca> <2a41acea0710081736r1b2c3c48k50d8ebd063dc3fc5@mail.gmail.com> <200710090038.l990cqsv043565@lava.sentex.ca> <2a41acea0710082137v4792b7cdwd5ebf8619666cf55@mail.gmail.com> <200710091649.l99Gnfk4048093@lava.sentex.ca>
next in thread | previous in thread | raw e-mail | index | archive | help
On 10/9/07, Mike Tancsa <mike@sentex.net> wrote: > At 12:37 AM 10/9/2007, Jack Vogel wrote: > > > Thanks, > > > I did find this reference > > > http://www.higherorder.com.au/2007/6/25/intel_82573_patch > > > > > > Is there a way from FreeBSD to tell remotely if its needed ? > > > >Well, there would be a way, reading the MANC register and > >seeing if the suspect bit is present, but am not sure if there > >is some important point at which the thing gets misprogrammed, > >its just best to use the patcher, its harmless if its not needed. > > > >Sorry, I realize its a hassle to boot to that wonder DOS :) > > > OK, did some tests on local PM nics here at the office. On one nic > (same model as what is causing us problems in the field) we can run > the program over and over again, and it always exits with a zero > value. Is this normal ? On another NIC that we recently bought, it > exits with a 1 which supposedly says "not needed". How do we know > that the update has taken ? Is there any danger of it losing its > reprogramming ? In short, how do we verify it "worked" > > The version I am using is > > lava# ls -l dcgdis.exe > -rw-r--r-- 1 root wheel 160029 Oct 4 2005 dcgdis.exe > lava# md5 dcgdis.exe > MD5 (dcgdis.exe) = a48d9e127c19528bd4a650e692b2f2be > lava# > > Is there a newer one ? There has only ever been one of these things, and its a binary wad to me just as to you, so I don't know why it returns success multple times, I guess it just checks the NIC type and does the write. People writing this are not Unix types, they are DOS tools programmers, should tell you something :) I was just talking to one of our Linux engineers and they actually export the ability to read and write the eeprom via ethtool, maybe I should look into adding something like a sysctl for that. Right now, just run it once, then test to see if the problem has disappeared. Jack
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?2a41acea0710091109o79ebf0d1q988449565f8e345d>