Linux PCI subsystem development
 help / color / mirror / Atom feed
From: "Limonciello, Mario" <mario.limonciello@amd.com>
To: Juno Computers USA <usa@junocomputers.com>
Cc: Bjorn Helgaas <helgaas@kernel.org>,
	"Greenman, Gregory" <gregory.greenman@intel.com>,
	Bjorn Helgaas <bhelgaas@google.com>,
	"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
	"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
	"linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>
Subject: Re: firmware-iwlwifi: Wireless AC 7265 lacks D3cold support
Date: Mon, 14 Aug 2023 11:58:40 -0500	[thread overview]
Message-ID: <912c659b-420e-4c2d-96f1-0ed6de5d4b4c@amd.com> (raw)
In-Reply-To: <C9EAD2BA-5148-4793-8427-D23F1EF2C084@getmailspring.com>



On 8/14/2023 11:56 AM, Juno Computers USA wrote:
> Hi,
> 
> I can provide some logs. Should I do it with pcie_port_pm=off or without?
> 

You could do it with both, just make it clear when you add the 
attachment description to the kernel bugzilla which logs are which.

Also; if you try my patch series please make sure you test without that 
parameter and indicate which logs contain it.

> On Aug 14 2023, at 12:41 pm, Limonciello, Mario 
> <mario.limonciello@amd.com> wrote:
> 
> 
> 
>     On 8/14/2023 11:35 AM, Bjorn Helgaas wrote:
>      > [+cc Mario, linux-pm]
>      >
>      > On Sun, Aug 13, 2023 at 03:33:21PM +0000, Greenman, Gregory wrote:
>      >> On Fri, 2023-08-11 at 15:34 -0400, Juno Computers USA wrote:
>      >>> Any updates on this?
>      >
>      > D3cold support has been a problem area, and there are some changes in
>      > progress [1] that could be related.
> 
>     Yeah; no harm in at least trying this series. I'd love another data
>     point with it.
> 
>      >
>      > Could you possibly collect the complete dmesg logs (with a recent
>      > upstream kernel, e.g., v6.4, if possible)? And the output of
>      > "sudo lspci -vv"? And the contents of /sys/firmware/acpi/tables/?
>      > You can attach them to the Debian bug report if that's convenient for
>      > you.
>      >
> 
>     Yes this could be related but it will come down to
>     1) Whether the root ports are considered power manageable.
>     2) The system uses S0ix or not.
> 
>     whether the series could help as it stands today.
> 
>     Please CC me into any kernel bugzilla that you open against a mainline
>     or stable kernel and can capture the lspci output, the dmesg and
>     acpidump and I'll look at it.
> 
>      > Bjorn
>      >
>      > [1]
>     https://lore.kernel.org/r/20230809185453.40916-1-mario.limonciello@amd.com
> 
>     BTW - Bjorn, can I have comments on the last patch in this series? I
>     have fixes ready locally for everything in the earlier patches that Andy
>     gave feedback but I was hoping for some feedback on the very last patch
>     before I sent out a v12.
> 
>     Thanks!
> 
>      >
>      >>> On Aug 3 2023, at 8:01 am, Juno Computers USA
>     <usa@junocomputers.com> wrote:
>      >>>> Dear Maintainer,
>      >>>>
>      >>>> If D3Cold is enabled from BIOS the tablet boots without Wifi.
>      >>>> The only two ways to enable wifi support is either by disabling
>      >>>> D3Cold from BIOS (not ideal) or adding pcie_port_pm=off to grub
>      >>>>
>      >>>> [   12.681303] iwlwifi 0000:01:00.0: Detected Intel(R) Dual
>     Band Wireless AC 7265, REV=0x210
>      >>>>
>      >>>> This is needed for our new Juno Tab 2
>      >>>>
>      >>>> https://junocomputers.com/us/product/juno-tab-2/
>      >>>>
>      >>>> I also filed this under Debian bug-tracker.
>      >>>>
>      >>>> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1036633
>      >>>> Thanks,
>      >>>>
>      >>>> Giovanni Caligaris
>      >>>> Juno Computers USA
>      >>>> P: (215) 509-5472
>      >>>> W: https://junocomputers.com/us
>      >>
>      >> This device is very old and actually already EOL, so I'll not be
>      >> able to get any support for this internally. D3 works fine with this
>      >> NIC on standard, off the shelf laptops, so I'd guess that the probem
>      >> could be rooted in the tablets' PCIe hardware or maybe the BIOS
>      >> itself.
> 

  parent reply	other threads:[~2023-08-14 16:59 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <658472FA-75CB-48AC-96C1-68BAA4AE597A@getmailspring.com>
     [not found] ` <FE32C1A0-5F23-4A21-BD55-4F152DE4D6D6@getmailspring.com>
2023-08-13 15:33   ` firmware-iwlwifi: Wireless AC 7265 lacks D3cold support Greenman, Gregory
2023-08-14 16:35     ` Bjorn Helgaas
2023-08-14 16:41       ` Limonciello, Mario
     [not found]         ` <C9EAD2BA-5148-4793-8427-D23F1EF2C084@getmailspring.com>
2023-08-14 16:58           ` Limonciello, Mario [this message]
     [not found]             ` <21332625-6BED-4BD1-85D7-52926C7D61F8@getmailspring.com>
2023-08-14 18:02               ` Limonciello, Mario
     [not found]                 ` <7505EB8D-2488-4A4D-A0E8-626FBBA6CCF8@getmailspring.com>
2023-08-14 18:15                   ` Limonciello, Mario

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=912c659b-420e-4c2d-96f1-0ed6de5d4b4c@amd.com \
    --to=mario.limonciello@amd.com \
    --cc=bhelgaas@google.com \
    --cc=gregory.greenman@intel.com \
    --cc=helgaas@kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=usa@junocomputers.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox