Comment 9 for bug 905246

Revision history for this message
Matthew O'Connor (uvirjf2u1144-matt-hknftjnl78lw) wrote : Re: [Bug 905246] Re: kernel BUG at/build/buildd/linux-3.0.0/arch/x86/kvm/mmu.c:703

3.3 doesn't exhibit the iSCSI initiator panic, but unfortunately causes
one of my two nodes (node B) to spontaneously reboot (no oops reported)
when it joins the DLM with node A. I am beginning to think node A has
some underlying issues, perhaps related to the last upgrade I did, and I
am tempted to perform a "clean"-install on it. Node A was the first and
only (to date) to exhibit the original CPU hang-bug that I commented
on. Node A started as 10.04 I believe, and was upgraded to 11.10. Node
B was clean-installed with 11.04 and upgraded to 11.10.

Node B is unfortunately a production node, so I have to roll back to
v3.0 and leave it there. I will try to isolate node A and get it some
(non-critical) company to perform further testing on kernels v3.3 and v3.2.

On 5/24/2012 3:43 PM, Joseph Salisbury wrote:
> @Matthew
>
> Can you possible test the latest v3.2 and/or the latest v3.3 kernels?
>
> v3.2: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.2.18-precise/
>
> v3.3: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.3.7-precise/
>

--

Sincerely,
  Matthew O'Connor

-----------------------------------------------------------------
Sr. Software Engineer
PGP/GPG Key: 0x55F981C4
Fingerprint: E5DC A0F8 5A40 E4DA 2CE6 B5A2 014C 2CBF 55F9 81C4

Engineering and Computer Simulations, Inc.
11825 High Tech Ave Suite 250
Orlando, FL 32817

Tel: 407-823-9991 x315
Fax: 407-823-8299
Email: <email address hidden>
Web: www.ecsorl.com
-----------------------------------------------------------------

CONFIDENTIAL NOTICE: The information contained in this electronic
message is legally privileged, confidential and exempt from disclosure
under applicable law. It is intended only for the use of the individual
or entity named above. If the reader of this message is not the intended
recipient, you are hereby notified that any dissemination, distribution
or copying of this message is strictly prohibited. If you have received
this communication in error, please notify the sender immediately by
return e-mail and delete the original message and any copies of it from
your computer system. Thank you.