Processed: Re: linux-image-3.0.0-1-686-pae: EEE-PC 1000H: cpufreq cannot be set to ondemand
Processing commands for control@bugs.debian.org:
> unmerge 637395
Bug#637395: linux-image-3.0.0-1-686-pae: EEE-PC 1000H: cpufreq cannot be set to ondemand
Bug#635348: FATAL: Error inserting ... (/lib/modules/3.0.0-1-486/kernel/drivers/...
Bug#636141: cpufrequtils: with kernel 3.0.0, loadcpufreq loads all freq drivers
Bug#636194: cpufrequtils: loadcpufreq should not try to load every driver
Disconnected #637395 from all other report(s).
> reassign 637395 src:linux-2.6 3.0.0-1
Bug #637395 {Done: Mattia Dongili <malattia@debian.org>} [cpufrequtils] linux-image-3.0.0-1-686-pae: EEE-PC 1000H: cpufreq cannot be set to ondemand
Bug reassigned from package 'cpufrequtils' to 'src:linux-2.6'.
Bug No longer marked as found in versions cpufrequtils/007-1.
Bug No longer marked as fixed in versions cpufrequtils/007-2.
Bug #637395 {Done: Mattia Dongili <malattia@debian.org>} [src:linux-2.6] linux-image-3.0.0-1-686-pae: EEE-PC 1000H: cpufreq cannot be set to ondemand
Bug Marked as found in versions linux-2.6/3.0.0-1.
> forwarded 637395 http://thread.gmane.org/gmane.linux.kernel.cpufreq/7402
Bug #637395 {Done: Mattia Dongili <malattia@debian.org>} [src:linux-2.6] linux-image-3.0.0-1-686-pae: EEE-PC 1000H: cpufreq cannot be set to ondemand
Set Bug forwarded-to-address to 'http://thread.gmane.org/gmane.linux.kernel.cpufreq/7402'.
> tags 637395 = upstream
Bug #637395 {Done: Mattia Dongili <malattia@debian.org>} [src:linux-2.6] linux-image-3.0.0-1-686-pae: EEE-PC 1000H: cpufreq cannot be set to ondemand
Added tag(s) upstream; removed tag(s) patch.
> quit
Stopping processing here.
Please contact me if you need assistance.
--
637395: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=637395
635348: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=635348
636141: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=636141
636194: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=636194
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
Reply to: