[LAU] Hard lock-ups -- Trying to narrow the cause

Ken Restivo ken at restivo.org
Mon May 25 02:23:34 EDT 2009


On Sun, May 24, 2009 at 07:14:17PM -0700, Aaron L. wrote:
> Ken,
> 
> I have an Intel soundcard:
> 
> aaron at mycomputername:~$ lspci |grep -e Audio
> 00:1f.5 Multimedia audio controller: Intel Corporation 82801EB/ER
> (ICH5/ICH5R) AC'97 Audio Controller (rev 02)
> 
> I'm hosed huh.
> 
> 

Not necessarily. It's a crappy chip, but it's not that hard to get it working. Check ALSA docs or ALSA mailing list, perhaps.

The one in my EEE has been very solid, using ALSA 1.0.18a. Everything works except line in, which is disabled somehow, but other than that it's fine, and I just spent the past few hours running JACK on it and praticing stuff for tomorrow.

FWIW, my chip is slightly different than yours:
00:1b.0 Audio device: Intel Corporation 82801G (ICH7 Family) High Definition Audio Controller (rev 02)

Which appears to be the exact same one I have in my Asus Core 2 Duo laptop too, and which doesn't work at all on that machine with ALSA 1.0.13, so maybe when I finish upgrading that Asus this week, it'll actually work for the first time ever.

Maybe check /proc/asound/version and see whatcha got in there, and be prepared to download the most recent ALSA driver source and build/install it.

-ken
----------------
> On Sun, May 24, 2009 at 6:41 PM, Ken Restivo <ken at restivo.org> wrote:
> 
> > On Sat, May 23, 2009 at 12:12:02PM -0400, Darren Landrum wrote:
> > > Just had another lockup, a hard one (not even the mouse pointer would
> > > move) In addition (and this always happens, I forgot to mention it), the
> > > audio in the sound buffer at the time of the lock-up will loop over and
> > > over again making a sort of jack-hammer noise depending on what was in
> > > there at the time.
> > >
> > > This time, I had no proprietary Nvidia driver going, so that's
> > > eliminated as the cause. Unfortunately, I didn't ping the machine
> > > because it suddenly occurred to me that I'd never tried to ping the
> > > machine when it was working, so any result might be meaningless. I'll be
> > > sure to capture that baseline today.
> > >
> > > The other things I've eliminated is Flash playback, as this happened
> > > when I was playing back a long mp3 (a BBC podcast) in Totem. One other
> > > pattern I've noticed is that these hangs always happen when I'm playing
> > > back something with audio. I guess the next logical test is to go a week
> > > or so without playing anything and see what happens.
> > >
> > > So, I think it has to be the sound card. Whether it's a driver issue or
> > > a hardware issue remains to be seen.
> > >
> > > You can consider this email an angry rant more than anything, I suppose.
> > > :-/ Thanks for the help.
> > >
> >
> > It wouldn't happen to be an HDA-Intel sound card, would it?
> >
> > -ken
> > _______________________________________________
> > Linux-audio-user mailing list
> > Linux-audio-user at lists.linuxaudio.org
> > http://lists.linuxaudio.org/mailman/listinfo/linux-audio-user
> >

> _______________________________________________
> Linux-audio-user mailing list
> Linux-audio-user at lists.linuxaudio.org
> http://lists.linuxaudio.org/mailman/listinfo/linux-audio-user




More information about the Linux-audio-user mailing list