Re: [patch 19/26] USB: mutual exclusion for EHCI init and port resets

> This addition certainly won't hurt.  Did we ever get any feedback as to 
> whether it actually helped?

ISTR that davem refused to try it, after reporting an
intermittent failure on the original patch (which only
addresses one end of that hardware race).

So, no ... but given we know that closing only one side
of the race isn't quite enough, I think we need it anyway.

- Dave

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

---

• Follow-Ups:
  • Re: [patch 19/26] USB: mutual exclusion for EHCI init and port resets
    • From: David Miller <[email protected]>

• References:
  • Re: [patch 19/26] USB: mutual exclusion for EHCI init and port resets
    • From: Alan Stern <[email protected]>

• Prev by Date: [PATCH] Cast __page_to_pfn to unsigned long in CONFIG_SPARSEMEM
• Next by Date: Re: broken suspend [Was: 2.6.24-rc2-mm1]
• Previous by thread: Re: [patch 19/26] USB: mutual exclusion for EHCI init and port resets
• Next by thread: Re: [patch 19/26] USB: mutual exclusion for EHCI init and port resets
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]