On Thu, 01 Sep 2011 11:50:38 -0700 James Bottomley <James.Bottomley@xxxxxxxxxxxxxxxxxxxxx> wrote: > On Thu, 2011-09-01 at 10:58 -0700, Roland Dreier wrote: > > > OK I found the bad commit,I got lucky... I lost some files but my > > > machine was able to complete the bisection. CC involved people > > > > > # bad: [b03e7495a862b028294f59fc87286d6d78ee7fa1] PCI: Set PCI-E Max Payload Size on fabric > > > > Hi Eric, > > > > I guess it would be useful to see "lspci -vv" output with a "good" kernel > > and with that bad patch applied. Most likely we should see some difference > > somewhere in the MaxPayload fields in the PCI Express capability of > > some device. > > > > Either the RAID controller or something else lies, and puts a value > > in the DevCap that it can't actually support, or else the patch is > > buggy and puts something out of range in a DevCtl somewhere. > > > While we investigate, I think the problems produced by the patch (data > corruption) are serious enough to warrant reverting it, please Jesse. Hm I haven't been paying attention to the compromise thread; how should I share these changes? Is master.kernel.org down indefinitely? Is there a new server at kernel.org I can use? -- Jesse Barnes, Intel Open Source Technology Center -- 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
