From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757496AbcCXLKb (ORCPT ); Thu, 24 Mar 2016 07:10:31 -0400 Received: from us-smtp-delivery-102.mimecast.com ([216.205.24.102]:48922 "EHLO us-smtp-delivery-102.mimecast.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1757383AbcCXLKU convert rfc822-to-8bit (ORCPT ); Thu, 24 Mar 2016 07:10:20 -0400 X-Greylist: delayed 409 seconds by postgrey-1.27 at vger.kernel.org; Thu, 24 Mar 2016 07:10:19 EDT From: Jason Taylor To: Thomas Gleixner , Matthias Prager CC: Sreekanth Reddy , linux-scsi , LKML , "x86@kernel.org" Subject: RE: [BUG] mpt2sas: driver init fails on kernel >=4.2 for 9211-8i IT Thread-Topic: [BUG] mpt2sas: driver init fails on kernel >=4.2 for 9211-8i IT Thread-Index: AQHRhZNjY+Ef/NfKBkOUWCUE5aQaPJ9obGQw Date: Thu, 24 Mar 2016 11:02:39 +0000 Message-ID: <99405e4d4b454ff59d81026597c7fd5a@WB-SVT-EXBE03.simplivity.com> References: <56EF049F.6050809@matthiasprager.de> <56EFBC55.9070209@matthiasprager.de> <56F018A0.7070307@matthiasprager.de> <56F021B9.9080305@matthiasprager.de> <56F1B2E5.1070605@matthiasprager.de> <56F34BB5.3090007@matthiasprager.de> In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-ms-exchange-transport-fromentityheader: Hosted x-originating-ip: [10.7.4.135] MIME-Version: 1.0 X-MC-Unique: YTssywj1SDSh6gS4hWaRZw-1 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8BIT Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org The last update we have from VMware is that the fix will be in 6.0p3/5.5p8 - both of which are targeted for a mid year release. -----Original Message----- From: Thomas Gleixner [mailto:tglx@linutronix.de] Sent: Thursday, March 24, 2016 2:06 AM To: Matthias Prager Cc: Sreekanth Reddy ; linux-scsi ; Jason Taylor ; LKML ; x86@kernel.org Subject: Re: [BUG] mpt2sas: driver init fails on kernel >=4.2 for 9211-8i IT 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: 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 --------------------------------------------------------------------------------------- PRIVACY STATEMENT: This message is a PRIVATE communication. This message and all attachments are a private communication sent by SimpliVity and are considered to be confidential or protected by privilege. If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution or use of the information contained in or attached to this message is strictly prohibited. Please notify the sender of the delivery error by replying to this message, and then delete it from your system. ---------------------------------------------------------------------------------------