All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christoph Fritz <chf.fritz@googlemail.com>
To: Heinz Diehl <htd+ml@fritha.org>
Cc: linux-kernel@vger.kernel.org, Thomas Gleixner <tglx@linutronix.de>
Subject: Re: lockup when C1E and high-resolution timers enabled
Date: Sat, 13 Jun 2015 22:58:47 +0200	[thread overview]
Message-ID: <1434229127.3382.2.camel@googlemail.com> (raw)
In-Reply-To: <20150613201936.GA16112@fritha.org>

On Sat, 2015-06-13 at 22:19 +0200, Heinz Diehl wrote:
> On 13.06.2015, Christoph Fritz wrote: 
> 
> >  - add kernel parameter "idle=halt" -> system runs fine
> >  - disable CONFIG_HIGH_RES_TIMERS -> system runs fine
> >  - change motherboard and disable C1E -> system runs fine
> >  - change CPU to AMD Phenom II X6 Processor -> system runs fine
> 
> I encountered quite some C1E related problems with different Gigabyte
> mainboards in the last few years. Try booting with
> acpi_skip_timer_override, it fixed most of those problems for me.
> 

Thanks for your hint, I already tried that: With kernel parameter
'acpi_skip_timer_override' kernel doesn't boot at all.


  reply	other threads:[~2015-06-13 20:59 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-13 19:53 lockup when C1E and high-resolution timers enabled Christoph Fritz
2015-06-13 20:19 ` Heinz Diehl
2015-06-13 20:58   ` Christoph Fritz [this message]
  -- strict thread matches above, loose matches on Subject: below --
2015-06-14  3:13 Daniel J Blueman
2015-06-14  4:39 ` Christoph Fritz
2015-06-14  7:54   ` Daniel J Blueman
2015-06-14 14:49     ` Christoph Fritz
2015-06-14 15:24       ` Daniel J Blueman
2015-06-14 23:38         ` Christoph Fritz
2015-06-14 16:47   ` Borislav Petkov
2015-06-14 23:05     ` Christoph Fritz
2015-06-15  7:54       ` Borislav Petkov
2015-06-15  8:01         ` Christoph Fritz
2015-06-15  8:10           ` Borislav Petkov
2015-07-13  7:32             ` Christoph Fritz

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=1434229127.3382.2.camel@googlemail.com \
    --to=chf.fritz@googlemail.com \
    --cc=htd+ml@fritha.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tglx@linutronix.de \
    /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.