lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <s5hfwnjxsya.wl%tiwai@suse.de>
Date:	Thu, 09 Jun 2011 11:19:41 +0200
From:	Takashi Iwai <tiwai@...e.de>
To:	Michal Hocko <mhocko@...e.cz>
Cc:	LKML <linux-kernel@...r.kernel.org>, alsa-devel@...a-project.org
Subject: Re: [alsa-devel] Headphone output doesn't work with 3.0.0-rc* anymore

At Thu, 9 Jun 2011 10:56:16 +0200,
Michal Hocko wrote:
> 
> On Thu 09-06-11 08:09:18, Takashi Iwai wrote:
> > At Wed, 8 Jun 2011 19:48:55 +0200,
> > Michal Hocko wrote:
> > > 
> > > On Wed 08-06-11 18:03:24, Takashi Iwai wrote:
> > > > At Tue, 7 Jun 2011 20:05:58 +0200,
> > > > Michal Hocko wrote:
> > > > > 
> > > > > Hi,
> > > > > before 3.0.0-rc1, when I plugged anything into headphone output of my
> > > > > laptop, speakers were disabled and the sound has been routed to the
> > > > > headphone output. This doesn't seem to work anymore starting with
> > > > > 3.0.0-rc1. Speakers stay on even if I plug something to the headphone
> > > > > output.
> > > > > Is this a bug or a new behavior that userspace has to cope
> > > > > with?
> > > > > 
> > > > > I am sorry for the lack of information but I have no idea what to
> > > > > provide.
> > > > 
> > > > Please give alsa-info.sh output at best.  Run it with --no-upload
> > > > option, and attach the output file.  This will contain most of
> > > > necessary information.
> > > 
> > > See attached. I have added also .39 output where things work as expected
> > > (just in case it could be useful).
> > 
> > Thanks, that's helpful.
> > As a quirk solution, could you try to pass model=auto option to
> > snd-hda-intel module?
> 
> Headphones work now but speakers are quite... I have tried to play
> with Headphone and Speaker controls in alsamixer but no changes.
> 
> Here is what I get in logs when the module is loaded:
> [ 5320.360277] HDA Intel 0000:00:1b.0: PCI INT A disabled
> [ 5326.920247] HDA Intel 0000:00:1b.0: power state changed by ACPI to D0
> [ 5326.920262] HDA Intel 0000:00:1b.0: power state changed by ACPI to D0
> [ 5326.920279] HDA Intel 0000:00:1b.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
> [ 5326.920375] HDA Intel 0000:00:1b.0: irq 42 for MSI/MSI-X
> [ 5326.920405] HDA Intel 0000:00:1b.0: setting latency timer to 64
> [ 5326.981085] input: HDA Intel Mic as /devices/pci0000:00/0000:00:1b.0/sound/card0/input18
> [ 5326.981262] input: HDA Intel Mic as /devices/pci0000:00/0000:00:1b.0/sound/card0/input19
> [ 5326.987934] input: HDA Intel Headphone as /devices/pci0000:00/0000:00:1b.0/sound/card0/input20
> 
> [maybe not important but input numbers are increasing for every new load]

No bug, it's the implementation issue of input layer :)

> There is another strange thing. After I stop mplayer and wait for some
> time (~1min) I can hear a "click" sound and then there is no sound at
> all... If I start mplayer in the meantime it just works...

This is possibly the powersave.  It means that the resume doesn't work
properly after powersave.

> If I try to remove the module and load it again then things work and stop
> working after first playback again.
> 
> > You may need to adjust the mixer after changing
> > this, but it should provide the full (even better) functionality.
> > It'll support also the auto-mic jack switching.
> 
> $ amixer | grep -i "auto.*mic"
> What is the control to look at?

There is no control.  Simply plugging the mic jack will switch the
recording source automatically.


Takashi
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