Mirror of the lttng-dev mailing list
 help / color / mirror / Atom feed
From: vchitlur@cisco.com (Venkatesh Babu Chitlur Srinivasa (vchitlur))
Subject: [ltt-dev] lttng enabled SMP kernel soft locks up
Date: Thu, 23 Sep 2010 19:44:54 -0700	[thread overview]
Message-ID: <FC9331191C9BB74CACACE2CB467A78F8039BF4BA@xmb-sjc-23b.amer.cisco.com> (raw)
In-Reply-To: <20100923152932.GA10476@Krystal>

-----Original Message-----
From: Mathieu Desnoyers [mailto:compudj@krystal.dyndns.org]

> Can you provide your .config for both the kernel that works and the
> kernel that doesn't ?

  Please see the attached config files.

> Maybe some other kernel option got selected. Also,
> please try to disable the added LTTng options (diffing between the two
> config files will help you there) to see if it helps.

The difference between the working config (.config.2.6.35.4) and non-working config (.config.2.6.35.4.lttng) is shown below:

[root at arch-lab4 linux-2.6.35]# diff .config.2.6.35.4.lttng .config.2.6.35.4
4c4
< # Thu Sep 23 09:55:03 2010
---
> # Thu Sep 23 08:35:21 2010
129,133d128
< CONFIG_HAVE_GET_CYCLES=y
< CONFIG_HAVE_TRACE_CLOCK=y
< # CONFIG_HAVE_TRACE_CLOCK_GENERIC is not set
< # CONFIG_HAVE_TRACE_CLOCK_32_TO_64 is not set
< CONFIG_HAVE_UNSYNCHRONIZED_TSC=y
188d182
< CONFIG_MARKERS=y
215,217d208
< CONFIG_HAVE_IMMEDIATE=y
< CONFIG_IMMEDIATE=y
< CONFIG_HAVE_LTT_DUMP_TABLES=y

So I disabled all LTTNG config variables as follows and rebuilt the kernel. But even this one is having the same soft lockup problem.

[root at arch-lab4 linux-2.6.35]# diff .config .config.2.6.35.4
4c4
< # Thu Sep 23 09:55:03 2010
---
> # Thu Sep 23 08:35:21 2010
129,133d128
< # CONFIG_HAVE_GET_CYCLES is not set
< # CONFIG_HAVE_TRACE_CLOCK is not set
< # CONFIG_HAVE_TRACE_CLOCK_GENERIC is not set
< # CONFIG_HAVE_TRACE_CLOCK_32_TO_64 is not set
< # CONFIG_HAVE_UNSYNCHRONIZED_TSC is not set
188d182
< # CONFIG_MARKERS is not set
215,217d208
< # CONFIG_HAVE_IMMEDIATE is not set
< # CONFIG_IMMEDIATE is not set
< # CONFIG_HAVE_LTT_DUMP_TABLES is not set


> Another point is to make sure you reinstall your modules too (make
> modules_install) when you deploy the lttng-patched kernel, and make sure
> you re-create your initrd if you have one.


 I did reinstall the modules and also re-created the initrd. Still the same problem.

 The only way I was able to get LTTng patched kernel booted up without soft lockup is with UP kernel (I disabled the SMP in config menu).

Regards,
  VBabu


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.casi.polymtl.ca/pipermail/lttng-dev/attachments/20100923/975250ca/attachment-0003.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: .config.2.6.35.4
Type: application/octet-stream
Size: 110151 bytes
Desc: .config.2.6.35.4
URL: <http://lists.casi.polymtl.ca/pipermail/lttng-dev/attachments/20100923/975250ca/attachment-0006.obj>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: .config.2.6.35.4.lttng
Type: application/octet-stream
Size: 110416 bytes
Desc: .config.2.6.35.4.lttng
URL: <http://lists.casi.polymtl.ca/pipermail/lttng-dev/attachments/20100923/975250ca/attachment-0007.obj>


WARNING: multiple messages have this Message-ID
From: vchitlur@cisco.com (Venkatesh Babu Chitlur Srinivasa (vchitlur))
Subject: [ltt-dev] lttng enabled SMP kernel soft locks up
Date: Thu, 23 Sep 2010 19:44:54 -0700	[thread overview]
Message-ID: <FC9331191C9BB74CACACE2CB467A78F8039BF4BA@xmb-sjc-23b.amer.cisco.com> (raw)
Message-ID: <20100924024454.DulSSH3Xj-K3dcNBS4sRPJZtV6kQiHqFfTfBQPivuqI@z> (raw)
In-Reply-To: <20100923152932.GA10476@Krystal>

