Hi Guenter,
> On 05/14/2016 10:07 AM, Guenter Roeck wrote:
> >Hi Wim,
> >
> >On 05/14/2016 09:41 AM, Wim Van Sebroeck wrote:
> >>Hi Guenter,
> >>
> >>>lockdep reports the following circular locking dependency.
> >>>
> >
> >You are faster than me this time. I was just about to send you a pull
>
Hi Guenter,
> On 05/14/2016 10:07 AM, Guenter Roeck wrote:
> >Hi Wim,
> >
> >On 05/14/2016 09:41 AM, Wim Van Sebroeck wrote:
> >>Hi Guenter,
> >>
> >>>lockdep reports the following circular locking dependency.
> >>>
> >
> >You are faster than me this time. I was just about to send you a pull
>
On 05/14/2016 10:07 AM, Guenter Roeck wrote:
Hi Wim,
On 05/14/2016 09:41 AM, Wim Van Sebroeck wrote:
Hi Guenter,
lockdep reports the following circular locking dependency.
You are faster than me this time. I was just about to send you a pull request.
Sorry for being late. The
On 05/14/2016 10:07 AM, Guenter Roeck wrote:
Hi Wim,
On 05/14/2016 09:41 AM, Wim Van Sebroeck wrote:
Hi Guenter,
lockdep reports the following circular locking dependency.
You are faster than me this time. I was just about to send you a pull request.
Sorry for being late. The
Hi Wim,
On 05/14/2016 09:41 AM, Wim Van Sebroeck wrote:
Hi Guenter,
lockdep reports the following circular locking dependency.
You are faster than me this time. I was just about to send you a pull request.
Sorry for being late. The watchdog-next branch in my repository on kernel.org
has
Hi Wim,
On 05/14/2016 09:41 AM, Wim Van Sebroeck wrote:
Hi Guenter,
lockdep reports the following circular locking dependency.
You are faster than me this time. I was just about to send you a pull request.
Sorry for being late. The watchdog-next branch in my repository on kernel.org
has
Hi Guenter,
> lockdep reports the following circular locking dependency.
>
> ==
> INFO: possible circular locking dependency detected ]
> 4.6.0-rc3-00191-gfabf418 #162 Not tainted
> ---
>
Hi Guenter,
> lockdep reports the following circular locking dependency.
>
> ==
> INFO: possible circular locking dependency detected ]
> 4.6.0-rc3-00191-gfabf418 #162 Not tainted
> ---
>
On 05/09/2016 06:53 AM, Clemens Gruber wrote:
On Thu, Apr 21, 2016 at 07:38:14AM -0700, Guenter Roeck wrote:
lockdep reports the following circular locking dependency.
==
INFO: possible circular locking dependency detected ]
On 05/09/2016 06:53 AM, Clemens Gruber wrote:
On Thu, Apr 21, 2016 at 07:38:14AM -0700, Guenter Roeck wrote:
lockdep reports the following circular locking dependency.
==
INFO: possible circular locking dependency detected ]
On Thu, Apr 21, 2016 at 07:38:14AM -0700, Guenter Roeck wrote:
> lockdep reports the following circular locking dependency.
>
> ==
> INFO: possible circular locking dependency detected ]
> 4.6.0-rc3-00191-gfabf418 #162 Not tainted
>
On Thu, Apr 21, 2016 at 07:38:14AM -0700, Guenter Roeck wrote:
> lockdep reports the following circular locking dependency.
>
> ==
> INFO: possible circular locking dependency detected ]
> 4.6.0-rc3-00191-gfabf418 #162 Not tainted
>
On Thu, Apr 21, 2016 at 03:50:55PM +0100, One Thousand Gnomes wrote:
> > Turns out the call to cancel_delayed_work_sync() in watchdog_release()
> > is not necessary and can be dropped. If the worker is no longer necessary,
> > the subsequent call to watchdog_update_worker() will cancel it. If it
On Thu, Apr 21, 2016 at 03:50:55PM +0100, One Thousand Gnomes wrote:
> > Turns out the call to cancel_delayed_work_sync() in watchdog_release()
> > is not necessary and can be dropped. If the worker is no longer necessary,
> > the subsequent call to watchdog_update_worker() will cancel it. If it
> Turns out the call to cancel_delayed_work_sync() in watchdog_release()
> is not necessary and can be dropped. If the worker is no longer necessary,
> the subsequent call to watchdog_update_worker() will cancel it. If it is
> already running, it won't do anything, since the worker function checks
> Turns out the call to cancel_delayed_work_sync() in watchdog_release()
> is not necessary and can be dropped. If the worker is no longer necessary,
> the subsequent call to watchdog_update_worker() will cancel it. If it is
> already running, it won't do anything, since the worker function checks
lockdep reports the following circular locking dependency.
==
INFO: possible circular locking dependency detected ]
4.6.0-rc3-00191-gfabf418 #162 Not tainted
---
systemd/1 is trying to acquire
lockdep reports the following circular locking dependency.
==
INFO: possible circular locking dependency detected ]
4.6.0-rc3-00191-gfabf418 #162 Not tainted
---
systemd/1 is trying to acquire
18 matches
Mail list logo
