From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Takashi Iwai <tiwai@suse.de>
Cc: Arjan van de Ven <arjan@linux.intel.com>,
LKML <linux-kernel@vger.kernel.org>,
pm list <linux-pm@lists.linux-foundation.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [2.6.30-rc1-git2 regressions] Hibernation broken and (minor but annoying) audio problem
Date: Tue, 14 Apr 2009 23:12:33 +0200 [thread overview]
Message-ID: <200904142312.33833.rjw@sisk.pl> (raw)
In-Reply-To: <s5hzlej308a.wl%tiwai@suse.de>
On Tuesday 14 April 2009, Takashi Iwai wrote:
> At Fri, 10 Apr 2009 00:57:41 +0200,
> Rafael J. Wysocki wrote:
> >
> > Second, KDE4 on openSUSE 11.1 sometimes fails to handle audio correctly after
> > a fresh boot. Everything seems to work, but there's no sound at all. It is
> > sufficient to close the X session and start the desktop environment again to
> > make it work, though (may that be async too? ;-)). The hardware in question is
> > Intel Corporation 82801G (ICH7 Family) High Definition Audio Controller
> > (rev 02) and the driver is snd_hda_intel.
>
> Is this problem still there?
Just a few minutes ago sound stopped working (that was after a resume from S3,
but not immediately after it), without anything suspicious in dmesg etc.
Restarting X fixed that.
Still, that doesn't happen very often and it is not readily reproducible.
> If restarting the X session fixes the problem, it could be a
> pulseaudio problem. But, then it doesn't sound like a kernel update
> issue.
Well, that may be a pulseaudio problem, but the very same pulsaudio apparently
worked well with 2.6.29-git<something>. That might be a coincidence, though.
> Could you check whether non-PA environment (e.g. linux console) works
> reliably?
Yes, it appears to work.
Thanks,
Rafael
next prev parent reply other threads:[~2009-04-14 21:13 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-09 22:57 [2.6.30-rc1-git2 regressions] Hibernation broken and (minor but annoying) audio problem Rafael J. Wysocki
2009-04-09 23:06 ` Linus Torvalds
2009-04-10 12:39 ` Rafael J. Wysocki
2009-04-10 18:58 ` [linux-pm] " Rafael J. Wysocki
2009-04-10 19:17 ` Linus Torvalds
2009-04-11 0:06 ` Rafael J. Wysocki
2009-04-11 1:19 ` Linus Torvalds
2009-04-11 1:45 ` Arjan van de Ven
2009-04-11 2:10 ` Arjan van de Ven
2009-04-11 10:46 ` Rafael J. Wysocki
2009-04-11 19:38 ` Rafael J. Wysocki
2009-04-11 19:55 ` Linus Torvalds
2009-04-11 20:05 ` Arjan van de Ven
2009-04-12 18:06 ` Rafael J. Wysocki
2009-04-12 18:27 ` Arjan van de Ven
2009-04-11 1:53 ` Arjan van de Ven
2009-04-11 2:35 ` Len Brown
2009-04-11 18:11 ` Linus Torvalds
2009-04-11 19:00 ` Heinz Diehl
2009-04-11 19:16 ` Arjan van de Ven
2009-04-11 19:50 ` Linus Torvalds
2009-04-11 20:11 ` Arjan van de Ven
2009-04-11 20:18 ` Arkadiusz Miskiewicz
2009-04-14 12:09 ` Takashi Iwai
2009-04-14 21:12 ` Rafael J. Wysocki [this message]
2009-04-15 13:13 ` Takashi Iwai
2009-04-15 20:59 ` Rafael J. Wysocki
2009-04-15 21:05 ` Linus Torvalds
2009-04-16 6:05 ` Takashi Iwai
2009-04-16 20:18 ` Rafael J. Wysocki
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=200904142312.33833.rjw@sisk.pl \
--to=rjw@sisk.pl \
--cc=akpm@linux-foundation.org \
--cc=arjan@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@lists.linux-foundation.org \
--cc=tiwai@suse.de \
--cc=torvalds@linux-foundation.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox