-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
hard lockup detected when vm starts with ftrace on #22
Comments
------- Comment From bssrikanth@in.ibm.com 2017-11-02 05:21:08 EDT------- |
------- Comment From satheera@in.ibm.com 2017-11-24 02:10:54 EDT------- I am able to hit with latest devel(4.14) 4.14.0-3.dev.git68b4afb.el7.centos.ppc64le Steps to reproduce:
cat ftrace.shmkdir -p /debug
Message from syslogd@localhost at Nov 24 02:03:07 ... error: Domain is already active in shutdown error: Failed to destroy domain vm1 Regards, |
------- Comment From naveen.n.rao@in.ibm.com 2017-11-24 05:33:38 EDT------- Thanks for confirming. It is not clear from your message if you tried by reverting the patch I mentioned above. There also seems to have been many watchdog fixes that went into v4.15, so it will be good to test with those for more reliable traces. I can take a look if you can spare the test machine for a day next week? |
------- Comment From gowrishankar.m@in.ibm.com 2017-11-02 04:10:28 EDT------- ------- Comment From bssrikanth@in.ibm.com 2017-11-02 04:21:08 EDT------- ------- Comment From brsriniv@in.ibm.com 2017-11-02 05:54:46 EDT------- Can we please get sosreport from the host and the guest? There is not really enough data here to proceed on this. ------- Comment From bssrikanth@in.ibm.com 2017-11-02 05:57:23 EDT------- From what I heard from Gowri and description of this issue.. hard lockup happens while booting guest with ftrace.. ------- Comment From bssrikanth@in.ibm.com 2017-11-02 06:00:02 EDT------- Forgot to mention: @gowri sosreport running as-is on hostos has issues... instead run ------- Comment From gowrishankar.m@in.ibm.com 2017-11-02 09:01:42 EDT------- Btw I am not quite sure how it would be possible to run sosreport as I could not execute any command once hard lockup detected and I find current ssh login as well as ipmi console login stops responding momentarily. @srikant, hope your team would be able to assist providing any other needed info as server is not with me (I spotted it while debugging some other bug). ------- Comment From bssrikanth@in.ibm.com 2017-11-02 09:09:30 EDT------- Sure Gowri. Since we cannot run sosreport after hitting issue, we will try to reset host and capture logs.. @satheesh would help here in getting required logs.. ------- Comment From brsriniv@in.ibm.com 2017-11-21 23:43:36 EDT------- Any updates on this? ------- Comment From srikar.dronamraju@in.ibm.com 2017-11-22 00:53:30 EDT------- Naveen, ------- Comment From naveen.n.rao@in.ibm.com 2017-11-23 11:38:01 EDT------- From the report above, this looks to be a ppc64le host. The patch above is for BE, so it is probably not applicable in this case. I am not able to conclude anything from the provided traces. Satheesh, ------- Comment From satheera@in.ibm.com 2017-11-24 01:10:54 EDT------- ------- Comment From satheera@in.ibm.com 2017-11-24 01:14:09 EDT------- ------- Comment From naveen.n.rao@in.ibm.com 2017-11-24 04:33:38 EDT------- ------- Comment From satheera@in.ibm.com 2017-11-28 08:12:02 EDT------- I had tried with latest hostos devel branch, yet to tryout with your suggestion of reverting that commit, planning to try out now, will update once have the results. Regards, ------- Comment From satheera@in.ibm.com 2017-11-28 08:51:21 EDT------- I am able to hit hardlockup even with reverting commit 6b847d7, [ 226.151759] virbr0: topology change detected, propagating Regards, ------- Comment From nevdull@us.ibm.com 2018-01-10 19:58:24 EDT------- ------- Comment From nevdull@us.ibm.com 2018-01-30 18:04:09 EDT------- It sounds like from comment 7 that we need a host running ftrace and then when we start a guest we will see the host develop problems. Correct? Can I have access to a host that I can use to investigate this further? ltc-test-ci1.aus.stglabs.ibm.com no longer seems available. ------- Comment From naveen.n.rao@in.ibm.com 2018-01-31 03:11:34 EDT------- ------- Comment From nevdull@us.ibm.com 2018-02-01 16:54:18 EDT------- ------- Comment From nevdull@us.ibm.com 2018-02-22 17:23:49 EDT------- |
------- Comment From naveen.n.rao@in.ibm.com 2018-03-12 04:51:36 EDT------- |
------- Comment From seg@us.ibm.com 2018-08-31 13:32:05 EDT------- |
cde:info Mirrored with LTC bug https://bugzilla.linux.ibm.com/show_bug.cgi?id=160778 </cde:info>
When I try to start a vm on host (4.14.0-1.rc4.dev.gitb27fc5c.el7.centos.ppc64le) with ftrace on (using function tracer), I see watchdog kickoff for cpu hard lockup as in below trace.
Earlier, I have enabled function tracing as in below script:
The text was updated successfully, but these errors were encountered: