[Bug 118015] Re: Feisty can't reboot after adding p4-clockmod to /etc/modules

2009-04-14 Thread Tim Gardner
cpu_freq is now built into the kernel. CONFIG_CPU_FREQ_DEFAULT_GOV_PERFORMANCE=y is set for i386/amd64. ** Also affects: linux (Ubuntu Jaunty) Importance: Medium Status: Triaged ** Changed in: linux (Ubuntu Jaunty) Status: Triaged => Fix Released -- Feisty can't reboot after ad

[Bug 118015] Re: Feisty can't reboot after adding p4-clockmod to /etc/modules

2008-08-28 Thread Leann Ogasawara
The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would appreciate it if you could please test this newer 2.6.27 Ubuntu kernel. There are one of two ways you should be able to test: 1) If you are comfortable

[Bug 118015] Re: Feisty can't reboot after adding p4-clockmod to /etc/modules

2008-04-22 Thread Ben Collins
** Changed in: linux (Ubuntu Hardy) Status: Triaged => Won't Fix -- Feisty can't reboot after adding p4-clockmod to /etc/modules https://bugs.launchpad.net/bugs/118015 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bug

[Bug 118015] Re: Feisty can't reboot after adding p4-clockmod to /etc/modules

2008-03-24 Thread Leann Ogasawara
** Changed in: linux (Ubuntu Hardy) Assignee: (unassigned) => Ubuntu Kernel Team (ubuntu-kernel-team) Status: Confirmed => Triaged -- Feisty can't reboot after adding p4-clockmod to /etc/modules https://bugs.launchpad.net/bugs/118015 You received this bug notification because you are

[Bug 118015] Re: Feisty can't reboot after adding p4-clockmod to /etc/modules

2008-03-07 Thread Henk Poley
No, I don't think I've ever got a reply. So, I'll keep using the "unnecessary symlinks" :-/ -- Feisty can't reboot after adding p4-clockmod to /etc/modules https://bugs.launchpad.net/bugs/118015 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubu

Re: [Bug 118015] Re: Feisty can't reboot after adding p4-clockmod to /etc/modules

2008-03-07 Thread Daniel Gimpelevich
On Mar 7, 2008, at 2:58 PM, Leann Ogasawara wrote: > Hi Henk, > > Just curious if you get a response back from Dave Jones? I know that I haven't. Anyway, does p4-clockmod even support ondemand? I think powernowd is likely required. -- "No gnu's is good gnu's." --Gary Gnu, "The Great Space Coa

[Bug 118015] Re: Feisty can't reboot after adding p4-clockmod to /etc/modules

2008-03-07 Thread Leann Ogasawara
Hi Henk, Just curious if you get a response back from Dave Jones? -- Feisty can't reboot after adding p4-clockmod to /etc/modules https://bugs.launchpad.net/bugs/118015 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mai

[Bug 118015] Re: Feisty can't reboot after adding p4-clockmod to /etc/modules

2008-01-04 Thread Henk Poley
I just mailed Dave Jones, the kernel's cpu frequency driver maintainer. As far as I can tell; Ubuntu doesn't actually start powernowd when the ondemand governor is available. So TERM signals do not apply here. Setting the governor to "performance" does, though. At the moment I'll just use the "unn

Re: [Bug 118015] Re: Feisty can't reboot after adding p4-clockmod to /etc/modules

2008-01-03 Thread Daniel Gimpelevich
On Jan 2, 2008, at 3:23 PM, Scott James Remnant wrote: > Sorry, but the suggested fix here is incorrect. > > All the powernowd stop script does is send the TERM signal to the > daemon, which is already performed by the sendsigs script; and set the > scaling governor to "performance", which is only

[Bug 118015] Re: Feisty can't reboot after adding p4-clockmod to /etc/modules

2008-01-02 Thread Scott James Remnant
Sorry, but the suggested fix here is incorrect. All the powernowd stop script does is send the TERM signal to the daemon, which is already performed by the sendsigs script; and set the scaling governor to "performance", which is only done so when the daemon is stopped by hand (e.g. when the packag