-----Original Message-----
From: Mathieu Desnoyers [mailto:compudj@krystal.dyndns.org]

> Can you provide your .config for both the kernel that works and the
> kernel that doesn't ?

  Please see the attached config files.

> Maybe some other kernel option got selected. Also,
> please try to disable the added LTTng options (diffing between the two
> config files will help you there) to see if it helps.

The difference between the working config (.config.2.6.35.4) and non-working config (.config.2.6.35.4.lttng) is shown below:

[root at arch-lab4 linux-2.6.35]# diff .config.2.6.35.4.lttng .config.2.6.35.4
4c4
< # Thu Sep 23 09:55:03 2010
---
> # Thu Sep 23 08:35:21 2010
129,133d128
< CONFIG_HAVE_GET_CYCLES=y
< CONFIG_HAVE_TRACE_CLOCK=y
< # CONFIG_HAVE_TRACE_CLOCK_GENERIC is not set
< # CONFIG_HAVE_TRACE_CLOCK_32_TO_64 is not set
< CONFIG_HAVE_UNSYNCHRONIZED_TSC=y
188d182
< CONFIG_MARKERS=y
215,217d208
< CONFIG_HAVE_IMMEDIATE=y
< CONFIG_IMMEDIATE=y
< CONFIG_HAVE_LTT_DUMP_TABLES=y

So I disabled all LTTNG config variables as follows and rebuilt the kernel. But even this one is having the same soft lockup problem.

[root at arch-lab4 linux-2.6.35]# diff .config .config.2.6.35.4
4c4
< # Thu Sep 23 09:55:03 2010
---
> # Thu Sep 23 08:35:21 2010
129,133d128
< # CONFIG_HAVE_GET_CYCLES is not set
< # CONFIG_HAVE_TRACE_CLOCK is not set
< # CONFIG_HAVE_TRACE_CLOCK_GENERIC is not set
< # CONFIG_HAVE_TRACE_CLOCK_32_TO_64 is not set
< # CONFIG_HAVE_UNSYNCHRONIZED_TSC is not set
188d182
< # CONFIG_MARKERS is not set
215,217d208
< # CONFIG_HAVE_IMMEDIATE is not set
< # CONFIG_IMMEDIATE is not set
< # CONFIG_HAVE_LTT_DUMP_TABLES is not set


> Another point is to make sure you reinstall your modules too (make
> modules_install) when you deploy the lttng-patched kernel, and make sure
> you re-create your initrd if you have one.


 I did reinstall the modules and also re-created the initrd. Still the same problem.

 The only way I was able to get LTTng patched kernel booted up without soft lockup is with UP kernel (I disabled the SMP in config menu).

Regards,
  VBabu


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.casi.polymtl.ca/pipermail/lttng-dev/attachments/20100923/975250ca/attachment-0002.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: .config.2.6.35.4
Type: application/octet-stream
Size: 110151 bytes
Desc: .config.2.6.35.4
URL: <http://lists.casi.polymtl.ca/pipermail/lttng-dev/attachments/20100923/975250ca/attachment-0004.obj>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: .config.2.6.35.4.lttng
Type: application/octet-stream
Size: 110416 bytes
Desc: .config.2.6.35.4.lttng
URL: <http://lists.casi.polymtl.ca/pipermail/lttng-dev/attachments/20100923/975250ca/attachment-0005.obj>


WARNING: multiple messages have this Message-ID
From: vchitlur@cisco.com (Venkatesh Babu Chitlur Srinivasa (vchitlur))
Subject: [ltt-dev] lttng enabled SMP kernel soft locks up
Date: Thu, 23 Sep 2010 19:44:54 -0700	[thread overview]
Message-ID: <FC9331191C9BB74CACACE2CB467A78F8039BF4BA@xmb-sjc-23b.amer.cisco.com> (raw)
Message-ID: <20100924024454.XWYAo58mfbr9k7JGwUdpJ4nlQKD6DT1FXtvrx8ODR_I@z> (raw)
In-Reply-To: <20100923152932.GA10476@Krystal>

