Bug 79912 - [sound] sound broken for 2 VIA chipsets: interrupt storm
Summary: [sound] sound broken for 2 VIA chipsets: interrupt storm
Status: Closed Overcome By Events
Alias: None
Product: Base System
Classification: Unclassified
Component: kern (show other bugs)
Version: Unspecified
Hardware: Any Any
: Normal Affects Only Me
Assignee: freebsd-multimedia (Nobody)
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-04-14 16:20 UTC by Leif Pedersen
Modified: 2017-06-27 04:38 UTC (History)
1 user (show)

See Also:


Attachments
dmesg-broken-sound.txt (10.46 KB, text/plain)
2005-04-14 19:25 UTC, Leif Pedersen
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Leif Pedersen 2005-04-14 16:20:11 UTC
      First, I apologize for the vagueness of my report and for not trying it on RC-2 yet.  The fact is I haven't had time yet, but I figured it is important to get your attention before RC-3 is released.  :)  I will follow up with any information you request.  Thanks

AFTER I start playing, the kernel emits:

Interrupt storm detected on "irq17: ohci0"; throttling interrupt source
pcm0:play:0: play interrupt timeout, channel dead
pcm0:play:0: play interrupt timeout, channel dead

Oddly enough, sometimes mplayer will play up to about 10 seconds of a song, then start stuttering (roughly, playing each 0.5 seconds of music twice).  xmms and amp never emit any sound, and appear to block as soon as they write().  Xmms's time-counter never advances past 00:00

Fix: 

unknown
How-To-Repeat:       play an mp3 with xmms or amp
Comment 1 Leif Pedersen 2005-04-14 19:25:25 UTC
I should add dmesg outputs (attached)

These machines use different kernel modules for sound:  Elrond uses
snd_cmi and Legolas uses snd_via8233, and both exhibit the same
symptoms.

Elrond's motherboard is an Asus A7M266-D, and Legolas is a laptop,
Athlon 64, with the chipset VIA K8T800+VT8235CE.  Sorry if my
subject is misleading, but I don't know what Elrond's chipset is.  I
thought it was VIA, but I can't find the spec.

At any rate, it's disturbing to me that they're exhibiting the same
symptom on multiple versions of FreeBSD.  This may be a symptom of a
fairly widespread problem.

Let me know what I can do to help.  I'm comfortable with cvsup and
patching.  Thanks!
Comment 2 Mark Linimon freebsd_committer freebsd_triage 2005-09-16 08:52:17 UTC
Responsible Changed
From-To: freebsd-i386->freebsd-multimedia

Over to maintainer(s).