Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S964952AbWHHPZm (ORCPT ); Tue, 8 Aug 2006 11:25:42 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S964951AbWHHPZm (ORCPT ); Tue, 8 Aug 2006 11:25:42 -0400 Received: from gw.goop.org ([64.81.55.164]:4266 "EHLO mail.goop.org") by vger.kernel.org with ESMTP id S964948AbWHHPZl (ORCPT ); Tue, 8 Aug 2006 11:25:41 -0400 Message-ID: <44D8ACFE.3060802@goop.org> Date: Tue, 08 Aug 2006 08:25:50 -0700 From: Jeremy Fitzhardinge User-Agent: Thunderbird 1.5.0.4 (X11/20060613) MIME-Version: 1.0 To: Arjan van de Ven CC: Andrew Morton , Linux Kernel Mailing List , NetDev Subject: Re: 2.6.18-rc3-mm2: bad e1000 device name References: <44D78A48.7050707@goop.org> <20060808004011.ab3cd65f.akpm@osdl.org> <44D8484E.9050904@goop.org> <44D8AB08.3000006@linux.intel.com> In-Reply-To: <44D8AB08.3000006@linux.intel.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 803 Lines: 23 Arjan van de Ven wrote: > Jeremy Fitzhardinge wrote: >> Andrew Morton wrote: >>> e1000 seems OK here. Don't know, sorry. >>> >> >> It's happening to all my ethernet-like devices: the Atheros wireless >> comes up as a mess too. It's different each time, so it looks like >> random uninitialized crud. >> > > is this the binary atheros driver? then please try without that.. It happens regardless of whether the atheros driver is loaded (or has ever been loaded). But it also happens to the atheros driver, so it isn't specific to the e1000. J - 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/