* No sound after returning from suspend-to-ram @ 2009-09-23 18:20 Ozan Çağlayan 2009-09-24 7:30 ` Takashi Iwai 0 siblings, 1 reply; 6+ messages in thread From: Ozan Çağlayan @ 2009-09-23 18:20 UTC (permalink / raw) To: alsa-devel, Takashi Iwai Hi, A user complains that after returning from suspend-to-ram, he isn't able to get any sound from his laptop until rebooting. I delayed reporting this one because I once thought that it may be related to Pulseaudio or some kind of mixer level problem but now I tried to suspect the kernel and the drivers as well. This is 2.6.30.5 with alsa-* 1.0.21a. I have dmesg and alsa-info outputs before and after s2ram: dmesg before s2ram: http://bugs.pardus.org.tr/attachment.cgi?id=4454 alsa-info before s2ram: http://bugs.pardus.org.tr/attachment.cgi?id=4455 dmesg after s2ram: http://bugs.pardus.org.tr/attachment.cgi?id=4456 alsa-info after s2ram: http://bugs.pardus.org.tr/attachment.cgi?id=4457 Note that a traceback is dumped in dmesg during resume. Maybe it will give a clue about the problem, dunno. And there's something like hda_codec: invalid CONNECT_LIST verb 12[2]:2100 in regular dmesg output, i wonder what does that mean too. Any ideas? Thanks, Ozan Caglayan ^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: No sound after returning from suspend-to-ram 2009-09-23 18:20 No sound after returning from suspend-to-ram Ozan Çağlayan @ 2009-09-24 7:30 ` Takashi Iwai 2009-09-24 19:03 ` Ozan Çağlayan 0 siblings, 1 reply; 6+ messages in thread From: Takashi Iwai @ 2009-09-24 7:30 UTC (permalink / raw) To: Ozan Çağlayan; +Cc: alsa-devel At Wed, 23 Sep 2009 21:20:19 +0300, Ozan Çağlayan wrote: > > Hi, > > A user complains that after returning from suspend-to-ram, he isn't able > to get any sound from his laptop until rebooting. Even reloading the driver doesn't fix? No sound even from the headphone? If so, it's weird. Likely the issue below the sound hardware level, i.e. PCI or somewhat the core stuff. > I delayed reporting > this one because I once thought that it may be related to Pulseaudio or > some kind of mixer level problem but now I tried to suspect the kernel > and the drivers as well. > > This is 2.6.30.5 with alsa-* 1.0.21a. I have dmesg and alsa-info outputs > before and after s2ram: > > dmesg before s2ram: > http://bugs.pardus.org.tr/attachment.cgi?id=4454 > > alsa-info before s2ram: > http://bugs.pardus.org.tr/attachment.cgi?id=4455 > > dmesg after s2ram: > http://bugs.pardus.org.tr/attachment.cgi?id=4456 > > alsa-info after s2ram: > http://bugs.pardus.org.tr/attachment.cgi?id=4457 > > > Note that a traceback is dumped in dmesg during resume. Maybe it will > give a clue about the problem, dunno. Hm, I don't see anything special there through a quick glance... > And there's something like > > hda_codec: invalid CONNECT_LIST verb 12[2]:2100 > > in regular dmesg output, i wonder what does that mean too. It means the widget 0x12 has an insufficient connection list. When you look at codec proc file, you find that it has connection 0. This is usually a hardware issue (e.g. a bug of codec chip). Takashi _______________________________________________ Alsa-devel mailing list Alsa-devel@alsa-project.org http://mailman.alsa-project.org/mailman/listinfo/alsa-devel ^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: No sound after returning from suspend-to-ram 2009-09-24 7:30 ` Takashi Iwai @ 2009-09-24 19:03 ` Ozan Çağlayan 2009-09-28 8:34 ` Takashi Iwai 0 siblings, 1 reply; 6+ messages in thread From: Ozan Çağlayan @ 2009-09-24 19:03 UTC (permalink / raw) To: Takashi Iwai; +Cc: alsa-devel Takashi Iwai wrote: > Even reloading the driver doesn't fix? No sound even from the > headphone? If so, it's weird. Likely the issue below the sound > hardware level, i.e. PCI or somewhat the core stuff. > He said that rmmod/modprobe'ing snd_hda_intel brings the sound back. Should I CC this to lkml for grabbing suspend guys' attention? Regards, ^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: No sound after returning from suspend-to-ram 2009-09-24 19:03 ` Ozan Çağlayan @ 2009-09-28 8:34 ` Takashi Iwai 2009-09-28 9:16 ` Ozan Çağlayan 0 siblings, 1 reply; 6+ messages in thread From: Takashi Iwai @ 2009-09-28 8:34 UTC (permalink / raw) To: Ozan Çağlayan; +Cc: alsa-devel At Thu, 24 Sep 2009 22:03:44 +0300, Ozan Çağlayan wrote: > > Takashi Iwai wrote: > > Even reloading the driver doesn't fix? No sound even from the > > headphone? If so, it's weird. Likely the issue below the sound > > hardware level, i.e. PCI or somewhat the core stuff. > > > > He said that rmmod/modprobe'ing snd_hda_intel brings the sound back. > Should I CC this to lkml for grabbing suspend guys' attention? Well, first we need to check the diff of alsa-info outputs between before/after suspend. If reloading the driver helps, usually it's no the issue of the PCM core but rather the driver itself. Takashi _______________________________________________ Alsa-devel mailing list Alsa-devel@alsa-project.org http://mailman.alsa-project.org/mailman/listinfo/alsa-devel ^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: No sound after returning from suspend-to-ram 2009-09-28 8:34 ` Takashi Iwai @ 2009-09-28 9:16 ` Ozan Çağlayan 2009-09-28 9:18 ` Takashi Iwai 0 siblings, 1 reply; 6+ messages in thread From: Ozan Çağlayan @ 2009-09-28 9:16 UTC (permalink / raw) To: Takashi Iwai; +Cc: alsa-devel Takashi Iwai wrote On 28-09-2009 11:34: > Well, first we need to check the diff of alsa-info outputs between > before/after suspend. If reloading the driver helps, usually it's no > the issue of the PCM core but rather the driver itself. > > This is the diff before/after suspend. I also wanted before/after/unload-reload alsa-info outputs. The amp-out values may be modified by the user just after the suspend but the unsolicited tag isn't changeable by the user, right? @@ -226,7 +226,7 @@ Node 0x19 [Beep Generator Widget] wcaps 0x700200: Mono Digital Node 0x1a [Pin Complex] wcaps 0x40018d: Stereo Amp-Out Amp-Out caps: ofs=0x1f, nsteps=0x1f, stepsize=0x05, mute=1 - Amp-Out vals: [0x0a 0x0a] + Amp-Out vals: [0x0c 0x0c] Pincap 0x0000001f: OUT HP Detect Trigger ImpSense Pin Default 0x01813030: [Jack] Line In at Ext Rear Conn = 1/8, Color = Blue @@ -237,7 +237,7 @@ 0x0a Node 0x1b [Pin Complex] wcaps 0x40018d: Stereo Amp-Out Amp-Out caps: ofs=0x1f, nsteps=0x1f, stepsize=0x05, mute=1 - Amp-Out vals: [0x0a 0x0a] + Amp-Out vals: [0x0c 0x0c] Pincap 0x0001001f: OUT HP EAPD Detect Trigger ImpSense EAPD 0x2: EAPD Pin Default 0x01014011: [Jack] Line Out at Ext Rear @@ -280,7 +280,7 @@ Conn = Analog, Color = Unknown DefAssociation = 0xf, Sequence = 0x0 Pin-ctls: 0x40: OUT - Unsolicited: tag=0f, enabled=1 + Unsolicited: tag=2f, enabled=1 Connection: 1 0x0e Node 0x1f [Pin Complex] wcaps 0x400081: Stereo @@ -370,7 +370,7 @@ crw-rw----+ 1 root audio 116, 4 Sep 23 15:32 /dev/snd/hwC0D0 crw-rw----+ 1 root audio 116, 5 Sep 23 15:32 /dev/snd/hwC0D1 crw-rw----+ 1 root audio 116, 24 Sep 23 18:59 /dev/snd/pcmC0D0c -crw-rw----+ 1 root audio 116, 16 Sep 23 20:04 /dev/snd/pcmC0D0p +crw-rw----+ 1 root audio 116, 16 Sep 23 20:34 /dev/snd/pcmC0D0p crw-rw----+ 1 root audio 116, 17 Sep 23 18:59 /dev/snd/pcmC0D1p crw-rw----+ 1 root audio 116, 30 Sep 23 15:32 /dev/snd/pcmC0D6c crw-rw----+ 1 root audio 116, 22 Sep 23 15:32 /dev/snd/pcmC0D6p @@ -466,8 +466,8 @@ Playback channels: Front Left - Front Right Limits: Playback 0 - 31 Mono: - Front Left: Playback 10 [32%] [-31.50dB] [on] - Front Right: Playback 10 [32%] [-31.50dB] [on] + Front Left: Playback 12 [39%] [-28.50dB] [on] + Front Right: Playback 12 [39%] [-28.50dB] [on] Simple mixer control 'PCM',0 Capabilities: pvolume pswitch Playback channels: Front Left - Front Right @@ -597,8 +597,8 @@ · · comment.dbmax 0 · · iface MIXER · · name 'Master Playback Volume' -· · value.0 10 -· · value.1 10 +· · value.0 12 +· · value.1 12 · } · control.4 { · · comment.access 'read write' @@ -952,5 +952,29 @@ -- [17038.984733] ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready [17328.304515] hda_codec: invalid CONNECT_LIST verb 12[2]:2100 +[17381.230771] ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready +-- +[19218.645128] uhci_hcd 0000:00:1d.0: PCI INT A disabled +[19218.847104] HDA Intel 0000:00:1b.0: PCI INT A disabled +[19218.858097] HDA Intel 0000:00:1b.0: power state changed by ACPI to D3 +[19218.880064] ACPI: Preparing to enter system sleep state S3 +-- +[19218.880463] Hardware name: AMILO Pro V2045 +[19218.880464] Modules linked in: rfcomm radeon drm i2c_algo_bit sco bridge stp bnep l2cap bluetooth ipv6 xt_state iptable_nat nf_nat nf_conntrack_ipv4 nf_conntrack nf_defrag_ipv4 vboxnetadp vboxnetflt iptable_mangle iptable_raw microcode iptable_filter ip_tables x_tables vboxdrv snd_hda_codec_si3054 snd_hda_codec_analog snd_hda_intel snd_hda_codec snd_hwdep snd_seq_dummy snd_seq_oss snd_seq_midi_event snd_seq snd_seq_device snd_pcm_oss snd_mixer_oss snd_pcm snd_timer pcmcia snd ipw2200 libipw video tifm_sd iTCO_wdt soundcore lib80211 iTCO_vendor_support ppdev output snd_page_alloc yenta_socket rsrc_n onstatic r8169 pcmcia_core parport_pc tifm_7xx1 tifm_core lp intel_agp parport agpgart mii serio_raw pcspkr joydev brd pata_acpi sdhci_pci sdhci mmc_core led_class ohci1394 ieee1394 ata_piix ahci ata_gen eric libata firewire_ohci firewire_core +[19218.880530] Pid: 4018, comm: pm-suspend Not tainted 2.6.30.5-126 #1 +-- +[19218.924201] pcieport-driver 0000:00:01.0: restoring config space at offset 0x3 (was 0x10000, writing 0x10008) +[19218.924241] HDA Intel 0000:00:1b.0: restoring config space at offset 0x4 (was 0xd000c004, writing 0xb0000004) +[19218.924247] HDA Intel 0000:00:1b.0: restoring config space at offset 0x3 (was 0x0, writing 0x8) +[19218.924255] HDA Intel 0000:00:1b.0: restoring config space at offset 0x1 (was 0x100006, writing 0x100002) +[19218.924285] pcieport-driver 0000:00:1c.0: restoring config space at offset 0xf (was 0x40100, writing 0x4010b) +-- +[19218.925149] sdhci-pci 0000:06:09.4: restoring config space at offset 0x1 (was 0x2100000, writing 0x2100106) +[19219.772226] HDA Intel 0000:00:1b.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16 +[19219.772234] HDA Intel 0000:00:1b.0: setting latency timer to 64 +[19220.140249] uhci_hcd 0000:00:1d.0: PCI INT A -> GSI 23 (level, low) -> IRQ 23 +-- +[19255.960448] ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready +[19262.099609] hda_codec: invalid CONNECT_LIST verb 12[2]:2100 _______________________________________________ Alsa-devel mailing list Alsa-devel@alsa-project.org http://mailman.alsa-project.org/mailman/listinfo/alsa-devel ^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: No sound after returning from suspend-to-ram 2009-09-28 9:16 ` Ozan Çağlayan @ 2009-09-28 9:18 ` Takashi Iwai 0 siblings, 0 replies; 6+ messages in thread From: Takashi Iwai @ 2009-09-28 9:18 UTC (permalink / raw) To: Ozan Çağlayan; +Cc: alsa-devel At Mon, 28 Sep 2009 12:16:46 +0300, Ozan Çağlayan wrote: > > Takashi Iwai wrote On 28-09-2009 11:34: > > Well, first we need to check the diff of alsa-info outputs between > > before/after suspend. If reloading the driver helps, usually it's no > > the issue of the PCM core but rather the driver itself. > > > > > > This is the diff before/after suspend. I also wanted > before/after/unload-reload alsa-info outputs. The amp-out values may be > modified by the user just after the suspend but the unsolicited tag > isn't changeable by the user, right? Right, this is odd. A remaining question is *what* actually doesn't work. Are both headphone and speaker outputs tested? thanks, Takashi _______________________________________________ Alsa-devel mailing list Alsa-devel@alsa-project.org http://mailman.alsa-project.org/mailman/listinfo/alsa-devel ^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2009-09-28 9:18 UTC | newest] Thread overview: 6+ messages (download: mbox.gz follow: Atom feed -- links below jump to the message on this page -- 2009-09-23 18:20 No sound after returning from suspend-to-ram Ozan Çağlayan 2009-09-24 7:30 ` Takashi Iwai 2009-09-24 19:03 ` Ozan Çağlayan 2009-09-28 8:34 ` Takashi Iwai 2009-09-28 9:16 ` Ozan Çağlayan 2009-09-28 9:18 ` Takashi Iwai
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.