public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Patrick McHardy <kaber@trash.net>
To: Andi Kleen <ak@suse.de>
Cc: Ed Tomlinson <tomlins@cam.org>,
	Alexander Nyberg <alexn@dsv.su.se>,
	Parag Warudkar <kernel-stuff@comcast.net>,
	linux-kernel@vger.kernel.org
Subject: Re: X86_64: 2.6.12-rc3 spontaneous reboot
Date: Tue, 26 Apr 2005 22:28:33 +0200	[thread overview]
Message-ID: <426EA471.203@trash.net> (raw)
In-Reply-To: <20050426142252.GJ5098@wotan.suse.de>

[-- Attachment #1: Type: text/plain, Size: 604 bytes --]

Andi Kleen wrote:
> Ok thanks for the information. I will stare a bit at the patch.
> 
> It is very mysterious though. Even if the patch was somehow wrong
> the worst thing that could happen is that you end up with interrupts
> off when you shouldnt, and the NMI watchdog is very good 
> at catching that.

I found that bringing back the cli in retint_swapgs fixed the problem,
so I traced back paths that could get there with interrupts enabled
and found int_restore_rest -> int_with_check -> retint_swapgs.
Adding a cli to int_restore_rest fixes the problem for me. I hope this
helps.

Regards
Patrick

[-- Attachment #2: x --]
[-- Type: text/plain, Size: 426 bytes --]

Index: arch/x86_64/kernel/entry.S
===================================================================
--- 585883113da6fe9142de95138c8ed8ca898a4ccc/arch/x86_64/kernel/entry.S  (mode:100644 sha1:3233a15cc4e074c00b75569f21c2844ee280b214)
+++ uncommitted/arch/x86_64/kernel/entry.S  (mode:100644)
@@ -307,6 +307,7 @@
 1:	movl $_TIF_NEED_RESCHED,%edi	
 int_restore_rest:
 	RESTORE_REST
+	cli
 	jmp int_with_check
 	CFI_ENDPROC
 		

  parent reply	other threads:[~2005-04-26 20:28 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-24  4:08 X86_64: 2.6.12-rc3 spontaneous reboot Parag Warudkar
2005-04-24  8:41 ` Alexander Nyberg
2005-04-24 13:03   ` Ed Tomlinson
2005-04-24 13:35     ` ismail dönmez
2005-04-25  8:44     ` Patrick McHardy
2005-04-25 15:35       ` Andi Kleen
2005-04-25 18:14         ` Alexander Nyberg
2005-04-26  0:04           ` Patrick McHardy
2005-04-26  8:26             ` Alexander Nyberg
2005-04-26 13:04         ` Patrick McHardy
2005-04-26 13:53           ` Andi Kleen
2005-04-26 13:57             ` Patrick McHardy
2005-04-26 14:18               ` Patrick McHardy
2005-04-26 14:22                 ` Andi Kleen
2005-04-26 14:51                   ` Patrick McHardy
2005-04-26 14:53                     ` Andi Kleen
2005-04-26 15:04                       ` Patrick McHardy
2005-04-27 12:59                         ` Andi Kleen
2005-04-27 22:05                           ` Patrick McHardy
2005-04-26 20:28                   ` Patrick McHardy [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-04-24 21:58 Parag Warudkar

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=426EA471.203@trash.net \
    --to=kaber@trash.net \
    --cc=ak@suse.de \
    --cc=alexn@dsv.su.se \
    --cc=kernel-stuff@comcast.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tomlins@cam.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