[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20130819105727.GA32308@gmail.com>
Date: Mon, 19 Aug 2013 12:57:27 +0200
From: Ingo Molnar <mingo@...nel.org>
To: Waiman Long <waiman.long@...com>
Cc: Thomas Gleixner <tglx@...utronix.de>,
Ingo Molnar <mingo@...hat.com>,
"H. Peter Anvin" <hpa@...or.com>, Arnd Bergmann <arnd@...db.de>,
linux-arch@...r.kernel.org, x86@...nel.org,
linux-kernel@...r.kernel.org,
Peter Zijlstra <peterz@...radead.org>,
Steven Rostedt <rostedt@...dmis.org>,
Andrew Morton <akpm@...ux-foundation.org>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Matt Fleming <matt.fleming@...el.com>,
Michel Lespinasse <walken@...gle.com>,
Andi Kleen <andi@...stfloor.org>,
Rik van Riel <riel@...hat.com>,
"Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Raghavendra K T <raghavendra.kt@...ux.vnet.ibm.com>,
George Spelvin <linux@...izon.com>,
Harvey Harrison <harvey.harrison@...il.com>,
"Chandramouleeswaran, Aswin" <aswin@...com>,
"Norton, Scott J" <scott.norton@...com>
Subject: Re: [PATCH v3 0/3] qrwlock: Introducing a queue read/write lock
implementation
* Waiman Long <waiman.long@...com> wrote:
> >Could be a CONFIG_BOOTPARAM_HARDLOCKUP_PANIC_VALUE=1
> >kernel?
> >
> >Thanks,
> >
> > Ingo
>
> My test system was a RHEL6.4 system. The 3.10 kernel
> config file was based on the original RHEL6.4 config
> file. So yes, the CONFIG_BOOTPARAM_HARDLOCKUP_PANIC_VALUE
> parameter was set.
Ok, good, so that's an expected panic.
Thanks,
Ingo
--
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