From: Andi Kleen <ak@linux.intel.com>
To: lkp@lists.01.org
Subject: Re: [x86LKP] PANIC: double fault, error_code: 0xffffffffffffffff
Date: Wed, 08 Oct 2014 19:19:48 -0700 [thread overview]
Message-ID: <20141009021948.GI3264@tassilo.jf.intel.com> (raw)
In-Reply-To: <20141007113311.GD16301@wfg-t540p.sh.intel.com>
[-- Attachment #1: Type: text/plain, Size: 179 bytes --]
> As the table shows, it's not an easily reproducible bug -- the possibility is
> less than 10%:
I think i found the problem. Thanks. Hopefully tests will pass now.
-Andi
WARNING: multiple messages have this Message-ID (diff)
From: Andi Kleen <ak@linux.intel.com>
To: Fengguang Wu <fengguang.wu@intel.com>
Cc: LKP <lkp@01.org>, Yuanhan Liu <yuanhan.liu@intel.com>,
linux-kernel@vger.kernel.org, Jet Chen <jet.chen@intel.com>,
Su Tao <tao.su@intel.com>
Subject: Re: [LKP] [x86LKP] PANIC: double fault, error_code: 0xffffffffffffffff
Date: Wed, 8 Oct 2014 19:19:48 -0700 [thread overview]
Message-ID: <20141009021948.GI3264@tassilo.jf.intel.com> (raw)
In-Reply-To: <20141007113311.GD16301@wfg-t540p.sh.intel.com>
> As the table shows, it's not an easily reproducible bug -- the possibility is
> less than 10%:
I think i found the problem. Thanks. Hopefully tests will pass now.
-Andi
next prev parent reply other threads:[~2014-10-09 2:19 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-04 13:47 [x86LKP] PANIC: double fault, error_code: 0xffffffffffffffff Fengguang Wu
2014-10-04 13:47 ` Fengguang Wu
2014-10-05 6:38 ` Andi Kleen
2014-10-05 6:38 ` Andi Kleen
2014-10-06 19:39 ` Andy Lutomirski
2014-10-06 20:37 ` Andi Kleen
2014-10-06 20:37 ` [LKP] " Andi Kleen
2014-10-07 11:33 ` Fengguang Wu
2014-10-07 11:33 ` [LKP] " Fengguang Wu
2014-10-09 2:19 ` Andi Kleen [this message]
2014-10-09 2:19 ` Andi Kleen
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=20141009021948.GI3264@tassilo.jf.intel.com \
--to=ak@linux.intel.com \
--cc=lkp@lists.01.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.