All of lore.kernel.org
 help / color / mirror / Atom feed
From: Adrian Bunk <bunk@stusta.de>
To: Jeff Chua <jeff.chua.linux@gmail.com>
Cc: linux-kernel@vger.kernel.org, David Miller <davem@davemloft.net>
Subject: Re: linux-2.6.19-rc2 tg3 problem
Date: Fri, 27 Oct 2006 22:31:09 +0200	[thread overview]
Message-ID: <20061027203109.GZ27968@stusta.de> (raw)
In-Reply-To: <b6a2187b0610270649t4cc71781y8e1695f02e1c608e@mail.gmail.com>

On Fri, Oct 27, 2006 at 09:49:54PM +0800, Jeff Chua wrote:
> On 10/26/06, Adrian Bunk <bunk@stusta.de> 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


  reply	other threads:[~2006-10-27 20:31 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-23 15:24 linux-2.6.19-rc2 tg3 problem Jeff Chua
2006-10-23 21:19 ` David Miller
2006-10-25  1:30 ` Adrian Bunk
2006-10-26  0:54   ` Jeff Chua
2006-10-26 15:24     ` Adrian Bunk
2006-10-27 13:49       ` Jeff Chua
2006-10-27 20:31         ` Adrian Bunk [this message]
2006-10-28  1:05           ` Jeff Chua
2006-10-28  3:20             ` linux-2.6.19-rc2 PCI problem Adrian Bunk
2006-10-28 10:24               ` Jeff Chua
2006-10-28 15:45                 ` Matthew Wilcox
2006-10-29  1:20                   ` Jeff Chua
2006-10-28  8:23             ` linux-2.6.19-rc2 tg3 problem Yinghai Lu

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20061027203109.GZ27968@stusta.de \
    --to=bunk@stusta.de \
    --cc=davem@davemloft.net \
    --cc=jeff.chua.linux@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.