mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: David Brownell <david-b@pacbell.net>
To: linux-usb-devel@lists.sourceforge.net
Cc: Colin Leroy <colin@colino.net>,
	linux-kernel@vger.kernel.org,
	Benjamin Herrenschmidt <benh@kernel.crashing.org>,
	Greg KH <greg@kroah.com>
Subject: Re: [linux-usb-devel] [PATCH] Ohci-hcd: fix endless loop
Date: Fri, 26 Nov 2004 08:38:10 -0800	[thread overview]
Message-ID: <200411260838.10508.david-b@pacbell.net> (raw)
In-Reply-To: <20041125191726.5ca95299@jack.colino.net>

On Thursday 25 November 2004 10:17, Colin Leroy wrote:
> Hi, 
> 
> Following patch fixes an endless loop that happens after having
> slept and resumed my iBook with a linux-wlan-ng controller plugged in,
> removed the stick and plugged it back (getting "IRQ lossage" message).

The infinite loop means that something trashed the stack, yes?

The "limit-- < -1000" test below should never be able to succeed
unless the previous "limit-- == 0" test got trashed by having
something obliterate the stack.  Possibly the driver for that WLAN
adapter.  Once that happens, all kinds of things will misbehave...

If you got the "IRQ INTR_SF lossage" diagnostic, there's clearly
some problem with IRQ handling after the resume ... is the iBook
firmware (or hardware) doing wierd stuff so that the normal PCI
IRQ calls stopped working?

And for that matter, "limit" is unsigned, so you must be getting
(and ignoring) some compiler warnings too.

This is not a good patch; not accepted.

- Dave


> Signed-off-by: Colin Leroy <colin@colino.net>
> --- a/drivers/usb/host/ohci-hcd.c	2004-11-25 19:00:25.000000000 +0100
> +++ b/drivers/usb/host/ohci-hcd.c	2004-11-25 19:08:59.000000000 +0100
> @@ -375,6 +375,11 @@
>  		spin_unlock_irqrestore (&ohci->lock, flags);
>  		set_current_state (TASK_UNINTERRUPTIBLE);
>  		schedule_timeout (1);
> +		if (limit-- < -1000) {
> +			ohci_warn (ohci, "Couldn't recover\n");
> +			ohci_restart(ohci);
> +			goto bail;
> +		}
>  		goto rescan;
>  	case ED_IDLE:		/* fully unlinked */
>  		if (list_empty (&ed->td_list)) {
> @@ -396,6 +401,7 @@
>  	dev->ep [epnum] = NULL;
>  done:
>  	spin_unlock_irqrestore (&ohci->lock, flags);
> +bail:
>  	return;
>  }
>  
> 
> 
> -------------------------------------------------------
> SF email is sponsored by - The IT Product Guide
> Read honest & candid reviews on hundreds of IT Products from real users.
> Discover which products truly live up to the hype. Start reading now. 
> http://productguide.itmanagersjournal.com/
> _______________________________________________
> linux-usb-devel@lists.sourceforge.net
> To unsubscribe, use the last form field at:
> https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
> 

  reply	other threads:[~2004-11-26 19:20 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-25 18:17 Colin Leroy
2004-11-26 16:38 ` David Brownell [this message]
2004-11-26 16:54   ` [linux-usb-devel] " Colin Leroy
2004-11-26 17:21     ` David Brownell
2004-11-26 22:07   ` Benjamin Herrenschmidt

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=200411260838.10508.david-b@pacbell.net \
    --to=david-b@pacbell.net \
    --cc=benh@kernel.crashing.org \
    --cc=colin@colino.net \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb-devel@lists.sourceforge.net \
    /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

all inboxes | Powered by JetHome®