From owner-freebsd-stable@FreeBSD.ORG Wed Jul 7 01:38:09 2004 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E930E16A4CF for ; Wed, 7 Jul 2004 01:38:09 +0000 (GMT) Received: from mail.datausa.com (mail.datausa.com [216.150.220.134]) by mx1.FreeBSD.org (Postfix) with SMTP id 7EA1443D5C for ; Wed, 7 Jul 2004 01:38:09 +0000 (GMT) (envelope-from freebsd@wcubed.net) Received: (qmail 39722 invoked from network); 7 Jul 2004 01:30:37 -0000 Received: from c-24-9-172-8.client.comcast.net (HELO wcubed.net) (24.9.172.8) by mail.datausa.com with SMTP; 7 Jul 2004 01:30:37 -0000 Message-ID: <40EB54F3.20205@wcubed.net> Date: Tue, 06 Jul 2004 19:42:11 -0600 From: Brad Waite User-Agent: Mozilla Thunderbird 0.5 (Windows/20040207) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Doug White References: <1068.24.9.172.8.1089064477.squirrel@webmail.wcubed.net> <20040706160201.X24627@carver.gumbysoft.com> <40EB532A.8020401@wcubed.net> <20040706183105.R24627@carver.gumbysoft.com> In-Reply-To: <20040706183105.R24627@carver.gumbysoft.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-stable@freebsd.org Subject: Re: Gigabits, watchdog timeouts and downtime, oh my! X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 07 Jul 2004 01:38:10 -0000 Doug White wrote: > On Tue, 6 Jul 2004, Brad Waite wrote: > > >>>>Decided to move into the Gigabit world yesterday and picked up a SMC >>>>9452TX for my 4.10-STABLE box. I rebuilt the kernel with the sk device >>>>and while it works somewhat, I'm getting 'sk0: watchdog timeout' errors >>>>and the card goes down for a few seconds before waking back up. This >>>>happens under relatively light traffic, too. >>> >>> >>>Sounds like autoneg flaking out; try a different cable? >>> >> >>No I didn't, but I did enable "PCI IRQs to IO-APIC mapping" in my BIOS. >> Everything works like a champ now. Woot! > > > Wierd. What brand/model of system or motherboard do you have? It seems odd > that theres even a toggle for that. > Micron NetFRAME MV5000 server, Intel MB440LX dual P-II. I stumbled across the solution on -questions where someone else did the same thing, so I'm not the only one.