From: Michael Roth <mroth@nessie.de>
To: Andrew Drake <zappacky.lists@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Funny problem with 2.6.28: Kernel stalls
Date: Mon, 29 Dec 2008 12:51:19 +0100 [thread overview]
Message-ID: <4958B9B7.8060505@nessie.de> (raw)
In-Reply-To: <495411FD.60409@gmail.com>
Andrew Drake schrieb:
> Michael Roth wrote:
>> The funny part: If I hit any key (on the keyboard connected by USB) the
>> kernel resumes to normal work until the next stall.
>>
>
> This sounds a little bit like my old problem... try kernel option nolapic_timer.
> It worked for me, perhaps it can do the same for you.
I didn't checked nolapic_timer (yet), but found these small changes to
the kernel config do the trick for me:
--- config-not-working 2008-12-28 16:09:29.000000000 +0100
+++ .config 2008-12-28 16:15:28.000000000 +0100
@@ -153,9 +153,8 @@
#
# Processor type and features
#
-CONFIG_TICK_ONESHOT=y
# CONFIG_NO_HZ is not set
-CONFIG_HIGH_RES_TIMERS=y
+# CONFIG_HIGH_RES_TIMERS is not set
CONFIG_GENERIC_CLOCKEVENTS_BUILD=y
# CONFIG_SMP is not set
# CONFIG_X86_MPPARSE is not set
@@ -278,7 +277,7 @@
# CONFIG_HZ_300 is not set
CONFIG_HZ_1000=y
CONFIG_HZ=1000
-CONFIG_SCHED_HRTICK=y
+# CONFIG_SCHED_HRTICK is not set
# CONFIG_KEXEC is not set
# CONFIG_CRASH_DUMP is not set
CONFIG_PHYSICAL_START=0x100000
next prev parent reply other threads:[~2008-12-29 11:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-25 15:14 Funny problem with 2.6.28: Kernel stalls Michael Roth
2008-12-25 23:06 ` Andrew Drake
2008-12-29 11:51 ` Michael Roth [this message]
2008-12-29 15:46 ` Thomas Gleixner
2009-01-08 12:47 ` Michael Roth
2009-01-14 9:45 ` Thomas Gleixner
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=4958B9B7.8060505@nessie.de \
--to=mroth@nessie.de \
--cc=linux-kernel@vger.kernel.org \
--cc=zappacky.lists@gmail.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.