From: Sedat Dilek <sedat.dilek@googlemail.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
Subject: Re: linux-next: Tree for April 14 (Call-traces: RCU/ACPI/WQ related?)
Date: Thu, 14 Apr 2011 12:19:07 +0200 [thread overview]
Message-ID: <BANLkTimT9OhHLL5NaPOP30MdiMfmmmEcyQ@mail.gmail.com> (raw)
In-Reply-To: <BANLkTinq=mC9rs5R3U8FPLCp-GgCJris_g@mail.gmail.com>
On Thu, Apr 14, 2011 at 11:16 AM, Sedat Dilek
<sedat.dilek@googlemail.com> wrote:
> [ Adding CC to RCU maintainer (Hi Paul :-)) ]
>
> Helping me for now with (see also Documentation/RCU/stallwarn.txt):
>
> # cat /sys/module/rcutree/parameters/rcu_cpu_stall_suppress
> 0
>
> # echo "1" > /sys/module/rcutree/parameters/rcu_cpu_stall_suppress
>
> # cat /sys/module/rcutree/parameters/rcu_cpu_stall_suppress
> 1
>
> - Sedat -
>
That workaround helped till a system-freeze when generating a tarball
from my current kernel-tree.
I switched back to my yesterday's linux-next kernel.
- Sedat -
> On Thu, Apr 14, 2011 at 10:59 AM, Sedat Dilek
> <sedat.dilek@googlemail.com> wrote:
>> On Thu, Apr 14, 2011 at 7:01 AM, Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>>> Hi all,
>>>
>>> Changes since 20110413:
>>>
>>> Dropped tree: xen
>>>
>>> The gfs2 tree lost its conflict.
>>>
>>> The net tree lost its build failure.
>>>
>>> The wireless tree lost all but one conflict.
>>>
>>> The trivial tree lost its conflict.
>>>
>>> The tip tree gained a conflict against Linus' tree.
>>>
>>> The usb tree gained a conflict against the s5p tree.
>>>
>>> The staging tree lost its conflicts.
>>>
>>> ----------------------------------------------------------------------------
>>
>> Just a quick hello and an attached dmesg.
>> Yesterday's linux-next (next-20110413) with same kernel-config was OK.
>>
>> ( Also, I have seen a section-mismatch in x86 (IIRC mm) missing
>> __init... but that's another story. )
>>
>> - Sedat -
>>
>> P.S.: diff between today's and yesterday's kernel-config
>>
>> $ diff -uprN /boot/config-2.6.39-rc3-next20110413.2-686-small
>> /boot/config-2.6.39-rc3-next20110414.2-686-small
>> --- /boot/config-2.6.39-rc3-next20110413.2-686-small 2011-04-13
>> 12:32:09.000000000 +0200
>> +++ /boot/config-2.6.39-rc3-next20110414.2-686-small 2011-04-14
>> 10:23:25.000000000 +0200
>> @@ -1,7 +1,7 @@
>> #
>> # Automatically generated make config: don't edit
>> # Linux/x86 2.6.39-rc3 Kernel Configuration
>> -# Wed Apr 13 11:55:54 2011
>> +# Thu Apr 14 09:43:03 2011
>> #
>> # CONFIG_64BIT is not set
>> CONFIG_X86_32=y
>> @@ -2602,6 +2602,7 @@ CONFIG_USB_UHCI_HCD=m
>> #
>> # Enable Host or Gadget support to see Inventra options
>> #
>> +# CONFIG_USB_RENESAS_USBHS is not set
>>
>> #
>> # USB Device Class drivers
>>
>
next prev parent reply other threads:[~2011-04-14 10:19 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-14 8:59 linux-next: Tree for April 14 (Call-traces: RCU/ACPI/WQ related?) Sedat Dilek
2011-04-14 9:16 ` Sedat Dilek
2011-04-14 10:19 ` Sedat Dilek [this message]
2011-04-14 22:19 ` Sedat Dilek
2011-04-14 22:44 ` Paul E. McKenney
2011-04-21 5:08 ` Paul E. McKenney
2011-04-21 9:07 ` Sedat Dilek
2011-04-21 10:24 ` Sedat Dilek
2011-04-21 12:49 ` Sedat Dilek
2011-04-21 14:28 ` Paul E. McKenney
2011-04-21 14:47 ` Sedat Dilek
2011-04-22 0:50 ` Paul E. McKenney
2011-04-22 9:40 ` Sedat Dilek
2011-04-22 15:02 ` Paul E. McKenney
2011-04-22 17:36 ` Sedat Dilek
2011-04-23 21:05 ` Paul E. McKenney
2011-04-23 21:16 ` Sedat Dilek
2011-04-23 23:04 ` Sedat Dilek
2011-04-23 23:08 ` Sedat Dilek
2011-04-24 6:27 ` Paul E. McKenney
2011-04-24 9:36 ` Sedat Dilek
2011-04-24 16:43 ` Paul E. McKenney
2011-04-26 5:06 ` Paul E. McKenney
2011-04-26 11:45 ` Sedat Dilek
2011-04-26 12:42 ` Paul E. McKenney
2011-04-26 12:50 ` Sedat Dilek
2011-04-26 15:42 ` Paul E. McKenney
2011-04-26 10:06 ` Peter Zijlstra
2011-04-26 11:31 ` Paul E. McKenney
2011-04-26 19:44 ` Paul E. McKenney
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=BANLkTimT9OhHLL5NaPOP30MdiMfmmmEcyQ@mail.gmail.com \
--to=sedat.dilek@googlemail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=paulmck@linux.vnet.ibm.com \
--cc=sedat.dilek@gmail.com \
--cc=sfr@canb.auug.org.au \
/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;
as well as URLs for NNTP newsgroup(s).