linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Sachin Sant <sachinp@linux.vnet.ibm.com>
To: linuxppc-dev@lists.ozlabs.org,
	Linux-Next Mailing List <linux-next@vger.kernel.org>
Subject: [PowerPC/next-20191114] Soft lockups post kernel boot on POWER9
Date: Fri, 15 Nov 2019 15:36:52 +0530	[thread overview]
Message-ID: <93F39201-82FD-4A66-B6D2-9A715DEA698F@linux.vnet.ibm.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 2762 bytes --]

Latest next kernel ( 8466d23e6e 5.4.0-rc7-next-20191114) boot on a POWER9 running
in non virtualized mode produces following soft lockups. Eventually the machine crawls
and has to be power cycled.

[   80.207155] watchdog: BUG: soft lockup - CPU#104 stuck for 22s! [tuned:4828]
[   80.207184] Modules linked in: tun bridge stp llc nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c ip6_tables nft_compat ip_set rfkill nf_tables nfnetlink kvm_hv i2c_dev kvm sunrpc ses opal_prd enclosure ipmi_powernv scsi_transport_sas ipmi_devintf leds_powernv sg ipmi_msghandler powernv_op_panel uio_pdrv_genirq uio ibmpowernv sch_fq_codel ip_tables ext4 mbcache jbd2 sd_mod ipr tg3 libata ptp pps_core
[   80.207246] CPU: 104 PID: 4828 Comm: tuned Not tainted 5.4.0-rc7-next-20191114-autotest #1
[   80.207255] NIP:  c0000000002dfb08 LR: c000000000921d3c CTR: 0000000000007ee8
[   80.207265] REGS: c00020070eff32e0 TRAP: 0901   Not tainted  (5.4.0-rc7-next-20191114-autotest)
[   80.207274] MSR:  900000000280b033 <SF,HV,VEC,VSX,EE,FP,ME,IR,DR,RI,LE>  CR: 42428282  XER: 20040000
[   80.207288] CFAR: c0000000002dfb24 IRQMASK: 0 
[   80.207288] GPR00: c000000000921d30 c00020070eff3570 c0000000015da800 c0000007ee132080 
[   80.207288] GPR04: c00020070eff3458 c00020070eff3458 0000000000000000 000020072b8f0000 
[   80.207288] GPR08: 5deadbeef0000100 0000000000000002 0000000000000000 000020072b8f0000 
[   80.207288] GPR12: 0000000000008000 c0002007ff6b6480 
[   80.207330] NIP [c0000000002dfb08] irq_work_sync+0x18/0x40
[   80.207340] LR [c000000000921d3c] cpufreq_dbs_governor_stop+0x8c/0xd0
[   80.207347] Call Trace:
[   80.207353] [c00020070eff3570] [c000000000921d30] cpufreq_dbs_governor_stop+0x80/0xd0 (unreliable)
[   80.207365] [c00020070eff35b0] [c000000000918614] cpufreq_stop_governor+0x64/0xb0
[   80.207375] [c00020070eff3620] [c00000000091c188] cpufreq_set_policy+0x268/0x470
[   80.207385] [c00020070eff36a0] [c00000000091c788] store_scaling_governor+0xa8/0x210
[   80.207394] [c00020070eff3ca0] [c000000000918384] store+0xf4/0x120
[   80.207405] [c00020070eff3cf0] [c0000000005148d8] sysfs_kf_write+0x68/0x80
[   80.207414] [c00020070eff3d10] [c000000000513d20] kernfs_fop_write+0x100/0x290
[   80.207425] [c00020070eff3d60] [c00000000041e7cc] __vfs_write+0x3c/0x70
[   80.207434] [c00020070eff3d80] [c00000000042214c] vfs_write+0xcc/0x240
[   80.207443] [c00020070eff3dd0] [c00000000042252c] ksys_write+0x7c/0x140
[   80.207454] [c00020070eff3e20] [c00000000000b278] system_call+0x5c/0x68
[   80.207461] Instruction dump:
[   80.207467] 4d820020 4bffcf7c 0fe00000 4e800020 00000000 00000000 81230000 71290002 
[   80.207480] 4d820020 60000000 7c210b78 7c421378 <81230000> 71290002 4d820020 7c210b78 

Boot log attached.

[-- Attachment #2: next-20191114.log --]
[-- Type: application/octet-stream, Size: 120388 bytes --]

                 reply	other threads:[~2019-11-15 10:09 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=93F39201-82FD-4A66-B6D2-9A715DEA698F@linux.vnet.ibm.com \
    --to=sachinp@linux.vnet.ibm.com \
    --cc=linux-next@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.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;
as well as URLs for NNTP newsgroup(s).