|
From: Bart V. A. <bar...@gm...> - 2009-07-17 06:51:43
|
On Fri, Jul 17, 2009 at 2:50 AM, Nicholas Nethercote<n.n...@gm...> wrote: > On Fri, Jul 17, 2009 at 2:40 AM, Bart Van >> +valgrind: > m_scheduler/scheduler.c:1199 (vgPlain_scheduler): the 'impossible' > happened. >>> +valgrind: VG_(scheduler), phase 3: run_innerloop detected host state invariant failure >>> + at 0x........: report_and_quit (m_libcassert.c:?) >>> + by 0x........: vgPlain_assert_fail (m_libcassert.c:?) >>> + by 0x........: vgPlain_scheduler (scheduler.c:?) >>> + by 0x........: run_a_thread_NORETURN (syswrap-linux.c:91) >> >> Is the above reproducible ? Have these results been obtained on a >> non-virtual or on a virtual machine ? > > I get it occasionally. This is a non-virtual machine. See > https://bugs.kde.org/show_bug.cgi?id=143888. It is supposedly a > kernel bug that has been fixed but it still comes up. Thanks for the info. Any idea whether the CPU brand (AMD or Intel) is relevant here ? I have not yet seen this issue on an Intel CPU running in 64-bit mode. Bart. |