From: Nebojsa Trpkovic <trxman@gmail.com>
To: cpufreq@lists.linux.org.uk
Subject: Re: cpu-freq causing kernel lock-up after upgrading to 1GB ram.
Date: Mon, 16 May 2005 19:08:05 +0200 [thread overview]
Message-ID: <4288D375.7040405@gmail.com> (raw)
In-Reply-To: <84EA05E2CA77634C82730353CBE3A84301CFC017@SAUSEXMB1.amd.com>
Done.
Langsdorf, Mark wrote:
>If this problem also occurs on Windows, please report
>it to your motherboard manufacturer immediately. They'll
>get it fixed.
>
>-Mark Langsdorf
>AMD, Inc.
>
>
>
>>-----Original Message-----
>>From: cpufreq-bounces@lists.linux.org.uk
>>[mailto:cpufreq-bounces@lists.linux.org.uk] On Behalf Of
>>Nebojsa Trpkovic
>>Sent: Sunday, May 15, 2005 6:50 PM
>>To: cpufreq@lists.linux.org.uk
>>Subject: Re: cpu-freq causing kernel lock-up after upgrading
>>to 1GB ram.
>>
>>
>>Same problem here - VNF3-250 - if there's one RAM module
>>C'n'Q works fine, and if I put two modules it freezes every
>>time I try to change frequency, no matter linux or windows.
>>So, it's not cpufreq related problem - it just buggy VNF3-250
>>C'n'Q inplementation.
>>
>>
>>
>>
>>chris stones wrote:
>>
>>
>>
>>>This is my first attempt at a bug report, so forgive me for
>>>
>>>
>>making a
>>
>>
>>>mess, I will try my best.
>>>
>>>-------------------------
>>>hardware:
>>>-------------------------
>>>mobo: Chaintech VNF3-250
>>>chipset: nForce-3
>>>CPU: amd64 Athlon 3400+
>>>Ram: 2 * Kingston 512Meg DDR400 PC3200 2T timeing 3-3-8-3.
>>>
>>>
>>(total 1GB)
>>
>>
>>>Swap : 1.3 Gb.
>>>
>>>--------------------------
>>>software:
>>>--------------------------
>>>Distro: Gentoo 2005.0 (comiped as 64bit with multilib)
>>>GCC: gcc version 3.4.3 20041125 (Gentoo Linux 3.4.3-r1, ssp-3.4.3-0,
>>>pie-8.7.7)
>>>kernel versions: gentoo 2.6.11-r7; vanilla-2.6.10; vanilla-2.6.11.9
>>>
>>>--------------------------
>>>description:
>>>--------------------------
>>>I have been using the modules freq_table, cpufreq_ondemand,
>>>powernow_k8 to regulate my cpu clock for over 6 months with the
>>>hardware configureation shown above, minus one 512meg ram module.
>>>
>>>Recently, i shutdown the box, and added the second memory
>>>
>>>
>>module. At
>>
>>
>>>the time, the cpu_fre drivers were compiled into the
>>>
>>>
>>kernel, shortly
>>
>>
>>>after booting, the system would freese when cpu_freq
>>>
>>>
>>lowered my cpu to
>>
>>
>>>its idle state of 1Ghz.
>>>
>>>These conditions must all be met to cause the lock-up.
>>>1) Both Ram moodules are used (1GB ram)
>>>2) the modules freq_table, cpufreq_ondemand, powernow_k8 are loaded.
>>>3) The lockup occurs when the cpu is slowing down from a period of
>>>heavy load.
>>>
>>>2 hours running memtest86 shows that my memory is not the problem.
>>>
>>>one one occasion, the kernel gave a memory dump before the
>>>
>>>
>>freeze. i
>>
>>
>>>regret i didnt take note of its rull contents, but a function trace
>>>line mentioned a cpu_freq function call.
>>>
>>>If i remove one of the 512meg memory modules, the cpu_freq
>>>performsperfectly, as it has for the past 6 months.
>>>
>>>Thankyou for taking the time to read my post.
>>>Is there anything i can do (other than go without ram or
>>>
>>>
>>cpu_freq) to
>>
>>
>>>solve this ? is there any more information you require from me ?
>>>
>>>I have googled, but found no other similar bug reports.
>>>
>>>From Chris.stones@gmail.com.
>>>
>>>_______________________________________________
>>>Cpufreq mailing list
>>>Cpufreq@lists.linux.org.uk
>>>http://lists.linux.org.uk/mailman/listinfo/cpufreq
>>>
>>>
>>>
>>_______________________________________________
>>Cpufreq mailing list
>>Cpufreq@lists.linux.org.uk
>>http://lists.linux.org.uk/mailman/listinfo/cpu> freq
>>
>>
>>
>>
>
>
>
>
next prev parent reply other threads:[~2005-05-16 17:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-16 15:19 cpu-freq causing kernel lock-up after upgrading to 1GB ram Langsdorf, Mark
2005-05-16 17:08 ` Nebojsa Trpkovic [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-05-15 16:37 chris stones
2005-05-15 23:49 ` Nebojsa Trpkovic
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=4288D375.7040405@gmail.com \
--to=trxman@gmail.com \
--cc=cpufreq@lists.linux.org.uk \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.