From: David Brownell <david-b@pacbell.net>
To: Pete Zaitcev <zaitcev@redhat.com>
Cc: Marcelo Tosatti <marcelo.tosatti@cyclades.com>,
linux-kernel@vger.kernel.org, spam99@2thebatcave.com,
<km@westend.com>
Subject: Re: uhci-hcd oops with 2.4.27/ intel D845GLVA
Date: Tue, 10 Aug 2004 21:37:26 -0700 [thread overview]
Message-ID: <200408102137.26004.david-b@pacbell.net> (raw)
In-Reply-To: <20040810135409.44d31d1e@lembas.zaitcev.lan>
On Tuesday 10 August 2004 1:54 pm, Pete Zaitcev wrote:
>
> The attached ought to fix Nick up (no way to tell about Kai because his
> report had no data). It consists of two things. First, it fixes the
> oops in the scan_async.
That's a NOP, ehci->async must never be null.
What oops? The original post didn't include a stack...
> Second, it prevents the oops from happening by
> ignoring the handoff failure (as the old code did, in effect). Either
> one should be sufficient, but this is why I use both. The if around
> scan_async is the right fix, so it's there on merit.
Erm, no that's a NOP.
> However, it yields
> a non-working EHCI if your BIOS is buggy.
Depends on the particular bug you're hypothesizing is in
the BIOS ... the original bug was fixed by Dell's patch on at
least two different motherboards. So you seem to want
a slightly different BIOS bug to be worked around ...
> I know that David Brownlee disagrees with writing zero into the
> configuration space, but it looks safer to me, because old code
> did write that zero.
Dave who? :)
Actually, I don't recall anyone providing a patch that addressing
that second type of BIOS bug before. Makes sense to me to fall
back to that old Linux bug; why not!
- Dave
>
> -- Pete
>
> --- linux-2.4.27/drivers/usb/host/ehci-hcd.c 2004-08-10 13:43:36.691040600
-0700
> +++ linux-2.4.21-17.EL-usb1/drivers/usb/host/ehci-hcd.c 2004-07-30
16:21:12.000000000 -0700
> @@ -303,7 +302,8 @@
> if (cap & (1 << 16)) {
> ehci_err (ehci, "BIOS handoff failed (%d, %04x)\n",
> where, cap);
> - return 1;
> + pci_write_config_dword (ehci->hcd.pdev, where, 0);
> + return 0;
> }
> ehci_dbg (ehci, "BIOS handoff succeeded\n");
> }
> @@ -547,7 +547,8 @@
>
> /* root hub is shut down separately (first, when possible) */
> spin_lock_irq (&ehci->lock);
> - ehci_work (ehci, NULL);
> + if (ehci->async)
> + ehci_work (ehci, NULL);
> spin_unlock_irq (&ehci->lock);
> ehci_mem_cleanup (ehci);
>
>
next prev parent reply other threads:[~2004-08-11 4:48 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-10 12:59 uhci-hcd oops with 2.4.27/ intel D845GLVA Kai Militzer
2004-08-10 17:10 ` Marcelo Tosatti
2004-08-10 17:10 ` Marcelo Tosatti
[not found] ` <mailman.1092163681.21436.linux-kernel2news@redhat.com>
2004-08-10 20:54 ` Pete Zaitcev
2004-08-11 4:37 ` David Brownell [this message]
2004-08-11 5:02 ` Pete Zaitcev
2004-08-11 7:16 ` David Brownell
2004-08-11 11:08 ` Nick Bartos
-- strict thread matches above, loose matches on Subject: below --
2004-08-09 12:15 Nick Bartos
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=200408102137.26004.david-b@pacbell.net \
--to=david-b@pacbell.net \
--cc=km@westend.com \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo.tosatti@cyclades.com \
--cc=spam99@2thebatcave.com \
--cc=zaitcev@redhat.com \
/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