From owner-freebsd-stable@FreeBSD.ORG Mon Oct 5 19:40:00 2009 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B3CF710656A9 for ; Mon, 5 Oct 2009 19:40:00 +0000 (UTC) (envelope-from jfvogel@gmail.com) Received: from mail-yw0-f197.google.com (mail-yw0-f197.google.com [209.85.211.197]) by mx1.freebsd.org (Postfix) with ESMTP id 69DEB8FC24 for ; Mon, 5 Oct 2009 19:40:00 +0000 (UTC) Received: by ywh35 with SMTP id 35so13505529ywh.7 for ; Mon, 05 Oct 2009 12:39:59 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type; bh=NuStorNNX649SLucT/ZOhXBaJWC8JQawmgKJRpEx9ro=; b=E0PezpeG769Mf3VWVxKkf3zPTEchN210itKhNLXYB6jtJbnhg4NMhxYsgFDJXu16Sd rcbRhEGNF4wZMo86F+AOtkUOjQ7EVeP4/+3Yf/qOtK7+JB5WCIHKIEnshd84hFJPFIp2 K1x/7iBrhOjKlVUb5MnggOmkHI7LWUhM35vQg= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=KQpZdMiozOzbVpI0rk4/aH3VSeNwluacd1hsv5KSeiL0fyWhw/YRCCBnE0sKMQfrfo Xd+f6utlWOmNZFG+sAabg84pds/y4PA5Qd7yjcelwtKzgRNihJC08X4bZ3u8H+NLv7wC pwjzKt/P2KrGlCU/P4Y3NTh7S78SSC3pi2bgE= MIME-Version: 1.0 Received: by 10.101.107.2 with SMTP id j2mr466852anm.135.1254771599789; Mon, 05 Oct 2009 12:39:59 -0700 (PDT) In-Reply-To: <57F8F331-E823-4F88-BDD5-A8B95A3B4CB6@danielbond.org> References: <4AB9638B.8040607@monkeybrains.net> <4AC5198E.7030609@monkeybrains.net> <4AC51B4C.7080905@monkeybrains.net> <2a41acea0910011450v41590f3dn112f367f26faed2d@mail.gmail.com> <4AC64835.3060107@monkeybrains.net> <2a41acea0910021237w415efa2cs4354a0f99aef8f6@mail.gmail.com> <4AC66437.4040704@monkeybrains.net> <6194E9BC-3A3D-4941-A777-88C7411905B0@danielbond.org> <2a41acea0910050957x2d085e90w2ebea7f9eb87c3e4@mail.gmail.com> <57F8F331-E823-4F88-BDD5-A8B95A3B4CB6@danielbond.org> Date: Mon, 5 Oct 2009 12:39:59 -0700 Message-ID: <2a41acea0910051239w7abad271n607295418fc2537f@mail.gmail.com> From: Jack Vogel To: Daniel Bond Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: FreeBSD Stable Subject: Re: em0 watchdog timeouts X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 05 Oct 2009 19:40:00 -0000 Sorry, its a Monday morning, I was being kinda facetious, guess it didn't work very well :) I apologize. I know it must be annoying for you, its as much so for me when its something I can't just fix because its not reproducible. So, I feel your pain. Will try to restrain my Monday blues in the future. Jack On Mon, Oct 5, 2009 at 11:32 AM, Daniel Bond wrote: > Hi Jack, > > I'll comment your mail inline: > > > On Oct 5, 2009, at 6:57 PM, Jack Vogel wrote: > > This posting just muddies the issue, first you talk about having a problem >> that >> involves Broadcom, ok, so post about that on something other than em :) >> > > I only meant to indicate that the problem might exist outside the intel > driver. > I'm also indicating that it happens with several drivers (bge, bce and em) > on several different machines, on both pci-x and pci-e. > > I'm sorry if this is confusing to you, but I still think it's relevant to > mention. > > >> Then you make some references to hardware that you "might have bought" >> but didn't, I'm not about debugging 'possible worlds problems' though so >> can't help you there either :) >> > > No. I only made references to hardware I actually used, and had real-world > issues with. > > >> Finally you never say what the actual hardware is, other than a person who >> I do not know told you it was the best performer... so, what exactly is >> it? >> > > Sepherosa is a guy that writes drivers for BSD based operating systems. > Including FreeBSD. He has a lot of knowledge in this area. > http://people.freebsd.org/~sephe/ > > The NIC you are referring to, the one sephe recommended me, is a 82571EB. I > didn't mention specific hardware, as I think it's more important > to note this is an issue I'm experiencing across different sets of hardware > and drivers. > > >> You have a problem once every 10 days, and at a specific time no less, >> this almost always means something in your environment, a cron job run >> amok, a piece of hardware that resets, I dunno, but the last thing I would >> suspect given this description is the driver. >> > > This is not what I wrote. I wrote I had a problem every 1-10 days, but it > would usually happen once every 3-4 days. At worst, every day in periods. > > It's not at any specific time. If you read my email correctly, I say it > *usually* happens arround 11-13:00, > but it has happened at random times too. > > This is my point exactly. I don't think it's the Intel-driver, I think the > problem is elsewhere. I had a suspicion it had to do with the combination of > nic + qlogic fc-controller, but I have no evidence of this. > > >> You need a good sysadmin for this debugging I would venture, not a driver >> developer. >> > > What I need is useful advice/help. I never stated I needed a driver > developer. > > I'd like to be able to run my favorite OS on cool hardware, in the future, > for a high-performing NFS-server, without problems like I've experienced the > past 6months, on a production system. > Please note that I'm managing a server-park almost completely based on > FreeBSD, and I'm running many NFS servers on other hardware, for other > services, without issues. > > I've seen several other FreeBSD-users having problems with this too, so I > think it's of importance for the project. As I mentioned originally, I'm > happy to dispose the hardware to any FreeBSD developer > that might want to look further into this. Debugging it further is above my > skill-set, I don't even know where to begin looking, especially since I > can't produce any panics. > > I'm sorry to say, but your reply was %0 useful, Jack. > > >> Jack >> >> > - Daniel >