I just reproduced it - Artem, I'll let you know when we have a possible fix but hopefully there won't be any need for you to beat up your hardware any more :) On Mon, Dec 21, 2015 at 04:08:11PM -0500, Tejun Heo wrote: > Hello, again. > > On Mon, Dec 21, 2015 at 03:07:21PM -0500, Tejun Heo wrote: > > Hello, Artem. > > > > Can you please apply the following patch on top and see whether > > anything changes? If it does make the issue go away, can you please > > revert the ".can_queue" part and test again? > > If the patch doesn't change anything, can you please try the > followings and see which one makes difference? > > 1. Exclude memory above 4G line with boot param "max_addr=4G". > 2. Disable highmem with "highmem=0". > 3. Try booting 64bit kernel. > > At the moment, the only thing I can think of which can explain the PAE > + bio_get_nr_vecs() situation is that the bio split code which is > activated by the bio_get_nr_vecs() somehow messes up 64bit or high > addresses on 32bit kernels. I scanned for the obvious but at bio > layer, memory is represented by struct page, so nothing obvious seems > broken. > > Note that for now I'm ignoring the debug dumps from the ahci debug > patch which indicates that the passed in addresses are all fine. It > is possible that the controller gets confused with certain receiving > addresses and reports failure on later commands or maybe there is a > different sequence of events which can encompass both that we don't > know of yet. It repros pretty easily, I should be able to just write some test code that sends down single specific IOs so no matter what the controller is doing we know exactly what IO triggered the error. I'm checking all the 64 bit/pae/etc. stuff now. -- 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
