linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: Takashi Iwai <tiwai@suse.de>
Cc: kernel list <linux-kernel@vger.kernel.org>
Subject: Re: thinkpad x60: sound problems in 4.15-rc1 was Re: thinkpad x60: sound problems in 4.14.0-next-20171114
Date: Tue, 2 Jan 2018 21:54:05 +0100	[thread overview]
Message-ID: <20180102205405.GB24307@amd> (raw)
In-Reply-To: <s5hindulwfv.wl-tiwai@suse.de>

[-- Attachment #1: Type: text/plain, Size: 1337 bytes --]

Hi!

> > > > > > pavel@amd:~$
> > > > > > 
> > > > > > Again, mplayer has problems, mpg123 works. This time mplayer started
> > > > > > playing video (w/o sound) after long delay.
> > > > > > 
> > > > > > Uh. huh. And now problems appeared in mpg123, too, and then went away
> > > > > > in mpg123 _and_ mplayer. Interesting.
> > > > > > 
> > > > > > I suspect some pulseaudio fun. chromium always has sound problems,
> > > > > > then I restart chromium and everything is ok. But something changed in
> > > > > > -next and 4.15-rc1, because mplayer did not have problems before.
> > > > > 
> > > > > Hm, there is no code change at all in sound/*.  If it happens only in
> > > > > linux-next, it must be something else...
> > > > 
> > > > It happened first in -next, now it is in 4.15-rc1.
> > > 
> > > So you meant a possible regression between 4.14 and 4.15-rc1?
> > 
> > Yes.
> 
> Hm, as far as I see, the only significant difference is the commit
> 20e3f985bb875fea4f86b04eba4b6cc29bfd6b71
>     ALSA: pcm: update tstamp only if audio_tstamp changed

Hmm. So audio here is broken in more than one way, but revert of
20e3f985 seems to make it better.

								Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]

      parent reply	other threads:[~2018-01-02 20:54 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-15 10:05 thinkpad x60: sound problems in 4.14.0-next-20171114 Pavel Machek
2017-11-15 10:43 ` Takashi Iwai
2017-11-15 11:11   ` Pavel Machek
2017-11-15 11:14     ` Takashi Iwai
2017-11-20 23:25       ` Pavel Machek
2017-11-27 16:30     ` thinkpad x60: sound problems in 4.15-rc1 was " Pavel Machek
2017-11-27 16:33       ` Takashi Iwai
2017-11-27 18:31         ` Pavel Machek
2017-11-27 18:35           ` Takashi Iwai
2017-11-27 18:44             ` Pavel Machek
2017-11-28  7:00               ` Takashi Iwai
2017-12-14  9:57                 ` Pavel Machek
2017-12-19  2:06                   ` vcaputo
2017-12-19  4:54                     ` vcaputo
2017-12-19 23:12                       ` vcaputo
2017-12-19 23:22                         ` Pavel Machek
2017-12-20  0:36                           ` vcaputo
2017-12-20  0:33                             ` Thomas Gleixner
2017-12-20  0:59                               ` vcaputo
2017-12-23  5:37                               ` vcaputo
2017-12-23 20:37                                 ` vcaputo
2017-12-23 20:33                                   ` Thomas Gleixner
2017-12-24 16:16                                     ` vcaputo
2017-12-28 10:41                                       ` Thomas Gleixner
2017-12-28 18:30                                         ` vcaputo
2017-12-28 23:24                                         ` [tip:x86/urgent] x86/apic: Switch all APICs to Fixed delivery mode tip-bot for Thomas Gleixner
2017-12-29 13:31                                         ` tip-bot for Thomas Gleixner
2017-12-29 13:35                                           ` Thomas Gleixner
2017-12-25 10:12                                 ` thinkpad x60: sound problems in 4.15-rc1 was Re: thinkpad x60: sound problems in 4.14.0-next-20171114 Pavel Machek
2017-12-25 10:09                       ` Pavel Machek
2018-01-02 20:54                 ` Pavel Machek [this message]

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=20180102205405.GB24307@amd \
    --to=pavel@ucw.cz \
    --cc=linux-kernel@vger.kernel.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).