The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: Christian Hoffmann <email@christianhoffmann.info>
Cc: john stultz <johnstul@us.ibm.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Long timeout when booting >= 2.6.38
Date: Mon, 16 May 2011 11:07:48 +0200 (CEST)	[thread overview]
Message-ID: <alpine.LFD.2.02.1105161105170.3078@ionos> (raw)
In-Reply-To: <4DD0335A.6050400@christianhoffmann.info>

On Sun, 15 May 2011, Christian Hoffmann wrote:
> new trace:
> http://dl.dropbox.com/u/21820416/traceing2.log.bz2
> 
> Sorry for delay.

Nothing to be sorry about. Thanks for providing the information. If I
decoded the problem correctly then this just unearthed a real long
standing bug. Does the patch below solve the problem ?

Thanks,

	tglx

--- linux-2.6.orig/kernel/time/tick-broadcast.c
+++ linux-2.6/kernel/time/tick-broadcast.c
@@ -522,10 +522,11 @@ static void tick_broadcast_init_next_eve
  */
 void tick_broadcast_setup_oneshot(struct clock_event_device *bc)
 {
+	int cpu = smp_processor_id();
+
 	/* Set it up only once ! */
 	if (bc->event_handler != tick_handle_oneshot_broadcast) {
 		int was_periodic = bc->mode == CLOCK_EVT_MODE_PERIODIC;
-		int cpu = smp_processor_id();
 
 		bc->event_handler = tick_handle_oneshot_broadcast;
 		clockevents_set_mode(bc, CLOCK_EVT_MODE_ONESHOT);
@@ -551,6 +552,15 @@ void tick_broadcast_setup_oneshot(struct
 			tick_broadcast_set_event(tick_next_period, 1);
 		} else
 			bc->next_event.tv64 = KTIME_MAX;
+	} else {
+		/*
+		 * The first cpu which switches to oneshot mode sets
+		 * the bit for all other cpus which are in the general
+		 * (periodic) broadcast mask. So the bit is set and
+		 * would prevent the first broadcast enter after this
+		 * to program the bc device.
+		 */
+		tick_broadcast_clear_oneshot(cpu);
 	}
 }
 

  reply	other threads:[~2011-05-16  9:07 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-02 18:49 Long timeout when booting >= 2.6.38 Christian Hoffmann
2011-05-02 19:09 ` john stultz
2011-05-02 20:42   ` Christian Hoffmann
2011-05-02 21:10     ` Christian Hoffmann
2011-05-02 22:12       ` john stultz
2011-05-02 21:49     ` john stultz
2011-05-02 22:27       ` Christian Hoffmann
2011-05-03  0:31         ` john stultz
2011-05-03 19:33           ` Christian Hoffmann
     [not found]           ` <4DC04E15.2030308@christianhoffmann.info>
2011-05-04  1:38             ` john stultz
2011-05-04  7:12               ` Christian Hoffmann
2011-05-04 17:04                 ` Christian Hoffmann
2011-05-04  1:00         ` john stultz
2011-05-04  7:31           ` Christian Hoffmann
2011-05-04  8:37             ` Thomas Gleixner
2011-05-04 16:47               ` Christian Hoffmann
2011-05-04 17:49                 ` Thomas Gleixner
2011-05-04 19:40                   ` Christian Hoffmann
2011-05-04 20:53                     ` Thomas Gleixner
2011-05-05 17:28                       ` Christian Hoffmann
2011-05-09  8:22                         ` Thomas Gleixner
2011-05-15 20:11                           ` Christian Hoffmann
2011-05-16  9:07                             ` Thomas Gleixner [this message]
2011-05-16 19:34                               ` Christian Hoffmann
2011-05-05  1:16             ` john stultz
2011-05-05  8:25               ` Thomas Gleixner
2011-05-05 17:47                 ` Christian Hoffmann
2011-05-05 18:41                   ` Thomas Gleixner
2011-05-03 18:12 ` David

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=alpine.LFD.2.02.1105161105170.3078@ionos \
    --to=tglx@linutronix.de \
    --cc=email@christianhoffmann.info \
    --cc=johnstul@us.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    /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