From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Authentication-Results: lists.ozlabs.org; spf=pass (mailfrom) smtp.mailfrom=atos.net (client-ip=193.56.114.164; helo=smtppost.atos.net; envelope-from=maheswari.a@atos.net; receiver=) Authentication-Results: lists.ozlabs.org; dmarc=none (p=none dis=none) header.from=atos.net Received: from smtppost.atos.net (smtppost.atos.net [193.56.114.164]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by lists.ozlabs.org (Postfix) with ESMTPS id 43BzRy046TzDrfW for ; Sun, 9 Dec 2018 06:10:01 +1100 (AEDT) Received: from mail2-ext.my-it-solutions.net (mail2-ext.my-it-solutions.net) by smarthost1.atos.net with smtp (TLS: TLSv1/SSLv3,256bits,ECDHE-RSA-AES256-GCM-SHA384) id 6269_1511_e225a17f_189b_469f_bf06_2c658cca3e42; Sat, 08 Dec 2018 20:09:56 +0100 Received: from mail1-int.my-it-solutions.net ([10.92.32.11]) by mail2-ext.my-it-solutions.net (8.15.2/8.15.2) with ESMTPS id wB8J9tF9011923 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK) for ; Sat, 8 Dec 2018 20:09:55 +0100 Received: from DEERLM99ETXMSX.ww931.my-it-solutions.net ([10.86.142.46]) by mail1-int.my-it-solutions.net (8.15.2/8.15.2) with ESMTPS id wB8J9tpP029855 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=FAIL) for ; Sat, 8 Dec 2018 20:09:55 +0100 Received: from DEFTHW99ETRMSX.ww931.my-it-solutions.net (10.86.142.99) by DEERLM99ETXMSX.ww931.my-it-solutions.net (10.86.142.46) with Microsoft SMTP Server (TLS) id 14.3.408.0; Sat, 8 Dec 2018 20:09:55 +0100 Received: from EUR01-HE1-obe.outbound.protection.outlook.com (10.86.142.137) by hybridsmtp.it-solutions.atos.net (10.86.142.99) with Microsoft SMTP Server (TLS) id 14.3.408.0; Sat, 8 Dec 2018 20:09:51 +0100 Received: from DB7PR02MB4393.eurprd02.prod.outlook.com (20.177.195.218) by DB7PR02MB3900.eurprd02.prod.outlook.com (20.176.237.205) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1404.20; Sat, 8 Dec 2018 19:09:44 +0000 Received: from DB7PR02MB4393.eurprd02.prod.outlook.com ([fe80::d8e4:2dfd:19f5:1b93]) by DB7PR02MB4393.eurprd02.prod.outlook.com ([fe80::d8e4:2dfd:19f5:1b93%4]) with mapi id 15.20.1404.023; Sat, 8 Dec 2018 19:09:43 +0000 From: "A, Maheswari" To: OpenBMC Maillist Subject: Help: Host powered ON and after seconds Host Power OFF script is started. Thread-Topic: Help: Host powered ON and after seconds Host Power OFF script is started. Thread-Index: AdSPKSqgkpWJpBkuRN+sti0pzv2s3A== Date: Sat, 8 Dec 2018 19:09:43 +0000 Message-ID: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: authentication-results: spf=none (sender IP is ) smtp.mailfrom=maheswari.a@atos.net; x-originating-ip: [103.43.203.195] x-ms-publictraffictype: Email x-microsoft-exchange-diagnostics: 1; DB7PR02MB3900; 6:+DqnfVnQS+wNe2zsGSsuZbEWOaOlsa/uxk4sZJHMQWn19BtyWJ3HQynn5wNskM77IOgcyahLyEABx6L3NEPbMJhfyC6okDtMMXFnXol916jeguiR6jZnQrteGxxVlJcxaz9Jor7Qzg84iY25HCiSd9joc7Pq0IliRHxNJlRXDtXgISkWW0LxUCy9UuKr6bm7UHcvG3RUScLqeZGC32bPVHrO883NpM7jJMSB98bkKv6re7OxCUIMY3ZeO7Zwj4FDyTX+zGx2o+dbVi7/+0TY6b8UHKPqAFM0tauh6jJkockMP5WGWvzeqzMZY2vFpKPtye5uwUfCMDStuz/tuhcAA3aS+0v60HUXtHd40wCJikbFJFF9B4nGkjwec/oT6N5yjOmDO+8HMiLZxH1aNC+E6k/Np0sS8aBr5bEWCFZJ57L/OZI9OlM3R32vkx2GsiySs7b+/yGTsWA/HIckeoV+5w==; 5:v3hDkUEcuLJgT2DMnz65lUYhbgcNKj1/Th8P9sLuPmSIqKm5264T+7kiX3RpsZqXN5TtTPD8Wb1BYf4wXdErIyD9tZPTxcu4sWAxc3eY4naYQ8Xc3s+nB9UB5HJYCEiJxY6AZPkaCrIR2SlKVcat2lmu0AifZjVPUmbo90ZPsio=; 7:A90+BPK2VrkZ+R+eN7NGu87mtSBg/FAdDDvT4SqEz4edX02Sp9knFCxtismfKkZel/AfWaXJaWIYY8B7+pGdQaa1i35bcXjGt+3mJPWfhohZ+EgCdT+vgylGMOJartPhQn+b9F3w3wK/FJPQ9Mqfpg== x-ms-exchange-antispam-srfa-diagnostics: SOS; x-ms-office365-filtering-correlation-id: 7588ef88-06ea-4e77-6600-08d65d40b66a x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390098)(7020095)(4652040)(8989299)(5600074)(711020)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(2017052603328)(7153060)(7193020); SRVR:DB7PR02MB3900; x-ms-traffictypediagnostic: DB7PR02MB3900: x-microsoft-antispam-prvs: x-ms-exchange-senderadcheck: 1 x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(8211001083)(6040522)(2401047)(5005006)(8121501046)(10201501046)(3231455)(999002)(944501520)(52105112)(93006095)(93001095)(3002001)(148016)(149066)(150057)(6041310)(20161123562045)(201703131423095)(201702281528075)(20161123555045)(201703061421075)(201703061406153)(20161123560045)(20161123558120)(20161123564045)(201708071742011)(7699051)(76991095); SRVR:DB7PR02MB3900; BCL:0; PCL:0; RULEID:; SRVR:DB7PR02MB3900; x-forefront-prvs: 0880FB6EC1 x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(346002)(136003)(376002)(39860400002)(366004)(396003)(199004)(189003)(14454004)(68736007)(106356001)(105586002)(97736004)(486006)(6116002)(790700001)(3846002)(7696005)(86362001)(26005)(14444005)(256004)(6506007)(102836004)(6916009)(99286004)(6436002)(316002)(476003)(551934003)(54896002)(53936002)(55016002)(9326002)(25786009)(6306002)(9686003)(7736002)(33656002)(81156014)(8676002)(71190400001)(71200400001)(81166006)(5660300001)(186003)(478600001)(74316002)(66066001)(8936002)(2906002)(460985005); DIR:OUT; SFP:1102; SCL:1; SRVR:DB7PR02MB3900; H:DB7PR02MB4393.eurprd02.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX:1; received-spf: None (protection.outlook.com: atos.net does not designate permitted sender hosts) x-microsoft-antispam-message-info: YfP9WWG2HpBVPqVmQue3u+v1kGcmBmceu8RJeWmGf0DlTfck+amIuvBreHfjX56xRuhc/q2j2T9JzmXXtkcgJ7x8vf+qTUdygU5DxrLUDpKBIbXS42sDBq+O2Z3FnzaaZvH1S6r7diJ3CJe5XaWPhCeqbhPkXliZAynKaff63Ll2P/23mcQBTB+ceFY9M2o8c4fLgAxZif0pGWSsTq5hPdvmD6zvWtu21Xrmx4VHfYcIzDMYVD39u6OdQn+dK+/b6h5CxpN/kwhBqK5t1DTjop3o3nGvM8GGnrMa02+8cQgq3ft6vVInfjm2CuQPtf+2J98GVVfhh5wiCj9LkiMJpvoZxsAnXTh62GmuGnbXJUk= spamdiagnosticoutput: 1:99 spamdiagnosticmetadata: NSPM Content-Type: multipart/alternative; boundary="_000_DB7PR02MB43933CFF8148D4AEA9328D3E92AB0DB7PR02MB4393eurp_" MIME-Version: 1.0 X-MS-Exchange-CrossTenant-Network-Message-Id: 7588ef88-06ea-4e77-6600-08d65d40b66a X-MS-Exchange-CrossTenant-originalarrivaltime: 08 Dec 2018 19:09:43.7839 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Hosted X-MS-Exchange-CrossTenant-id: 33440fc6-b7c7-412c-bb73-0e70b0198d5a X-MS-Exchange-Transport-CrossTenantHeadersStamped: DB7PR02MB3900 X-OriginatorOrg: atos.net X-BeenThere: openbmc@lists.ozlabs.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Development list for OpenBMC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 08 Dec 2018 19:10:08 -0000 --_000_DB7PR02MB43933CFF8148D4AEA9328D3E92AB0DB7PR02MB4393eurp_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hi, I had basic understanding of below processes and its dependency in openbmc. button_power.exe power_control.exe ( without timeout and interval for GPIO Pgood pin polling= ). Chassis_control.py System_manager.py ( which is again depends on skeleton/configs/Platform.py. In my case I have created one dummy = Platform.py by referring existing openbmc platform). Issues is observed in below two scenarios: 1. Whenever I am pressing power button. 2. Whenever sending REST command to Power On the Host. (RequestedHostTra= nsition --> ON). Issue: In both scenarios I am able to power on the host, But We are getting wa= tchdog Timeout and, after some time target is reached quiesce state, and Host power OFF scri= pt is also started Running. (Linked host-poweroff script in obmc-host-stop.target.requires ). Also phosphor-state-manager is always getting Host state as HOST_STATE_= QUIESCE_TGT in sysStateChange() functionality. 1. What are all the process is responsible to send Host state signal as = quiesce to phosphor-host-state-manager. ?. 2. If phosphor-watchdog or system_manager is responsible.Please let us k= now clear view of understanding. 3. In our platform, We are not using BOOTCOUNT sensor concept as initial= phase. Please refer short journal log: Nov 09 05:38:04 HOSTNAME phosphor-watchdog[1338]: Timer Expired Nov 09 05:38:04 HOSTNAME systemd-journald[640]: Forwarding to syslog missed= 11 messages. Nov 09 05:38:04 HOSTNAME phosphor-watchdog[1338]: watchdog: Timed out Nov 09 05:38:04 HOSTNAMEi systemd[1]: Created slice system-op\x2docc\x2ddis= able.slice. Nov 09 05:38:04 HOSTNAME systemd[1]: Detaching egress BPF program from cgro= up failed: Invalid argument Nov 09 05:38:04 HOSTNAME systemd[1]: Starting OpenPOWER OCC Active Disable.= .. Nov 09 05:38:04 HOSTNAME systemd[1]: Reached target Quiesce Target. Nov 09 05:38:04 HOSTNAME systemd[1]: Stopping Phosphor poweron watchdog... Nov 09 05:38:04 HOSTNAME systemd[1]: Stopped Phosphor poweron watchdog. Nov 09 05:38:04 HOSTNAME phosphor-host-state-manager[1215]: Auto reboot ena= bled, rebooting Nov 09 05:38:04 HOSTNAME phosphor-host-state-manager[1215]: Beginning reboo= t... Nov 09 05:38:04 HOSTNAME phosphor-host-state-manager[1215]: Host State tran= saction request Thanks Maheswari A --_000_DB7PR02MB43933CFF8148D4AEA9328D3E92AB0DB7PR02MB4393eurp_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Hi,

 

I had basic understanding of below processes and its= dependency in openbmc.

 

button_power.exe

power_control.exe ( without timeout and interval for= GPIO Pgood pin polling ).

Chassis_control.py

System_manager.py ( which is again depends on skeleton/configs/Platform.py.

          &n= bsp;            = ;            &n= bsp;   In my case I have created one dummy Platform.py by referri= ng existing openbmc platform).

 

Issues is observed in below two scenarios:

  1. Whenever I am pressing power button.
  2. Whenever sending REST command to Power On the Host. (= RequestedHostTransition à ON).
  3. =

 

Issue:

  

    In both scenarios I am able = to power on the host, But We are getting watchdog Timeout and,

   after some time target is reached quies= ce state, and Host power OFF script is also started Running.

   (Linked host-poweroff script in &n= bsp;obmc-host-stop.target.requires ).  

   

    Also phosphor-state-manager = is always getting Host state as HOST_STATE_QUIESCE_TGT in sysStateChange() functionality.=

   

 

  1. What = are all the process is responsible to send Host state signal as quiesce to = phosphor-host-state-manager. ?.
  2. If ph= osphor-watchdog or system_manager is responsible.Please let us know clear v= iew of understanding.
  3. In ou= r platform, We are not using BOOTCOUNT sensor concept as initial phase.

 

Please refer short journal log:

Nov 09 05:38:04 HOSTNAME phosphor-watchdog[1338]: Ti= mer Expired

Nov 09 05:38:04 HOSTNAME systemd-journald[640]: Forw= arding to syslog missed 11 messages.

Nov 09 05:38:04 HOSTNAME phosphor-watchdog[1338]: wa= tchdog: Timed out

Nov 09 05:38:04 HOSTNAMEi systemd[1]: Created slice = system-op\x2docc\x2ddisable.slice.

Nov 09 05:38:04 HOSTNAME systemd[1]: Detaching egres= s BPF program from cgroup failed: Invalid argument

Nov 09 05:38:04 HOSTNAME systemd[1]: Starting OpenPO= WER OCC Active Disable...

Nov 09 05:38:04 HOSTNAME systemd[1]: Reached target = Quiesce Target.

Nov 09 05:38:04 HOSTNAME systemd[1]: Stopping Phosph= or poweron watchdog...

Nov 09 05:38:04 HOSTNAME systemd[1]: Stopped Phospho= r poweron watchdog.

Nov 09 05:38:04 HOSTNAME phosphor-host-state-manager= [1215]: Auto reboot enabled, rebooting

Nov 09 05:38:04 HOSTNAME phosphor-host-state-manager= [1215]: Beginning reboot...

Nov 09 05:38:04 HOSTNAME phosphor-host-state-manager= [1215]: Host State transaction request

 

Thanks

Maheswari A

--_000_DB7PR02MB43933CFF8148D4AEA9328D3E92AB0DB7PR02MB4393eurp_--