Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753173AbZAYVWa (ORCPT ); Sun, 25 Jan 2009 16:22:30 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751501AbZAYVWT (ORCPT ); Sun, 25 Jan 2009 16:22:19 -0500 Received: from mail.tmr.com ([64.65.253.246]:58567 "EHLO partygirl.tmr.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751479AbZAYVWS (ORCPT ); Sun, 25 Jan 2009 16:22:18 -0500 Message-ID: <497CD808.5060506@tmr.com> Date: Sun, 25 Jan 2009 16:22:16 -0500 From: Bill Davidsen User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.1.19) Gecko/20081217 Fedora/1.1.14-1.fc9 pango-text SeaMonkey/1.1.14 MIME-Version: 1.0 Newsgroups: gmane.linux.kernel,gmane.linux.network.general To: linux-net@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: What happened to this NIC? Any ideas? References: <20090124192450.GA4721@tatooine.rebelbase.local> In-Reply-To: <20090124192450.GA4721@tatooine.rebelbase.local> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 830 Lines: 20 markus reichelt wrote: > Just for the fun of it, I plugged the faulty NIC into a sole win > machine, it worked. Doesn't work in the linux machine afterwards, > though. First time that I observe such strange behaviour, any ideas > what could be the cause? > Did you put it in the same slot? Was there a firmware upgrade recently? Those are the things I would check, but not with any great expectation of finding the cause. -- Bill Davidsen "We have more to fear from the bungling of the incompetent than from the machinations of the wicked." - from Slashdot -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/