ild0:342] child exiting.
Bailing main loop. Exit reason: UID changed.
[ 69.250950]
[ 69.251227] ==
[ 69.252022] [ INFO: possible circular locking dependency detected ]
[ 69.252715] 4.11.0-rc6-00240-gd215aab #1 Not tainte
[ 23.762311] ==
[ 23.763199] [ INFO: possible circular locking dependency detected ]
[ 23.764101] 4.11.0-rc6-00237-g6362ef3 #1 Not tainted
[ 23.764847] ---
[ 23.765822] trinity-main/352 is tr
18.172662]
[ 18.173782] ==
[ 18.177716] [ INFO: possible circular locking dependency detected ]
[ 18.181715] 4.8.0-rc5-00438-g7c14957 #1 Not tainted
[ 18.184921] ---
[ 18.188716] swap
; >
> > caused below changes:
> >
>
>
> >
> > [ 21.116124] ==========
> > [ 21.116124] [ INFO: possible circular locking dependency detected ]
> > [ 21.116127] 4.6.0-rc5-00302-g409ca71 #1 Not tainted
> > [ 21.11612
swapin in khugepaged")
>
> on test machine: vm-kbuild-1G: 2 threads qemu-system-x86_64 -enable-kvm -cpu
> Haswell,+smep,+smap with 1G memory
>
> caused below changes:
>
>
> [ 21.116124] ======
> [ 21.116124] [
: possible circular locking dependency detected ]
[ 17.687174] 4.5.0-rc6-1-gdd9a6fe #64 Not tainted
[ 17.688127] ---
[ 17.689216] bootlogd/2434 is trying to acquire lock:
[ 17.690167] ((&buf->work)){+.+...}, at: []
flu
15.345268] ==
[ 15.345268] ==
[ 15.346491] [ INFO: possible circular locking dependency detected ]
[ 15.346491] [ INFO: possible circular locking dependency detected ]
[ 15.347758] 4.5.0-rc3-00013-g681c3cb #2 Not tainted
[ 15.347
On Fri, 20 Mar 2015 16:37:12 +0800, Huang Ying
wrote:
> FYI, we noticed the below changes on
>
> git://git.kernel.org/pub/scm/linux/kernel/git/davem/net-next.git master
> commit baf606d9c9b12517e47e0d1370e8aa9f7323f210 ("ipv4,ipv6: grab rtnl
> before locking the socket")
>
...
> -> #0 (rtnl_mute
e:SYSC_perf_event_open | 0 | 7
> > > | 2 |
> > > | backtrace:SyS_perf_event_open | 0 | 7
> > > | 2 |
> > &g
cktrace:SyS_perf_event_open | 0 | 7
> >| 2 |
> > | backtrace:trace_create_cpu_file| 0 | 1
> >||
> > | backtrace:init_tracer_debugfs | 0 | 1
> > | |
> > | backtrace:tracer_init_debugfs |
|
> | backtrace:init_tracer_debugfs | 0 | 1
> ||
> | backtrace:tracer_init_debugfs | 0 | 1
> ||
> ++++----+
>
> [ 29.644027] CE: hpet increased min_delta_ns to 253
| 0 | 0
> | 1 |
> | backtrace:SyS_write | 0 | 0
> | 1 |
> +--+---++---+
>
> [5.0270
https://bugzilla.redhat.com/attachment.cgi?id=874823
poma
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org
During suspend-to-RAM, I see an info message below. Could anybody
advice how to debug this problem or anyone has experienced this
before? (ARM mach)
Thanks a lot for any help.
[ 172.637547] ==
[ 172.637555] [ INFO: possible circular
Miles Lane writes:
> [ 24.990076] [ INFO: possible circular locking dependency detected ]
> [ 24.990086] 3.11.0-rc6+ #154 Not tainted
> [ 24.990094] ---
> [ 24.990103] crda/1159 is trying to acquire lock:
> [ 24.99011
[ 24.990076] [ INFO: possible circular locking dependency detected ]
[ 24.990086] 3.11.0-rc6+ #154 Not tainted
[ 24.990094] ---
[ 24.990103] crda/1159 is trying to acquire lock:
[ 24.990111] (genl_mutex){+.+.+.}, at: []
genl_lock+0x12
gt;[ 23.245632] [ INFO: possible circular locking dependency detected ]
<4>[ 23.245635] 3.10.3-capigig #1 Tainted: GW
<4>[ 23.245637] ---
<4>[ 23.245639] swapper/0/0 is trying to acquire lock:
<4>[ 23.245666]
[ 130.287724] ==
[ 130.287732] [ INFO: possible circular locking dependency detected ]
[ 130.287742] 3.10.0-rc1-0.7-default+ #9 Not tainted
[ 130.287749] ---
[ 130.287758] trinity-child3
Hi Peter,
Le 07/03/2013 09:08, Peter Chen a écrit :
> On Wed, Mar 06, 2013 at 11:33:02AM +0100, Maxime Ripard wrote:
>> [2.149645] other info that might help us debug this:
>> [2.149645]
>> [2.157667] Possible unsafe locking scenario:
>> [2.157667]
>> [2.163598]CPU0
sts.infradead.org/pipermail/linux-arm-kernel/2013-February/151837.html
>
>
> [1.893905] ==============
> [1.900097] [ INFO: possible circular locking dependency detected
Hi Alexander,
Thanks for your reply.
Le 06/03/2013 14:43, Alexander Shishkin a écrit :
> On 6 March 2013 12:33, Maxime Ripard
> wrote:
>> Just noticed this in 3.9-rc1 on an iMX28 (ARM) board with a config
>> based on mxs_defconfig. I'm using the patchset "Add tested id
>> switch and vbus conn
On 6 March 2013 12:33, Maxime Ripard wrote:
> Hi,
>
> Just noticed this in 3.9-rc1 on an iMX28 (ARM) board with a config
> based on mxs_defconfig. I'm using the patchset "Add tested id switch
> and vbus connect detect support for Chipidea" from Peter Chen in its
> 10th version [1], rebased on top
==
[ 1.900097] [ INFO: possible circular locking dependency detected ]
[1.906381] 3.9.0-rc1-00024-g39231ac #475 Not tainted
[1.911441] ---
[1.917716] swapper/0 is trying to acquire lock:
[1.922341] (&(&ci->lock)->
lockdep-mess.patch
>
> Unfortunately the patches seem to be stuck there for now despite quite
> a few reports about this (including seemingly relevant background
> noise about hangs in distro bugzillas).
> -Daniel
> ----------
>
> [ 489.832113] [ INFO
despite quite
a few reports about this (including seemingly relevant background
noise about hangs in distro bugzillas).
-Daniel
--
[ 489.832113] [ INFO: possible circular locking dependency detected ]
[ 489.832115] 3.8.0-rc5 #99 Not tainted
[ 48
s/3.8.0-rc1/
FWIW, this is still present with 3.8.0-rc2.
C.
> [ 97.803049] ======
> [ 97.803051] [ INFO: possible circular locking dependency detected ]
> [ 97.803059] 3.8.0-rc1-dir
t suggesting that the mxs
> > frame buffer driver (drivers/video/mxsfb.c) is doing something bad?
> >
> > Shawn
> >
> > >
> > > [ 602.229899] ==
> > > [ 602.229
s doing something bad?
>
> Shawn
>
> >
> > [ 602.229899] ==============
> > [ 602.229905] [ INFO: possible circular locking dependency detected ]
> > [ 602.229926] 3.8.0-rc1-3-gde4ae7f #767 Not tainted
> > [ 602.229933]
patch daee779 (console: implement
lockdep support for console_lock). Is it suggesting that the mxs
frame buffer driver (drivers/video/mxsfb.c) is doing something bad?
Shawn
>
> [ 602.229899] ======
> [ 602.229905] [ INFO: possible circ
nature.de/bits/3.8.0-rc1/
>
> [ 97.803049] ==
> [ 97.803051] [ INFO: possible circular locking dependency detected ]
> [ 97.803059] 3.8.0-rc1-dirty #2 Not tainted
> [ 97.803060]
It seems that I'm running into the same locking issue. My setup is:
- i.MX28 (ARM)
- v3.8-rc1
- mxs_defconfig
Shawn
[ 602.229899] ==
[ 602.229905] [ INFO: possible circular locking dependency detected ]
[ 602.229926] 3.8.0-rc1-
049] ==
[ 97.803051] [ INFO: possible circular locking dependency detected ]
[ 97.803059] 3.8.0-rc1-dirty #2 Not tainted
[ 97.803060] ---
[ 97.803066] kworker/0:1/235 is trying to acquire lock:
[ 97.803097] ((fb_notifier_list).rwsem){.+.+.+},
Got during suspend to disk:
[ 269.784867] [ INFO: possible circular locking dependency detected ]
[ 269.784869] 3.8.0-rc1 #1 Not tainted
[ 269.784870] ---
[ 269.784871] kworker/u:3/56 is trying to acquire lock:
[ 269.784878
On Tue 14-08-12 23:13:31, Al Viro wrote:
> On Wed, Aug 15, 2012 at 12:09:27AM +0200, Jan Kara wrote:
> > OK, this is a theoretical deadlock since mqueue (virtual) filesystem
> > cannot
> > really be frozen. But we should convert the mqueue code to deal with new
> > lock ordering of i_mutex and m
On Wed, Aug 15, 2012 at 12:09:27AM +0200, Jan Kara wrote:
> OK, this is a theoretical deadlock since mqueue (virtual) filesystem cannot
> really be frozen. But we should convert the mqueue code to deal with new
> lock ordering of i_mutex and mnt_want_write() anyway to make lockdep happy
> if anyt
here is a different back trace on that commit.
> > > >
> > > > [3.255043] ==========
> > > > [3.255052] [ INFO: possible circular locking dependency detected ]
> > > > [
On Tue, Aug 07, 2012 at 04:54:44PM +0200, Sasha Levin wrote:
> On 08/06/2012 08:34 AM, Al Viro wrote:
> > On Sat, Aug 04, 2012 at 12:59:31PM +0200, Sasha Levin wrote:
> >> Hi all,
> >>
> >> While fuzzing with trinity inside a KVM tools guest, using latest -next
> >> kernel, I've stumbled on the du
3.255052] [ INFO: possible circular locking dependency detected ]
> > [3.255052] 3.5.0-rc6-bisect-00355-geb04c28 #4 Not tainted
> > [3.255052] ---
> > [3.255052] init/1 is trying to acquire lock:
On 08/06/2012 08:34 AM, Al Viro wrote:
> On Sat, Aug 04, 2012 at 12:59:31PM +0200, Sasha Levin wrote:
>> Hi all,
>>
>> While fuzzing with trinity inside a KVM tools guest, using latest -next
>> kernel, I've stumbled on the dump below.
>>
>> I think this is the result of commit 765927b2 ("switch de
On Tue, Aug 07, 2012 at 01:04:12PM +0800, Fengguang Wu wrote:
> FYI, here is a different back trace on that commit.
>
> [3.255043] ==
> [3.255052] [ INFO: possible circular locking dependency detected ]
> [3.255052] 3
On Sat, Aug 04, 2012 at 12:59:31PM +0200, Sasha Levin wrote:
> Hi all,
>
> While fuzzing with trinity inside a KVM tools guest, using latest -next
> kernel, I've stumbled on the dump below.
>
> I think this is the result of commit 765927b2 ("switch dentry_open() to
> struct path, make it grab r
[ 62.090519] ==
[ 62.091016] [ INFO: possible circular locking dependency detected ]
[ 62.091016] 3.6.0-rc1-next-20120803-sasha #544 Tainted: GW
[ 62.091016] ---
[ 62.091016] trinity-child0/6077 is trying
On Wed, 13 Feb 2008, Jiri Kosina wrote:
> From: Jiri Kosina <[EMAIL PROTECTED]>
>
> loop - fix deadlock against block
>
> A: B:
> bdev_open() for ino X
>(locks bd_mutex for bdev Y)
> lo_ioctl(LOOP_
On Wed, 13 Feb 2008, Zdenek Kabelac wrote:
> ===
> [ INFO: possible circular locking dependency detected ]
> 2.6.25-rc1 #29
> ---
> losetup/26595 is trying to acquire l
Hi
I'm getting this INFO message from losetup I'm using in my scripts:
if more info is needed from my side just ask.
(haven't seen this with 2.6.24..., using T61, 64bit kernel)
Bye
Zdenek
===
[ INFO: possible circular loc
On Dec 18, 2007 9:58 PM, Zhu Yi <[EMAIL PROTECTED]> wrote:
>
> On Tue, 2007-12-18 at 15:57 +0100, Johannes Berg wrote:
> > Thanks. This is a bug in iwlwifi.
> >
> > The problem is actually another case where my workqueue debugging with
> > lockdep is triggering a warning :))
> >
> > Here's the thin
On Tue, 2007-12-18 at 15:57 +0100, Johannes Berg wrote:
> Thanks. This is a bug in iwlwifi.
>
> The problem is actually another case where my workqueue debugging with
> lockdep is triggering a warning :))
>
> Here's the thing:
>
> iwl3945_cancel_deferred_work does
>
> cancel_delayed_work_sync
> Sorry. GMail doesn't support sending unwrapped text, as far as I can
> tell. I will send the log segment to you as an attachment. Also,
> when I sent my .config inline to Andrew recently, it tripped his spam
> filter. I'll attach it as well.
Thanks. This is a bug in iwlwifi.
The problem is
On Tue, 2007-12-18 at 09:03 -0500, Miles Lane wrote:
> I have only seen this happen once, and cannot reproduce it. I'll keep
> trying, though.
>
> Dec 16 22:10:48 syntropy kernel: [ 231.718023]
> ===
Do you have a version that isn't line-wrap
I have only seen this happen once, and cannot reproduce it. I'll keep
trying, though.
Dec 16 22:10:48 syntropy kernel: [ 231.718023]
===
Dec 16 22:10:48 syntropy kernel: [ 231.718025] [ INFO: possible
circular locking dependency det
On Thu, Aug 16, 2007 at 09:23:48PM +0100, Alan Cox wrote:
> On Thu, 16 Aug 2007 19:50:43 +0200
> Authenticated <[EMAIL PROTECTED]> wrote:
>
> >
> > =======
> > [ INFO: possible circular locking dependency det
On Thu, 16 Aug 2007 19:50:43 +0200
Authenticated <[EMAIL PROTECTED]> wrote:
>
> ===
> [ INFO: possible circular locking dependency detected ]
> 2.6.20-1.2948.self #1
> --
===
[ INFO: possible circular locking dependency detected ]
2.6.20-1.2948.self #1
---
squid/4058 is trying to acquire lock:
(tty_mutex){--..}, at: [] print_warning+0x8b/0x12e
but task is
On Fri, 2007-08-10 at 02:47 +0400, Alexey Starikovskiy wrote:
> > Presumably the new debugging patches in -mm
> > (workqueue-debug-flushing-deadlocks-with-lockdep.patch and
> > workqueue-debug-work-related-deadlocks-with-lockdep.patch) think they have
> > found a potential deadlock in ACPI. I don
Andrew Morton wrote:
> On Thu, 9 Aug 2007 16:24:48 -0400
> "Miles Lane" <[EMAIL PROTECTED]> wrote:
>
>> [ INFO: possible circular locking dependency detected ]
>> 2.6.23-rc2-mm1 #7
>> ---
>> ka
On Thu, 9 Aug 2007 16:24:48 -0400
"Miles Lane" <[EMAIL PROTECTED]> wrote:
> [ INFO: possible circular locking dependency detected ]
> 2.6.23-rc2-mm1 #7
> ---
> kacpid/53 is trying to acquire lock:
> (&ec-&
[ INFO: possible circular locking dependency detected ]
2.6.23-rc2-mm1 #7
---
kacpid/53 is trying to acquire lock:
(&ec->lock){--..}, at: [] mutex_lock+0x1c/0x1f
but task is already holding lock:
(&dpc->work){--..}, at: [] run_
I've not seen this reported...
[ 9564.772749]
[ 9564.772752] ===
[ 9564.772757] [ INFO: possible circular locking dependency detected ]
[ 9564.772760] 2.6.21-rc6-gc2481cc4 #9
[ 9564.7
===
[ INFO: possible circular locking dependency detected ]
2.6.20 #2
---
soffice.bin/29030 is trying to acquire lock:
(sk_lock-AF_INET){--..}, at: [<78259420>] tcp_sendmsg+0x16/0xafa
bu
59 matches
Mail list logo
