Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: James Courtier-Dutton <James@superbug.co.uk>
To: Eric Shattow <lucent@gmail.com>
Cc: alsa-devel <alsa-devel@lists.sourceforge.net>
Subject: Re: amd64 bus error
Date: Wed, 05 Apr 2006 21:34:22 +0100	[thread overview]
Message-ID: <443429CE.8040304@superbug.co.uk> (raw)
In-Reply-To: <2c746f620604051315w53d94a5bo5236778a28397959@mail.gmail.com>

Eric Shattow wrote:
> This may be a hardware error on your computer platform.  Is the bug
> reproducible? If not, you should try replacing the CPU/ram of your
> test machine.
> 
>  Eric
> 
> On 4/5/06, James Courtier-Dutton <James@superbug.co.uk> wrote:
>> Here is a backtrace of a alsa application that ran for about 1 hour
>> before giving this:
>>
>> [New Thread 1098918240 (LWP 23392)]
>>
>> Program received signal SIGBUS, Bus error.
>> [Switching to Thread 1098918240 (LWP 23392)]
>> 0x00002aaaac51bcc8 in ao_alsa_loop (iarg=<value optimized out>)
>>     at start_alsa.c:494
>> 494                     if (poll (pfd, nfds, 200000) < 0) {
>>
>>
>> Have we had any bus error type fixes to alsa-driver between the current
>> ubuntu alsa version and the latest?
>> The poll() call above is with alsa file descriptors.
>>
>> James
>>

I ran one cycle of memtest86+ on it, and it has no errors.
I don't think this is a hardware problem.

James




-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642

      reply	other threads:[~2006-04-05 20:34 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-05 11:36 amd64 bus error James Courtier-Dutton
2006-04-05 20:15 ` Eric Shattow
2006-04-05 20:34   ` James Courtier-Dutton [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=443429CE.8040304@superbug.co.uk \
    --to=james@superbug.co.uk \
    --cc=alsa-devel@lists.sourceforge.net \
    --cc=lucent@gmail.com \
    /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