Received: by 10.223.164.221 with SMTP id h29csp1426686wrb; Mon, 2 Oct 2017 07:34:34 -0700 (PDT) X-Google-Smtp-Source: AOwi7QAdM3uM8o1hVDRwtGyD+S5SP/bIQqKGsQYVEi2ZffgZ5kcN3Ztixil0Sc9i2K0ZMGhzgRgN X-Received: by 10.98.190.19 with SMTP id l19mr14711954pff.309.1506954874243; Mon, 02 Oct 2017 07:34:34 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1506954874; cv=none; d=google.com; s=arc-20160816; b=a54fuKrpWJszgpkGID18RwA4mXSvP6yzEi8VVZmghURPWfV0WlImogs3cclX0KDiA8 OMe5Cw81G9yex/D5qCDFNP8+d1GXzdTFSWKGvRaxwiR0rmeKjd1+1cuk+q+sJHCZfqdW OU5PcnbCgZlXMVPhwi9pXT+ImjbfVkoBBY9a2DTZ7akbH3coemu/q1lDZXK11M5HHM0x WQ+/eHXrsP4Kz0XnL+ViAd1A8+HVGTJSIZdTI6RUzuQ/rhBeVGg90PH7K3DhRfzkz5q1 ZMtRrnvqd7Y6maYdXGF7Pm9KcrP+ueDzZeJZw/Em5Lz0S4fRpC5HN4mNVJJX8YJxYh+Q dUaQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding :content-language:in-reply-to:mime-version:user-agent:date :message-id:from:references:to:subject:arc-authentication-results; bh=Jg94y7DUdejFDF78y4nbknN0BUCz8vozYmUg7UJ3zRw=; b=K+qrdbTN3rwOzCm/DbgY1HZlOuTNlfekRYsGHReADEzA2RNTG+wDi330i6w3CKeNxw ic+cADQIDEm3QDlmdm/rplIEMBodDRf8H6vlsxqZ+0RpqKXiR49Nd3HPaFae83nUt18E ol34E41NP3AuhUdt5gfOTOoFlPUhYwly/aJh9DfnWcooITSY8FEhhytesKNqboNWJ3Yz ZNXB4Jn53NbGmS0gsGZIxgK1eMcqKLnp1m4dF9odK2yc8Kb5l+rsu3DfO/7eDz0pviYB 5mc3nfUleuY3ID8K45/olf008dhP9I9uSPSTdqZHhPnmphZPP7HKCJTsE2k7XksuLQQd hlbw== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id j19si8382643pll.243.2017.10.02.07.34.19; Mon, 02 Oct 2017 07:34:34 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751430AbdJBOcv (ORCPT + 99 others); Mon, 2 Oct 2017 10:32:51 -0400 Received: from mx2.suse.de ([195.135.220.15]:58098 "EHLO mx1.suse.de" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1751084AbdJBOct (ORCPT ); Mon, 2 Oct 2017 10:32:49 -0400 X-Virus-Scanned: by amavisd-new at test-mx.suse.de Received: from relay1.suse.de (charybdis-ext.suse.de [195.135.220.254]) by mx1.suse.de (Postfix) with ESMTP id 4A6C5AAB6; Mon, 2 Oct 2017 14:32:48 +0000 (UTC) Subject: Re: mptsas driver cannot detect hotplugging disk with the LSI SCSI SAS1068 controller in Ubuntu guest on VMware To: Gavin Guo , linux-scsi@vger.kernel.org, linux-kernel References: From: Hannes Reinecke Message-ID: <1ad520f6-a1d8-5ce7-ee74-83edfdbfd39b@suse.de> Date: Mon, 2 Oct 2017 16:32:47 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.3.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 09/27/2017 09:33 AM, Gavin Guo wrote: > There is a problem in the latest upstream kernel with the device: > > $ grep -i lsi lspci > 03:00.0 Serial Attached SCSI controller [0107]: LSI Logic / Symbios > Logic SAS1068 PCI-X Fusion-MPT SAS [1000:0054] (rev 01) > > The device is simulated by the VMware ESXi 5.5 > > When hotplugging a new disk to the Guest Ubuntu OS, the latest kernel > cannot automatically probe the disk. However, on the v3.19.0-80.88 > kernel, the disk can be dynamically probed and show the following > info message: > > mptsas: ioc0: attaching ssp device: fw_channel 0, fw_id 1, phy 1, > sas_addr 0x5000c29a6bdae0f5 > scsi 2:0:1:0: Direct-Access VMware Virtual disk 1.0 PQ: 0 > ANSI: 2 > sd 2:0:1:0: Attached scsi generic sg2 type 0 > sd 2:0:1:0: [sdb] 2097152 512-byte logical blocks: (1.07 GB/1.00 GiB) > sd 2:0:1:0: [sdb] Write Protect is off > sd 2:0:1:0: [sdb] Mode Sense: 61 00 00 00 > sd 2:0:1:0: [sdb] Cache data unavailable > sd 2:0:1:0: [sdb] Assuming drive cache: write through > sdb: unknown partition table > sd 2:0:1:0: [sdb] Attached SCSI disk > > After looking up the message: > mptsas: ioc0: attaching ssp device: fw_channel 0, fw_id 1, phy 1, > sas_addr 0x5000c29a6bdae0f5 > > I found it comes from the path: > mptsas_firmware_event_work -> mptsas_send_sas_event -> > mptsas_hotplug_work -> mptsas_add_end_device > > I'll appreciate if anyone can give the idea: If it's possible that the > irq from the simulated LSI SAS controller didn't come in to trigger > the event? However, it can work on the v3.19 kernel so if there is > any driver implementation issue in the latest kernel. > This is an issue with the mptsas driver, who originally assumed that no system will have direct-attached SAS devices. VMWare chose to implement exactly that, so the hotplug detection logic is flawed here. I'll be sending a patch. Cheers, Hannes -- Dr. Hannes Reinecke Teamlead Storage & Networking hare@suse.de +49 911 74053 688 SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg GF: F. Imendörffer, J. Smithard, J. Guild, D. Upmanyu, G. Norton HRB 21284 (AG Nürnberg) From 1579677274363332634@xxx Wed Sep 27 07:34:04 +0000 2017 X-GM-THRID: 1579677274363332634 X-Gmail-Labels: Inbox,Category Forums