From: bugzilla-daemon@bugzilla.kernel.org
To: kvm@vger.kernel.org
Subject: [Bug 206831] New: Intel AC 9260 wifi doesn't load in vm(sys-net under qubes os)
Date: Thu, 12 Mar 2020 13:02:52 +0000 [thread overview]
Message-ID: <bug-206831-28872@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=206831
Bug ID: 206831
Summary: Intel AC 9260 wifi doesn't load in vm(sys-net under
qubes os)
Product: Virtualization
Version: unspecified
Kernel Version: 5.6-rc4
Hardware: Intel
OS: Linux
Tree: Mainline
Status: NEW
Severity: high
Priority: P1
Component: kvm
Assignee: virtualization_kvm@kernel-bugs.osdl.org
Reporter: lipan.ovidiu@gmail.com
Regression: No
I recently updated my qubes r4.1 fc31 to kernel 5.6-rc4(due lack of Nvidia rtx
2080 support under the old kernel). Now the NV card works properly but I've
lost the wifi connection under sys-net vm. I must mention it used to works
perfectly on the older kernel version(actually any version up to 5.6, including
5.5.9 freshly compiled). I also updated the sys-net vm kernel verision to
5.6-rc4 but I still have the issue. Here is the output of dmseg of sys-net:
[ 7.332438] iwlwifi 0000:00:06.0: Failed to load firmware chunk!
[ 7.332458] iwlwifi 0000:00:06.0: iwlwifi transaction failed, dumping
registers
[ 7.332476] iwlwifi 0000:00:06.0: iwlwifi device config registers:
[ 7.338624] iwlwifi 0000:00:06.0: 00000000: 25268086 00180406 02800029
00000000 f2010004 00000000 00000000 00000000
[ 7.338651] iwlwifi 0000:00:06.0: 00000020: 00000000 00000000 00000000
15501a56 00000000 000000c8 00000000 0000010b
[ 7.338677] iwlwifi 0000:00:06.0: 00000040: 00020010 00008ec0 00102810
0045e812 10120000 00000000 00000000 00000000
[ 7.338701] iwlwifi 0000:00:06.0: 00000060: 00000000 00080812 00000000
00000000 00000002 00000000 00000000 00000000
[ 7.338725] iwlwifi 0000:00:06.0: 00000080: 000f0011 00002000 00003000
00000000 00000000 00000000 00000000 00000000
[ 7.338749] iwlwifi 0000:00:06.0: 000000a0: 00000000 00000000 00000000
00000000 00000000 00000000 00000000 00000000
[ 7.338773] iwlwifi 0000:00:06.0: 000000c0: 00000000 00000000 0023d001
0d000008 00804005 fee97000 00000000 00004300
[ 7.338797] iwlwifi 0000:00:06.0: 000000e0: 00000000 00000000 00000000
00000000 00000000 00000000 00000000 00000000
[ 7.338822] iwlwifi 0000:00:06.0: Read failed at 0x100
[ 7.338836] iwlwifi 0000:00:06.0: Could not load the [0] uCode section
[ 7.338860] iwlwifi 0000:00:06.0: Failed to start INIT ucode: -110
[ 7.338877] iwlwifi 0000:00:06.0: Collecting data: trigger 16 fired.
[ 7.588505] iwlwifi 0000:00:06.0: Not valid error log pointer 0x00000000 for
Init uCode
[ 7.588537] iwlwifi 0000:00:06.0: Fseq Registers:
[ 7.588557] iwlwifi 0000:00:06.0: 0x66C2C9EE | FSEQ_ERROR_CODE
[ 7.588579] iwlwifi 0000:00:06.0: 0x00000000 | FSEQ_TOP_INIT_VERSION
[ 7.588602] iwlwifi 0000:00:06.0: 0x815790C8 | FSEQ_CNVIO_INIT_VERSION
[ 7.588624] iwlwifi 0000:00:06.0: 0x0000A371 | FSEQ_OTP_VERSION
[ 7.588645] iwlwifi 0000:00:06.0: 0xF133AC29 | FSEQ_TOP_CONTENT_VERSION
[ 7.588668] iwlwifi 0000:00:06.0: 0xAFFDD78E | FSEQ_ALIVE_TOKEN
[ 7.588689] iwlwifi 0000:00:06.0: 0xB1F3B688 | FSEQ_CNVI_ID
[ 7.588709] iwlwifi 0000:00:06.0: 0x6F9FEAC3 | FSEQ_CNVR_ID
[ 7.588729] iwlwifi 0000:00:06.0: 0x01000200 | CNVI_AUX_MISC_CHIP
[ 7.588753] iwlwifi 0000:00:06.0: 0x01300202 | CNVR_AUX_MISC_CHIP
[ 7.588778] iwlwifi 0000:00:06.0: 0x0000485B |
CNVR_SCU_SD_REGS_SD_REG_DIG_DCDC_VTRIM
[ 7.588856] iwlwifi 0000:00:06.0: 0x0BADCAFE |
CNVR_SCU_SD_REGS_SD_REG_ACTIVE_VDIG_MIRROR
[ 7.588929] iwlwifi 0000:00:06.0: Firmware not running - cannot dump error
[ 7.601717] iwlwifi 0000:00:06.0: Failed to run INIT ucode: -110
Any help will be highly appreciated.
Thank you
--
You are receiving this mail because:
You are watching the assignee of the bug.
reply other threads:[~2020-03-12 13:02 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=bug-206831-28872@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=kvm@vger.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