Got a panic after install latest 4.7-rc2 kernel and reboot: Part of the console log: ... [ OK ] Started udev Kernel Device Manager. Starting udev Coldplug all Devices... Mounting Configuration File System... [ 15.885956] Fusion MPT base driver 3.04.20 [ 15.913658] Copyright (c) 1999-2008 LSI Corporation [ 15.943390] bnx2: QLogic bnx2 Gigabit Ethernet Driver v2.2.6 (January 29, 2014) [ OK [ 15.987978] bnx2 0000:04:00.0 eth0: Broadcom NetXtreme II BCM5709 1000Base-SX (C0) PCI Express found at mem de000000, IRQ 16, node addr 00:21:5e:86:18:14 ] Mounted Config[ 16.078465] [drm] Initialized drm 1.1.0 20060810 uration File Sys[ 16.078879] bnx2 0000:04:00.1 eth1: Broadcom NetXtreme II BCM5709 1000Base-SX (C0) PCI Express found at mem e0000000, IRQ 16, node addr 00:21:5e:86:18:16 tem. [ 16.079896] bnx2 0000:04:00.0 enp4s0f0: renamed from eth0 [ 16.240019] Fusion MPT SAS Host driver 3.04.20 [ 16.240391] qla2xxx [0000:00:00.0]-0005: : QLogic Fibre Channel HBA Driver: 8.07.00.33-k. [ OK [ 16.315861] qla2xxx [0000:06:02.0]-001d: : Found an ISP2422 irq 24 iobase 0xffffc90001b76000. ] Started udev C[ 16.315941] mptbase: ioc0: Initiating bringup oldplug all Devi[ 16.410194] bnx2 0000:04:00.1 enp4s0f1: renamed from eth1 ces. [ 16.593067] ioc0: LSISAS1064E B1: Capabilities={Initiator} [ 16.744222] scsi host0: qla2xxx [ 16.763495] qla2xxx [0000:06:02.0]-00fb:0: QLogic QMI2472 - PCI-X Combo 4Gb Fibre Channel Mezzanine HBA. [ 16.820244] qla2xxx [0000:06:02.0]-00fc:0: ISP2422: PCI-X Mode 1 (133 MHz) @ 0000:06:02.0 hdma+ host#=0 fw=7.03.00 (9496). [ 16.886545] qla2xxx [0000:06:02.1]-001d: : Found an ISP2422 irq 25 iobase 0xffffc90001b6e000. [ 16.887890] [drm] radeon kernel modesetting enabled. Startin[ 16.967904] [drm] initializing kernel modesetting (RV100 0x1002:0x515E 0x1014:0x0305 0x02). g Show Plymouth Boot Screen... Starting dracut initqueue hook... [ [[ 17.073049] [drm] register mmio base: 0xF3FF0000 [ 17.080626] BUG: unable to handle kernel NULL pointer dereference at 0000000000000050 [ 17.080653] IP: [<ffffffffa019f309>] qla24xx_process_response_queue+0x49/0x4b0 [qla2xxx] [ 17.080654] PGD 0 [ 17.080655] Oops: 0000 [#1] SMP [ 17.080664] Modules linked in: radeon(+) i2c_algo_bit drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops ttm mptsas(+) qla2xxx(+) scsi_transport_sas mptscsih drm scsi_transport_fc bnx2 serio_raw mptbase i2c_core dm_mirror dm_region_hash dm_log dm_multipath dm_mod [ 17.080666] CPU: 6 PID: 0 Comm: swapper/6 Not tainted 4.7.0-rc2 #1 [ 17.080667] Hardware name: IBM BladeCenter LS22 -[79013SG]-/Server Blade, BIOS -[L8E164AUS-1.07]- 05/25/2011 [ 17.080668] task: ffff8802269f5200 ti: ffff880226a08000 task.ti: ffff880226a08000 [ 17.080681] RIP: 0010:[<ffffffffa019f309>] [<ffffffffa019f309>] qla24xx_process_response_queue+0x49/0x4b0 [qla2xxx] [ 17.080681] RSP: 0018:ffff880227d83da0 EFLAGS: 00010002 [ 17.080682] RAX: 0000000000000000 RBX: 0000000000000032 RCX: 00000000ffffffff [ 17.080683] RDX: 0000000000000006 RSI: ffff88041fc5a000 RDI: ffff8800c97d47d8 [ 17.080684] RBP: ffff880227d83e20 R08: ffff880226a08000 R09: ffff880226a0be90 [ 17.080684] R10: 00000000fffb9ff1 R11: 0000000000000005 R12: ffff88041fc5a000 [ 17.080685] R13: ffff8800c97d47d8 R14: ffff880222280000 R15: 0000000000018013 [ 17.080686] FS: 0000000000000000(0000) GS:ffff880227d80000(0000) knlGS:0000000000000000 [ 17.080687] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 17.080687] CR2: 0000000000000050 CR3: 0000000001c06000 CR4: 00000000000006e0 [ 17.080688] Stack: [ 17.080689] 00000000000000c2 ffff880227d83dc8 ffffffff81418365 ffffffff82249a80 [ 17.080691] ffff8804204c81a8 ffff880227d83dd8 ffffffff81437ea1 ffff880227d83e00 [ 17.080692] ffffffff814409a7 ffffffff82249a80 db371812f4d3708d 0000000000000032 [ 17.080692] Call Trace: [ 17.080698] <IRQ> [ 17.080698] [<ffffffff81418365>] ? tty_wakeup+0x35/0x70 [ 17.080700] [<ffffffff81437ea1>] ? uart_write_wakeup+0x21/0x30 [ 17.080703] [<ffffffff814409a7>] ? serial8250_tx_chars+0x1b7/0x270 [ 17.080714] [<ffffffffa01a1a81>] qla24xx_intr_handler+0x101/0x300 [qla2xxx] [ 17.080715] [<ffffffff8143be5e>] ? serial8250_interrupt+0x5e/0xd0 [ 17.080718] [<ffffffff810e2ea1>] handle_irq_event_percpu+0x41/0x1c0 [ 17.080719] [<ffffffff810e305b>] handle_irq_event+0x3b/0x60 [ 17.080721] [<ffffffff810e63af>] handle_fasteoi_irq+0x8f/0x140 [ 17.080724] [<ffffffff8102fdeb>] handle_irq+0xab/0x130 [ 17.080726] [<ffffffff810aa52a>] ? atomic_notifier_call_chain+0x1a/0x20 [ 17.080728] [<ffffffff816c8f4d>] do_IRQ+0x4d/0xd0 [ 17.080730] [<ffffffff816c6e0c>] common_interrupt+0x8c/0x8c [ 17.080733] <EOI> [ 17.080733] [<ffffffff81064626>] ? native_safe_halt+0x6/0x10 [ 17.080735] [<ffffffff81037a7e>] default_idle+0x1e/0xd0 [ 17.080736] [<ffffffff8103821f>] arch_cpu_idle+0xf/0x20 [ 17.080737] [<ffffffff810cd803>] default_idle_call+0x33/0x40 [ 17.080739] [<ffffffff810cdb19>] cpu_startup_entry+0x309/0x3a0 [ 17.080741] [<ffffffff81050d4c>] start_secondary+0x15c/0x1a0 [ 17.080754] Code: 00 00 65 48 8b 04 25 28 00 00 00 48 89 45 d0 31 c0 48 8b 47 58 a8 02 0f 84 c5 00 00 00 48 8b 46 50 49 89 f4 65 8b 15 27 ae e6 5f <39> 50 50 74 11 89 50 50 48 8b 46 50 8b 40 50 41 89 86 60 8b 00 [ 17.080765] RIP [<ffffffffa019f309>] qla24xx_process_response_queue+0x49/0x4b0 [qla2xxx] [ 17.080765] RSP <ffff880227d83da0> [ 17.080765] CR2: 0000000000000050 [ 17.080770] ---[ end trace 79a625515cd8f625 ]--- [ 17.080771] Kernel panic - not syncing: Fatal exception in interrupt [ 17.108583] Kernel Offset: disabled [ 19.053674] ---[ end Kernel panic - not syncing: Fatal exception in interrupt [-- MARK -- Sun Jun 12 10:25:00 2016] Connection closed by foreign host. blade: ERROR: console lost [-- Console down -- Sun Jun 12 10:25:23 2016] [-- Console up -- Sun Jun 12 10:25:23 2016]
Host info: IBM LS22 Blade Quad-Core AMD Opteron(tm) Processor 2384 16384 MB memory, 468 GB disk space
I wonder if this really is a bug in serial/tty (it's filed as one). The qla24xx stuff in the debug output to me indicated that it might be something in that driver, hence it might be wise to get its developers involed. Or what do you think Russel? Sincerely, your regression tracker (who feels a a bit unsure how to proceed with this bug) for Linux 4.7 (http://bit.ly/28JRmJo )
Created attachment 220991 [details] candidate fix Hi can you try if above patch makes any difference?
FWIW, I'd guess this might be the fix for the problem http://thread.gmane.org/gmane.linux.kernel/2257008/
(In reply to Thorsten Leemhuis from comment #4) > FWIW, I'd guess this might be the fix for the problem > http://thread.gmane.org/gmane.linux.kernel/2257008/ yes I can't reproduce it on latest 4.9-rc2 move bug status to RESOLVED