Received: by 2002:ac0:a5b6:0:0:0:0:0 with SMTP id m51-v6csp4552391imm; Wed, 30 May 2018 07:42:33 -0700 (PDT) X-Google-Smtp-Source: ADUXVKIV4uQY6The+mOhLxkK3AArnZfAl68EbGaaMif0ad5O7KLHqxd1D9FMsQL1UPRYu2okimZ3 X-Received: by 2002:a17:902:8:: with SMTP id 8-v6mr3070577pla.287.1527691353725; Wed, 30 May 2018 07:42:33 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1527691353; cv=none; d=google.com; s=arc-20160816; b=NCkdPtnoI9vnQHms02S/LSBfh18BOTs/grQ8QTEiyjNubYMLw82HdwHU7mouKQX8dR H4kGgvd6c0TBw3RSgFah3UP2xFkcv7tadj9J4U4FmdGYVyqqYB9ZknEbbV9EpvK+k3Rf ubX455Ek1aTqPyQGyBeOSpWdIrb78FJLutcBbsJ+bxG1crh0zhxHZt3lKGazR+5mF+EU 3kgWC6jyw/U0ZY3B1W5jFjU+4DMZCnrIZv42uoQB2jhC3kSGzL56w86u3rmIsBXcYBBB OfLOvawTizmZjYQae47+jIPYXma3IpLpNxy8ATepHMV0Ke08bllIpV9cqHdVhMO2aQ8b vLZQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:dkim-signature :arc-authentication-results; bh=pbzz31BQ4VOd2oJgI3EIIM5sBJkSTjow/eoGtmHM3JA=; b=E2JQcogwb2AIyZApu+dhscZw8gbO2Wp7aGIlfgEZ+1xtptecvHk4vAph3rh0rSm3ln RYb2SS/eR9dyCcvjR550p2qdtGwfSAWY+N6gaxejPoE5Tp+9p7aWq7wG29lMYy2hYUGB PVogp/UlnpgCNhwTz5xbn+iMHrPKEjhl7x+Tce1/1ufkv39jxo1LN0VaL2UdWOkNF0k9 A+zCtAt29AhaAIo3VAlg08kBg79qsdPH+n/8lJz7BM6nqBmG2yosizuSefMaHeATMaZW Y1VLEHvJsISEpl2j2ngpvP8KGCHGQj3DWKjdFv0MpX7OoWlCcWowIKglXKXlR7V1oQmx PSGg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@google.com header.s=20161025 header.b=jipFrYxm; 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; dmarc=pass (p=REJECT sp=REJECT dis=NONE) header.from=google.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id y18-v6si27206177pgv.202.2018.05.30.07.42.19; Wed, 30 May 2018 07:42:33 -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; dkim=pass header.i=@google.com header.s=20161025 header.b=jipFrYxm; 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; dmarc=pass (p=REJECT sp=REJECT dis=NONE) header.from=google.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753494AbeE3Olu (ORCPT + 99 others); Wed, 30 May 2018 10:41:50 -0400 Received: from mail-yb0-f178.google.com ([209.85.213.178]:38150 "EHLO mail-yb0-f178.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753196AbeE3Ols (ORCPT ); Wed, 30 May 2018 10:41:48 -0400 Received: by mail-yb0-f178.google.com with SMTP id q62-v6so4951196ybg.5 for ; Wed, 30 May 2018 07:41:47 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=pbzz31BQ4VOd2oJgI3EIIM5sBJkSTjow/eoGtmHM3JA=; b=jipFrYxmkFjC9itcXM1EuKHFhfQ4GKjDwnCQ0y4mla/kGDoqhvYA+svVV4Mlof7vkp xdMtJ6klpkdP2YK0AQCs3OmZI204G4e+JVmFN4fYsapjhSlQjSY1EDTjAzqyKsgPmHbg PNrU91CInypUJhx5fEjUng+UqpZmpcFCM7RRpPGlKhmcgqoBNIXfE+2r34Bpa+GGWB+A 24WaI0sOuHPeIhTEOL8YZwUv0nIJEcg89ruGAljoPH0myCZhCVnsKEL/6T4sA9q7sLLA hG+dHUrTOEDphI5tsXxv1Xp2glj2iCVZblQY8xRRlwVVvICz4zNNOKKEm1QljZMnAyL6 RcgA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=pbzz31BQ4VOd2oJgI3EIIM5sBJkSTjow/eoGtmHM3JA=; b=FAKCexUW6I8b4h31ulNEEbnh7m2E3dXDfm0CS0wQxYyKM2vSIHsdsiSFdrib93oLe1 FF9UeqC3QuTNWb5uPXJVmlsb462aU7WTiYvLpZvuHyuZE1xJv0f736ZhNl/zcLU2dv/E hoDgOwQs1rsmROKE2zInWuwvsEJs2DcquRdlGLu/i3jdzqM4Z3nHxGFHASoBVGJATb/h nwTvWs72GCsn6rRUiRyE3X125vbCX1XdES9Jl5gCNthxmUxGFvu338aqJpiBUEvogarC Tds6nC1Tj9HJvOz47BOoe44UODDFgpGAC1y91E+4Xl9KZ/WBJCGEBXz/vOURNst+bf59 NeEw== X-Gm-Message-State: ALKqPweRMVDqOprQ5Wh6FGsyBDHeT44R6q9GkE4tdN29YP4PABZyQnTf 4MQyZu22M7BsVgIrWOYwAQYvIUNhf2ImkAJGnVyX X-Received: by 2002:a25:550:: with SMTP id 77-v6mr1653104ybf.324.1527691307009; Wed, 30 May 2018 07:41:47 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Bjorn Helgaas Date: Wed, 30 May 2018 07:41:35 -0700 Message-ID: Subject: Fwd: [Bug 199879] New: Very basic the Pci device is not resumed from suspend mode To: linux-pci@vger.kernel.org Cc: Linux Kernel Mailing List , Linux PM list Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org [+cc linux-pci, linux-kernel, linux-pm] I'm not sure I understand the problem yet, so please correct me if I'm wrong: - Your system has both Nvidia and Intel graphics devices - When you use Intel graphics, lspci, lshw, and /proc/bus/pci for the Nvidia device show invalid data (0xff) after suspend/resume - When you use Nvidia graphics, suspend/resume doesn't work (instead of resuming, you just get a blank screen) Can you attach the output of "sudo lspci -vv" to the bugzilla, please? ---------- Forwarded message --------- From: Date: Tue, May 29, 2018 at 1:29 PM Subject: [Bug 199879] New: Very basic the Pci device is not resumed from suspend mode To: https://bugzilla.kernel.org/show_bug.cgi?id=199879 Bug ID: 199879 Summary: Very basic the Pci device is not resumed from suspend mode Product: Drivers Version: 2.5 Kernel Version: kernel-4.15.17 Hardware: x86-64 OS: Linux Tree: Mainline Status: NEW Severity: high Priority: P1 Component: PCI Assignee: drivers_pci@kernel-bugs.osdl.org Reporter: uzg@wp.pl Regression: No Hi, I have problem with very basic device. Device pci-e not resume from suspend. Only sleep. I have a problem with anyone interested in it, because everyone thinks it is the fault of the device drivers themselves. But this is not a problem. This device is a basic device. I've already installed drivers on various hardware and it has always been ok, but not this time. I'm an electronics technician. After diagnosing what I managed, in my opinion the device remains asleep. Where does my application come from? I have multiuser mode and I do not use this device. After suspend lspci and lshw show normal data. Normal data is in /proc/bus/pci/... Next suspend and resume, and... lspci see hardware, but is error lshw see hardware as undefined device data in /proc/bus/pci/... is only 0xFF Hardware sleep, not work, not ready. This is bug. But since the problem concerns the graphics card in the configuration with the second default Intel card, everyone thinks that this is another driver problem as always and nobody wants to take a look at it :( The problem is easy to recognize. On the internet, I've seen a lot of unresolved problems in which I could see exactly what I found. My hardware is Lenovo with NVidia and Intel Graphics. Problem is with NVidia. I tested Z710 and Z50-70. The first symptom of the problem is lspci in multiuser mode (or when is XServer with intel graphics). After suspend NVidia have e.g "rev. A1", after resume is "rev. FF". Next symptom lshw and /proc/bus/pci/... When system started with normal NVidia driver, system not resume and halt, only black screen. There are many examples on the Internet with unsolved problems e.g https://www.lwks.com/index.php?option=com_kunena&func=view&catid=21&id=124374&Itemid=81 -- You are receiving this mail because: You are watching the assignee of the bug.