All of lore.kernel.org
 help / color / mirror / Atom feed
From: Han Pingtian <hanpt@linux.vnet.ibm.com>
To: linuxppc-dev@lists.ozlabs.org
Subject: Re: [RFC] powerpc/pseries: Increase busy loop in pseries_cpu_die
Date: Tue, 7 Feb 2017 09:05:58 +0800	[thread overview]
Message-ID: <20170207010558.GA5493@localhost.localdomain> (raw)
In-Reply-To: <1486407496-12151-1-git-send-email-bauerman@linux.vnet.ibm.com>

On Mon, Feb 06, 2017 at 04:58:16PM -0200, Thiago Jung Bauermann wrote:
> This was reproduced in v4.10-rc6 as well, but I don't have a crash log
> handy for that version right now. Sorry.
> 
This is the crash log of v4.10:

roselp4 login: [  505.097727] sysrq: SysRq : Changing Loglevel
[  505.097743] sysrq: Loglevel set to 9
[  595.183727] iommu: Removing device 0021:01:00.0 from group 0
[  605.213053] pci_bus 0021:01: busn_res: [bus 01-ff] is released
[  605.213204] rpadlpar_io: slot PHB 33 removed
[  624.623544] min_free_kbytes is not updated to 16826 because user defined value 547628 is preferred
[  647.574039] cpu 152 (hwid 152) Ready to die...
[  647.803624] cpu 153 (hwid 153) Ready to die...
[  647.813371] cpu 154 (hwid 154) Ready to die...
[  647.823646] cpu 155 (hwid 155) Ready to die...
[  647.833371] cpu 156 (hwid 156) Ready to die...
[  647.843392] cpu 157 (hwid 157) Ready to die...
[  647.853368] cpu 158 (hwid 158) Ready to die...
[  647.863358] cpu 159 (hwid 159) Ready to die...
[  648.233756] cpu 144 (hwid 144) Ready to die...
[  648.383417] cpu 145 (hwid 145) Ready to die...
[  648.383488] cpu 146 (hwid 146) Ready to die...
[  648.383551] cpu 147 (hwid 147) Ready to die...
[  648.402845] cpu 148 (hwid 148) Ready to die...
[  648.403329] cpu 149 (hwid 149) Ready to die...
[  648.403384] cpu 150 (hwid 150) Ready to die...
[  648.413398] cpu 151 (hwid 151) Ready to die...
[  648.583466] cpu 136 (hwid 136) Ready to die...
[  648.833672] cpu 137 (hwid 137) Ready to die...
[  648.843481] cpu 138 (hwid 138) Ready to die...
[  648.843541] cpu 139 (hwid 139) Ready to die...
[  648.843589] cpu 140 (hwid 140) Ready to die...
[  648.843635] cpu 141 (hwid 141) Ready to die...
[  648.853426] cpu 142 (hwid 142) Ready to die...
[  648.863105] Querying DEAD? cpu 142 (142) shows 2
[  648.863697] cpu 143 (hwid 143) Ready to die...
[  649.013280] cpu 128 (hwid 128) Ready to die...
[  649.253575] cpu 129 (hwid 129) Ready to die...
[  649.253634] cpu 130 (hwid 130) Ready to die...
[  649.253689] cpu 131 (hwid 131) Ready to die...
[  649.253741] cpu 132 (hwid 132) Ready to die...
[  649.253793] cpu 133 (hwid 133) Ready to die...
[  649.253836] cpu 134 (hwid 134) Ready to die...
[  649.253885] cpu 135 (hwid 135) Ready to die...
[  649.353116] cpu 120 (hwid 120) Ready to die...
[  649.553776] cpu 121 (hwid 121) Ready to die...
[  649.563626] Querying DEAD? cpu 122 (122) shows 2
cpu 0x7b: Vector: 400 (Instruction Access) at [c000000007bc7d40]
    pc: f81f0070801f0078
    lr: f81f0070801f0078
    sp: ec20d28
   msr: 8000000042801000
  current = 0xc000000474838600
  paca    = 0xc000000007b65300   softe: 0        irq_happened: 0x01
    pid   = 0, comm = swapper/123
Linux version 4.10.0-rc6 (bauermann@u1604le) (gcc version 5.4.0 20160609 (Ubuntu/IBM 5.4.0-6ubuntu1~16.04.4) ) #1 SMP Fri Feb 3 18:55:20 BRST 2017
WARNING: exception is not recoverable, can't continue
enter ? for help
SP (ec20d28) is in userspace
7b:mon> e
cpu 0x7b: Vector: 400 (Instruction Access) at [c000000007bc7d40]
    pc: f81f0070801f0078
    lr: f81f0070801f0078
    sp: ec20d28
   msr: 8000000042801000
  current = 0xc000000474838600
  paca    = 0xc000000007b65300   softe: 0        irq_happened: 0x01
    pid   = 0, comm = swapper/123
Linux version 4.10.0-rc6 (bauermann@u1604le) (gcc version 5.4.0 20160609 (Ubuntu/IBM 5.4.0-6ubuntu1~16.04.4) ) #1 SMP Fri Feb 3 18:55:20 BRST 2017
7b:mon> 

  reply	other threads:[~2017-02-07  1:06 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-06 18:58 [RFC] powerpc/pseries: Increase busy loop in pseries_cpu_die Thiago Jung Bauermann
2017-02-07  1:05 ` Han Pingtian [this message]
2017-02-07  2:10 ` Michael Ellerman
2017-02-07  2:56 ` Balbir Singh
2017-02-07 15:32   ` Thiago Jung Bauermann
2017-02-08  2:59     ` Michael Ellerman

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=20170207010558.GA5493@localhost.localdomain \
    --to=hanpt@linux.vnet.ibm.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.