All of lore.kernel.org
 help / color / mirror / Atom feed
diff for duplicates of <20170728190349.GM3730@linux.vnet.ibm.com>

diff --git a/a/1.txt b/N1/1.txt
index a36f0ee..47c303c 100644
--- a/a/1.txt
+++ b/N1/1.txt
@@ -30,16 +30,15 @@ On Fri, Jul 28, 2017 at 06:27:05PM +0100, Jonathan Cameron wrote:
 > > 
 > > So I look for "rcu_preempt" timer events and find these:
 > > 
-> > rcu_preempt-9     [019] ....   827.579114: timer_init: timer=ffff8017d5fc7da0
-> > rcu_preempt-9     [019] d..1   827.579115: timer_start: timer=ffff8017d5fc7da0 function=process_timeout 
+> > rcu_preempt-9     [019] ....   827.579114: timer_init: timerÿff8017d5fc7da0
+> > rcu_preempt-9     [019] d..1   827.579115: timer_start: timerÿff8017d5fc7da0 function=process_timeout 
 > > 
 > > Next look for "ffff8017d5fc7da0" and I don't find anything else.
 > It does show up off the bottom of what would fit in pastebin...
 > 
->      rcu_preempt-9     [001] d..1   837.681077: timer_cancel: timer=ffff8017d5fc7da0
->      rcu_preempt-9     [001] ....   837.681086: timer_init: timer=ffff8017d5fc7da0
->      rcu_preempt-9     [001] d..1   837.681087: timer_start: timer=ffff8017d5fc7da0 function=process_timeout expires=4295101298 [timeout=1] cpu=1 idx=0 flags=
-
+>      rcu_preempt-9     [001] d..1   837.681077: timer_cancel: timerÿff8017d5fc7da0
+>      rcu_preempt-9     [001] ....   837.681086: timer_init: timerÿff8017d5fc7da0
+>      rcu_preempt-9     [001] d..1   837.681087: timer_start: timerÿff8017d5fc7da0 function=process_timeout expiresB95101298 [timeout=1] cpu=1 idx=0 flags
 Odd.  I would expect an expiration...  And ten seconds is way longer
 than the requested one jiffy!
 
@@ -58,7 +57,7 @@ than the requested one jiffy!
 > There is an errata work around for the timers on this particular board.
 > I'm only vaguely aware of it, so may be unconnected.
 > 
-> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/clocksource/arm_arch_timer.c?h=v4.13-rc2&id=bb42ca47401010fc02901b5e8f79e40a26f208cb
+> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/clocksource/arm_arch_timer.c?h=v4.13-rc2&id»42ca47401010fc02901b5e8f79e40a26f208cb
 > 
 > Seems unlikely though! + we've not yet seen it on the other chips that
 > errata effects (not that that means much).
diff --git a/a/content_digest b/N1/content_digest
index 4027099..6e06758 100644
--- a/a/content_digest
+++ b/N1/content_digest
@@ -10,19 +10,8 @@
  "ref\020170728182053.000072aa@huawei.com\0"
  "From\0Paul E. McKenney <paulmck@linux.vnet.ibm.com>\0"
  "Subject\0Re: RCU lockup issues when CONFIG_SOFTLOCKUP_DETECTOR=n - any one else seeing this?\0"
- "Date\0Fri, 28 Jul 2017 12:03:50 -0700\0"
- "To\0Jonathan Cameron <Jonathan.Cameron@huawei.com>\0"
- "Cc\0dzickus@redhat.com"
-  sfr@canb.auug.org.au
-  linuxarm@huawei.com
-  Nicholas Piggin <npiggin@gmail.com>
-  abdhalee@linux.vnet.ibm.com
-  sparclinux@vger.kernel.org
-  akpm@linux-foundation.org
-  linuxppc-dev@lists.ozlabs.org
-  David Miller <davem@davemloft.net>
-  linux-arm-kernel@lists.infradead.org
- " tglx@linutronix.de\0"
+ "Date\0Fri, 28 Jul 2017 19:03:50 +0000\0"
+ "To\0linux-arm-kernel@lists.infradead.org\0"
  "\00:1\0"
  "b\0"
  "On Fri, Jul 28, 2017 at 06:27:05PM +0100, Jonathan Cameron wrote:\n"
@@ -57,16 +46,15 @@
  "> > \n"
  "> > So I look for \"rcu_preempt\" timer events and find these:\n"
  "> > \n"
