[Mattia Dongili]
> actually I can imagine what happened. You always relied on
> cpufrequtils to load the kernel modules and never configured
> /etc/default/cpufreqd. There is not much that I can do for that
> other than duplicating the approach in cpufrequtils or depending on
> it (which is wrong
On Sun, 30 May 2010 11:14:21 +0900 Mattia Dongili wrote:
> On Sun, May 30, 2010 at 10:46:25AM +0900, Mattia Dongili wrote:
> > severity 583663 important
> > tags 583663 - patch
> >
> > On Sat, May 29, 2010 at 01:18:09PM +0200, Francesco Poli (t1000) wrote:
> ...
> > > I am under the impression th
On Sun, May 30, 2010 at 10:46:25AM +0900, Mattia Dongili wrote:
> severity 583663 important
> tags 583663 - patch
>
> On Sat, May 29, 2010 at 01:18:09PM +0200, Francesco Poli (t1000) wrote:
...
> > I am under the impression that this bug is due to incomplete LSB header
> > dependencies: the attach
severity 583663 important
tags 583663 - patch
On Sat, May 29, 2010 at 01:18:09PM +0200, Francesco Poli (t1000) wrote:
> Package: cpufreqd
> Version: 2.4.2-1
> Severity: important
> Tags: patch
> User: initscripts-ng-de...@lists.alioth.debian.org
> Usertags: incorrect-dependencies
>
>
> Hi Mattia
severity 583663 seriuos
thanks
The patch seem correct, assuming cpufreqd should start after the
kernel modules for cpufreq handling are loaded.
Assuming this affect all users with the new default setup in Debian
(parallel booting), I am raising the severity to serious.
Happy hacking,
--
Petter
Package: cpufreqd
Version: 2.4.2-1
Severity: important
Tags: patch
User: initscripts-ng-de...@lists.alioth.debian.org
Usertags: incorrect-dependencies
Hi Mattia! :)
Since the parallellized boot was enabled, cpufreqd has no longer been
automatically started during boot.
The error message is:
6 matches
Mail list logo
