From: Michael Elkins <me@toesinperil.com>
To: Jeff Garzik <jgarzik@mandrakesoft.com>,
Linus Torvalds <torvalds@transmeta.com>
Cc: Rui Sousa <rsousa@grad.physics.sunysb.edu>,
usb@in.tum.de, linux-kernel@vger.kernel.org,
Alan Cox <alan@lxorguk.ukuu.org.uk>
Subject: Re: [PATCH] Re: PROBLEM: kernel 2.4.0-test11-ac1 hang with usb-uhci and emu10k1
Date: Thu, 23 Nov 2000 23:06:14 -0800 [thread overview]
Message-ID: <20001123230614.A32540@toesinperil.com> (raw)
In-Reply-To: <3A1DA2F7.94114CD2@mandrakesoft.com> <Pine.LNX.4.10.10011231551210.1702-100000@penguin.transmeta.com> <20001123020203.A30491@toesinperil.com> <Pine.LNX.4.21.0011231028030.17678-100000@grad.physics.sunysb.edu> <20001123174952.B7591@in.tum.de> <20001123144517.A31910@toesinperil.com> <3A1DA2F7.94114CD2@mandrakesoft.com>
In-Reply-To: <3A1DA2F7.94114CD2@mandrakesoft.com>; from jgarzik@mandrakesoft.com on Thu, Nov 23, 2000 at 06:06:31PM -0500
On Thu, Nov 23, 2000 at 06:06:31PM -0500, Jeff Garzik wrote:
> Michael Elkins wrote:
> >
> > On Thu, Nov 23, 2000 at 05:49:52PM +0100, Georg Acher wrote:
> > It hangs in start_uhci():
> >
> > /* disable legacy emulation */
> > pci_write_config_word (dev, USBLEGSUP, USBLEGSUP_DEFAULT);
> >
> > The loop that the call is in gets iterated 5 times. For i < 4, the
> > if (!(dev->resource[i].flags & 1))
> > is TRUE, but on i==4, it drops into the bottom of the loop to execute
> > check_region() and then pci_write_config_word(), where it hangs.
>
> It may not make a difference, but that check is flat out wrong.
The loop still exhibits the same behavior.
/usr/include/linux/ioport.h:#define IORESOURCE_IO 0x00000100 /* Resource type */
Definitely a different value, however.
> Apply this patch... (untested, you may need to include ioport.h)
fyi, ioport.h isn't required.
On Thu, Nov 23, 2000 at 03:53:27PM -0800, Linus Torvalds wrote:
> Try changing the thing around a bit: make the above place say
>
> /* disable legacy emulation */
> pci_write_config_word (dev, USBLEGSUP, 0);
>
> and then AFTER we have successfully done a request_irq() call, we
> can enable PCI interrupts with
>
> /* Enable PIRQ */
> pci_write_config_word (dev, USBLEGSUP, USBLEGSUP_DEFAULT);
>
> Does that make it happier?
Yep! That seems to have fixed it. Added the pci_write_config_word() after
the request_irq() in alloc_uhci().
me
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2000-11-24 7:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-23 10:02 Michael Elkins
2000-11-23 15:32 ` Rui Sousa
2000-11-23 16:49 ` Georg Acher
2000-11-23 22:45 ` Michael Elkins
2000-11-23 23:06 ` [PATCH] " Jeff Garzik
2000-11-23 23:53 ` Linus Torvalds
2000-11-24 13:04 ` [patch-2.4.0-test11] various small fixes Tigran Aivazian
2000-11-24 7:06 ` Michael Elkins [this message]
2000-11-24 16:30 ` [PATCH] Re: PROBLEM: kernel 2.4.0-test11-ac1 hang with usb-uhci and emu10k1 Linus Torvalds
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=20001123230614.A32540@toesinperil.com \
--to=me@toesinperil.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=jgarzik@mandrakesoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rsousa@grad.physics.sunysb.edu \
--cc=torvalds@transmeta.com \
--cc=usb@in.tum.de \
/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®