All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jack Steiner <steiner@sgi.com>
To: Greg KH <greg@kroah.com>
Cc: Tony Luck <tony.luck@gmail.com>, Keith Owens <kaos@sgi.com>,
	linux-kernel@vger.kernel.org, linux-ia64@vger.kernel.org
Subject: Re: 2.6.14-rc1 breaks tg3 on ia64
Date: Sat, 17 Sep 2005 16:34:34 +0000	[thread overview]
Message-ID: <20050917163434.GB24322@sgi.com> (raw)
In-Reply-To: <20050917161617.GA23171@kroah.com>

On Sat, Sep 17, 2005 at 09:16:17AM -0700, Greg KH wrote:
> On Sat, Sep 17, 2005 at 11:59:14AM -0400, John W. Linville wrote:
> > On Sat, Sep 17, 2005 at 08:47:03AM -0700, Tony Luck wrote:
> > > > >So does reverting this patch solve the problem?
> > > > 
> > > > I reversing
> > > > http://kernel.org/git/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h\x064b53dbcc977dbf2753a67c2b8fc1c061d74f21,
> > > > which appears to be the latest version of this patch.  There was a
> > > > patch reject in sparc64, but the common code was reverted.  IA64 (SGI
> > > > Altix) with that patch reverted now boots 2.6.14-rc1.
> > > 
> > > Anyone know anything more about this problem?  I'm not seeing it
> > > on any of my systems ... so perhaps it only affects cards with a
> > > PCI bridge on them, or cards that haven't already been initialized
> > > by EFI.
> > 
> > I posted a patch on Wednesday:
> > 
> > 	http://www.ussg.iu.edu/hypermail/linux/kernel/0509.1/2193.html
> > 
> > The original reporter (Keith Owens <kaos@sgi.com>) confirmed this
> > patch to fix the problem.
> 
> Yes, and a number of people objected to that patch.  Care to respond to
> them?

We are working on an SN-only workaround. No guarantee, but the person
working on it is optimistic that we can fix the problem in SN code
w/o making any generic changes. I should know more on Monday.

Long term, we are making SN ACPI compliant - or at leeast a lot closer.


> 
> thanks,
> 
> greg k-h
> -
> To unsubscribe from this list: send the line "unsubscribe linux-ia64" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

-- 
Thanks

Jack Steiner (steiner@sgi.com)          651-683-5302
Principal Engineer                      SGI - Silicon Graphics, Inc.



WARNING: multiple messages have this Message-ID (diff)
From: Jack Steiner <steiner@sgi.com>
To: Greg KH <greg@kroah.com>
Cc: Tony Luck <tony.luck@gmail.com>, Keith Owens <kaos@sgi.com>,
	linux-kernel@vger.kernel.org, linux-ia64@vger.kernel.org
Subject: Re: 2.6.14-rc1 breaks tg3 on ia64
Date: Sat, 17 Sep 2005 11:34:34 -0500	[thread overview]
Message-ID: <20050917163434.GB24322@sgi.com> (raw)
In-Reply-To: <20050917161617.GA23171@kroah.com>

On Sat, Sep 17, 2005 at 09:16:17AM -0700, Greg KH wrote:
> On Sat, Sep 17, 2005 at 11:59:14AM -0400, John W. Linville wrote:
> > On Sat, Sep 17, 2005 at 08:47:03AM -0700, Tony Luck wrote:
> > > > >So does reverting this patch solve the problem?
> > > > 
> > > > I reversing
> > > > http://kernel.org/git/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=064b53dbcc977dbf2753a67c2b8fc1c061d74f21,
> > > > which appears to be the latest version of this patch.  There was a
> > > > patch reject in sparc64, but the common code was reverted.  IA64 (SGI
> > > > Altix) with that patch reverted now boots 2.6.14-rc1.
> > > 
> > > Anyone know anything more about this problem?  I'm not seeing it
> > > on any of my systems ... so perhaps it only affects cards with a
> > > PCI bridge on them, or cards that haven't already been initialized
> > > by EFI.
> > 
> > I posted a patch on Wednesday:
> > 
> > 	http://www.ussg.iu.edu/hypermail/linux/kernel/0509.1/2193.html
> > 
> > The original reporter (Keith Owens <kaos@sgi.com>) confirmed this
> > patch to fix the problem.
> 
> Yes, and a number of people objected to that patch.  Care to respond to
> them?

We are working on an SN-only workaround. No guarantee, but the person
working on it is optimistic that we can fix the problem in SN code
w/o making any generic changes. I should know more on Monday.

Long term, we are making SN ACPI compliant - or at leeast a lot closer.


> 
> thanks,
> 
> greg k-h
> -
> To unsubscribe from this list: send the line "unsubscribe linux-ia64" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

-- 
Thanks

Jack Steiner (steiner@sgi.com)          651-683-5302
Principal Engineer                      SGI - Silicon Graphics, Inc.



  reply	other threads:[~2005-09-17 16:34 UTC|newest]

Thread overview: 34+ 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:22 ` Keith Owens
2005-09-13  5:37 ` David S. Miller
2005-09-13  5:37   ` David S. Miller
2005-09-13  6:17 ` Keith Owens
2005-09-13  6:17   ` Keith Owens
2005-09-13  6:47   ` David S. Miller
2005-09-13  6:47     ` David S. Miller
2005-09-13  6:59   ` Greg KH
2005-09-13  6:59     ` Greg KH
2005-09-13  6:48 ` Keith Owens
2005-09-13  6:48   ` Keith Owens
2005-09-13  7:27 ` Keith Owens
2005-09-13  7:27   ` Keith Owens
2005-09-17 15:47   ` Tony Luck
2005-09-17 15:47     ` Tony Luck
2005-09-17 15:59     ` John W. Linville
2005-09-17 15:59       ` John W. Linville
2005-09-17 16:16       ` Greg KH
2005-09-17 16:16         ` Greg KH
2005-09-17 16:34         ` Jack Steiner [this message]
2005-09-17 16:34           ` Jack Steiner
2005-09-17 16:48           ` John W. Linville
2005-09-17 16:48             ` John W. Linville
2005-09-17 16:46         ` John W. Linville
2005-09-17 16:46           ` John W. Linville
2005-09-18  6:23       ` David S. Miller
2005-09-18  6:23         ` David S. Miller
2005-09-18  6:33         ` Tony Luck
2005-09-18  6:33           ` Tony Luck
2005-09-18 11:44         ` Jack Steiner
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=20050917163434.GB24322@sgi.com \
    --to=steiner@sgi.com \
    --cc=greg@kroah.com \
    --cc=kaos@sgi.com \
    --cc=linux-ia64@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tony.luck@gmail.com \
    /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.