Date: Mon, 14 May 2007 21:50:47 -0700 From: "Jack Vogel" <jfvogel@gmail.com> To: "Randy Bush" <randy@psg.com> Cc: FreeBSD Current <freebsd-current@freebsd.org>, LI Xin <delphij@delphij.net> Subject: Re: em driver Message-ID: <2a41acea0705142150l547fcf12o96d92ce5413948d5@mail.gmail.com> In-Reply-To: <46492CFC.6060506@psg.com> References: <17993.9973.237807.213217@roam.psg.com> <46492B3B.3020305@delphij.net> <46492CFC.6060506@psg.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 5/14/07, Randy Bush <randy@psg.com> wrote: > LI Xin wrote: > > Randy Bush wrote: > >> could the em driver have been borked by the recent changes such that > >> once a day or so it went out for a few minutes to an hour? if so, did > >> the changes three days ago fix it? > > What do you mean by "went out"? According to my understanding 1.175 of > > if_em.c seems to fix the case where em(4) fails to attach on certain > > hardware... > > running fine. stops moving packets for five to 60 minutes. starts moving > packets again. all with no intervention, in rack, long way away. e.g. see > two stops in > > http://rip.psg.com/~randy/070514.em0-borkage.png > > no other hosts with same symptom, though three with em ethers updated at > same time. > > and, of course, it used to work fine until cvsup of May 8 12:03 (gmt). > everything always "used to work." :) What do you expect anyone to do based on this data??? For all I know someone in another room is turning off a switch every couple hours :) So if you want to report a problem, put yourself in the place of the engineer who has to fix it, what would you want... well, how about hardware description, pci config, log file output, I dont know, something that would give me a chance of knowing what the problem is. Jack
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?2a41acea0705142150l547fcf12o96d92ce5413948d5>