From mboxrd@z Thu Jan 1 00:00:00 1970 From: Tamas Papp Subject: Re: STI problem and workaround for Dell XPS 13 (Skylake, 2016) / Broadcom BCM4350 Date: Thu, 03 Mar 2016 08:16:06 +0100 Message-ID: <8737s8uj49.fsf@gmail.com> References: <87h9gpp5rt.fsf@gmail.com> <87a8mhotmk.fsf@gmail.com> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from mail-wm0-f51.google.com ([74.125.82.51]:34121 "EHLO mail-wm0-f51.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754786AbcCCHQK (ORCPT ); Thu, 3 Mar 2016 02:16:10 -0500 Received: by mail-wm0-f51.google.com with SMTP id p65so21025379wmp.1 for ; Wed, 02 Mar 2016 23:16:09 -0800 (PST) In-reply-to: Sender: linux-pm-owner@vger.kernel.org List-Id: linux-pm@vger.kernel.org To: yu chen Cc: linux-pm@vger.kernel.org On Wed, Mar 02 2016, yu chen wrote: > Currently the 0000:3c and 0000:3a might have the same pnp object name PXSX, > unfortunately the 'echo' will find the first math device in the > wakable list, and maybe > 0000:3c was probed before 0000:3a, so... maybe this is a weakness. > > Maybe you can disabled the wakable feature directly in device sysfs, > for example, > echo 0 > /sys/devices/pci0000:00/0000:3a:00.0/power/wakeup, > you might need to find out where 0000:3a:00.0 is. I tried that, but the module has problems after wakeup. I have to remove and insert it again with modprobe. Still, this is an OK workaround, thanks for the help. I still don't know if I should file this as a bug, and if yes, where. Best, Tamas