From: Carsten Emde <C.Emde@osadl.org>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
RT <linux-rt-users@vger.kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
John Kacur <jkacur@redhat.com>,
Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Subject: Re: [ANNOUNCE] 3.6.11.1-rt32
Date: Sun, 14 Apr 2013 23:13:29 +0200 [thread overview]
Message-ID: <516B1BF9.3000002@osadl.org> (raw)
In-Reply-To: <1365529616.25498.75.camel@gandalf.local.home>
Hi Steven,
>>> I'm pleased to announce the 3.6.11.1-rt32 stable release.
>> Unfortunately, there is another compile error:
>> drivers/gpu/drm/i915/i915_gem.c: In function ‘i915_gem_wait_for_error’:
>> drivers/gpu/drm/i915/i915_gem.c:118:3: warning: passing argument 1 of
>> ‘rt_spin_lock’ from incompatible pointer type [enabled by default]
>> In file included from include/linux/spinlock.h:273:0,
>> from include/linux/wait.h:24,
>> from include/linux/fs.h:396,
>> from include/drm/drmP.h:47,
>> from drivers/gpu/drm/i915/i915_gem.c:28:
>> [..]
>> I would propose to adopt the mechanism that Sebastian introduced in
>> 3.8.4-rt2 (https://lkml.org/lkml/2013/3/26/600). The kernel compiles
>> and runs without any problem with the below patch on a system that
>> requires the i915 driver module.
> Thanks Carsten, I'll be updating this later today.
Thank you.
> BTW, did you get any core dumps from the work queue race that we've
> been seeing?
No, not yet. Originally, the farm systems did not use crashkernels by
default. I understood that it does no harm but could help in cases like
this one. Therefore, I've started to reconfigure all farm system with
crashkernels - starting with the two systems that had the work queue
race crashes. The kernel messages here (one is a 12-core, the other one
a 32-core box) look exactly like the one
(https://lkml.org/lkml/2013/3/18/325)
you saw in your 40-core machine (https://lkml.org/lkml/2013/3/18/430).
We'll need to wait for the next crash that will give us a core dump we
may then dissect.
-Carsten.
next prev parent reply other threads:[~2013-04-14 21:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-29 3:25 [ANNOUNCE] 3.6.11.1-rt32 Steven Rostedt
2013-04-02 1:37 ` Carsten Emde
2013-04-11 17:50 ` Steven Rostedt
2013-04-02 3:13 ` Carsten Emde
2013-04-09 17:46 ` Steven Rostedt
2013-04-14 21:13 ` Carsten Emde [this message]
2013-04-12 15:47 ` John Kacur
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=516B1BF9.3000002@osadl.org \
--to=c.emde@osadl.org \
--cc=bigeasy@linutronix.de \
--cc=jkacur@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
/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