All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Henningsson <david.henningsson@canonical.com>
To: "Nikita N." <nikitan@operamail.com>,
	Clemens Ladisch <clemens@ladisch.de>,
	alsa-devel@alsa-project.org
Subject: Re: Speaker burnout
Date: Tue, 31 Mar 2015 11:34:13 +0200	[thread overview]
Message-ID: <551A6A15.1070605@canonical.com> (raw)
In-Reply-To: <1427726222.1872206.247049189.3E3BB0F7@webmail.messagingengine.com>



On 2015-03-30 16:37, Nikita N. wrote:
> We are the devs involved in dCore porting, and that is one of our users
> report:
> http://forum.tinycorelinux.net/index.php/topic,18225
>
> We verified that in few of our legacy laptops.
> It didn't reproduce for every laptop, but indeed in a couple of them,
> the temperature of the speakers reached extremes levels in few seconds,
> only unplugging the AC/DC cable saved them.
> This is a serious problem in our opinion, and we would hate to see our
> dCore reputation spoiled.
> We hate to admit, but it is *NOT* our bug, and would hate to see this
> bug reverse engineered into a virus/malware (on Linux, or other OS) and
> see ourselves blamed for it.
> So we would like to keep the incident quiet, and we are going to remove
> that thread from our forum.
> On the other side, we would expect any action from ALSA project in
> removing that tool and/or exposing the real individual/s guilty of
> writing that tool.
>
> Thank you for your attentions and looking forward your feedback.

My opinion is that; it would have been better if the laptop had hardware 
protection against these kinds of failures, but now that it apparently 
has not, it should be fixed at the second best level, i e, kernel drivers.

Preferrably by not exposing (at least not by default) the highest levels 
of speaker output.

If you have any concrete examples (alsa-info please!) of speakers that 
can be burned out, and you know a maximum speaker volume where this 
never happens, I think we should artifically lower the max volume to 
this level so that no mixer application can set the speaker volume 
higher than that.

-- 
David Henningsson, Canonical Ltd.
https://launchpad.net/~diwic

  parent reply	other threads:[~2015-03-31  9:34 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         ` David Henningsson [this message]
2015-03-31 10:06           ` Speaker burnout 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
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=551A6A15.1070605@canonical.com \
    --to=david.henningsson@canonical.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=clemens@ladisch.de \
    --cc=nikitan@operamail.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.