public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Thomas Renninger <trenn@suse.de>
To: Marti Raudsepp <marti@juffo.org>
Cc: cpufreq@vger.kernel.org, Dave Jones <davej@redhat.com>,
	Thomas Gleixner <tglx@linutronix.de>,
	Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
	x86@kernel.org, Mark Langsdorf <mark.langsdorf@amd.com>,
	Rusty Russell <rusty@rustcorp.com.au>,
	Andreas Herrmann <andreas.herrmann3@amd.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] powernow-k8: On load failure, remind the user to enable support in BIOS setup
Date: Wed, 20 Jan 2010 16:56:51 +0100	[thread overview]
Message-ID: <201001201656.51376.trenn@suse.de> (raw)
In-Reply-To: <160211accaba09e778c6.1264001606@newn>

On Wednesday 20 January 2010 16:33:26 Marti Raudsepp wrote:
>  arch/x86/kernel/cpu/cpufreq/powernow-k8.c |  15 +++++++++------
>  1 files changed, 9 insertions(+), 6 deletions(-)
> 
> 
> In most cases this is simply user error or bad BIOS defaults, rather
> than a firmware problem.

Not acknowledged.
Bad BIOS defaults is a firmware problem.

But most often this happens if people upgrade their CPU and do not 
update their BIOS.
Or the vendor does not recognise the new CPU even if the BIOS got 
updated.

The itself message might be an enhancment, IMO it's not worth a patch.
But do not revert the FW_BUG part!

People complain to lkml or to the cpufreq list that cpufreq does not 
work. The [Firmware Bug] (FW_BUG) already reminds them to do following 
steps:
  - Read up the BIOS setting description
  - Update the BIOS
  - If it still does not work complain to the vendor

Also this string gets picked up by the linuxfirmwarekit and it could not 
detect anymore that the BIOS does not export cpufreq tables which is 
very often *not* a wrong BIOS default, in which case the message is 
misleading.

   Thomas

> Signed-off-by: Marti Raudsepp <marti@juffo.org>
> 
> diff --git a/arch/x86/kernel/cpu/cpufreq/powernow-k8.c 
b/arch/x86/kernel/cpu/cpufreq/powernow-k8.c
> --- a/arch/x86/kernel/cpu/cpufreq/powernow-k8.c
> +++ b/arch/x86/kernel/cpu/cpufreq/powernow-k8.c
> @@ -789,17 +789,20 @@
>  				(struct pst_s *)(psb+1), maxvid);
>  	}
>  	/*
> -	 * If you see this message, complain to BIOS manufacturer. If
> -	 * he tells you "we do not support Linux" or some similar
> -	 * nonsense, remember that Windows 2000 uses the same legacy
> -	 * mechanism that the old Linux PSB driver uses. Tell them it
> -	 * is broken with Windows 2000.
> +	 * If you see this message, check that Cool'N'Quiet is enabled
> +	 * in your BIOS setup. If that fails, complain to your BIOS
> +	 * manufacturer. If he tells you "we do not support Linux" or
> +	 * some similar nonsense, remember that Windows 2000 uses the
> +	 * same legacy mechanism that the old Linux PSB driver uses.
> +	 * Tell them it is broken with Windows 2000.
>  	 *
>  	 * The reference to the AMD documentation is chapter 9 in the
>  	 * BIOS and Kernel Developer's Guide, which is available on
>  	 * www.amd.com
>  	 */
> -	printk(KERN_ERR FW_BUG PFX "No PSB or ACPI _PSS objects\n");
> +	printk(KERN_ERR PFX "No PSB or ACPI _PSS objects\n");
> +	printk(KERN_ERR PFX "Make sure that Cool'N'Quiet support is "
> +		"enabled in your BIOS setup\n");
>  	return -ENODEV;
>  }
>  
> 


  reply	other threads:[~2010-01-20 15:56 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-20 15:33 [PATCH] powernow-k8: On load failure, remind the user to enable support in BIOS setup Marti Raudsepp
2010-01-20 15:56 ` Thomas Renninger [this message]
2010-01-20 17:19   ` Marti Raudsepp

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=201001201656.51376.trenn@suse.de \
    --to=trenn@suse.de \
    --cc=andreas.herrmann3@amd.com \
    --cc=cpufreq@vger.kernel.org \
    --cc=davej@redhat.com \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.langsdorf@amd.com \
    --cc=marti@juffo.org \
    --cc=mingo@redhat.com \
    --cc=rusty@rustcorp.com.au \
    --cc=tglx@linutronix.de \
    --cc=x86@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox