Hello, Robert, bl0 (would be cool if this were your real name :) On Tue, Jan 08, 2013 at 10:48:43PM -0600, Robert Hancock wrote: > >>Do you think something should be done about it in the linux sata_sil > >>driver? For a lack of a better solution, here is my suggestion. There is > >>already one option 'slow_down' for problematic disks. Another option, for > >>example 'cache_line_workaround', could be added for problematic > >>motherboards. If enabled, the most straightforward way is to set cache > >>line size to 0 and not worry about the fifo_cfg register. > > > >Here is the code I currently have, attached as a diff. (This diff is not > >against the latest git tree, it's against an older linux version which I > >use.) > > I wouldn't mind something like this as an option, anyway. Jeff, > Tejun, thoughts? I don't know. This thread makes me want to eat obsessivly, cry in fetal position and then puke and wet my pants. The issue has been there from the beginning. The current code seems to cope with, I hope, majority of configurations; unfortunately, for the problematic ones, there hasn't been any sensible explanation or reliable way to detect what is causing the problem. I don't even know how we should blacklist them. Is it chipset-specific or system-specific? ie. Should we blacklist north/south bridges or DMI system identifiers? Having a module option is easy and can be helpful for the very rare cases where the admin is aware of the issue, but, in general, it doesn't really help that much. So, let's throw in a module option. Other than that, no idea. \pukes -- tejun -- To unsubscribe from this list: send the line "unsubscribe linux-ide" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
