[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAMiJ5CXFUmZVhqtthFSo_68sv9oLtadHWYvum=mnJv9ECLf9Fw@mail.gmail.com>
Date: Mon, 23 Feb 2015 18:02:30 -0300
From: Rafael David Tinoco <inaddy@...ntu.com>
To: Peter Zijlstra <peterz@...radead.org>
Cc: Linus Torvalds <torvalds@...ux-foundation.org>,
LKML <linux-kernel@...r.kernel.org>,
Thomas Gleixner <tglx@...utronix.de>,
Jens Axboe <axboe@...nel.dk>,
Frederic Weisbecker <fweisbec@...il.com>,
Gema Gomez <gema.gomez-solano@...onical.com>,
Christopher Arges <chris.j.arges@...onical.com>,
Dave Jones <davej@...hat.com>
Subject: Re: smp_call_function_single lockups
>
> [11396.096002] Hardware name: OpenStack Foundation OpenStack Nova, BIOS Bochs 01/01/2011
>
> But its a virtual machine right? Its not running bare metal, its running
> a !virt kernel on a virt machine, so maybe some of the virt muck is
> borked?
>
> A very subtly broken APIC emulation would be heaps of 'fun'.
Indeed, I'll dig hypervisor changes... Anyway, this initial stack
trace was first seen during the "frequent lockups in 3.18rc4"
discussion:
https://lkml.org/lkml/2014/11/14/656
RIP: 0010:[<ffffffff9c11e98a>] [<ffffffff9c11e98a>]
generic_exec_single+0xea/0x1d0
At that time seen by Dave Jones, and running bare metal (if i remember
correctly).
--
Rafael Tinoco
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists