From: Orion Poplawski <orion@cora.nwra.com>
To: linux-kernel@vger.kernel.org
Subject: How to debug random bus errors?
Date: Fri, 22 Sep 2006 11:11:14 -0600 [thread overview]
Message-ID: <ef15fm$uhs$1@sea.gmane.org> (raw)
We're seeing programs die with "bus error" (SIGBUS) randomly on a dual
processor Opteron machine. I've run memtest86+ and cpuburn stress tests
with no failure. gdb on a core file seems uninteresting. Is there some
way to trace the kernel to try to get more insight?
Thanks!
--
Orion Poplawski
System Administrator 303-415-9701 x222
NWRA/CoRA Division FAX: 303-415-9702
3380 Mitchell Lane orion@cora.nwra.com
Boulder, CO 80301 http://www.cora.nwra.com
next reply other threads:[~2006-09-22 17:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-22 17:11 Orion Poplawski [this message]
2006-09-22 19:33 ` How to debug random bus errors? Linus Torvalds
2006-09-22 21:20 ` Orion Poplawski
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='ef15fm$uhs$1@sea.gmane.org' \
--to=orion@cora.nwra.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