Am 24.03.2016 um 07:06 schrieb Thomas Gleixner: > On Thu, 24 Mar 2016, Matthias Prager wrote: >> The timeout happens reliably after two warm boots with a 'bad' kernel >> after coming from a 'good' kernel, and also after one cold boot with a >> 'bad' kernel (meaning cold booting a 'bad' kernel leads directly to the >> timeout and warm booting needs a second run to produce the timeout). I >> haven't tested bare metal yet - I can do that tomorrow if necessary. > > That's on VMWare, right? Jason has seen the same issue: Correct ESXi 5.1 patchlevel 3070626 (the two controllers are passed through to the VM). > > http://marc.info/?l=linux-kernel&m=145280623530135&w=2 > http://marc.info/?l=linux-kernel&m=145523785705624&w=2 > > "Works fine on real hardware and KVM. Filed an issue with VMware and the fix > is in the works." > > Jason, what's the state of this? > > Thanks, > > tglx > -- 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
