All of lore.kernel.org
 help / color / mirror / Atom feed
From: john stultz <johnstul@us.ibm.com>
To: Lee Revell <rlrevell@joe-job.com>
Cc: Andi Kleen <ak@suse.de>,
	Parag Warudkar <kernel-stuff@comcast.net>,
	lkml <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 3/4] new timeofday x86-64 arch specific changes (v. B1)
Date: Wed, 08 Jun 2005 19:12:13 -0700	[thread overview]
Message-ID: <1118283133.5754.41.camel@cog.beaverton.ibm.com> (raw)
In-Reply-To: <1118281635.6247.42.camel@mindpipe>

On Wed, 2005-06-08 at 21:47 -0400, Lee Revell wrote:
> On Wed, 2005-06-08 at 15:51 +0200, Andi Kleen wrote:
> > On Mon, Jun 06, 2005 at 07:46:22AM -0400, Parag Warudkar wrote:
> > > On Monday 06 June 2005 05:29, Andi Kleen wrote:
> > > > And does it work with nopmtimer ?
> > > >
> > > > -Andi
> > > 
> > > Thanks for trimming the CC list. 
> > > 
> > > No it doesn't work with nopmtimer - music still plays fast. I have to go back 
> > > to 2.6.11 to get it to play at right speed. 
> > 
> > Then it is something else, not the pmtimer.
> > 
> > I dont know what it could be. Do a binary search? 
> 
> XMMS has a long history of buggy ALSA support, which has improved
> lately.  Make sure you're using the latest version.
> 
> Also try 2.6.11 with ALSA 1.0.9, maybe it's an interaction between ALSA
> and the new gettimeofday patches.

Wahzuntme! :)  Well, I'd be very interested if my patches were to blame,
but I believe Parag said it happened with or without my patches.

Parag: If I'm incorrect and the issue goes away without my patches,
please let me know as I want to get to the bottom of it. 

thanks
-john



  reply	other threads:[~2005-06-09  2:12 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-02 18:27 [PATCH 3/4] new timeofday x86-64 arch specific changes (v. B1) Parag Warudkar
2005-06-02 18:39 ` Nishanth Aravamudan
2005-06-02 23:05   ` Parag Warudkar
2005-06-02 23:20     ` john stultz
2005-06-02 23:33       ` Parag Warudkar
2005-06-02 23:50       ` Parag Warudkar
2005-06-03  7:05         ` Ulrich Windl
2005-06-03 15:24         ` john stultz
2005-06-05 17:05           ` Dominik Brodowski
2005-06-06  3:04             ` Parag Warudkar
2005-06-06  3:14               ` Dominik Brodowski
2005-06-10  0:48               ` George Anzinger
2005-06-06  9:21             ` Andi Kleen
2005-06-06  9:24               ` Dominik Brodowski
2005-06-06  9:30                 ` Andi Kleen
2005-06-06 13:32               ` Vojtech Pavlik
2005-06-06 22:53             ` john stultz
2005-06-03 16:30         ` Andi Kleen
2005-06-03 18:27           ` john stultz
2005-06-03 19:02             ` Christoph Lameter
2005-06-03 19:21               ` john stultz
2005-06-05 11:27             ` Andi Kleen
2005-06-06 22:51               ` john stultz
2005-06-04 18:40           ` Parag Warudkar
2005-06-05 11:28             ` Andi Kleen
2005-06-05 14:15               ` Parag Warudkar
2005-06-05 20:51                 ` Lee Revell
2005-06-05 21:41                   ` Parag Warudkar
2005-06-05 22:13                     ` Lee Revell
2005-06-06  9:29                 ` Andi Kleen
2005-06-06 11:46                   ` Parag Warudkar
2005-06-08 13:51                     ` Andi Kleen
2005-06-09  1:47                       ` Lee Revell
2005-06-09  2:12                         ` john stultz [this message]
2005-06-09  2:42                           ` Parag Warudkar
2005-06-09 14:17                           ` Andi Kleen
2005-06-03 13:32       ` Parag Warudkar
2005-06-02 18:40 ` john stultz
  -- strict thread matches above, loose matches on Subject: below --
2005-06-02 18:51 Parag Warudkar
2005-06-01 23:09 [PATCH 1/4] new timeofday core subsystem " john stultz
2005-06-01 23:12 ` [PATCH 2/4] new timeofday i386 arch specific changes " john stultz
2005-06-01 23:13   ` [PATCH 3/4] new timeofday x86-64 " john stultz
2005-06-02  0:37     ` Parag Warudkar
2005-06-02 17:34       ` john stultz

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=1118283133.5754.41.camel@cog.beaverton.ibm.com \
    --to=johnstul@us.ibm.com \
    --cc=ak@suse.de \
    --cc=kernel-stuff@comcast.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rlrevell@joe-job.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.