mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Shawn Starr <Shawn.Starr@statpro.com>
To: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: [3.13-rc/78] random SIGBUS errors + 3.14-rc0 - KVM/QEMU - CPU hang issues
Date: Fri, 24 Jan 2014 13:53:28 +0000	[thread overview]
Message-ID: <2D0D6BCF6E60AC409111CEB14208943C0104BA28@TORINTEXCMBXP1.STATNET.statpro.com> (raw)

Hello folks,

After a couple days of uptime, with Google Chrome + Flash. This has happened twice, will crash with a SIGBUS and subsequent launches of Google Chrome will SIGBUS. In addition other programs may or may not SIGBUS but the whole system becomes unstable until a full reboot. I only see kaudit logs from kernel but nothing looks unusual and there are no other noticed messages indicating anything wrong.

Anyone else noticed SIGBUS issues w/ 3.13-rcX (-rc8 or final?)

For 3.14-rc0 in Fedora (rawhide non-debug repo), spinning up a VM w/ KVM causes kernel to report CPU hang by 'qemu' process, it's early in the 3.14 cycle so I expect things to be wild a bit but wanted to report that if anyone else hasn't noticed yet.

Thanks,

Shawn Starr
Sr. Linux Administrator 
StatPro | Toronto
Tel. +1 (416) 619-3972 | Fax. +1 (416) 598-9530
Twitter. @statprogroup
www.statpro.com

Looking for a bit of holiday cheer? Watch StatPro's latest video

StatPro Canada Inc. registered Office: 33 Yonge Street, Suite 1101, Toronto ON, M5E 1G4. StatPro Canada Inc. is a member of StatPro Group plc. 



This message is private and confidential. If you have received this message in error, please notify us and remove it from your system. Any views or opinions presented in this email are solely those of the author and might not represent those of StatPro. Warning: Although StatPro has taken reasonable precautions to ensure no viruses are present in this email, the company cannot accept responsibility for any loss or damage arising from the use of this email or attachments.

                 reply	other threads:[~2014-01-24 14:29 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=2D0D6BCF6E60AC409111CEB14208943C0104BA28@TORINTEXCMBXP1.STATNET.statpro.com \
    --to=shawn.starr@statpro.com \
    --cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®