Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S263053AbTKWAYN (ORCPT ); Sat, 22 Nov 2003 19:24:13 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S263101AbTKWAYN (ORCPT ); Sat, 22 Nov 2003 19:24:13 -0500 Received: from www.mail15.com ([62.118.249.44]:777 "EHLO www.mail15.com") by vger.kernel.org with ESMTP id S263053AbTKWAYI (ORCPT ); Sat, 22 Nov 2003 19:24:08 -0500 Message-ID: <3FBFF7D8.8070404@myrealbox.com> Date: Sat, 22 Nov 2003 15:57:12 -0800 From: walt Organization: none User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6b) Gecko/20031119 X-Accept-Language: en-us, en MIME-Version: 1.0 To: linux-kernel@vger.kernel.org Subject: tg3 / Broadcom question for Jeff Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 3712 Lines: 75 Hi Jeff, If you'll recall, I'm the one with the ASUS A7V8X with the built-in Broadcom ethernet chip which won't work until I do an ifconfig down/up cycle. I just learned about the -xxx flag to lspci and I hope the info below may shed some light on this long-standing bug. This is lspci -vvv -xxx right after booting the machine (ethernet not yet working): 00:09.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5702 Gigabit Ethernet (rev 02) Subsystem: Asustek Computer, Inc.: Unknown device 80a9 Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap+ 66Mhz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- 90: 09 02 00 01 00 00 00 00 00 00 00 00 c8 00 00 00 145,149c145,149 < b0: 00 00 00 00 01 00 00 00 00 00 00 00 01 00 00 00 < c0: 00 00 00 00 01 00 00 00 00 00 00 00 01 00 00 00 < d0: 00 00 00 00 01 00 00 00 00 00 00 00 01 00 00 00 < e0: 00 00 00 00 01 00 00 00 00 00 00 00 01 00 00 00 < f0: 00 00 00 00 01 00 00 00 00 00 00 00 01 00 00 00 --- > b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 > c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 > d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 > e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 > f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 You can see that only a few bits have flipped, but it makes everything work until the next reboot. I got the same result three different times, so this is not random behavior. Is this of any help to you? - 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/