On Wed, 2009-02-25 at 18:07 +0100, Jan-Bernd Themann wrote:
> Hi,
>
> yes, sorry for the funny wrapping... and thanks for your quick answer!
>
> Peter Zijlstra wrote:
> > On Wed, 2009-02-25 at 16:05 +0100, Jan-Bernd Themann wrote:
> >
> >
> >> - When "open" is called for a registered network d
Hi,
yes, sorry for the funny wrapping... and thanks for your quick answer!
Peter Zijlstra wrote:
> On Wed, 2009-02-25 at 16:05 +0100, Jan-Bernd Themann wrote:
>
>
>> - When "open" is called for a registered network device, port->port_lock
>> is taken first,
>> then ehea_fw_handles.lock
>> -
On Wed, 2009-02-25 at 16:05 +0100, Jan-Bernd Themann wrote:
> - When "open" is called for a registered network device, port->port_lock
> is taken first,
> then ehea_fw_handles.lock
> - When "open" is left these locks are released in a proper way (inverse
> order)
So this has:
port->port_lock
Hi,
we have investigated this problem but didn't understand to root cause of
this problem so far.
The things we observed:
- The warning is only shown when the ehea module is loaded while the
machine is booting.
- If you load the module later (modprobe) no warnings are shown
- Machine never actuall
While booting 2.6.29-rc6 on a powerpc box came across this
circular dependency with eHEA driver.
===
[ INFO: possible circular locking dependency detected ]
2.6.29-rc6 #2
---
ip/2174 is trying
