From owner-freebsd-stable@FreeBSD.ORG Wed Jul 7 01:30:33 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 5E1D516A4CF for ; Wed, 7 Jul 2004 01:30:33 +0000 (GMT) Received: from mail.datausa.com (mail.datausa.com [216.150.220.134]) by mx1.FreeBSD.org (Postfix) with SMTP id D6A9D43D41 for ; Wed, 7 Jul 2004 01:30:32 +0000 (GMT) (envelope-from freebsd@wcubed.net) Received: (qmail 35992 invoked from network); 7 Jul 2004 01:23:00 -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:23:00 -0000 Message-ID: <40EB532A.8020401@wcubed.net> Date: Tue, 06 Jul 2004 19:34:34 -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> In-Reply-To: <20040706160201.X24627@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:30:33 -0000 Doug White wrote: > On Mon, 5 Jul 2004, Brad Waite wrote: > > >>Hey all, >> >>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! Thanks, for the suggestion, though. Brad