From: Takashi Iwai <tiwai@suse.de>
To: Friedrich Ewaldt <friedrich.ewaldt@gmx.de>
Cc: Thierry Vignaud <tvignaud@mandrakesoft.com>,
alsa-user@lists.sourceforge.net,
alsa-devel@lists.sourceforge.net
Subject: Re: Re: [Alsa-user] fm801 driver status?
Date: Mon, 16 Dec 2002 16:12:09 +0100 [thread overview]
Message-ID: <s5hznr6roae.wl@alsa2.suse.de> (raw)
In-Reply-To: <3DFA25F1.2000705@gmx.de>
At Fri, 13 Dec 2002 19:24:49 +0100,
Friedrich Ewaldt wrote:
>
> Takashi Iwai wrote:
>
> >>lspci -n output:
> >>
> >>00:0b.0 Class 0401: 1319:0801 (rev a0)
> >>00:0b.1 Class 0980: 1319:0801 (rev a0)
> >>
> >>
> >
> >thanks, could you try the attached patch?
> >at least, the weird messages for allocation of invalid i/o ports
> >should disappear. not sure whether this cures the lock-up problem,
> >though.
> >
> >
> >Takashi
> >
> >
> done. The error in /var/log/messages doesn't appear any longer (I only
> get these 'sharing IRQ ...' messages). Thanks! But the system still
> locks up when stopping playback :-(
to be sure, could you elaborate the symptom again and the detail of
your system (kernel version, applied patches, ALSA version)?
especially, please check the following:
- loading the module and unloading it immediately works?
- the port and irq number are correct, i.e. match with the resources
listed on lspci?
- playback (via aplay) works? does the system hang up at the start,
during the playback or at the stop?
- during the playback, does the count in /proc/interrupts increases?
(check with another terminal)
a typical reason of such a hang up is either the wrong spinlocks,
unexpected infinite loops in the driver code, or the interrupt
storms. if it's the interrupt storm, then it can be related with the
hardware, often motherboard chipset, or BIOS version.
or, could it be because of ACPI? did you apply it?
ciao,
Takashi
-------------------------------------------------------
This sf.net email is sponsored by:
With Great Power, Comes Great Responsibility
Learn to use your power at OSDN's High Performance Computing Channel
http://hpc.devchannel.org/
next prev parent reply other threads:[~2002-12-16 15:12 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-12 14:45 fm801 driver status? Friedrich Ewaldt
2002-12-12 15:08 ` [Alsa-user] " Takashi Iwai
2002-12-12 16:27 ` Friedrich Ewaldt
2002-12-12 17:32 ` Takashi Iwai
2002-12-13 9:53 ` Thierry Vignaud
2002-12-13 11:17 ` Friedrich Ewaldt
2002-12-13 16:29 ` Takashi Iwai
2002-12-13 16:33 ` Thierry Vignaud
2002-12-13 16:57 ` Friedrich Ewaldt
2002-12-13 17:02 ` Takashi Iwai
2002-12-13 18:24 ` Friedrich Ewaldt
2002-12-16 15:12 ` Takashi Iwai [this message]
2002-12-16 20:55 ` Friedrich Ewaldt
2002-12-17 18:11 ` Takashi Iwai
2002-12-18 13:28 ` Friedrich Ewaldt
2002-12-19 11:31 ` Takashi Iwai
2002-12-19 20:21 ` Friedrich Ewaldt
2002-12-13 11:15 ` Friedrich Ewaldt
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=s5hznr6roae.wl@alsa2.suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@lists.sourceforge.net \
--cc=alsa-user@lists.sourceforge.net \
--cc=friedrich.ewaldt@gmx.de \
--cc=tvignaud@mandrakesoft.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 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.