All of lore.kernel.org
 help / color / mirror / Atom feed
From: Karsten Malcher <debian@km.hopto.org>
To: Ken Moffat <zarniwhoop@ntlworld.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Freezing system after kernel 3.2
Date: Tue, 09 Feb 2016 17:03:57 +0100	[thread overview]
Message-ID: <56BA0DED.4020603@home.decotrain.de> (raw)
In-Reply-To: <20160209035104.GA23082@milliways>

I have to found out that freezing can occur under kernel 3.2 too, but far less common.
So the interesting question is why in newer kernels this will occur very often?

I could found a solution for the problem in the linked Blog.
When you disable Cool' n' Quiet the system is running stable with newer kernel too!

So it seems to be a buggy BIOS that is causing 2 big problems:
1. RAM can only be used with 3264 MB of 4096 MB.
2. When Cool' n' Quiet is enabled the system is freezing within an minute.

I have reported this to Asrock, but i don't think they will do anything for an older mainboard ...

You can found several problems regarding freezing with the RS480 chip,
but not together with the frequency scaling (Cool'n'Quiet).
This problems occur with other chipsets too.

How the frequency scaling is working?
I have found some hints about disabling C1 and C6 states will help to solve the problem:

https://forum.teksyndicate.com/t/amd-system-keeps-freezing/78380/17
https://rog.asus.com/forum/showthread.php?60224-amd-system-keeps-freezing&s=03842b8ef2cb1a25bc458b6fe56c9213&p=492388&viewfull=1#post492388
https://community.amd.com/message/2645600#2645600

But i have no settings about this states in my BIOS.
Has the behaviour of the frequency scaling drivers changed somehow?

  parent reply	other threads:[~2016-02-09 16:04 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-08 18:08 Freezing system after kernel 3.2 Karsten Malcher
2016-02-09  3:51 ` Ken Moffat
2016-02-09 10:42   ` Karsten Malcher
2016-02-09 16:03   ` Karsten Malcher [this message]
     [not found]     ` <20160209194217.GA16581@milliways>
2016-02-10 15:12       ` Karsten Malcher

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=56BA0DED.4020603@home.decotrain.de \
    --to=debian@km.hopto.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=zarniwhoop@ntlworld.com \
    /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.