public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Will Beers <whbeers@mbio.ncsu.edu>
To: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] proper bios handoff in ehci-hcd
Date: Tue, 13 Jul 2004 01:30:58 -0400	[thread overview]
Message-ID: <40F37392.4040902@mbio.ncsu.edu> (raw)
In-Reply-To: <40CF0049.2010307@pacbell.net>

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

> Stuart Hayes here at Dell has identified this or/and mix-up in the
> ehci-hcd driver.  Because of this, ehci-hcd is not properly released by
> BIOSes supporting full 2.0 and port behavior can then become erratic.

This change actually breaks USB altogether on an Asus P4P800, as I noticed when I updated to 2.6.8-rc1.

I get the following messages at boot:

-----
Jul 12 23:34:06 willdesktop kernel: ehci_hcd 0000:00:1d.7: BIOS handoff failed (104, 1010001)
Jul 12 23:34:06 willdesktop kernel: ehci_hcd 0000:00:1d.7: can't reset
Jul 12 23:34:06 willdesktop kernel: ehci_hcd 0000:00:1d.7: init 0000:00:1d.7 fail, -95
Jul 12 23:34:06 willdesktop kernel: ehci_hcd: probe of 0000:00:1d.7 failed with error -95
-----

I've seen a few other people with this problem, and reversing the change makes everything work perfectly again, maybe this was the cause of it all?  (sorry if I missed the fix before)

(included patch reverses it)

-Will

-----------------------------------------------------------------------------


diff -Nru a/drivers/usb/host/ehci-hcd.c b/drivers/usb/host/ehci-hcd.c
--- a/drivers/usb/host/ehci-hcd.c       2004-07-13 01:09:00.000000000 -0400
+++ b/drivers/usb/host/ehci-hcd.c       2004-07-13 01:08:32.000000000 -0400
@@ -293,7 +293,7 @@
                struct pci_dev *pdev = to_pci_dev(ehci->hcd.self.controller);
 
                /* request handoff to OS */
-               cap |= 1 << 24;
+               cap &= 1 << 24;
                pci_write_config_dword(pdev, where, cap);
 
                /* and wait a while for it to happen */

[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/x-pkcs7-signature, Size: 3186 bytes --]

  reply	other threads:[~2004-07-13  5:31 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-14 20:30 [PATCH] proper bios handoff in ehci-hcd Gary_Lerhaupt
2004-06-15 13:57 ` [linux-usb-devel] " David Brownell
2004-07-13  5:30   ` Will Beers [this message]
     [not found]     ` <200407130744.22920.andjoh@rydsbo.net>
2004-07-13  6:16       ` Will Beers
2004-07-13 18:07   ` [linux-usb-devel] " Olaf Hering
2004-07-13 20:26     ` David Brownell
2004-07-13 20:44       ` Will Beers
2004-07-13 21:11         ` David Brownell
2004-07-13 21:24           ` Will Beers
2004-07-13 21:35             ` David Brownell
2004-07-13 21:43               ` Will Beers
2004-07-13 21:31           ` Will Beers

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=40F37392.4040902@mbio.ncsu.edu \
    --to=whbeers@mbio.ncsu.edu \
    --cc=linux-kernel@vger.kernel.org \
    /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