From: Eliot Blennerhassett <eliot@blennerhassett.gen.nz>
To: Clemens Ladisch <clemens@ladisch.de>,
David Henningsson <david.henningsson@canonical.com>
Cc: Takashi Iwai <tiwai@suse.de>,
alsa-devel@alsa-project.org, "Nikita N." <nikitan@operamail.com>
Subject: Re: Speaker burnout
Date: Tue, 07 Apr 2015 19:49:37 +1200 [thread overview]
Message-ID: <55238C11.5000404@blennerhassett.gen.nz> (raw)
In-Reply-To: <5523868A.3020502@ladisch.de>
On 07/04/15 19:26, Clemens Ladisch wrote:
> In theory, it would be possible to do the mixing in the analog domain.
> But there is no way to find out what the HDA codec actually does except
> trying it out.
Dear testers, please perform the following steps:
1. Place laptop on heat-resistant surface in a well-ventilated space.
Have a fire extinguisher handy. Put on your earmuffs.
2. Start stopwatch
3. Set all alsa volumes to maximum
3.1 If screaming noise not already evident, play this full-scale square wave
4.1 If smoke or flames appear from your laptop, stop stopwatch.
Extinguish any flames.
4.2 If 30 seconds elapsed without smoke, terminate the test.
5. Report back to us the results, if necessary borrow a friend's
computer to do so.
Hmmm, why isn't anyone volunteering to do this testing?
Seriously, How is the safe limit going to be determined?
next prev parent reply other threads:[~2015-04-07 7:49 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-28 14:03 bug Nikita N.
2015-03-30 7:19 ` bug Clemens Ladisch
2015-03-30 10:27 ` bug Nikita N.
2015-03-30 11:13 ` bug Clemens Ladisch
2015-03-30 14:37 ` bug Nikita N.
2015-03-31 7:18 ` bug Eliot Blennerhassett
2015-03-31 8:19 ` bug Nikita N.
2015-03-31 8:38 ` bug Clemens Ladisch
2015-03-31 9:05 ` bug Nikita N.
2015-03-31 12:42 ` bug Clemens Ladisch
2015-03-31 8:41 ` potential speaker burnout Eliot Blennerhassett
2015-03-31 8:24 ` bug Ricard Wanderlof
2015-03-31 8:56 ` bug Nikita N.
2015-03-31 9:14 ` bug Ricard Wanderlof
2015-03-31 10:26 ` bug Maarten de Boer
2015-03-31 10:49 ` bug Nikita N.
2015-03-31 11:05 ` bug Maarten de Boer
2015-03-31 11:44 ` bug Ricard Wanderlof
2015-03-31 8:54 ` bug Eliot Blennerhassett
2015-03-31 9:34 ` Speaker burnout David Henningsson
2015-03-31 10:06 ` Nikita N.
2015-03-31 10:43 ` David Henningsson
2015-03-31 10:57 ` Alexander E. Patrakov
2015-03-31 11:23 ` Nikolay Dimitrov
2015-03-31 11:31 ` Ricard Wanderlof
2015-03-31 11:45 ` David Henningsson
2015-03-31 13:47 ` Torsten Schenk
2015-03-31 19:14 ` Nikita N.
2015-04-05 16:36 ` Takashi Iwai
2015-04-05 16:11 ` Takashi Iwai
2015-04-07 5:30 ` Eliot Blennerhassett
2015-04-07 7:09 ` David Henningsson
2015-04-07 7:26 ` Clemens Ladisch
2015-04-07 7:49 ` Eliot Blennerhassett [this message]
2015-04-07 10:55 ` David Henningsson
2015-04-07 11:29 ` Ricard Wanderlof
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=55238C11.5000404@blennerhassett.gen.nz \
--to=eliot@blennerhassett.gen.nz \
--cc=alsa-devel@alsa-project.org \
--cc=clemens@ladisch.de \
--cc=david.henningsson@canonical.com \
--cc=nikitan@operamail.com \
--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 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.