linux-kernel - Re: crash with 6.7 rc2 and rc3

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <022c67aa-b90a-4756-8725-5f7fba7dc780@sapience.com>
Date:   Tue, 28 Nov 2023 14:56:37 -0500
From:   Genes Lists <lists@...ience.com>
To:     Bagas Sanjaya <bagasdotme@...il.com>, tglx@...utronix.de,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        gregory.greenman@...el.com, kvalo@...nel.org,
        Linux Wireless <linux-wireless@...r.kernel.org>
Cc:     Linux Regressions <regressions@...ts.linux.dev>
Subject: Re: crash with 6.7 rc2 and rc3

On 11/28/23 05:39, Genes Lists wrote:
> On 11/28/23 00:31, Bagas Sanjaya wrote:
>> On Mon, Nov 27, 2023 at 03:55:37PM -0500, Genes Lists wrote:
>>>
>>> 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
>>
>> Do you have any full system logs that can be attached?
>>
>> Anyway, thanks for the regression report. I'm adding it to regzbot:
>>
>> #regzbot ^introduced: v6.7-rc1..v6.7-rc2
>>
> 
> journalctl -k for 6.6.2 and the last bisect
> 
> gene
> 

6.6.3 crashes for me same way - also an intel NUC also crashes with 
6.6.3 buty works on 6.6.2. Will take a while before I get additional 
info on the latter box.

gene