From: Sergio Callegari <sergio.callegari@gmail.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: Borislav Petkov <bp@alien8.de>, linux-kernel@vger.kernel.org
Subject: Re: IDE Floppy support for IOMEGA Zip Drive broken in 3.16 -> 3.17 transition
Date: Thu, 20 Aug 2015 17:08:58 +0200 [thread overview]
Message-ID: <55D5ED8A.5000306@gmail.com> (raw)
In-Reply-To: <20150820080846.GA11599@infradead.org>
Hi Christoph,
thanks for your answer!
Any clue on how to help/speed up this? Was there any exchange with them when you
first provided your patch back in 2014? Can it be restarted?
My feeling is that the issue fixed with 045065d8a300a37218c548e9aa7becd581c6a0e8
was in fact the real paper over the bug. As distros start picking kernels with
045065d8a300a37218c548e9aa7becd581c6a0e8 the issue is like to bite more and more.
And it is a subtle bug. In some cases takes ages before revealing, making one
feel confident on a system that is in fact broken. And takes ages to bisect
(took me almost 7 days).
Best,
Sergio
On 20/08/2015 10:08, Christoph Hellwig wrote:
> Hi Sergio,
>
> On Tue, Aug 18, 2015 at 09:44:28AM +0200, Sergio Callegari wrote:
>> Hi,
>>
>> I have bisected the issue down to
>>
>> [045065d8a300a37218c548e9aa7becd581c6a0e8] [SCSI] fix qemu boot hang problem
>>
>> Bisecting has been a painful job due to the fact that the bug may show only
>> many hours after the system boot.
>>
>> The commit above in fact is not the culprit, but a fix to an issue that was
>> hiding the real bug on my system. See
>>
>> http://marc.info/?l=linux-kernel&m=143973820612978&w=2
>>
>> The real issue is with sata host lock and seems to be biting a few other
>> people as well
>>
>> https://bbs.archlinux.org/viewtopic.php?id=189324
>>
>> A patch fixing the issue was sent to the LKML back in Nov 2014 by Christoph
>> Hellwig (who is reading in CC)
>>
>> https://lkml.org/lkml/2014/11/20/581
>>
>> I have tested the patch and it works for me.
>>
>> What is expected to happen now?
> As mentioned in that thread we need more input from the libata people
> on what kind of race this is papering over.
next prev parent reply other threads:[~2015-08-20 15:09 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-25 20:58 IDE Floppy support for IOMEGA Zip Drive broken in 3.16 -> 3.17 transition Sergio Callegari
2015-06-25 21:31 ` Borislav Petkov
2015-08-18 7:44 ` Sergio Callegari
2015-08-20 8:08 ` Christoph Hellwig
2015-08-20 15:08 ` Sergio Callegari [this message]
2015-08-24 17:07 ` "scsi: convert host_busy to atomic_t" series causes regressions for some hardware configurations Sergio Callegari
2015-08-25 11:00 ` Christoph Hellwig
2015-08-26 7:14 ` Sergio Callegari
2015-08-30 10:54 ` Sergio Callegari
2015-09-07 7:31 ` Sergio Callegari
2015-09-07 17:51 ` Christoph Hellwig
2015-07-02 16:11 ` IDE Floppy support for IOMEGA Zip Drive broken in 3.16 -> 3.17 transition Ondrej Zary
2015-07-03 6:50 ` Sergio Callegari
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=55D5ED8A.5000306@gmail.com \
--to=sergio.callegari@gmail.com \
--cc=bp@alien8.de \
--cc=hch@infradead.org \
--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;
as well as URLs for NNTP newsgroup(s).