Re: Problem with several Creative Labs soundcards, possibly more?

[Lee Revell <rlrevell@joe-job.com>]

Please don't top post.

On Fri, 2005-10-21 at 21:58 -0500, Nazo wrote:
> If I boot with pci=noacpi, the normal mandriva kernel hangs just after
> it says hit I for interactive setup.  The vanilla one starts up, but,
> when I try to play an audio file, I have the same problem.  Bear in
> mind when saying the problem lies with the kernel that I've seen this
> issue on several different kernel versions.
> 
> As for my motherboard, it's a Gigabyte 9NDA3J.  The chipset is the
> nForce 3 Ultra (which I believe is basically just a nForce 3 250 with
> the only change being the socket type, but, I'm not 100% sure.)  I
> think I saw some things using the 250 driver for the motherboard
> rather than saying ultra, but, like I said, I think this is probably
> ok.
> 

OK, it still sounds like a kernel problem.  The IRQ handling code in the
emu10k1 driver is quite simple and almost certainly free of bugs.  OTOH,
I see TONS of reports like this on LKML, and it's always an ACPI issue.

Unless someone on alsa-devel has a better idea, I think you need to
report this on the kernel bugzilla.

Can you check /proc/interrupts and see if the number of interrupts for
your soundcard increases when you play sounds?  Also please post the
output of "dmesg" after rebooting the machine and trying to play a
sound.

Lee

> On 10/21/05, Lee Revell <rlrevell@joe-job.com> wrote:
> > 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