public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Keith Owens <kaos@sgi.com>
To: "David S. Miller" <davem@davemloft.net>
Cc: linux-kernel@vger.kernel.org, linux-ia64@vger.kernel.org
Subject: Re: 2.6.14-rc1 breaks tg3 on ia64
Date: Tue, 13 Sep 2005 16:17:33 +1000	[thread overview]
Message-ID: <23056.1126592253@kao2.melbourne.sgi.com> (raw)
In-Reply-To: Your message of "Mon, 12 Sep 2005 22:37:55 MST." <20050912.223755.56102921.davem@davemloft.net>

On Mon, 12 Sep 2005 22:37:55 -0700 (PDT), 
"David S. Miller" <davem@davemloft.net> wrote:
>From: Keith Owens <kaos@sgi.com>
>Date: Tue, 13 Sep 2005 15:22:17 +1000
>
>> 2.6.14-rc1 + kdb on ia64 (SGI Altix).
>> 
>> tg3.c:v3.39 (September 5, 2005)
>> ACPI: PCI Interrupt 0001:01:04.0[A]: no GSI
>> BRIDGE ERR_STATUS 0x800
>> BRIDGE ERR_STATUS 0x800
>> PCI BRIDGE ERROR: int_status is 0x800 for 011c32:slab0:widget15:bus0
>>     Dumping relevant 011c32:slab0:widget15:bus0 registers for each bit set...
>>         11: PCI bus device select timeout
>>             PCI Error Address Register: 0x3000000316808
>>             PCI Error Address: 0x316808
>>     PIC Multiple Interrupt Register is 0x800
>>         11: PCI bus device select timeout
>> 
>> Followed by a machine check and reboot :(  2.6.13 worked fine.  Any
>> ideas which patch to backout this time?
>
>Does copying over the 2.6.13 tg3.[ch] driver over into your
>2.6.14-rc1 tree make it work?

No, the 2.6.13 driver in 2.6.14-rc1 has exactly the same problem.

The last time that tg3 broke like this, it was because of the patch
below, in 2.6.13-rc6.  That was backed out in 2.6.13-rc7.  Was the PCI
patch (or equivalent) reinstated in 2.6.14-rc1?

From: John W. Linville <linville@tuxdriver.com>
Date: Fri, 5 Aug 2005 01:06:10 +0000 (-0700)
Subject: [PATCH] PCI: restore BAR values after D3hot->D0 for devices that need it
X-Git-Tag: v2.6.13-rc6
X-Git-Url: http://kernel.org/git/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=fec59a711eef002d4ef9eb8de09dd0a26986eb77


  reply	other threads:[~2005-09-13  6:17 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-13  5:22 2.6.14-rc1 breaks tg3 on ia64 Keith Owens
2005-09-13  5:37 ` David S. Miller
2005-09-13  6:17   ` Keith Owens [this message]
2005-09-13  6:47     ` David S. Miller
2005-09-13  6:48     ` Keith Owens
2005-09-13  6:59     ` Greg KH
2005-09-13  7:27       ` Keith Owens
2005-09-17 15:47         ` Tony Luck
2005-09-17 15:59           ` John W. Linville
2005-09-17 16:16             ` Greg KH
2005-09-17 16:34               ` Jack Steiner
2005-09-17 16:48                 ` John W. Linville
2005-09-17 16:46               ` John W. Linville
2005-09-18  6:23             ` David S. Miller
2005-09-18  6:33               ` Tony Luck
2005-09-18 11:44               ` Jack Steiner
     [not found] <20050919204523.GD15838@sgi.com>
2005-09-19 22:43 ` Mike Habeck
2005-09-20  1:14   ` David S. Miller

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=23056.1126592253@kao2.melbourne.sgi.com \
    --to=kaos@sgi.com \
    --cc=davem@davemloft.net \
    --cc=linux-ia64@vger.kernel.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox