From: Fengguang Wu <fengguang.wu@intel.com>
To: Jani Nikula <jani.nikula@linux.intel.com>
Cc: dri-devel@lists.freedesktop.org,
Yuanhan Liu <yuanhan.liu@intel.com>,
Jesse Barnes <jbarnes@virtuousgeek.org>,
Jet Chen <jet.chen@intel.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [drm] INFO: possible recursive locking detected
Date: Mon, 2 Jun 2014 16:28:49 +0800 [thread overview]
Message-ID: <20140602082849.GA10412@localhost> (raw)
In-Reply-To: <87mwdvhh4c.fsf@intel.com>
On Mon, Jun 02, 2014 at 11:04:35AM +0300, Jani Nikula wrote:
> On Fri, 30 May 2014, Jet Chen <jet.chen@intel.com> wrote:
> > Hi Jesse,
> >
> > 0day kernel testing robot got the below dmesg and the first bad commit is
> >
> > git://people.freedesktop.org/~jbarnes/linux async-fb-probe
>
> Do I understand correctly that this is only present in one of Jesse's
> personal branches? The distribution seems quite out of proportion...
Yes, it only happens in Jesse's async-fb-probe branch. Sorry for CC
more mailing lists than necessary!
Thanks,
Fengguang
WARNING: multiple messages have this Message-ID (diff)
From: Fengguang Wu <fengguang.wu@intel.com>
To: Jani Nikula <jani.nikula@linux.intel.com>
Cc: Jet Chen <jet.chen@intel.com>,
Jesse Barnes <jbarnes@virtuousgeek.org>,
Yuanhan Liu <yuanhan.liu@intel.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
dri-devel@lists.freedesktop.org
Subject: Re: [drm] INFO: possible recursive locking detected
Date: Mon, 2 Jun 2014 16:28:49 +0800 [thread overview]
Message-ID: <20140602082849.GA10412@localhost> (raw)
In-Reply-To: <87mwdvhh4c.fsf@intel.com>
On Mon, Jun 02, 2014 at 11:04:35AM +0300, Jani Nikula wrote:
> On Fri, 30 May 2014, Jet Chen <jet.chen@intel.com> wrote:
> > Hi Jesse,
> >
> > 0day kernel testing robot got the below dmesg and the first bad commit is
> >
> > git://people.freedesktop.org/~jbarnes/linux async-fb-probe
>
> Do I understand correctly that this is only present in one of Jesse's
> personal branches? The distribution seems quite out of proportion...
Yes, it only happens in Jesse's async-fb-probe branch. Sorry for CC
more mailing lists than necessary!
Thanks,
Fengguang
next prev parent reply other threads:[~2014-06-02 8:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-30 4:21 [drm] INFO: possible recursive locking detected Jet Chen
2014-06-02 8:04 ` Jani Nikula
2014-06-02 8:04 ` Jani Nikula
2014-06-02 8:28 ` Fengguang Wu [this message]
2014-06-02 8:28 ` Fengguang Wu
-- strict thread matches above, loose matches on Subject: below --
2014-06-02 6:53 [drm] INFO: task swapper:1 blocked for more than 120 seconds Fengguang Wu
2014-06-02 7:26 ` [drm] INFO: possible recursive locking detected Fengguang Wu
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=20140602082849.GA10412@localhost \
--to=fengguang.wu@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=jani.nikula@linux.intel.com \
--cc=jbarnes@virtuousgeek.org \
--cc=jet.chen@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=yuanhan.liu@intel.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 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.