Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Lee Revell <rlrevell@joe-job.com>
To: Nazo <nazosan@gmail.com>
Cc: alsa-user@lists.sourceforge.net,
	alsa-devel <alsa-devel@lists.sourceforge.net>
Subject: Re: Problem with several Creative Labs soundcards, possibly more?
Date: Fri, 21 Oct 2005 19:58:53 -0400	[thread overview]
Message-ID: <1129939134.4724.26.camel@mindpipe> (raw)
In-Reply-To: <a5a496a90510211519y15711764ode0a2fe4053695d8@mail.gmail.com>

On Fri, 2005-10-21 at 17:19 -0500, Nazo wrote:
> When I got it to sucessfully boot, and tried to play something, it
> played one frame over and over in a loop (kind of like what happens
> when the system locks up in the middle of a game or something.)  When
> the application was closed and another different sound file was
> attempted, it gave an IO error and no sound came out at all.  Based on
> the way it kind of acted like the hardware locked up or something, my
> first guess would be maybe something along the lines of an IRQ
> conflict or somesuch?  That's just a guess though.  Anyway, he thought
> it might be useful if I provided some extra info, so I've added them
> to the bottom of the message:
> 

OK, this is a classic sign that interrupts are not being acknowledged
properly.  It's not a problem with the ALSA drivers but with the kernel.
Probably an ACPI issue.

What is the make and model of your motherboard?

Does it work if you boot with "pci=noacpi"?

Lee




-------------------------------------------------------
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl

       reply	other threads:[~2005-10-21 23:58 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <a5a496a90510190840v7f7d2345s133b06eaad0a4719@mail.gmail.com>
     [not found] ` <ad2655cb0510190920n5a0a4ddby@mail.gmail.com>
     [not found]   ` <a5a496a90510191156i24c69e17yc35184577090f9f5@mail.gmail.com>
     [not found]     ` <4356C414.9060008@superbug.co.uk>
     [not found]       ` <a5a496a90510191414n651099e8x9d9952638ce84729@mail.gmail.com>
     [not found]         ` <4356C875.5030607@superbug.co.uk>
     [not found]           ` <a5a496a90510191845w55200b77y927dc92470b15784@mail.gmail.com>
     [not found]             ` <a5a496a90510211519y15711764ode0a2fe4053695d8@mail.gmail.com>
2005-10-21 23:58               ` Lee Revell [this message]
2005-10-22  2:58                 ` Problem with several Creative Labs soundcards, possibly more? Nazo
2005-10-22  5:09                   ` Lee Revell
     [not found]                     ` <a5a496a90510220024n490d6564t23125c52986b322c@mail.gmail.com>
2005-10-22 17:12                       ` Lee Revell
2005-10-22 17:24                         ` [Alsa-user] " Nazo
2005-10-22 17:27                           ` Lee Revell
2005-10-22 20:29                   ` Lee Revell
2005-10-23  1:00                     ` Nazo
2005-10-23  1:07                       ` Bill Unruh
2005-10-23  1:43                         ` [Alsa-user] " Nazo
2005-10-23  2:44                           ` Bill Unruh
2005-10-23  2:14                       ` [Alsa-devel] " Lee Revell
2005-10-23  2:28                         ` Re: [Alsa-user] " Nazo
2005-10-24  4:47                           ` Tim Sawchuck
2005-10-24  4:52                           ` Tim Sawchuck

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=1129939134.4724.26.camel@mindpipe \
    --to=rlrevell@joe-job.com \
    --cc=alsa-devel@lists.sourceforge.net \
    --cc=alsa-user@lists.sourceforge.net \
    --cc=nazosan@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