From: Sedat Dilek <sedat.dilek@gmail.com>
To: Daniel Vetter <daniel.vetter@ffwll.ch>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
x86@kernel.org, Ingo Molnar <mingo@redhat.com>,
Thomas Gleixner <tglx@linutronix.de>,
Paul McKenney <paulmck@linux.vnet.ibm.com>,
Paul McKenney <paul.mckenney@linaro.org>,
DRI <dri-devel@lists.freedesktop.org>,
Dave Airlie <airlied@redhat.com>
Subject: Re: linux-next: Tree for Apr 18 [ call-trace: drm | x86 | smp | rcu related? ]
Date: Fri, 19 Apr 2013 18:43:20 +0200 [thread overview]
Message-ID: <CA+icZUVE-ikxEp65bUHMp0WEPX_MDbA06ykzeSxygJv=9f45ig@mail.gmail.com> (raw)
In-Reply-To: <CA+icZUXjTGSG+tejOAFgXr8EpKd7dL=-W41ha_-0N=roAxN3eg@mail.gmail.com>
On Fri, Apr 19, 2013 at 12:27 PM, Sedat Dilek <sedat.dilek@gmail.com> wrote:
> On Fri, Apr 19, 2013 at 12:19 PM, Sedat Dilek <sedat.dilek@gmail.com> wrote:
>> On Thu, Apr 18, 2013 at 11:59 PM, Sedat Dilek <sedat.dilek@gmail.com> wrote:
>>> On Thu, Apr 18, 2013 at 9:48 PM, Daniel Vetter <daniel.vetter@ffwll.ch> wrote:
>>>> On Thu, Apr 18, 2013 at 3:05 PM, Sedat Dilek <sedat.dilek@gmail.com> wrote:
>>>>> On Thu, Apr 18, 2013 at 10:28 AM, Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>>>>>> Hi all,
>>>>>>
>>>>>> Changes since 20130417:
>>>>>>
>>>>>> New Trees: rpmsg (actually added yesterday)
>>>>>> ppc-temp (replacing powerpc for this week)
>>>>>>
>>>>>> The ceph tree gained a conflict against Linus' tree.
>>>>>>
>>>>>> The net-next tree gained a conflict against the infiniband tree.
>>>>>>
>>>>>> The usb tree gained a build failure so I used the version from
>>>>>> next-20130417.
>>>>>>
>>>>>> I added two merge fix patches after the gen-gpio tree.
>>>>>>
>>>>>> The ppc-temp tree gained a conflict against the metag tree.
>>>>>>
>>>>>> The akpm tree lost a patch that turned up elsewhere.
>>>>>>
>>>>>> ----------------------------------------------------------------------------
>>>>>>
>>>>>
>>>>> Not sure what the root-cause for this call-trace is (see screenshot).
>>>>>
>>>>> This is reproducible when running my kernel build-script (4 parallel-make-jobs).
>>>>>
>>>>> Any hints welcome!
>>>>
>>>> The panic handlers in our modeset code are pretty decent fubar - they
>>>> take mutexes all over the place. So I think the backtrace you see
>>>> there is actually a secondary effect. I've looked into fixing this up,
>>>> but the issue is that drivers themselves have tons of state protected
>>>> with mutexes, which all potentially affects the panic handler. So I've
>>>> given up on that for now ...
>>>
>>> Thanks for taking care.
>>>
>>> On suspicion [1] I have reverted [2]... NOPE.
>>>
>>> - Sedat -
>>>
>>> [1] http://marc.info/?l=linux-kernel&m=136631921208895&w=2
>>> [2] http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=5a90d1a95356de7a32acb2e5309ac579a891af8f
>>>
>>
>> Hmmm, the issue seems to be gone with today's Linux-Next (next-20130419).
>> My kernel-build is still running with no call-trace...
>>
>
> NO, It's no good.
>
I tried to switch from SLUB to SLAB...
...and also from VIRT_CPU_ACCOUNTING_GEN to TICK_CPU_ACCOUNTING.
2x NOPE.
In one kernel-build I saw in my console...
semop(1): encountered an error: Identifier removed
...if this says sth. to you.
- Sedat -
- Sedat -
> - Sedat -
>
> [1] http://www.youtube.com/watch?v=LwicaralvS0
>
>> - Sedat -
>>
>>>> -Daniel
>>>> --
>>>> Daniel Vetter
>>>> Software Engineer, Intel Corporation
>>>> +41 (0) 79 365 57 48 - http://blog.ffwll.ch
next prev parent reply other threads:[~2013-04-19 16:43 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CA+icZUVWC+Rgd9wh4Z4CPZkEa9Pm2=2udnY5=UD1nnH0Wot1pQ@mail.gmail.com>
2013-04-18 19:48 ` linux-next: Tree for Apr 18 [ call-trace: drm | x86 | smp | rcu related? ] Daniel Vetter
2013-04-18 21:59 ` Sedat Dilek
2013-04-19 10:19 ` Sedat Dilek
[not found] ` <CA+icZUXjTGSG+tejOAFgXr8EpKd7dL=-W41ha_-0N=roAxN3eg@mail.gmail.com>
2013-04-19 16:43 ` Sedat Dilek [this message]
2013-04-19 18:53 ` Sedat Dilek
2013-04-19 19:19 ` Rik van Riel
2013-04-19 20:12 ` Davidlohr Bueso
[not found] ` <CA+icZUVjx7pDJWo3tGxX3ANXtiTP0_Q1YyOowANhn1wzcSgWaA@mail.gmail.com>
2013-04-19 21:24 ` Linus Torvalds
2013-04-19 21:39 ` Paul E. McKenney
2013-04-19 22:12 ` Sedat Dilek
2013-04-19 22:34 ` Sedat Dilek
2013-04-19 22:50 ` Linus Torvalds
2013-04-19 22:55 ` Sedat Dilek
2013-04-19 23:02 ` Linus Torvalds
2013-04-20 0:06 ` Sedat Dilek
2013-04-20 0:19 ` Sedat Dilek
2013-04-20 12:46 ` Sedat Dilek
2013-04-20 15:59 ` Rik van Riel
2013-04-20 17:04 ` Sedat Dilek
2013-04-20 20:00 ` Davidlohr Bueso
2013-04-20 21:03 ` Sedat Dilek
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='CA+icZUVE-ikxEp65bUHMp0WEPX_MDbA06ykzeSxygJv=9f45ig@mail.gmail.com' \
--to=sedat.dilek@gmail.com \
--cc=airlied@redhat.com \
--cc=daniel.vetter@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=paul.mckenney@linaro.org \
--cc=paulmck@linux.vnet.ibm.com \
--cc=sfr@canb.auug.org.au \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
/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).