-----Original Message-----
From: Mathieu Desnoyers [mailto:compudj@krystal.dyndns.org]

> Can you provide your .config for both the kernel that works and the
> kernel that doesn't ?

  Please see the attached config files.

> Maybe some other kernel option got selected. Also,
> please try to disable the added LTTng options (diffing between the two
> config files will help you there) to see if it helps.

The difference between the working config (.config.2.6.35.4) and non-working config (.config.2.6.35.4.lttng) is shown below:

[root at arch-lab4 linux-2.6.35]# diff .config.2.6.35.4.lttng .config.2.6.35.4
4c4
< # Thu Sep 23 09:55:03 2010
---
> # Thu Sep 23 08:35:21 2010
129,133d128
< CONFIG_HAVE_GET_CYCLES=y
< CONFIG_HAVE_TRACE_CLOCK=y
< # CONFIG_HAVE_TRACE_CLOCK_GENERIC is not set
< # CONFIG_HAVE_TRACE_CLOCK_32_TO_64 is not set
< CONFIG_HAVE_UNSYNCHRONIZED_TSC=y
188d182
< CONFIG_MARKERS=y
215,217d208
< CONFIG_HAVE_IMMEDIATE=y
< CONFIG_IMMEDIATE=y
< CONFIG_HAVE_LTT_DUMP_TABLES=y

So I disabled all LTTNG config variables as follows and rebuilt the kernel. But even this one is having the same soft lockup problem.

[root at arch-lab4 linux-2.6.35]# diff .config .config.2.6.35.4
4c4
< # Thu Sep 23 09:55:03 2010
---
> # Thu Sep 23 08:35:21 2010
129,133d128
< # CONFIG_HAVE_GET_CYCLES is not set
< # CONFIG_HAVE_TRACE_CLOCK is not set
< # CONFIG_HAVE_TRACE_CLOCK_GENERIC is not set
< # CONFIG_HAVE_TRACE_CLOCK_32_TO_64 is not set
< # CONFIG_HAVE_UNSYNCHRONIZED_TSC is not set
188d182
< # CONFIG_MARKERS is not set
215,217d208
< # CONFIG_HAVE_IMMEDIATE is not set
< # CONFIG_IMMEDIATE is not set
< # CONFIG_HAVE_LTT_DUMP_TABLES is not set


> Another point is to make sure you reinstall your modules too (make
> modules_install) when you deploy the lttng-patched kernel, and make sure
> you re-create your initrd if you have one.


 I did reinstall the modules and also re-created the initrd. Still the same problem.

 The only way I was able to get LTTng patched kernel booted up without soft lockup is with UP kernel (I disabled the SMP in config menu).

Regards,
  VBabu


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.casi.polymtl.ca/pipermail/ltt-dev/attachments/20100923/975250ca/attachment-0001.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: .config.2.6.35.4
Type: application/octet-stream
Size: 110151 bytes
Desc: .config.2.6.35.4
URL: <http://lists.casi.polymtl.ca/pipermail/ltt-dev/attachments/20100923/975250ca/attachment-0002.obj>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: .config.2.6.35.4.lttng
Type: application/octet-stream
Size: 110416 bytes
Desc: .config.2.6.35.4.lttng
URL: <http://lists.casi.polymtl.ca/pipermail/ltt-dev/attachments/20100923/975250ca/attachment-0003.obj>


  reply	other threads:[~2010-09-24  2:44 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-21 20:02 Venkatesh Babu Chitlur Srinivasa (vchitlur)
2010-09-21 20:02 ` Venkatesh Babu Chitlur Srinivasa (vchitlur)
2010-09-21 20:02 ` Venkatesh Babu Chitlur Srinivasa (vchitlur)
2010-09-23 15:29 ` Mathieu Desnoyers
2010-09-24  2:44   ` Venkatesh Babu Chitlur Srinivasa (vchitlur) [this message]
2010-09-24  2:44     ` Venkatesh Babu Chitlur Srinivasa (vchitlur)
2010-09-24  2:44     ` Venkatesh Babu Chitlur Srinivasa (vchitlur)

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=FC9331191C9BB74CACACE2CB467A78F8039BF4BA@xmb-sjc-23b.amer.cisco.com \
    --to=vchitlur@cisco.com \
    /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