From: Orion Poplawski <orion@cora.nwra.com>
To: Linus Torvalds <torvalds@osdl.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: How to debug random bus errors?
Date: Fri, 22 Sep 2006 15:20:29 -0600 [thread overview]
Message-ID: <4514539D.8010704@cora.nwra.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0609221225500.4388@g5.osdl.org>
Linus Torvalds wrote:
>
> On Fri, 22 Sep 2006, Orion Poplawski wrote:
>> 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?
>
> Which kernel?
>
Sorry, 2.6.17-1.2142_FC4smp, so fairly recent.
> Other than that, does it tend to happen to the same particular program? It
> might just be a user space bug that needs a specific set of things to
> happen. Some of those bugs go away when you disable address space
> randomization etc, since they can depend on just pure luck (or rather,
> lack there-of).
So far just one program. Forgot about address space randomization, may
need to look into turning that off to help debugging.
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
prev parent reply other threads:[~2006-09-22 21:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-22 17:11 How to debug random bus errors? Orion Poplawski
2006-09-22 19:33 ` Linus Torvalds
2006-09-22 21:20 ` Orion Poplawski [this message]
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=4514539D.8010704@cora.nwra.com \
--to=orion@cora.nwra.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.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