From: Bob Picco <bob.picco@hp.com>
To: linux-ia64@vger.kernel.org
Subject: Re: ia64 uaccess changes?
Date: Fri, 04 Feb 2005 11:51:29 +0000 [thread overview]
Message-ID: <20050204115129.GZ17600@localhost.localdomain> (raw)
In-Reply-To: <1107509583.2555.51.camel@linux-znh>
Andrew Morton wrote: [Fri Feb 04 2005, 06:39:44AM EST]
> Bob Picco <bob.picco@hp.com> wrote:
> >
> > Well I was seeing the same problem with 2.6.11-rc2-mm1-mhp1.
> > This fixed it for me. I thought a patch had been sent upstream to Tony.
> > I'm not proposing this as a patch. I believe it was already done.
> >
> > bob
> >
> >
> > diff -ruNp -X /home/picco/losl/dontdiff linux-2.6.11-rc2-mm1-mhp1-orig/arch/ia64/kernel/entry.S linux-2.6.11-rc2-mm1-mhp1/arch/ia64/kernel/entry.S
> > --- linux-2.6.11-rc2-mm1-mhp1-orig/arch/ia64/kernel/entry.S 2005-01-26 15:29:06.000000000 -0500
> > +++ linux-2.6.11-rc2-mm1-mhp1/arch/ia64/kernel/entry.S 2005-01-27 14:30:41.000000000 -0500
> > @@ -987,7 +987,7 @@ dont_preserve_current_frame:
> > shladd in0=loc1,3,r17
> > mov in1=0
> > ;;
> > - .align 32
> > + TEXT_ALIGN(32)
> > rse_clear_invalid:
> > #ifdef CONFIG_ITANIUM
> > // cycle 0
>
> That's already in Linus's tree. And mine. So it's something else.
>
> Were you seeing the same oops?
>
I was seeing the one in create_elf_tables. So this doesn't sound the same
as your problem. Sorry.
bob
prev parent reply other threads:[~2005-02-04 11:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-04 9:33 ia64 uaccess changes? Zou Nan hai
2005-02-04 9:37 ` Andrew Morton
2005-02-04 9:44 ` Keith Owens
2005-02-04 11:35 ` Bob Picco
2005-02-04 11:39 ` Andrew Morton
2005-02-04 11:51 ` Bob Picco [this message]
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=20050204115129.GZ17600@localhost.localdomain \
--to=bob.picco@hp.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 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.