lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date:	Mon, 2 Apr 2007 10:25:46 -0500
From:	"Langsdorf, Mark" <mark.langsdorf@....com>
To:	"wixor" <wixorpeek@...il.com>
cc:	linux-kernel@...r.kernel.org
Subject: RE: System hang on athlon64 cpufreq change

 
> On 3/16/07, Langsdorf, Mark <mark.langsdorf@....com> wrote:
> > The processor is not changing frequency in response to your
> > launch of mplayer.  The powersave governor forces it to the
> > lowest frequency regardless of system load.  You really want
> > to use ondemand for dynamic frequency scaling.
> >
> > Can you use a serial or network console to capture any messages
> > the kernel is sending when mplayer starts?
> >
> Well, that's the point - i fix cpu speed at 1ghz and everything works
> UNTIL I launch mplayer. I've just reproduced this (set governor,
> launched mplayer and waited 15-20 mins) and the whole system seems
> frozen - just like before. Network is down (no responses to ping). How
> to redirect dmesg to serial port? (I'm running 2.6.19 kernel and
> 8.34.8 fglrx driver.)

My point is that is there is no cpufreq change when you
start mplayer with the powersave governor.  Have you 
disabled powernow! entirely (by removing the module) and
demonstrated that mplayer works on your machine at all?

To redirect the console, add console=ttyS0,115200 to your 
kernel command line and run a serial console from the serial 
port on the test machine to another machine, and then use your 
preferred serial port capture program (minicom or whatever) 
to capture the text.
 
> Thanks and sorry for 2week delay... (btw - now it is you [ati] who is
> responsible for both my cpu and gpu drivers, yes? :D)

AMD bought ATI, not the other way around.  That said, elements
of AMD are responsible for the PowerNow! driver, and other 
elements of AMD are responsible for the fglrx driver.

-Mark Langsdorf
Operating Systems Research Center
AMD, Inc.


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