- "> > rcu_preempt-9     [019] ....   827.579114: timer_init: timer=ffff8017d5fc7da0\n"
- "> > rcu_preempt-9     [019] d..1   827.579115: timer_start: timer=ffff8017d5fc7da0 function=process_timeout \n"
+ "> > rcu_preempt-9     [019] ....   827.579114: timer_init: timer\303\277ff8017d5fc7da0\n"
+ "> > rcu_preempt-9     [019] d..1   827.579115: timer_start: timer\303\277ff8017d5fc7da0 function=process_timeout \n"
  "> > \n"
  "> > Next look for \"ffff8017d5fc7da0\" and I don't find anything else.\n"
  "> It does show up off the bottom of what would fit in pastebin...\n"
  "> \n"
- ">      rcu_preempt-9     [001] d..1   837.681077: timer_cancel: timer=ffff8017d5fc7da0\n"
- ">      rcu_preempt-9     [001] ....   837.681086: timer_init: timer=ffff8017d5fc7da0\n"
- ">      rcu_preempt-9     [001] d..1   837.681087: timer_start: timer=ffff8017d5fc7da0 function=process_timeout expires=4295101298 [timeout=1] cpu=1 idx=0 flags=\n"
- "\n"
+ ">      rcu_preempt-9     [001] d..1   837.681077: timer_cancel: timer\303\277ff8017d5fc7da0\n"
+ ">      rcu_preempt-9     [001] ....   837.681086: timer_init: timer\303\277ff8017d5fc7da0\n"
+ ">      rcu_preempt-9     [001] d..1   837.681087: timer_start: timer\303\277ff8017d5fc7da0 function=process_timeout expiresB95101298 [timeout=1] cpu=1 idx=0 flags\n"
  "Odd.  I would expect an expiration...  And ten seconds is way longer\n"
  "than the requested one jiffy!\n"
  "\n"
@@ -85,7 +73,7 @@
  "> There is an errata work around for the timers on this particular board.\n"
  "> I'm only vaguely aware of it, so may be unconnected.\n"
  "> \n"
- "> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/clocksource/arm_arch_timer.c?h=v4.13-rc2&id=bb42ca47401010fc02901b5e8f79e40a26f208cb\n"
+ "> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/clocksource/arm_arch_timer.c?h=v4.13-rc2&id\302\27342ca47401010fc02901b5e8f79e40a26f208cb\n"
  "> \n"
  "> Seems unlikely though! + we've not yet seen it on the other chips that\n"
  "> errata effects (not that that means much).\n"
@@ -103,4 +91,4 @@
  "> > \n"
  >
 
-1d675d8a1570aadf88ad7ab775650a509b56d37e3ea3454bb050a78e38a1ea6f
+e7490fb264341cc1207abf9201ffdeb0d73a6989091f15f378d61418ca9b10f6

diff --git a/a/content_digest b/N2/content_digest
index 4027099..92a3dd4 100644
--- a/a/content_digest
+++ b/N2/content_digest
@@ -8,21 +8,10 @@
  "ref\020170728142403.0000122b@huawei.com\0"
  "ref\020170728165529.GF3730@linux.vnet.ibm.com\0"
  "ref\020170728182053.000072aa@huawei.com\0"
- "From\0Paul E. McKenney <paulmck@linux.vnet.ibm.com>\0"
- "Subject\0Re: RCU lockup issues when CONFIG_SOFTLOCKUP_DETECTOR=n - any one else seeing this?\0"
+ "From\0paulmck@linux.vnet.ibm.com (Paul E. McKenney)\0"
+ "Subject\0RCU lockup issues when CONFIG_SOFTLOCKUP_DETECTOR=n - any one else seeing this?\0"
  "Date\0Fri, 28 Jul 2017 12:03:50 -0700\0"
- "To\0Jonathan Cameron <Jonathan.Cameron@huawei.com>\0"
- "Cc\0dzickus@redhat.com"
-  sfr@canb.auug.org.au
-  linuxarm@huawei.com
-  Nicholas Piggin <npiggin@gmail.com>
-  abdhalee@linux.vnet.ibm.com
-  sparclinux@vger.kernel.org
-  akpm@linux-foundation.org
-  linuxppc-dev@lists.ozlabs.org
-  David Miller <davem@davemloft.net>
-  linux-arm-kernel@lists.infradead.org
- " tglx@linutronix.de\0"
+ "To\0linux-arm-kernel@lists.infradead.org\0"
  "\00:1\0"
  "b\0"
  "On Fri, Jul 28, 2017 at 06:27:05PM +0100, Jonathan Cameron wrote:\n"
@@ -103,4 +92,4 @@
  "> > \n"
  >
 
-1d675d8a1570aadf88ad7ab775650a509b56d37e3ea3454bb050a78e38a1ea6f
+aafc3f027afae8460399bb3c8ab85e97e11fe5d09ec9f73addfcbc88381fa9c9

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.