public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: Keith Owens <kaos@sgi.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] 2.5.50+ patch for the impatient...
Date: Fri, 06 Dec 2002 14:15:43 +0000	[thread overview]
Message-ID: <marc-linux-ia64-105590709805511@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590709805503@msgid-missing>

On Thu, 5 Dec 2002 00:13:59 -0800, 
David Mosberger <davidm@napali.hpl.hp.com> wrote:
>For those of you who're impatiently waiting for a 2.5.xx update, I put
>a preliminary patch at:
>
>  ftp://ftp.hpl.hp.com/pub/linux-ia64/patch-2.5.50-1.968-lia64.diff.gz
>
>The patch is relative to revision 1.968 of Linus' bitkeeper tree
>(which is 2.5.50 with a bunch of additional patches).  Only the Ski
>simulator has been tested.  Kernel modules are definitely broken at
>the moment, since the ia64-part of the in-kernel module-loader is
>missing (I don't use modules myself and in any case it may be better
>to wait until things have settled down a bit; it looks like Rich
>Henderson has convinced Rusty to make modules effectively shared
>objects).

kdb for 2.5 kernels is also completely broken.  It needs the section
data in kallsyms and Rusty has deleted that information.  See
http://www.kerneltrap.org/node.php?idP0.  Do not expect kdb for any
2.5 kernel until Rusty puts the debugging data back.  And BTW, do not
expect ksymoops to work either.



  parent reply	other threads:[~2002-12-06 14:15 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-05  8:13 [Linux-ia64] 2.5.50+ patch for the impatient David Mosberger
2002-12-05 16:19 ` Matt_Domsch
2002-12-05 17:06 ` Jesse Barnes
2002-12-05 17:08 ` David Mosberger
2002-12-05 22:50 ` Matt Domsch
2002-12-06 14:15 ` Keith Owens [this message]
2002-12-07  4:57 ` David Mosberger

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=marc-linux-ia64-105590709805511@msgid-missing \
    --to=kaos@sgi.com \
    --cc=linux-ia64@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