Re: [gentoo-amd64] complete crash with ondemand scheduler

[Beso]

as a scheduler for athlons i reccomend userspace with powernowd enabled. on
my pc i start cpufrequtils with userspace at boot, and then i load powernowd
at boot with the option -n (for options on powernowd see the
/etc/conf.d/powernowd file and infos). that cpu governor gives the best freq
scaling with niced processes and good interoperability.
to come to the problem: i've never experienced such problems, if not when
using ati-drivers in the xorg conf, but not reinstalling the package after
kernel rebuild. after rebuilding or upgrading you'll always have to
reinstall the ati-drivers....

2007/8/2, Raffaele BELARDI <raffaele.belardi@××.com>:
>
> When I enable the ondemand scheduler on my Athlon64 3200+ I get
> immediate crash: video fills up with blinking colored lines, X cannot be
> killed, the box does not ping, I need to hard reset. Other than that the
> box is a stable mythtv station.
>
> The motherboard is an Asus M2NPV-VM. Cool'n'Quiet is enabled in the
> BIOS. Vanilla kernel with no binary drivers (actually, initially I was
> using the proprietary nvidia graphics driver, which I though was the
> culprit, but switching to open source driver did not solve), running
> almost no ~amd64.
> On my other box, an Athlon64 3000+/Asus K8VSE with same kernel, ondemand
> works perfectly.
>
> The only 'strange' hw on the 3200+ is a DVB tuner, the Hauppauge
> HVR1300. Tonight I will try to remove it and see if it is related with
> this problem.
>
> Has anybody had similar problems with ondemand scheduler?
> Any hints on how to debug the problem would be greatly appreciated.
> Neither syslog nor xorg.log report anything unusual.
>
> thanks,
>
> raffaele
> --
> gentoo-amd64@g.o mailing list
>
>


-- 
dott. ing. beso