From: Genes Lists <lists@sapience.com>
To: tglx@linutronix.de, linux-kernel@vger.kernel.org,
gregory.greenman@intel.com, kvalo@kernel.org,
linux-wireless@vger.kernel.org
Subject: crash with 6.7 rc2 and rc3
Date: Mon, 27 Nov 2023 15:55:37 -0500 [thread overview]
Message-ID: <c46a6462-8263-455c-a6ea-1860020f5fab@sapience.com> (raw)
lenovo laptop boots fine under 6.7rc1 and older including 6.6.2 stable.
but not for 6.7 rc2 or rc3.
It has a intel 7260 (rev 3) wireless and :
cpu family : 6
model : 60
model name : Intel(R) Core(TM) i7-4800MQ CPU @ 2.70GHz
stepping : 3
microcode : 0x28
As of 6.7 rc2 / rc3 it crashes towards the end of boot bringing up
services - some parts of crash scrolled off the screen so I apologize
if this (manually transcribed) trace didn't catch the first part.
I did a git bisect between rc1 and rc2 but was unable to reproduce the
crash for some reason. (I did not do make clean between each bisects).
During the bisect it booted every time, but networking was not
functional for any of the bisects.
Hope it's okay to report even though git bisect didn't get anywhere.
Gene
This is the what I got from screen :
CS: 0010 DS: 000 ES: 0000 CR0: 0000000080050033
CR2: 00007f30cf49ba38 CR3: 000000025b620004 CR4: 00000000001706f0
Call Trace:
<IRQ>
? die_addr+0x36/0x90
? exc_general_protection+0x1c5/0x430
? asm_exc_gemeral_protection+0x26/0x30
? iwl_phy_db_set_section+0xd6/0x1f0 [iwlwifi]
? __kmem_cache_alloc_node+0x1d5/0x2b0
? iwl_phy_db_set_section+0xd6/0x1f0 [iwlwifi]
? iwl_phy_db_set_section+0xd6/0x1f0 [iwlwifi]
__kmalloc_node_track_caller+0x51/0x160
kmemdup+0x20/0x50
iwl_phy_db_set_section+0xd6/0x1f0 [iwlwifi]
iwl_wait_phy_db_entry+0x2f/0x40 [iwlmvm]
iwl_notification_wait+0xb0/0xf0 [iwlwifi]
iwl_mvm_rx_common+0x8e/0x320 [iwlwifi]
iwl_pcie_napi_poll+0x2d/0x150 [iwlwifi]
__napi_poll+0x2b/0x1c0
net_rx_action+0x2b4/0x320
__do_softirq+0xff/0x339
net_rx_action+0x2b4/0x320
__do_softirq.part.0+0x88/0xa0
</IRQ>
<TASK>
__local_bh_enable_ip+0x91/0xa0
iwl_pcie_irq_handler+0x58d/0xc40 [iwlwifi]
? __pfx_irq_thread_fn+0x10/0x10
irq_thread_fn+0x23/0x60
irq_thread+0xfe/0x60
? __pfx_irq_thread_dtor+0x10/0x10
? __pfx_irq_thread+0x10/0x10
kthread+0xfa/0x130
? pff_kthread+0x10/0x10
ret_from_fork+0x34/0x50
? __pfx_kthread+0x10/0x10
ret_from_fork_asm+0x1b/0x30
next reply other threads:[~2023-11-27 20:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-27 20:55 Genes Lists [this message]
2023-11-28 5:31 ` Bagas Sanjaya
2023-11-28 10:39 ` Genes Lists
2023-11-28 19:56 ` Genes Lists
2023-11-29 17:53 ` Genes Lists
2023-11-30 3:52 ` Bagas Sanjaya
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=c46a6462-8263-455c-a6ea-1860020f5fab@sapience.com \
--to=lists@sapience.com \
--cc=gregory.greenman@intel.com \
--cc=kvalo@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=tglx@linutronix.de \
/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
all inboxes | Powered by JetHome®