All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andy Lutomirski <luto@amacapital.net>
To: lkp@lists.01.org
Subject: Re: [x86LKP] PANIC: double fault, error_code: 0xffffffffffffffff
Date: Mon, 06 Oct 2014 12:39:41 -0700	[thread overview]
Message-ID: <5432EFFD.6090201@amacapital.net> (raw)
In-Reply-To: <20141005063802.GE3264@tassilo.jf.intel.com>

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

On 10/04/2014 11:38 PM, Andi Kleen wrote:
>> [    5.087621] Freeing unused kernel memory: 1248K (ffff8800014c8000 - ffff880001600000)
>> [    5.136856] Freeing unused kernel memory: 1936K (ffff88000181c000 - ffff880001a00000)
>> [    5.167951] random: init urandom read with 5 bits of entropy available
>> [   19.307116] PANIC: double fault, error_code: 0xffffffffffffffff
>> [   19.309941] Kernel panic - not syncing: Machine halted.
> 
> That's odd. I actually tested it in KVM.
> 
> Will try with your config.

In case it helps, Fengguang's bot seems to use rather old userspace
code.  It's entirely possible that it's doing something different with
arch_prctl than your userspace, causing gs or gsbase to behave differently.

--Andy

> 
>> kvm=(
>> 	qemu-system-x86_64
>> 	-cpu kvm64
>> 	-enable-kvm
>> 	-kernel $kernel
>> 	-initrd $initrd
>> 	-m 320
>> 	-smp 2
>> 	-net nic,vlan=1,model=e1000
>> 	-net user,vlan=1
>> 	-boot order=nc
>> 	-no-reboot
>> 	-watchdog i6300esb
>> 	-rtc base=localtime
>> 	-serial stdio
>> 	-display none
>> 	-monitor null 
>> )
> 
> -Andi
> 


  reply	other threads:[~2014-10-06 19:39 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 [this message]
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
2014-10-09  2:19         ` [LKP] " 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=5432EFFD.6090201@amacapital.net \
    --to=luto@amacapital.net \
    --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.