All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Angelo Dell'Aera" <buffer@antifork.org>
To: Jan Killius <jkillius@arcor.de>
Cc: Linux-Kernel <linux-kernel@vger.kernel.org>,
	Andrew Morton <akpm@osdl.org>
Subject: Re: Oops with cpufreq on 2.6.5-mm1
Date: Tue, 6 Apr 2004 11:51:49 +0200	[thread overview]
Message-ID: <20040406115149.6fc6edf8.buffer@antifork.org> (raw)
In-Reply-To: <20040406000500.GA26760@gate.unimatrix>

On Tue, 6 Apr 2004 02:05:00 +0200
Jan Killius <jkillius@arcor.de> wrote:

>Hi,
>cpufreq make an Oops on loading. I have attached the oops.

The problem seems to be located in find_psb_table(). In fact, 
while powernow_table is correctly initialized, it's never assigned
to data->powernow_table thus leading to a NULL pointer dereferencing
in cpufreq_frequency_table_cpuinfo(). Try this patch please.

Regards.

--

Angelo Dell'Aera 'buffer' 
Antifork Research, Inc.	  	http://buffer.antifork.org


--- linux-2.6.5-mm1/arch/i386/kernel/cpu/cpufreq/powernow-k8.c.old	2004-04-06 11:46:41.000000000 +0200
+++ linux-2.6.5-mm1/arch/i386/kernel/cpu/cpufreq/powernow-k8.c	2004-04-06 11:48:29.000000000 +0200
@@ -634,6 +634,8 @@
 			return -EIO;
 		}
 
+		data->powernow_table = powernow_table;
+
 		printk(KERN_INFO PFX "currfid 0x%x (%d MHz), currvid 0x%x\n",
 		       data->currfid, find_freq_from_fid(data->currfid), data->currvid);
 




  reply	other threads:[~2004-04-06  9:52 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-06  0:05 Oops with cpufreq on 2.6.5-mm1 Jan Killius
2004-04-06  9:51 ` Angelo Dell'Aera [this message]
2004-04-06 10:49   ` Dave Jones
  -- strict thread matches above, loose matches on Subject: below --
2004-04-06  8:45 Jan Killius
2004-04-06 10:16 Jan Killius
2004-04-06 13:54 ` Dave Jones
2004-04-06 14:53   ` Jan Killius
2004-04-06 15:03     ` Dave Jones
2004-04-07  0:26 Jan Killius

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=20040406115149.6fc6edf8.buffer@antifork.org \
    --to=buffer@antifork.org \
    --cc=akpm@osdl.org \
    --cc=jkillius@arcor.de \
    --cc=linux-kernel@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.