Bug 1398767

Summary: [abrt] NMI watchdog: BUG: soft lockup - CPU#3 stuck for 23s! [modprobe:2252]
Product: [Fedora] Fedora Reporter: pbruso
Component: kernelAssignee: Kernel Maintainer List <kernel-maint>
Status: CLOSED NOTABUG QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: rawhideCC: cz172638, gansalmon, ichavero, itamar, jonathan, kernel-maint, madhu.chinakonda, mchehab, pbruso
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/5dbba8dd02df651fa68339731228db95773f57c3
Whiteboard: abrt_hash:a99f51c21be74185807b03217180d62a1477cec8;
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-08-31 00:59:22 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
File: dmesg none

Description pbruso 2016-11-25 21:29:56 UTC 
Description of problem:
Tried to boot live media but hangs with "soft lockup" error.  Add modprobe.blacklist=atp870u to boot command line and
the system boots sucessfully but my SCSI card is not enabled.  Run modprobe atp870u in terminal of the booted system
and the "soft lockup" error occurs.  The atp870u kernel module worked fine up through Fedora 23.

Additional info:
reporter:       libreport-2.8.0
NMI watchdog: BUG: soft lockup - CPU#3 stuck for 23s! [modprobe:2252]
Modules linked in: atp870u(+) udf fuse ip6t_REJECT nf_reject_ipv6 ip6t_rpfilter xt_conntrack ip_set nfnetlink ebtable_broute bridge ebtable_nat ip6table_security ip6table_mangle ip6table_raw ip6table_nat nf_conntrack_ipv6 nf_defrag_ipv6 nf_nat_ipv6 iptable_security iptable_mangle iptable_raw iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack ebtable_filter ebtables ip6table_filter ip6_tables amdkfd arc4 rtl8187 amd_iommu_v2 snd_hda_codec_hdmi radeon snd_hda_intel snd_hda_codec mac80211 snd_ctxfi snd_hda_core coretemp kvm_intel snd_hwdep i2c_algo_bit cfg80211 snd_seq snd_seq_device ttm iTCO_wdt eeprom_93cx6 gpio_ich iTCO_vendor_support kvm rfkill snd_pcm drm_kms_helper irqbypass drm snd_timer snd soundcore i2c_i801 i2c_smbus lpc_ich shpchp asus_atk0110 acpi_cpufreq
 tpm_tis tpm_tis_core tpm nfsd auth_rpcgss nfs_acl lockd grace nls_utf8 isofs squashfs ata_generic pata_acpi serio_raw firewire_ohci r8169 8021q mii garp firewire_core stp llc mrp crc_itu_t sky2 pata_jmicron fjes sunrpc scsi_transport_iscsi loop
CPU: 3 PID: 2252 Comm: modprobe Not tainted 4.8.6-300.fc25.x86_64 #1
Hardware name: System manufacturer P5K3 Deluxe/P5K3 Deluxe, BIOS 1206    04/16/2009
task: ffff95b180a41d80 task.stack: ffff95b1dc2d8000
RIP: 0010:[<ffffffffb73f37b0>]  [<ffffffffb73f37b0>] delay_tsc+0x40/0x60
RSP: 0018:ffff95b1dc2db9e8  EFLAGS: 00000206
RAX: 0000012b1001cb27 RBX: ffff95b1e63127c8 RCX: 0000000000000003
RDX: 0000012b00000000 RSI: 0000012b10005edd RDI: 00000000002ddc2c
RBP: ffff95b1dc2db9e8 R08: 0000000000000003 R09: 0000000000000005
R10: 0000000000000000 R11: 0000000000000417 R12: 0000000000000004
R13: ffff95b1e63127c8 R14: 00000000000000b2 R15: ffff95b1e6312000
FS:  00007f124327c5c0(0000) GS:ffff95b1efd80000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007fab10b999c8 CR3: 00000001c0ac5000 CR4: 00000000000406e0
Stack:
 ffff95b1dc2db9f8 ffffffffb73f3707 ffff95b1dc2dba10 ffffffffc085c4d6
 ffff95b1e5e3a000 ffff95b1dc2dbae8 ffffffffc085d1f6 0000000000000202
 ffff95b1e6312e90 ffff95b1e6312818 ffff95b1e6312958 ffff95b1e63127c8
