Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1750708AbWJ0UbL (ORCPT ); Fri, 27 Oct 2006 16:31:11 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1752443AbWJ0UbL (ORCPT ); Fri, 27 Oct 2006 16:31:11 -0400 Received: from emailhub.stusta.mhn.de ([141.84.69.5]:20232 "HELO mailout.stusta.mhn.de") by vger.kernel.org with SMTP id S1750708AbWJ0UbK (ORCPT ); Fri, 27 Oct 2006 16:31:10 -0400 Date: Fri, 27 Oct 2006 22:31:09 +0200 From: Adrian Bunk To: Jeff Chua Cc: linux-kernel@vger.kernel.org, David Miller Subject: Re: linux-2.6.19-rc2 tg3 problem Message-ID: <20061027203109.GZ27968@stusta.de> References: <20061025013022.GG27968@stusta.de> <20061026152455.GI27968@stusta.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.13 (2006-08-11) Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2449 Lines: 76 On Fri, Oct 27, 2006 at 09:49:54PM +0800, Jeff Chua wrote: > On 10/26/06, Adrian Bunk wrote: > > >That wasn't clear from your bug report. > > Sorry. Didn't want to bombard with too much unnecessary info. linux-kernel has a 100 kB size limit - everything below this limit is OK... > >You said 2.6.18-rc2 -> 2.6.19-rc2 broke. > >Can you identify between which -rc kernels it broke? > > Ok, I managed to trace down to .. > > 2.6.18 ok > 2.6.19-rc1 bad > > > >Please send complete "dmesg -s 1000000" for the time after tg3 loads for > >both the last working and the first non-working -rc kernel. > > > 2.6.18 (good) ... > > tg3.c:v3.65 (August 07, 2006) > ACPI: PCI Interrupt 0000:02:00.0[A] -> GSI 16 (level, low) -> IRQ 16 > PCI: Setting latency timer of device 0000:02:00.0 to 64 > eth0: Tigon3 [partno(BCM5751PKFBG) rev 4001 PHY(5750)] (PCI Express) > 10/100/1000BaseT Ethernet 00:13:72:7b:2a:f0 > eth0: RXcsums[1] LinkChgREG[1] MIirq[1] ASF[0] Split[0] WireSpeed[1] > TSOcap[1] > eth0: dma_rwctrl[76180000] dma_mask[64-bit] > ip_tables: (C) 2000-2006 Netfilter Core Team > ip_conntrack version 2.4 (8192 buckets, 65536 max) - 224 bytes per conntrack > tg3: eth0: Link is up at 100 Mbps, full duplex. > tg3: eth0: Flow control is on for TX and on for RX. > > > > 2.6.19 (bad) ... > > tg3.c:v3.66 (September 23, 2006) > ACPI: PCI Interrupt 0000:02:00.0[A] -> GSI 16 (level, low) -> IRQ 16 > tg3: Cannot find proper PCI device base address, aborting. > ACPI: PCI interrupt for device 0000:02:00.0 disabled > ip_tables: (C) 2000-2006 Netfilter Core Team > ip_conntrack version 2.4 (8192 buckets, 65536 max) - 228 bytes per conntrack >... That's still pretty terse... If there is anything interesting in the dmesg, it's above this point (Please send complete "dmesg -s 1000000" for both cases). If this won't help, the next step will be to bisect for the commit that broke it for you. > Thanks, > Jeff. cu Adrian -- "Is there not promise of rain?" Ling Tan asked suddenly out of the darkness. There had been need of rain for many days. "Only a promise," Lao Er said. Pearl S. Buck - Dragon Seed - 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/