Hello, I solved the mystery, I found that the element who triggers the bug ( random hang at boot with kernel 3.17 and 3.18 ) is the combination of 3 elements : - the use of a SATA DVD burner ( Liteon iHAS124 C ) on a ICH7 Sata controler - the use of a gigabyte motherboard GA-P31-DSL3 ( bios F10A, ICH7 controler, intel P31 chipset ) - commit 74665016086615bbaa3fa6f83af410a0a4e029ee ( scsi: convert host_busy to atomic_t ) If I connect this Sata DVD burner and a sata harddisk by using the SATA ports of the motherboard then the bug will occur ( but the bug will occur only on kernels 3.17 and 3.18, there is no problems with older kernels, and no problems with Windows 7 ) If I disconnect the SATA DVD burner then the bug is gone, no problems with kernels 3.17 and 3.18, And if I connect the SATA DVD burner on my JMicron SATA/IDE PCIe card then there is no problem, no bugs, this is a perfect workaround for my problem, because I can use kernel 3.17/3.18 without problem with this configuration. But I don't know which element I should blame, my gigabyte motherboard ? ( faulty bios ? ) The use of "atomic_t" in scsi source code ? ( innapropriate way to handle SATA devices, it breaks compatibility with some PC configurations ? ) Le 14/11/2014 08:32, Christoph Hellwig a écrit : > On Thu, Nov 13, 2014 at 11:55:38PM +0100, Barto wrote: >> it's interesting, with this commit >> 74665016086615bbaa3fa6f83af410a0a4e029ee I have the bug : >> >> scsi: convert host_busy to atomic_t : > > At this point we'll need a bisction between v3.16 as the last good > point, and 74665016086615bbaa3fa6f83af410a0a4e029ee as the known bad > point. > -- To unsubscribe from this list: send the line "unsubscribe linux-scsi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