Call Trace:
 [<ffffffffb73f3707>] __const_udelay+0x27/0x30
 [<ffffffffc085c4d6>] atp_set_host_id+0x36/0x70 [atp870u]
 [<ffffffffc085d1f6>] atp870u_probe+0x596/0xdf6 [atp870u]
 [<ffffffffb74393b5>] local_pci_probe+0x45/0xa0
 [<ffffffffb743a803>] pci_device_probe+0x103/0x150
 [<ffffffffb752e633>] driver_probe_device+0x223/0x430
 [<ffffffffb752e91f>] __driver_attach+0xdf/0xf0
 [<ffffffffb752e840>] ? driver_probe_device+0x430/0x430
 [<ffffffffb752bfbc>] bus_for_each_dev+0x6c/0xc0
 [<ffffffffb752dd3e>] driver_attach+0x1e/0x20
 [<ffffffffb752d750>] bus_add_driver+0x170/0x270
 [<ffffffffc0015000>] ? 0xffffffffc0015000
 [<ffffffffb752f240>] driver_register+0x60/0xe0
 [<ffffffffc0015000>] ? 0xffffffffc0015000
 [<ffffffffb7438d1c>] __pci_register_driver+0x4c/0x50
 [<ffffffffc001501e>] atp870u_driver_init+0x1e/0x1000 [atp870u]
 [<ffffffffb7002190>] do_one_initcall+0x50/0x180
 [<ffffffffb72264a9>] ? kmem_cache_alloc_trace+0x159/0x1b0
 [<ffffffffb71b69a6>] ? do_init_module+0x27/0x1ef
 [<ffffffffb71b69de>] do_init_module+0x5f/0x1ef
 [<ffffffffb712ce80>] load_module+0x2170/0x29d0
 [<ffffffffb7129ba0>] ? __symbol_put+0x60/0x60
 [<ffffffffb712d853>] SYSC_init_module+0x173/0x190
 [<ffffffffb712d98e>] SyS_init_module+0xe/0x10
 [<ffffffffb7802572>] entry_SYSCALL_64_fastpath+0x1a/0xa4
Code: 31 48 c1 e2 20 48 89 d6 48 09 c6 0f ae e8 0f 31 48 c1 e2 20 48 09 d0 48 89 c1 48 29 f1 48 39 cf 76 19 f3 90 65 8b 0d 78 69 c1 48 <41> 39 c8 74 db 48 29 c6 41 89 c8 48 01 f7 eb c1 5d c3 0f 1f 40
Comment 1 pbruso 2016-11-25 21:29:59 UTC 
Created attachment 1224462 [details]
File: dmesg
Comment 2 Laura Abbott 2017-01-17 01:17:57 UTC 
*********** MASS BUG UPDATE **************
We apologize for the inconvenience.  There is a large number of bugs to go through and several of them have gone stale.  Due to this, we are doing a mass bug update across all of the Fedora 25 kernel bugs.
 
Fedora 25 has now been rebased to 4.9.3-200.fc25.  Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel.
 
If you have moved on to Fedora 26, and are still experiencing this issue, please change the version to Fedora 26.
 
If you experience different issues, please open a new bug report for those.
Comment 3 pbruso 2017-02-06 22:44:05 UTC 
This bug still exists in Fedora 26.
Comment 4 pbruso 2018-08-31 00:59:22 UTC 
This problem only occurs when loading the module and no devices are yet connected on the SCSI bus.  Prior to Fedora 24 the kernel would continue gracefully in such a case.  The module works normal and properly when devices are connected and powered.