[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <42b8bfd5-3012-4c49-b9ef-7a9beb5956f1@VA3EHSMHS041.ehs.local>
Date: Fri, 31 May 2013 12:12:07 -0700
From: Sören Brinkmann <soren.brinkmann@...inx.com>
To: Michal Simek <michal.simek@...inx.com>,
Mike Turquette <mturquette@...aro.org>,
Lai Jiangshan <laijs@...fujitsu.com>,
<paulmck@...ux.vnet.ibm.com>
CC: Sören Brinkmann <soren.brinkmann@...inx.com>,
<linux-kernel@...r.kernel.org>,
<linux-arm-kernel@...ts.infradead.org>, <git@...inx.com>
Subject: [BUG] zynq | CCF | SRCU
Hi,
we recently encountered some kernel panics when we compiled one of our
drivers as module and tested inserting/removing the module.
Trying to debug this issue, I could reproduce it on the mainline kernel
with a dummy module.
What happens is, that when on driver remove clk_notifier_unregister() is
called and no other notifier for that clock is registered, the kernel
panics.
I'm not sure what is going wrong here. If there is a bug (and if where)
or I'm just using the infrastructure the wrong way,... So, any hint is
appreciated.
I attach the output from the crashing system. The stacktrace indicates a
crash in 'srcu_readers_seq_idx()'.
I also attach the module I used to trigger the issue and a patch on top
of mainline commit a93cb29acaa8f75618c3f202d1cf43c231984644 which has
the DT modifications I need to make the module find its clock and boot
with my initramfs.
Thanks,
Sören
View attachment "output.log" of type "text/plain" (16689 bytes)
View attachment "clk_notif_dbg.c" of type "text/x-csrc" (2017 bytes)
View attachment "0001-zynq-Clock-notify-debug-on-zc702.patch" of type "text/x-diff" (1469 bytes)
Powered by blists - more mailing lists