public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Valdis.Kletnieks@vt.edu
To: Thomas Renninger <trenn@suse.de>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	linux-kernel@vger.kernel.org
Subject: Re: 2.6.33-rc6 - BUG at drivers/cpufreq/cpufreq.c:88
Date: Mon, 08 Feb 2010 12:25:27 -0500	[thread overview]
Message-ID: <8111.1265649927@localhost> (raw)
In-Reply-To: Your message of "Fri, 05 Feb 2010 10:26:32 +0100." <201002051026.33057.trenn@suse.de>

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

On Fri, 05 Feb 2010 10:26:32 +0100, Thomas Renninger said:
> On Thursday 04 February 2010 17:00:02 Valdis.Kletnieks@vt.edu wrote:
> > Hit this one again while setting up to bisect another issue.  I've verified
> > that the fix *is* someplace in 2.6.33-rc6-mmotm0201 (as that one lives at least
> > all the way to single-user mode), so I'm basically asking that somebody find
> > the commit that fixes it and make sure it gets into 2.6.33-final.  I'd offer
> > the commit number for the fix, but I'm hoping somebody recognizes it and pushes
> > it so I don't have bisect to find the fixing commit.
> > 
> > Thomas?  Did you have a fix for this that hasn't been pulled by Linus yet?
> The fix is to remove the patch.
> 
> > Refresher:  The bad commit was:
> > 
> > commit 46aeb7430f79cb4d03e17fedd6399884ab3aa697
> > Author: Thomas Renninger <trenn@suse.de>
> > Date:   Mon Dec 14 11:44:11 2009 +0100
> > 
> >     [CPUFREQ] Fix race in cpufreq_update_policy()
> This one never hit Linus tree?
> It was in -mm, but got reverted.
> 
> Did you bisect on another tree?

Good catch, Thomas.

Looks like a miscue on my part - although the timestamp on the vmlinuz in /boot
matched the one in arch/x86/boot/bzImage, the file size matched  the one left
at the end of that bisect from last time.  Looks like I managed to cd into the
wrong /usr/src/linux-* when I copied the bzImage to /boot.

"D'Oh!" - H. Simpson.

Sorry for the inconvenience.


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

      reply	other threads:[~2010-02-08 17:26 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-04 16:00 2.6.33-rc6 - BUG at drivers/cpufreq/cpufreq.c:88 Valdis.Kletnieks
2010-02-05  9:26 ` Thomas Renninger
2010-02-08 17:25   ` Valdis.Kletnieks [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=8111.1265649927@localhost \
    --to=valdis.kletnieks@vt.edu \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.org \
    --cc=trenn@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