All of lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: david.ronis@mcgill.ca
Cc: alsa-devel@lists.sourceforge.net
Subject: Re: RE: Oops in latest CVS
Date: Mon, 01 Dec 2003 12:41:06 +0100	[thread overview]
Message-ID: <s5had6cbwa5.wl@alsa2.suse.de> (raw)
In-Reply-To: <200311301628.hAUGS4bV010629@ronispc.chem.mcgill.ca>

At Sun, 30 Nov 2003 11:28:04 -0500,
David Ronis wrote:
> 
> --text follows this line--
> 
> I've been complaining for several months about Oops's, lockups, etc.,
> on my Sony Viao Z5050S laptop.  Sometimes I would simply freeze,
> sometimes I got an oops (several of which have been posted), and last
> week, I actually got some sound, albeit very corrupted.
> 
> Last night I did a CVS update, rebuilt and installed, and promptly
> froze when I tried to use sound.  (I have things set up to have the
> modules loaded and unloaded automatically).  I was in X (gnome), and a
> second USB mouse installed, and a PCMCI modem card plugged in.
> 
> After unplugging all the add-in devices and rebooting, I decided to
> give alsa another try, hoping at least to get the poor-quality sound I
> had in the last version or perhaps an oops.  To my suprise it worked
> PERFECTLY!  What was different, is that I tried alsa before plugging
> any of the other devices in and before starting X.  Moreover, once
> alsa's modules were installed, everything else could be installed and
> the system seems stable.
> 
> Could the problem may have something to do with the fact that IRQ9
> is shared on this machine?  Here's what /proc/interrupts says:
> 
>   9:      72787          XT-PIC  Ricoh Co Ltd RL5c475, eth0, usb-uhci, NM256AV
> 
> I've copied the output of lshw below.  You'll notice lots of things use IRQ9.
> 
> Any suggestions?

the combination of USB and this chip is really bad, especially when
USB device is not initialized.  this will issue unprocessed
interrupts.
also, starting ALSA nm256 driver after X is problematic, too, since X
will break the video RAM area, which is shared with the sound driver
as a sound buffer.
hence,  USB -> ALSA -> X would the best order of initialization, i
guess.


Takashi


-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
Does SourceForge.net help you be more productive?  Does it
help you create better code?  SHARE THE LOVE, and help us help
YOU!  Click Here: http://sourceforge.net/donate/

      reply	other threads:[~2003-12-01 11:41 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-30 16:28 Oops in latest CVS David Ronis
2003-12-01 11:41 ` Takashi Iwai [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=s5had6cbwa5.wl@alsa2.suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@lists.sourceforge.net \
    --cc=david.ronis@mcgill.ca \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.