From: Heiner Kallweit <hkallweit1@gmail.com>
To: Borislav Petkov <bp@alien8.de>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>,
x86@kernel.org, "H. Peter Anvin" <hpa@zytor.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] x86/reboot/quirks: Add Zotac ZBOX CI327 nano PCI reboot quirk
Date: Thu, 10 Dec 2020 21:32:34 +0100 [thread overview]
Message-ID: <706c9de3-57de-9a82-737f-842f972ec596@gmail.com> (raw)
In-Reply-To: <20201210190418.GG26529@zn.tnic>
Am 10.12.2020 um 20:04 schrieb Borislav Petkov:
> On Tue, Dec 01, 2020 at 12:39:57PM +0100, Heiner Kallweit wrote:
>> On this system the M.2 PCIe WiFi card isn't detected after reboot,
>> only after cold boot. reboot=pci fixes this behavior.
>> In [0] the same issue is described, although on another system and
>> with another Intel WiFi card. In case it's relevant, both systems
>> have Celeron CPU's.
>> The dicussion in [0] involved the PCI maintainer, and proposal was
>> to go with the PCI reboot quirk on affected systems until a more
>> generic fix is available.
>>
>> [0] https://bugzilla.kernel.org/show_bug.cgi?id=202399
>
> But this quirk is for your system only - the one in the bugzilla entry
> would need another one? Or?
>
Right, as Bjorn wrote in comment 14:
".., and there may be many systems with this issue and we may be adding
such quirks frequently. But maybe that's the only option, since we
don't know any other way to fix this."
I'd prefer that the autor of a quirk also has the hw to test it on.
Therefore I just added the quirk for my system as a template to the
bug report.
> Thx.
>
Heiner
next prev parent reply other threads:[~2020-12-10 20:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-01 11:39 [PATCH] x86/reboot/quirks: Add Zotac ZBOX CI327 nano PCI reboot quirk Heiner Kallweit
2020-12-10 19:04 ` Borislav Petkov
2020-12-10 20:32 ` Heiner Kallweit [this message]
2020-12-30 17:50 ` [tip: x86/misc] x86/reboot: " tip-bot2 for Heiner Kallweit
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=706c9de3-57de-9a82-737f-842f972ec596@gmail.com \
--to=hkallweit1@gmail.com \
--cc=bp@alien8.de \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).