From: Ramkumar R <andyetitmoves@gmail.com>
To: "Michał Pytasz" <mpytasz@posejdon.wpk.p.lodz.pl>,
cpufreq@lists.linux.org.uk
Subject: Re: Temporary freezes in AMD Sempron 2800+
Date: Mon, 6 Jun 2005 23:41:12 +0530 [thread overview]
Message-ID: <9a9bfc1705060611114a1f2596@mail.gmail.com> (raw)
In-Reply-To: <200506061956.16644.mpytasz@posejdon.wpk.p.lodz.pl>
[-- Attachment #1: Type: text/plain, Size: 2027 bytes --]
On 6/6/05, Michał Pytasz <mpytasz@posejdon.wpk.p.lodz.pl> wrote:
> On Monday 06 of June 2005 19:21, Ramkumar R wrote:
> > no....i don't have (and don't want to install :) ) windows...do u mean
> > stuff like bit errors when u mean memory problems ? i just got this
> > laptop (about a month back)...and i had run memtest successfully when
> > i bought it...
>
> Well, I've seen such a problem with athlon64 and faulty hynix module (probably
> You can find it in list archive). After I had it replaced everything became
> stable, memtest did pass with faulty module, too. Problem occured when cpu
> was going from low to high frequency.
mine hangs temporarily for *any* change in frequency though....
> That's why I asked about Windoze, I did not mean using it for work, but it may
> give a hint if it is a hardware problem. I don't think it could be a driver
> problem since I have similar machine with same CPU (Mobile Sempron 2800+, via
> k8n800) and it runs stable (with linux gentoo). I think it could be one of
> two problems:
> 1. Software: missconfigured kernel or misslinked libraries in the system (but
> in this case it should not hang hard and I guess there would be no
> correlation with frequency scaling)
i don't get that misslinked libraries part....please excuse my
ignorance but since the problem occurs even with the kernel level
ondemand governor, is this likely to be a problem...
> 2. Hardware problem.
just thinking that if it had been an hardware error, isn't it more
likely to be random rather than something which occurs repeatably when
the speed changes...i know only of memtest amongst hardware testing
utilities...if you know of any other utility which can probably help
me in this, please tell me.
>
> If You wish, I could send You my kernel config.
>
yeah sure, lets hope that helps :)
Ramkumar.
> Michal
>
--
The day Microsoft makes something that doesn't suck
is probably the day they start making vacuum cleaners.
-Ernst Jan Plugge
[-- Attachment #2: Type: text/plain, Size: 147 bytes --]
_______________________________________________
Cpufreq mailing list
Cpufreq@lists.linux.org.uk
http://lists.linux.org.uk/mailman/listinfo/cpufreq
next prev parent reply other threads:[~2005-06-06 18:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-06 14:49 Temporary freezes in AMD Sempron 2800+ Ramkumar R
[not found] ` <200506061659.19854.mpytasz@pai.net.pl>
[not found] ` <9a9bfc1705060609302b5d803f@mail.gmail.com>
2005-06-06 17:06 ` Michał Pytasz
[not found] ` <9a9bfc170506061021620e487a@mail.gmail.com>
[not found] ` <200506061956.16644.mpytasz@posejdon.wpk.p.lodz.pl>
2005-06-06 18:11 ` Ramkumar R [this message]
2005-06-06 19:23 ` Ramkumar R
2005-06-06 20:38 ` Ramkumar R
-- strict thread matches above, loose matches on Subject: below --
2005-06-06 19:54 Langsdorf, Mark
2005-06-06 20:45 Langsdorf, Mark
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=9a9bfc1705060611114a1f2596@mail.gmail.com \
--to=andyetitmoves@gmail.com \
--cc=cpufreq@lists.linux.org.uk \
--cc=mpytasz@posejdon.wpk.p.lodz.pl \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox