mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Colin Leroy <colin@colino.net>
To: David Brownell <david-b@pacbell.net>
Cc: linux-usb-devel@lists.sourceforge.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 17:54:54 +0100	[thread overview]
Message-ID: <20041126175454.17b62cf5@pirandello> (raw)
In-Reply-To: <200411260838.10508.david-b@pacbell.net>

On 26 Nov 2004 at 08h11, David Brownell wrote:

Hi, 

> 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. 

Sure? the (limit -- == 0) gotoes higher to test again.
from what I understand the loop goes back to rescan 1000 times, then once 
to sanitize, then to back to rescan again infinetely...
I may be wrong but I don't think there's a stack corruption there.

> 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?

No, the rest of the computer worked fine.

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

Yes, noticed and sent a second patch.

-- 
Colin

  reply	other threads:[~2004-11-27  3:36 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 ` [linux-usb-devel] " David Brownell
2004-11-26 16:54   ` Colin Leroy [this message]
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=20041126175454.17b62cf5@pirandello \
    --to=colin@colino.net \
    --cc=benh@kernel.crashing.org \
    --cc=david-b@pacbell.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

Powered by JetHome