From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Andi Kleen <ak@suse.de>, LKML <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Pavel Machek <pavel@ucw.cz>,
Michal Piotrowski <michal.k.k.piotrowski@gmail.com>
Subject: Re: [2.6.23-rc1 REGRESSION] CPU hotplug totally broken on HPC nx6325 (x86_64)
Date: Thu, 26 Jul 2007 21:22:49 +0200 [thread overview]
Message-ID: <200707262122.50517.rjw@sisk.pl> (raw)
In-Reply-To: <alpine.LFD.0.999.0707260924150.3442@woody.linux-foundation.org>
On Thursday, 26 July 2007 18:43, Linus Torvalds wrote:
>
> On Thu, 26 Jul 2007, Rafael J. Wysocki wrote:
> >
> > On my Turion64-based HPC nx6325 with the 2.6.23-rc1 x86_64 kernel doing
> >
> > # echo 0 > /sys/devices/system/cpu/cpu1/online
> >
> > causes the system to crash in a spectacular fashion (call traces going
> > continuously on the console, no reaction to anything except for the power
> > button). For this reason, suspend and hibernation don't work as well.
>
> Yeah, I really shouldn't have applied that patch. I didn't notice that it
> not only cleaned up the direct memcpy's, it also re-introduced the damn
> broken code that we fixed once already.
>
> Dammit, that read-only debug support IS NOT WORTH THIS CRAP.
>
> I absolutely *detest* it when "debugging features" end up being the thing
> that causes crashes. I think it shows a total lack of taste and
> understanding, and I'm totally tired of it. This has happened too many
> times.
>
> Andi: please don't send this patch *ever* again. If a patch that is
> supposed to help debugging just causes problems, that patch should be
> thrown away FOREVER.
>
> Andrew - on that same note: please throw away the dwarf traceback crap
> from your tree that Andi is still apparently pushing. Exact same issue.
>
> Debugging "helper" code that has historically only caused problems. We
> could equally well just enable frame pointers for debugging and add the
> trivial code to follow that instead, and it would work (the way it has
> worked on x86 basically forever).
>
> Rafael, does reverting just this part (and leaving the "text_poke()"
> cleanups) work for you?
Yes, it does, with the appended fix on top. :-)
Greetings,
Rafael
---
arch/i386/kernel/alternative.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
Index: linux-2.6.23-rc1/arch/i386/kernel/alternative.c
===================================================================
--- linux-2.6.23-rc1.orig/arch/i386/kernel/alternative.c
+++ linux-2.6.23-rc1/arch/i386/kernel/alternative.c
@@ -432,7 +432,7 @@ void __init alternative_instructions(voi
*/
void __kprobes text_poke(void *oaddr, unsigned char *opcode, int len)
{
- memcpy(addr, opcode, len);
+ memcpy(oaddr, opcode, len);
sync_core();
/* Not strictly needed, but can speed CPU recovery up. Ignore cross cacheline
case. */
next prev parent reply other threads:[~2007-07-26 19:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-26 12:40 Rafael J. Wysocki
2007-07-26 16:43 ` Linus Torvalds
2007-07-26 19:22 ` Rafael J. Wysocki [this message]
2007-07-26 19:59 ` Linus Torvalds
2007-07-31 1:23 ` Chris Wright
2007-07-31 1:50 ` Linus Torvalds
2007-07-31 2:16 ` Chris Wright
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=200707262122.50517.rjw@sisk.pl \
--to=rjw@sisk.pl \
--cc=ak@suse.de \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michal.k.k.piotrowski@gmail.com \
--cc=pavel@ucw.cz \
--cc=torvalds@linux-foundation.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
all inboxes | Powered by JetHome®