public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: David Brownell <david-b@pacbell.net>
To: Greg KH <greg@kroah.com>
Cc: Lukas Hejtmanek <xhejtman@mail.muni.cz>,
	linux-kernel@vger.kernel.org,
	linux-usb-devel@lists.sourceforge.net
Subject: Re: Scheduling while atomic (2.6.10-rc3-bk13)
Date: Mon, 20 Dec 2004 11:52:16 -0800	[thread overview]
Message-ID: <200412201152.16329.david-b@pacbell.net> (raw)
In-Reply-To: <20041220184814.GA21215@kroah.com>

[-- Attachment #1: Type: text/plain, Size: 523 bytes --]

On Monday 20 December 2004 10:48 am, Greg KH wrote:

> 
> David, it looks like you grab a spinlock, and then call msleep(20);
> which causes this warning.
> 
> Care to fix it?

How bizarre ... I must have been tested that without spinlock
debugging, for some reason.  Grr.  I usually leave that on,
just to prevent stuff like this.

Here's a quick'n'dirty patch, msleep --> mdelay.  I'd rather
not mdelay for that long, but this late in 2.6.10 it's safer.
(And this is also what OHCI does in that same code path.)

- Dave


[-- Attachment #2: Diff --]
[-- Type: text/x-diff, Size: 365 bytes --]

--- 1.43/drivers/usb/host/ehci-hub.c	Fri Dec 17 18:57:39 2004
+++ edited/drivers/usb/host/ehci-hub.c	Mon Dec 20 11:48:01 2004
@@ -122,7 +122,7 @@
 		writel (temp, &ehci->regs->port_status [i]);
 	}
 	i = HCS_N_PORTS (ehci->hcs_params);
-	msleep (20);
+	mdelay (20);
 	while (i--) {
 		temp = readl (&ehci->regs->port_status [i]);
 		if ((temp & PORT_SUSPEND) == 0)

  reply	other threads:[~2004-12-20 19:52 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-19 23:10 Scheduling while atomic (2.6.10-rc3-bk13) Lukas Hejtmanek
2004-12-20 18:48 ` Greg KH
2004-12-20 19:52   ` David Brownell [this message]
2004-12-20 20:57     ` Lee Revell
2004-12-20 21:31       ` [linux-usb-devel] " David Brownell
2004-12-20 21:32         ` Lee Revell
2004-12-21 19:20     ` Greg KH

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=200412201152.16329.david-b@pacbell.net \
    --to=david-b@pacbell.net \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb-devel@lists.sourceforge.net \
    --cc=xhejtman@mail.muni.cz \
    /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