linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andi Kleen <ak@suse.de>
To: mikpe@csd.uu.se
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.4.21-rc1 on x86_64 oops at shutdown -h
Date: 24 Apr 2003 22:43:29 +0200	[thread overview]
Message-ID: <p73r87rwrri.fsf@oldwotan.suse.de> (raw)
In-Reply-To: <16040.16960.528537.454110@gargle.gargle.HOWL.suse.lists.linux.kernel>

mikpe@csd.uu.se writes:

> 2.4.21-rc1 on x86_64 oopses on me at shutdown -h in certain situations.
> It's repeatable. Here's the raw oops:

Ah I know what the problem is. I already fixed it in CVS two weeks ago, but 
the merge with marcelo was in the brokenness window and I forgot about
it because of the long delay (the patch got only applied three weeks
later or so)

Just copy arch/x86_64/lib/copy_user.S from an 2.4.20 kernel or revert the 
changes in  that file in 2.4.21-rc1, that should fix it.

Thanks for testing,
-Andi

       reply	other threads:[~2003-04-24 20:31 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <16040.16960.528537.454110@gargle.gargle.HOWL.suse.lists.linux.kernel>
2003-04-24 20:43 ` Andi Kleen [this message]
2003-04-25 11:54   ` 2.4.21-rc1 on x86_64 oops at shutdown -h mikpe
2003-04-24 20:00 mikpe

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=p73r87rwrri.fsf@oldwotan.suse.de \
    --to=ak@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mikpe@csd.uu.se \
    /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;
as well as URLs for NNTP newsgroup(s).