From: Gernot Kohlhaas <gernot.kohlhaas@googlemail.com>
To: tiwai@suse.de
Cc: alsa-devel@alsa-project.org
Subject: Re: SB X-Fi driver fixes (Re: Testers wanted: New SB X-Fi driver)
Date: Mon, 08 Jun 2009 20:21:59 +0200 [thread overview]
Message-ID: <4A2D56C7.2090505@googlemail.com> (raw)
In-Reply-To: <s5hbpoz3pbj.wl%tiwai@suse.de>
Hi!
Works like a charme, except for some crashes I had...
Three crashes two days ago (in audacious) and two in xmms.
Sound keeps looping (a few ms) and my whole system is totally frozen.
After that I can't find any usable output in my log-files (no output
from the crash at all).
I'll play around a bit and see if I can crash it again.
Anything I should try/look for?
BTW: Is there any way to achive Low Pass Filtering with "on-board"
ALSA-Tools/Methods?
ATM I am using a ladspa plugin that I specified in my .asoundrc.
Kernel: 2.6.29-gentoo-r5 x86_64
gcc-4.3.3
glibc-2.8_p20080602-r1
lspci -vv
05:00.0 Multimedia audio controller: Creative Labs SB X-Fi
Subsystem: Creative Labs X-Fi XtremeGamer FATAL1TY PRO
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
ParErr- Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort-
<TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 64 (1000ns min, 1250ns max), Cache Line Size: 32 bytes
Interrupt: pin A routed to IRQ 16
Region 0: I/O ports at ec00 [size=32]
Region 1: Memory at fea00000 (64-bit, non-prefetchable) [size=2M]
Region 3: Memory at f8000000 (64-bit, non-prefetchable) [size=64M]
Capabilities: [40] Power Management version 2
Flags: PMEClk- DSI+ D1+ D2+ AuxCurrent=0mA
PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [50] Message Signalled Interrupts: Mask- 64bit+
Count=1/1 Enable-
Address: 0000000000000000 Data: 0000
Kernel driver in use: SB-XFi
Kernel modules: snd-ctxfi
dmesg:
SB-XFi 0000:05:00.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
--
http://www.gnupp.de/verschluesselung/warum.html
Key ID: 0x4C0B2250
Key: http://home.arcor.de/mr_maniac/ANDERES/public.gpg
next prev parent reply other threads:[~2009-06-08 18:22 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-04 18:42 Testers wanted: New SB X-Fi driver MonsieurWeller
2009-06-06 9:14 ` Takashi Iwai
[not found] ` <1244376026.6985.5.camel@polo-desktop>
2009-06-07 16:10 ` Takashi Iwai
2009-06-08 12:03 ` SB X-Fi driver fixes (Re: Testers wanted: New SB X-Fi driver) Takashi Iwai
2009-06-08 18:21 ` Gernot Kohlhaas [this message]
2009-06-08 19:28 ` Takashi Iwai
2009-06-08 20:16 ` Gernot Kohlhaas
2009-06-09 1:51 ` Takashi Iwai
2009-06-09 2:20 ` Takashi Iwai
2009-06-09 3:50 ` The Source
2009-06-09 5:32 ` Takashi Iwai
2009-06-09 5:23 ` Gernot Kohlhaas
2009-06-09 5:39 ` Takashi Iwai
2009-06-09 5:44 ` Gernot Kohlhaas
2009-06-09 6:24 ` Takashi Iwai
2009-06-09 9:54 ` Takashi Iwai
2009-06-09 17:11 ` Gernot Kohlhaas
2009-06-15 12:58 ` Takashi Iwai
2009-06-15 16:17 ` Gernot Kohlhaas
2009-06-28 13:07 ` Bjoern Olausson
2009-06-10 2:31 ` Lee Revell
2009-06-10 13:21 ` Sebastian Schneider
2009-06-10 13:33 ` Takashi Iwai
2009-06-10 14:02 ` Sebastian Schneider
2009-06-10 14:04 ` Takashi Iwai
[not found] ` <1244650915.4173.6.camel@polo-desktop>
2009-06-10 17:42 ` Testers wanted: New SB X-Fi driver Takashi Iwai
-- strict thread matches above, loose matches on Subject: below --
2009-06-08 18:35 SB X-Fi driver fixes (Re: Testers wanted: New SB X-Fi driver) Gernot Kohlhaas
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=4A2D56C7.2090505@googlemail.com \
--to=gernot.kohlhaas@googlemail.com \
--cc=alsa-devel@alsa-project.org \
--cc=tiwai@suse.de \
/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