Re: amd and clones with oleo

[Jude DaShiell]

If I background the oleo build I ought to be able to run top and capture 
that output in the same typescript file.  I'll have that for you later 
today, thanks.

On Sat, 2 Jan 2016, Marcin Cieslak wrote:

> Date: Fri, 1 Jan 2016 20:01:45
> From: Marcin Cieslak <address@hidden>
> To: Jude DaShiell <address@hidden>
> Cc: address@hidden
> Subject: Re: amd and clones with oleo
>
> On Fri, 1 Jan 2016, Jude DaShiell wrote:
>
> > I am using archlinux as a distribution and failed to get oleo built on an amd
> > k8 Athelon machine and an Acer aspire 5003 Laptop which is an amd clone.  I
> > can't provide relevant details on what happened on the acer machine since
> > whenever I attempt a build, the build runs for a while then shuts the laptop
> > off even when the laptop is connected to power and not using its battery.  I
> > will be able to provide a typescript file for the amd k8 athelon case though.
> > Before I do any of that though, I would like to know if amd and its clones are
> > even supported by oleo since if this is not yet the case fixing these problems
> > would be a feature request rather than a bug.
>
> On Fri, 1 Jan 2016, Jude DaShiell wrote:
>
> > I stopped the configure when checking for working mktime step hung for an hour
> > and a half.
> >
> > Script started on Fri 01 Jan 2016 08:04:37 AM EST
> > address@hidden oleo-1.99.16]# rm config.status
> > rm: cannot remove ???config.status???: No such file or directory
> > address@hidden oleo-1.99.16]# less config.sub
> > config.sub: No such file or directory
> > address@hidden oleo-1.99.16]# ./configure --without-x && make
>
> (...)
>
> > checking for working mktime... address@hidden oleo-1.99.16]# exit
> > exit
> >
> > Script done on Fri 01 Jan 2016 09:42:15 AM EST
>
> Thanks. Can you check which processes are running at the time
> this mktime() check works?
>
> Shutting down the CPU completely indicates hardware problem.
> It is possible that the CPU is defect (and it overheats itself).
> You might also have a problem with cooling (broken or blocked
> cooling path) or improperly/not applied cooling paste.
>
> I have once resolved similar problem by ripping the laptop
> apart completely and removing all the dust and ash (the
> owner was a heavy smoker). It did run quietly and without
> problems after...
>
> But having said that I'd like to know which process is
> driving your CPU usage so high. Can you see it on "top"?
>
> Marcin

--