All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Renninger <trenn@suse.de>
To: Ariel@bellino.com.ar
Cc: cpufreq@vger.kernel.org
Subject: Re: Possible bug
Date: Tue, 24 Jul 2012 14:01:53 +0200	[thread overview]
Message-ID: <201207241401.54084.trenn@suse.de> (raw)
In-Reply-To: <WC20120721070908.150028@bellino.com.ar>

On Saturday, July 21, 2012 09:09:08 AM Ariel Norberto Bellino wrote:
> Hi.
> 
> I'm not sure if this is a bug, but I couldn't find any useful information,
> so here I write. Hope it's not a problem.
> 
> cpufreq-info shows this in my laptop:
> hardware limits: 800 MHz - 2.53 GHz
> available frequency steps: *2.53 GHz, 2.53 GHz*, 1.60 GHz, 800 MHz
This should be a typical and well-known BIOS setup.
For some reason some BIOSes export the highest frequency twice (or with
one HZ difference or similar). Linux kernel should be able to handle this
gracefully. This is nothing to worry about.

  Thomas

  reply	other threads:[~2012-07-24 12:01 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-21  7:09 Possible bug Ariel Norberto Bellino
2012-07-24 12:01 ` Thomas Renninger [this message]
2012-07-24 12:07   ` Jukka Ruohonen
2012-07-25  4:23     ` Ariel Norberto Bellino
  -- strict thread matches above, loose matches on Subject: below --
2016-05-06 19:48 David Kiarie
     [not found] ` <5d645be8-fbd0-0454-af00-baf34a2816a0@iommu.org>
     [not found]   ` <5d645be8-fbd0-0454-af00-baf34a2816a0-6ukY98dZOFrYtjvyW6yDsg@public.gmane.org>
2016-05-07  8:33     ` David Kiarie
2016-03-31 12:34 Possible Bug Roger H Newell
2016-03-31 14:37 ` Valdis.Kletnieks at vt.edu
     [not found]   ` <56FD5089.5070302@canonical.com>
2016-03-31 17:52     ` Valdis.Kletnieks at vt.edu
2016-03-31 18:16       ` Roger H Newell
2016-03-31 19:23         ` Valdis.Kletnieks at vt.edu
2016-03-31 20:22           ` Roger H Newell
     [not found]             ` <56FDD8D9.9010408@gmail.com>
2016-04-01 13:00               ` Roger H Newell
     [not found] ` <56FD38C4.8030201@gmail.com>
2016-03-31 15:08   ` Roger H Newell
     [not found]     ` <56FD4C35.5040301@gmail.com>
2016-03-31 16:25       ` Roger H Newell
2016-03-31 17:22         ` Valdis.Kletnieks at vt.edu
2016-03-31 16:30     ` Carlo Caione
     [not found]       ` <56FD5358.5010101@gmail.com>
2016-03-31 17:29         ` Roger H Newell
2016-03-31 18:42           ` Valdis.Kletnieks at vt.edu
2011-07-23 20:25 Possible bug Reuben Thomas
2009-12-08 13:18 ml-raid
2009-12-09  1:57 ` Neil Brown
2009-12-09  9:39   ` ml-raid
2003-06-09 19:40 Possible Bug Angelo
2002-10-01 15:44 possible bug undertow
2002-10-01 16:37 ` DervishD
2002-10-03  1:29   ` Denis Vlasenko
2002-10-02 22:38     ` DervishD

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=201207241401.54084.trenn@suse.de \
    --to=trenn@suse.de \
    --cc=Ariel@bellino.com.ar \
    --cc=cpufreq@vger.kernel.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 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.