Messages in this thread Patch in this message |  | | | Date | Sun, 25 Jun 2006 03:49:13 -0700 | | From | Andrew Morton <> | | Subject | Re: Problem with 2.6.17-mm2 |
| |
On Sun, 25 Jun 2006 12:35:23 +0200 Ralf Hildebrandt <Ralf.Hildebrandt@charite.de> wrote:
> 2.6.17 and 2.6.17.1 work OK, but using -mm2 gives me two oddieties:
OK, thanks.
> 1) A lot of "unexpected IRQ trap at vector X" for X=[09,07]
hm, ack_bad_irq(). That isn't supposed to happen.
Ingo, Thomas - it's possible that -mm2's genirq is affecting x86?
> 2) A problem with the powernow_k8 driver, which makes the kernel puke upon modprobe (at the end of my dmes output).
yup, I uploaded the below for for that into the hot-fixes directory.
--- a/drivers/cpufreq/cpufreq.c~cpu-hotplug-make-cpu_notifier-related-notifier-calls-__cpuinit-only-fix-fix +++ a/drivers/cpufreq/cpufreq.c @@ -1551,7 +1551,7 @@ static struct notifier_block __cpuinitda * (and isn't unregistered in the meantime). * */ -int __cpuinit cpufreq_register_driver(struct cpufreq_driver *driver_data) +int cpufreq_register_driver(struct cpufreq_driver *driver_data) { unsigned long flags; int ret; _ - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
|  |