From: Programmingkid <programmingkidx@gmail.com>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: Li Qiang <liqiang6-s@360.cn>,
qemu-devel qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] Patch causes Mac OS X to print dead controller messages
Date: Mon, 6 Mar 2017 10:18:51 -0500 [thread overview]
Message-ID: <0DFFD63A-FC17-44D7-9452-2EEE7A89D2B7@gmail.com> (raw)
In-Reply-To: <1488791436.18653.22.camel@redhat.com>
On Mar 6, 2017, at 4:10 AM, Gerd Hoffmann wrote:
> On Mi, 2017-03-01 at 23:08 -0500, Programmingkid wrote:
>> commit 95ed56939eb2eaa4e2f349fe6dcd13ca4edfd8fb
>> usb: ohci: limit the number of link eds
>>
>> This patch causes Mac OS X to continuously print this message:
>> USBF: 35.508 AppleUSBOHCI[0x1187000] Watchdog detected dead controller (hcca #: 0, hc#: 863)
>>
>> I used git bisect to find this patch. None of the USB devices work when connected to the OHCI USB controller.
>
> Hmm, ok, appearently the limit is too strict for macos. Can you try to
> increase ED_LINK_LIMIT ?
I used the value of 20 and it worked.
prev parent reply other threads:[~2017-03-06 15:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-02 4:08 [Qemu-devel] Patch causes Mac OS X to print dead controller messages Programmingkid
2017-03-06 9:10 ` Gerd Hoffmann
2017-03-06 15:18 ` Programmingkid [this message]
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=0DFFD63A-FC17-44D7-9452-2EEE7A89D2B7@gmail.com \
--to=programmingkidx@gmail.com \
--cc=kraxel@redhat.com \
--cc=liqiang6-s@360.cn \
--cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).