Ping^3?
This issue is still present in qemu 1.3 and current git (1.4-tobe) versions,
and the said commit is still revertable, and reverting it still fixes the
problem...
I wonder why only debian users suffer from this problem ;)
Thanks,
/mjt
12.11.2012 19:13, Michael Tokarev wrote:
Ping^2 ?
Ping^2 ?
/mjt
27.10.2012 12:31, Michael Tokarev wrote:
> Ping?
>
> On 19.09.2012 12:08, Michael Tokarev wrote:
>> This reverts commit 67c5322d7000fd105a926eec44bc1765b7d70bdd:
>>
>> I'm not sure if the retry logic has ever worked when not using FIFO
>> mode. I
>> found this while writi
Ping?
/mjt
On 19.09.2012 12:08, Michael Tokarev wrote:
> This reverts commit 67c5322d7000fd105a926eec44bc1765b7d70bdd:
>
> I'm not sure if the retry logic has ever worked when not using FIFO mode.
> I
> found this while writing a test case although code inspection confirms it
> is
>
This reverts commit 67c5322d7000fd105a926eec44bc1765b7d70bdd:
I'm not sure if the retry logic has ever worked when not using FIFO mode. I
found this while writing a test case although code inspection confirms it is
definitely broken.
The TSR retry logic will never actually happen