mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Larry Finger <Larry.Finger@lwfinger.net>
To: LKML <linux-kernel@vger.kernel.org>
Cc: Ingo Molnar <mingo@elte.hu>,
	wireless <linux-wireless@vger.kernel.org>,
	Alok Kataria <akataria@vmware.com>, Dan Hecht <dhecht@vmware.com>
Subject: Re: (Very old) Regression following commit bfc0f59
Date: Sat, 21 Jan 2012 20:27:40 -0600	[thread overview]
Message-ID: <4F1B741C.3050903@lwfinger.net> (raw)
In-Reply-To: <4F1B71F5.6020000@lwfinger.net>

On 01/21/2012 08:18 PM, Larry Finger wrote:
> I recently discovered that an ancient laptop built by Mtech and containing an
> AMD K6 450/2 CPU was generating errors when using the Cardbus versions of
> Broadcom cards using either b43 of b43legacy. Expecting some change in those
> drivers or ssb, I found a kernel old enough to work without the error, and did a
> bisection. I was very surprised when "x86: merge tsc calibration", which is
> commit bfc0f5947afa5e3a13e55867f4478c8a92c11dca (dated July 1, 2008), turned out
> to be the source of the regression. It was verified by generating a reversion
> patch. One main difference is that the bad code gets a processor speed of
> 214.398 MHz, whereas reverting the commit yields 428.845 MHz, which is more in
> keeping with the stated frequency of 450 MHz. As the machine is more than 10
> years old, the clock may have drifted considerably.

The newest kernel that was running on this laptop was 3.2-rc4. When I updated to 
3.3-rc1, the problem above was fixed, thus nothing needs to be done.

Larry


       reply	other threads:[~2012-01-22  2:27 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <4F1B71F5.6020000@lwfinger.net>
2012-01-22  2:27 ` Larry Finger [this message]
2012-01-21 22:44 Larry Finger

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=4F1B741C.3050903@lwfinger.net \
    --to=larry.finger@lwfinger.net \
    --cc=akataria@vmware.com \
    --cc=dhecht@vmware.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=mingo@elte.hu \
    /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

Powered by JetHome