public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: Dave Hansen <dave@sr71.net>, gregkh <gregkh@suse.de>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	USB list <linux-usb@vger.kernel.org>
Subject: Re: USB disconnects every 30 seconds (2.6.27-rc8)
Date: Sat, 4 Oct 2008 00:24:40 +0200 (CEST)	[thread overview]
Message-ID: <alpine.LFD.2.00.0810040018200.4404@apollo> (raw)
In-Reply-To: <Pine.LNX.4.44L0.0810031608000.6462-100000@iolanthe.rowland.org>

On Fri, 3 Oct 2008, Alan Stern wrote:
> On Fri, 3 Oct 2008, Dave Hansen wrote:
> There are a number of other places in the trace where delays are
> shorter than they should be.  This is out of my area of expertise, so 
> I'm CC'ing Thomas Gleixner.  With luck he'll be able to help.
> 
> Thomas, the background for this problem is available here:
> 
> 	http://marc.info/?l=linux-kernel&m=122305738430115&w=2

Is NOHZ and HIGHRES disabled on those kernels? Hugh spotted a typo in
that code today. Fix is below. It causes jiffies to increment too fast
which explains your short delays.

Thanks,

	tglx
---
diff --git a/kernel/time/tick-broadcast.c b/kernel/time/tick-broadcast.c
index bd70345..cb01cd8 100644
--- a/kernel/time/tick-broadcast.c
+++ b/kernel/time/tick-broadcast.c
@@ -235,7 +235,8 @@ static void tick_do_broadcast_on_off(void *why)
 	case CLOCK_EVT_NOTIFY_BROADCAST_FORCE:
 		if (!cpu_isset(cpu, tick_broadcast_mask)) {
 			cpu_set(cpu, tick_broadcast_mask);
-			if (bc->mode == TICKDEV_MODE_PERIODIC)
+			if (tick_broadcast_device.mode ==
+			    TICKDEV_MODE_PERIODIC)
 				clockevents_shutdown(dev);
 		}
 		if (*reason == CLOCK_EVT_NOTIFY_BROADCAST_FORCE)
@@ -245,7 +246,8 @@ static void tick_do_broadcast_on_off(void *why)
 		if (!tick_broadcast_force &&
 		    cpu_isset(cpu, tick_broadcast_mask)) {
 			cpu_clear(cpu, tick_broadcast_mask);
-			if (bc->mode == TICKDEV_MODE_PERIODIC)
+			if (tick_broadcast_device.mode ==
+			    TICKDEV_MODE_PERIODIC)
 				tick_setup_periodic(dev, 0);
 		}
 		break;



  reply	other threads:[~2008-10-03 22:25 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-03 17:45 USB disconnects every 30 seconds (2.6.27-rc8) Dave Hansen
2008-10-03 18:40 ` Alan Stern
2008-10-03 19:08   ` Dave Hansen
2008-10-03 20:55     ` Alan Stern
2008-10-03 22:24       ` Thomas Gleixner [this message]
2008-10-03 22:46         ` Dave Hansen
2008-10-03 23:06       ` Dave Hansen
2008-10-04  8:48         ` Marcel Holtmann
2008-10-04 16:33           ` Alan Stern
2008-10-04 18:12         ` Alan Stern
2008-10-05 17:59           ` Dave Hansen
2008-10-05 19:16             ` Alan Stern
2008-10-05 20:31               ` Dave Hansen
2008-10-03 19:23   ` Alan Stern
2008-10-03 19:56     ` Dave Hansen
2008-10-03 20:55       ` Alan Stern

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.00.0810040018200.4404@apollo \
    --to=tglx@linutronix.de \
    --cc=dave@sr71.net \
    --cc=gregkh@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=stern@rowland.harvard.edu \
    /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