lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAOMZO5C1kS09cbQG4Y6QOHF4MAeXaFwsfwE2kCp1G0NsgmvO5g@mail.gmail.com>
Date:	Fri, 22 Feb 2013 23:08:16 -0300
From:	Fabio Estevam <festevam@...il.com>
To:	Frank Li <lznuaa@...il.com>
Cc:	Jim Baxter <jim_baxter@...tor.com>, netdev@...r.kernel.org
Subject: Re: [PATCH 1/1] net: fec: fix miss init spinlock

Frank,

On Fri, Feb 22, 2013 at 9:46 PM, Frank Li <lznuaa@...il.com> wrote:

> Does it happen when run ptp4?
> I am working on put xmit to NAPI and remove lock.

Jim reported the way to reproduce this issue in a previous post in this thread:

"Thank you, I have tried your new patch, it fixes the boot deadlock but when I
run the ptp4l command I get another dead lock:

On client running "./ptp4l -S -i eth0 -s -m"


On the i.MX6:

root@...q35:~# ptp4l -H -m -i eth0 -p /dev/ptp0
ptp4l[98.894]: selected /dev/ptp0 as PTP clock
ptp4l[98.896]: failed to read out the clock frequency adjustment: Operation not
supported
ptp4l[98.900]: driver changed our HWTSTAMP options
ptp4l[98.900]: tx_type   1 not 1
ptp4l[98.900]: rx_filter 1 not 12
ptp4l[98.901]: port 1: INITIALIZING to LISTENING on INITIALIZE
ptp4l[98.902]: port 0: INITIALIZING to LISTENING on INITIALIZE
ptp4l[104.901]: port 1: LISTENING to MASTER on ANNOUNCE_RECEIPT_TIMEOUT_EXPIRES
[  111.161885] =================================
[  111.166249] [ INFO: inconsistent lock state ]
[  111.170616] 3.5.7.3-01268-g6696bd7-dirty #2 Not tainted
[  111.175848] ---------------------------------"
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