Re: tg3 BUG: spinlock lockup suspected

2016-10-19 Thread Meelis Roos 
> Can you please share the Linux Distribution information along with sparc 
> machine specification.

Sun Fire V210 (dual UltraSPARC IIIi), onboard NICs with tg3 
driver. Debian unstable snapshot (as last seen in Debian):

deb http://snapshot.debian.org/archive/debian/20150725T121538Z/ unstable main 
contrib non-free

except for udev and libudev1 that are 218-8 (older) because the latest 
udev at that moment was broken.

This implies gcc version 4.9.3 (Debian 4.9.3-2).


> Regards,
> Deepak Khungar
> 
> On Wed, Oct 19, 2016 at 10:18 AM, Siva Reddy Kallam 
>  wrote:
>   On Mon, Oct 17, 2016 at 6:35 PM, Meelis Roos  wrote:
>   >> > Now I reproduced the bug even with 4.7-rc1 so it is older than 
> 4.7. Will
>   >> > test further.
>   >>
>   >> It gets stranger and stranger - my old 4.7 image worked fine, freshly
>   >> compiled 4.7 exhibits the same problem.
>   >>
>   >> Toolchain has not changed, that I know for sure.
>   >>
>   >> What may have changed is kernel .config. My old conf was with 
> whatever I
>   >> had during 4.7. Then I upgraded to 4.8-rc3 and then 4.8 and selected
>   >> values for "make oldconfig" new entries. Then went back to 4.7-rc1 
> and
>   >> then to 4.7 with this config, answering quiestion about new options 
> when
>   >> any appeared. Diff is not available since I do not have the old 
> configs
>   >> archived.
>   >
>   > I did some more digging. Found an older configuration that is working
>   > and recreated a newer one that is bad, for the same 4.7 kernel. This 
> is
>   > reproducible now, from "make clean" state.
>   >
>   > Working config from 4.7-rc4 attached as config-4.7, broken config from
>   > 4.7 attached as config-4.7-bad.
>   >
>   > Will try to bisect the configs as time permits. But looking at the
>   > stack traces, the issue is probably timing related, when ip and 
> dhclient
>   > do something with the same lock. seq_read that outputs stats could be
>   > reading /proc/net/dev that reads counters from each interface.
>   >
>   > ifupdown seems to use the following for dhcp interfaces:
>   >   up
>   >     [[/bin/ip link set dev %iface% address %hwaddress%]]
>   >     /sbin/dhclient -v -pf /run/dhclient.%iface%.pid -lf 
> /var/lib/dhcp/dhclient.%iface%.leases -I -df 
> /var/lib/dhcp/dhclient6.%iface%.leases %iface% \
>   > ...
>   >
>   > so ip link is setting link up, this creates some work for the
>   > background, and the dhclient goes adn reads /proc/net/dev, and lockup 
> is
>   > suspected but not proven?
>   >
>   > I started a loop for test, doing cat /proc/net/dev in a loop and at 
> the
>   > same link link up and down from console, but up and down is slow 
> process
>   > and the loop did not seem to trigger the warning over night, so it was
>   > not so simple.
>   >
>   I am busy with other priority tasks. One of my colleague Deepak will
>   work this with you.
>   I added him to CC list.
>   Thanks.
>   >
>   >> > > [   83.716570] BUG: spinlock lockup suspected on CPU#0, 
> dhclient/1014
>   >> > > [   83.797819]  lock: 0xfff000123c8e4a08, .magic: dead4ead, 
> .owner: ip/1001, .owner_cpu: 1
>   >> > > [   83.903130] CPU: 0 PID: 1014 Comm: dhclient Not tainted 4.8.0 
> #4
>   >> > > [   83.982129] Call Trace:
>   >> > > [   84.014160]  [004b7220] spin_dump+0x60/0xa0
>   >> > > [   84.078203]  [004b73a0] do_raw_spin_lock+0xa0/0x120
>   >> > > [   84.106344] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
>   >> > > [   84.107193] ip (1001) used greatest stack depth: 2168 bytes 
> left
>   >> > > [   84.306955]  [0092c0d0] _raw_spin_lock_bh+0x30/0x40
>   >> > > [   84.380188]  [100822cc] tg3_get_stats64+0xc/0x80 [tg3]
>   >> > > [   84.456885]  [007fac8c] dev_get_stats+0x2c/0xc0
>   >> > > [   84.525506]  [0081a4e8] dev_seq_printf_stats+0x8/0xe0
>   >> > > [   84.600986]  [0081a5e4] dev_seq_show+0x24/0x40
>   >> > > [   84.668467]  [005cb6c4] seq_read+0x2c4/0x440
>   >> > > [   84.733656]  [0060b97c] proc_reg_read+0x3c/0x80
>   >> > > [   84.802282]  [005a219c] __vfs_read+0x1c/0x140
>   >> > > [   84.868613]  [005a2310] vfs_read+0x50/0x100
>   >> > > [   84.932662]  [005a265c] SyS_read+0x3c/0xa0
>   >> > > [   84.995573]  [004061d4] 
> linux_sparc_syscall32+0x34/0x60
>   >> > > [   85.073748] * CPU[  0]: TSTATE[0044f0001a22] 
> TPC[f79a16b0] TNPC[f79a16b4] TASK[dhclient:1014]
>   >> > > [   85.208732]              TPC[f79a16b0] O7[f79405c8] I7[0] 
> RPC[0]
>   >> > > [   85.287633]   CPU[  1]: TSTATE[004480001605] 
> TPC[004b26f0] TNPC[004d0b0c] TASK[swapper/1:0]
>   >> > > [   

Re: tg3 BUG: spinlock lockup suspected

2016-10-19 Thread Meelis Roos 
> Can you please share the Linux Distribution information along with sparc 
> machine specification.

Sun Fire V210 (dual UltraSPARC IIIi), onboard NICs with tg3 
driver. Debian unstable snapshot (as last seen in Debian):

deb http://snapshot.debian.org/archive/debian/20150725T121538Z/ unstable main 
contrib non-free

except for udev and libudev1 that are 218-8 (older) because the latest 
udev at that moment was broken.

This implies gcc version 4.9.3 (Debian 4.9.3-2).


> Regards,
> Deepak Khungar
> 
> On Wed, Oct 19, 2016 at 10:18 AM, Siva Reddy Kallam 
>  wrote:
>   On Mon, Oct 17, 2016 at 6:35 PM, Meelis Roos  wrote:
>   >> > Now I reproduced the bug even with 4.7-rc1 so it is older than 
> 4.7. Will
>   >> > test further.
>   >>
>   >> It gets stranger and stranger - my old 4.7 image worked fine, freshly
>   >> compiled 4.7 exhibits the same problem.
>   >>
>   >> Toolchain has not changed, that I know for sure.
>   >>
>   >> What may have changed is kernel .config. My old conf was with 
> whatever I
>   >> had during 4.7. Then I upgraded to 4.8-rc3 and then 4.8 and selected
>   >> values for "make oldconfig" new entries. Then went back to 4.7-rc1 
> and
>   >> then to 4.7 with this config, answering quiestion about new options 
> when
>   >> any appeared. Diff is not available since I do not have the old 
> configs
>   >> archived.
>   >
>   > I did some more digging. Found an older configuration that is working
>   > and recreated a newer one that is bad, for the same 4.7 kernel. This 
> is
>   > reproducible now, from "make clean" state.
>   >
>   > Working config from 4.7-rc4 attached as config-4.7, broken config from
>   > 4.7 attached as config-4.7-bad.
>   >
>   > Will try to bisect the configs as time permits. But looking at the
>   > stack traces, the issue is probably timing related, when ip and 
> dhclient
>   > do something with the same lock. seq_read that outputs stats could be
>   > reading /proc/net/dev that reads counters from each interface.
>   >
>   > ifupdown seems to use the following for dhcp interfaces:
>   >   up
>   >     [[/bin/ip link set dev %iface% address %hwaddress%]]
>   >     /sbin/dhclient -v -pf /run/dhclient.%iface%.pid -lf 
> /var/lib/dhcp/dhclient.%iface%.leases -I -df 
> /var/lib/dhcp/dhclient6.%iface%.leases %iface% \
>   > ...
>   >
>   > so ip link is setting link up, this creates some work for the
>   > background, and the dhclient goes adn reads /proc/net/dev, and lockup 
> is
>   > suspected but not proven?
>   >
>   > I started a loop for test, doing cat /proc/net/dev in a loop and at 
> the
>   > same link link up and down from console, but up and down is slow 
> process
>   > and the loop did not seem to trigger the warning over night, so it was
>   > not so simple.
>   >
>   I am busy with other priority tasks. One of my colleague Deepak will
>   work this with you.
>   I added him to CC list.
>   Thanks.
>   >
>   >> > > [   83.716570] BUG: spinlock lockup suspected on CPU#0, 
> dhclient/1014
>   >> > > [   83.797819]  lock: 0xfff000123c8e4a08, .magic: dead4ead, 
> .owner: ip/1001, .owner_cpu: 1
>   >> > > [   83.903130] CPU: 0 PID: 1014 Comm: dhclient Not tainted 4.8.0 
> #4
>   >> > > [   83.982129] Call Trace:
>   >> > > [   84.014160]  [004b7220] spin_dump+0x60/0xa0
>   >> > > [   84.078203]  [004b73a0] do_raw_spin_lock+0xa0/0x120
>   >> > > [   84.106344] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
>   >> > > [   84.107193] ip (1001) used greatest stack depth: 2168 bytes 
> left
>   >> > > [   84.306955]  [0092c0d0] _raw_spin_lock_bh+0x30/0x40
>   >> > > [   84.380188]  [100822cc] tg3_get_stats64+0xc/0x80 [tg3]
>   >> > > [   84.456885]  [007fac8c] dev_get_stats+0x2c/0xc0
>   >> > > [   84.525506]  [0081a4e8] dev_seq_printf_stats+0x8/0xe0
>   >> > > [   84.600986]  [0081a5e4] dev_seq_show+0x24/0x40
>   >> > > [   84.668467]  [005cb6c4] seq_read+0x2c4/0x440
>   >> > > [   84.733656]  [0060b97c] proc_reg_read+0x3c/0x80
>   >> > > [   84.802282]  [005a219c] __vfs_read+0x1c/0x140
>   >> > > [   84.868613]  [005a2310] vfs_read+0x50/0x100
>   >> > > [   84.932662]  [005a265c] SyS_read+0x3c/0xa0
>   >> > > [   84.995573]  [004061d4] 
> linux_sparc_syscall32+0x34/0x60
>   >> > > [   85.073748] * CPU[  0]: TSTATE[0044f0001a22] 
> TPC[f79a16b0] TNPC[f79a16b4] TASK[dhclient:1014]
>   >> > > [   85.208732]              TPC[f79a16b0] O7[f79405c8] I7[0] 
> RPC[0]
>   >> > > [   85.287633]   CPU[  1]: TSTATE[004480001605] 
> TPC[004b26f0] TNPC[004d0b0c] TASK[swapper/1:0]
>   >> > > [   85.420338]             

Re: tg3 BUG: spinlock lockup suspected

2016-10-18 Thread Siva Reddy Kallam 
On Mon, Oct 17, 2016 at 6:35 PM, Meelis Roos  wrote:
>> > Now I reproduced the bug even with 4.7-rc1 so it is older than 4.7. Will
>> > test further.
>>
>> It gets stranger and stranger - my old 4.7 image worked fine, freshly
>> compiled 4.7 exhibits the same problem.
>>
>> Toolchain has not changed, that I know for sure.
>>
>> What may have changed is kernel .config. My old conf was with whatever I
>> had during 4.7. Then I upgraded to 4.8-rc3 and then 4.8 and selected
>> values for "make oldconfig" new entries. Then went back to 4.7-rc1 and
>> then to 4.7 with this config, answering quiestion about new options when
>> any appeared. Diff is not available since I do not have the old configs
>> archived.
>
> I did some more digging. Found an older configuration that is working
> and recreated a newer one that is bad, for the same 4.7 kernel. This is
> reproducible now, from "make clean" state.
>
> Working config from 4.7-rc4 attached as config-4.7, broken config from
> 4.7 attached as config-4.7-bad.
>
> Will try to bisect the configs as time permits. But looking at the
> stack traces, the issue is probably timing related, when ip and dhclient
> do something with the same lock. seq_read that outputs stats could be
> reading /proc/net/dev that reads counters from each interface.
>
> ifupdown seems to use the following for dhcp interfaces:
>   up
> [[/bin/ip link set dev %iface% address %hwaddress%]]
> /sbin/dhclient -v -pf /run/dhclient.%iface%.pid -lf 
> /var/lib/dhcp/dhclient.%iface%.leases -I -df 
> /var/lib/dhcp/dhclient6.%iface%.leases %iface% \
> ...
>
> so ip link is setting link up, this creates some work for the
> background, and the dhclient goes adn reads /proc/net/dev, and lockup is
> suspected but not proven?
>
> I started a loop for test, doing cat /proc/net/dev in a loop and at the
> same link link up and down from console, but up and down is slow process
> and the loop did not seem to trigger the warning over night, so it was
> not so simple.
>
I am busy with other priority tasks. One of my colleague Deepak will
work this with you.
I added him to CC list.
Thanks.
>
>> > > [   83.716570] BUG: spinlock lockup suspected on CPU#0, dhclient/1014
>> > > [   83.797819]  lock: 0xfff000123c8e4a08, .magic: dead4ead, .owner: 
>> > > ip/1001, .owner_cpu: 1
>> > > [   83.903130] CPU: 0 PID: 1014 Comm: dhclient Not tainted 4.8.0 #4
>> > > [   83.982129] Call Trace:
>> > > [   84.014160]  [004b7220] spin_dump+0x60/0xa0
>> > > [   84.078203]  [004b73a0] do_raw_spin_lock+0xa0/0x120
>> > > [   84.106344] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
>> > > [   84.107193] ip (1001) used greatest stack depth: 2168 bytes left
>> > > [   84.306955]  [0092c0d0] _raw_spin_lock_bh+0x30/0x40
>> > > [   84.380188]  [100822cc] tg3_get_stats64+0xc/0x80 [tg3]
>> > > [   84.456885]  [007fac8c] dev_get_stats+0x2c/0xc0
>> > > [   84.525506]  [0081a4e8] dev_seq_printf_stats+0x8/0xe0
>> > > [   84.600986]  [0081a5e4] dev_seq_show+0x24/0x40
>> > > [   84.668467]  [005cb6c4] seq_read+0x2c4/0x440
>> > > [   84.733656]  [0060b97c] proc_reg_read+0x3c/0x80
>> > > [   84.802282]  [005a219c] __vfs_read+0x1c/0x140
>> > > [   84.868613]  [005a2310] vfs_read+0x50/0x100
>> > > [   84.932662]  [005a265c] SyS_read+0x3c/0xa0
>> > > [   84.995573]  [004061d4] linux_sparc_syscall32+0x34/0x60
>> > > [   85.073748] * CPU[  0]: TSTATE[0044f0001a22] 
>> > > TPC[f79a16b0] TNPC[f79a16b4] TASK[dhclient:1014]
>> > > [   85.208732]  TPC[f79a16b0] O7[f79405c8] I7[0] RPC[0]
>> > > [   85.287633]   CPU[  1]: TSTATE[004480001605] 
>> > > TPC[004b26f0] TNPC[004d0b0c] TASK[swapper/1:0]
>> > > [   85.420338]  TPC[trace_hardirqs_off+0x10/0x20] 
>> > > O7[rcu_idle_enter+0x64/0xa0] I7[cpu_startup_entry+0x1b0/0x240] 
>> > > RPC[rest_init+0x178/0x1a0]
>> > > [   85.664600] tg3 :00:02.0 eth0: Link is up at 100 Mbps, full duplex
>> > > [   85.750515] tg3 :00:02.0 eth0: Flow control is off for TX and off 
>> > > for RX
>> > > [   85.843994] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
>
> --
> Meelis Roos (mr...@linux.ee)

Re: tg3 BUG: spinlock lockup suspected

2016-10-18 Thread Siva Reddy Kallam 
On Mon, Oct 17, 2016 at 6:35 PM, Meelis Roos  wrote:
>> > Now I reproduced the bug even with 4.7-rc1 so it is older than 4.7. Will
>> > test further.
>>
>> It gets stranger and stranger - my old 4.7 image worked fine, freshly
>> compiled 4.7 exhibits the same problem.
>>
>> Toolchain has not changed, that I know for sure.
>>
>> What may have changed is kernel .config. My old conf was with whatever I
>> had during 4.7. Then I upgraded to 4.8-rc3 and then 4.8 and selected
>> values for "make oldconfig" new entries. Then went back to 4.7-rc1 and
>> then to 4.7 with this config, answering quiestion about new options when
>> any appeared. Diff is not available since I do not have the old configs
>> archived.
>
> I did some more digging. Found an older configuration that is working
> and recreated a newer one that is bad, for the same 4.7 kernel. This is
> reproducible now, from "make clean" state.
>
> Working config from 4.7-rc4 attached as config-4.7, broken config from
> 4.7 attached as config-4.7-bad.
>
> Will try to bisect the configs as time permits. But looking at the
> stack traces, the issue is probably timing related, when ip and dhclient
> do something with the same lock. seq_read that outputs stats could be
> reading /proc/net/dev that reads counters from each interface.
>
> ifupdown seems to use the following for dhcp interfaces:
>   up
> [[/bin/ip link set dev %iface% address %hwaddress%]]
> /sbin/dhclient -v -pf /run/dhclient.%iface%.pid -lf 
> /var/lib/dhcp/dhclient.%iface%.leases -I -df 
> /var/lib/dhcp/dhclient6.%iface%.leases %iface% \
> ...
>
> so ip link is setting link up, this creates some work for the
> background, and the dhclient goes adn reads /proc/net/dev, and lockup is
> suspected but not proven?
>
> I started a loop for test, doing cat /proc/net/dev in a loop and at the
> same link link up and down from console, but up and down is slow process
> and the loop did not seem to trigger the warning over night, so it was
> not so simple.
>
I am busy with other priority tasks. One of my colleague Deepak will
work this with you.
I added him to CC list.
Thanks.
>
>> > > [   83.716570] BUG: spinlock lockup suspected on CPU#0, dhclient/1014
>> > > [   83.797819]  lock: 0xfff000123c8e4a08, .magic: dead4ead, .owner: 
>> > > ip/1001, .owner_cpu: 1
>> > > [   83.903130] CPU: 0 PID: 1014 Comm: dhclient Not tainted 4.8.0 #4
>> > > [   83.982129] Call Trace:
>> > > [   84.014160]  [004b7220] spin_dump+0x60/0xa0
>> > > [   84.078203]  [004b73a0] do_raw_spin_lock+0xa0/0x120
>> > > [   84.106344] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
>> > > [   84.107193] ip (1001) used greatest stack depth: 2168 bytes left
>> > > [   84.306955]  [0092c0d0] _raw_spin_lock_bh+0x30/0x40
>> > > [   84.380188]  [100822cc] tg3_get_stats64+0xc/0x80 [tg3]
>> > > [   84.456885]  [007fac8c] dev_get_stats+0x2c/0xc0
>> > > [   84.525506]  [0081a4e8] dev_seq_printf_stats+0x8/0xe0
>> > > [   84.600986]  [0081a5e4] dev_seq_show+0x24/0x40
>> > > [   84.668467]  [005cb6c4] seq_read+0x2c4/0x440
>> > > [   84.733656]  [0060b97c] proc_reg_read+0x3c/0x80
>> > > [   84.802282]  [005a219c] __vfs_read+0x1c/0x140
>> > > [   84.868613]  [005a2310] vfs_read+0x50/0x100
>> > > [   84.932662]  [005a265c] SyS_read+0x3c/0xa0
>> > > [   84.995573]  [004061d4] linux_sparc_syscall32+0x34/0x60
>> > > [   85.073748] * CPU[  0]: TSTATE[0044f0001a22] 
>> > > TPC[f79a16b0] TNPC[f79a16b4] TASK[dhclient:1014]
>> > > [   85.208732]  TPC[f79a16b0] O7[f79405c8] I7[0] RPC[0]
>> > > [   85.287633]   CPU[  1]: TSTATE[004480001605] 
>> > > TPC[004b26f0] TNPC[004d0b0c] TASK[swapper/1:0]
>> > > [   85.420338]  TPC[trace_hardirqs_off+0x10/0x20] 
>> > > O7[rcu_idle_enter+0x64/0xa0] I7[cpu_startup_entry+0x1b0/0x240] 
>> > > RPC[rest_init+0x178/0x1a0]
>> > > [   85.664600] tg3 :00:02.0 eth0: Link is up at 100 Mbps, full duplex
>> > > [   85.750515] tg3 :00:02.0 eth0: Flow control is off for TX and off 
>> > > for RX
>> > > [   85.843994] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
>
> --
> Meelis Roos (mr...@linux.ee)

Re: tg3 BUG: spinlock lockup suspected

2016-10-13 Thread Siva Reddy Kallam 
On Mon, Oct 10, 2016 at 5:21 PM, Siva Reddy Kallam
 wrote:
> On Sun, Oct 9, 2016 at 12:35 AM, Meelis Roos  wrote:
>>> > That did not go well - bisect found the following commit but that does
>>> > not seem to be related at all. So probably the reproducibility is not
>>> > 100% but more random.
>>>
>>> Now I reproduced the bug even with 4.7-rc1 so it is older than 4.7. Will
>>> test further.
>>
>> It gets stranger and stranger - my old 4.7 image worked fine, freshly
>> compiled 4.7 exhibits the same problem.
>>
>> Toolchain has not changed, that I know for sure.
>>
>> What may have changed is kernel .config. My old conf was with whatever I
>> had during 4.7. Then I upgraded to 4.8-rc3 and then 4.8 and selected
>> values for "make oldconfig" new entries. Then went back to 4.7-rc1 and
>> then to 4.7 with this config, answering quiestion about new options when
>> any appeared. Diff is not available since I do not have the old configs
>> archived.
>>
>> Any ideas where to continue from here?
> Probably, You can do fresh system installation if possible.
> Any way, I will try to reproduce with 4.7 and 4.8 kernel versions.
> Will let you know my response in 1-2 days.
We are unable to reproduce with Intel system. we tried with both 4.7
and 4.8 kernel versions.
We are trying to get one SPARC system. We will let you know once we
are done with reproducing with SPARC system.
>>
>>>
>>> >
>>> >
>>> > 4c5773f9f5462dcb372857813918bbfe8c0cdcdd is the first bad commit
>>> > commit 4c5773f9f5462dcb372857813918bbfe8c0cdcdd
>>> > Author: Krzysztof Kozlowski 
>>> > Date:   Sat May 28 11:54:12 2016 +0200
>>> >
>>> > dt-bindings: clock: Add license and reformat Exynos5410 clock IDs
>>> >
>>> > Add license and copyrights (file introduced in 2014) to header with
>>> > Exynos5410 clock IDs. Additionally reformat it to improve readability.
>>> >
>>> > Signed-off-by: Krzysztof Kozlowski 
>>> > Acked-by: Stephen Boyd 
>>> > Reviewed-by: Javier Martinez Canillas 
>>> > Signed-off-by: Sylwester Nawrocki 
>>> >
>>> > :04 04 acbd432e11366a8eb8775942bc7b8caa476226e2 
>>> > 08e3a3f98c3d4fa2a93123c3f21b2847c06b4665 M  include
>>> >
>>> >
>>> > The whiole bisect log seems to dig around in unrelated places so at best
>>> > it just narrows the window by adding some known-bad data points.
>>> >
>>> > git bisect start
>>> > # good: [523d939ef98fd712632d93a5a2b588e477a7565e] Linux 4.7
>>> > git bisect good 523d939ef98fd712632d93a5a2b588e477a7565e
>>> > # bad: [ef0e1ea8856bed6ff8394d3dfe77f2cab487ecea] Merge tag 
>>> > 'arc-4.8-rc4-fixes' of 
>>> > git://git.kernel.org/pub/scm/linux/kernel/git/vgupta/arc
>>> > git bisect bad ef0e1ea8856bed6ff8394d3dfe77f2cab487ecea
>>> > # good: [e0b3f595d13b3e9ce9cdf53935e7f304c04b5b2b] affs ->d_compare(): 
>>> > don't bother with ->d_inode
>>> > git bisect good e0b3f595d13b3e9ce9cdf53935e7f304c04b5b2b
>>> > # bad: [77a87824ed676ca8ff8482e4157d3adb284fd381] 
>>> > clocksource/drivers/clps_711x: fixup for "ARM: clps711x:
>>> > git bisect bad 77a87824ed676ca8ff8482e4157d3adb284fd381
>>> > # bad: [27acbec338113a75b9d72aeb53149a3538031dda] Merge 
>>> > git://www.linux-watchdog.org/linux-watchdog
>>> > git bisect bad 27acbec338113a75b9d72aeb53149a3538031dda
>>> > # bad: [7f155c702677d057d03b192ce652311de5434697] Merge tag 
>>> > 'nfs-for-4.8-1' of git://git.linux-nfs.org/projects/trondmy/linux-nfs
>>> > git bisect bad 7f155c702677d057d03b192ce652311de5434697
>>> > # good: [797cee982eef9195736afc5e7f3b8f613c41d19a] Merge branch 
>>> > 'stable-4.8' of git://git.infradead.org/users/pcmoore/audit
>>> > git bisect good 797cee982eef9195736afc5e7f3b8f613c41d19a
>>> > # bad: [1056c9bd2702ea1bb79abf9bd1e78c578589d247] Merge tag 
>>> > 'clk-for-linus-4.8' of 
>>> > git://git.kernel.org/pub/scm/linux/kernel/git/clk/linux
>>> > git bisect bad 1056c9bd2702ea1bb79abf9bd1e78c578589d247
>>> > # bad: [1ff435d3571199a799ba6ccfe05544dcd21b9fb3] Merge branch 
>>> > 'clk-st-critical' into clk-next
>>> > git bisect bad 1ff435d3571199a799ba6ccfe05544dcd21b9fb3
>>> > # bad: [0e4504470667d355b53ca3c9802fdd2120c9f946] clk: samsung: 
>>> > exynos5433: Add CLK_IGNORE_UNUSED flag to PCIE device
>>> > git bisect bad 0e4504470667d355b53ca3c9802fdd2120c9f946
>>> > # bad: [880c81b3b6604a004d56b5975c8bed47276e8bf6] clk: samsung: 
>>> > exynos5440: Constify all clock initializers
>>> > git bisect bad 880c81b3b6604a004d56b5975c8bed47276e8bf6
>>> > # bad: [b3a96eed8e84780d300b79b58047ea277ba358b7] clk: samsung: 
>>> > exynos3250: Move platform driver and of_device_id to init section
>>> > git bisect bad b3a96eed8e84780d300b79b58047ea277ba358b7
>>> > # bad: [4528dd8ed477bf202bd33ee48d38d656672d37f8] dt-bindings: clock: Add 
>>> > watchdog and SSS clock IDs to Exynos5410
>>> > git bisect bad 4528dd8ed477bf202bd33ee48d38d656672d37f8
>>> > # bad:

Re: tg3 BUG: spinlock lockup suspected

2016-10-13 Thread Siva Reddy Kallam 
On Mon, Oct 10, 2016 at 5:21 PM, Siva Reddy Kallam
 wrote:
> On Sun, Oct 9, 2016 at 12:35 AM, Meelis Roos  wrote:
>>> > That did not go well - bisect found the following commit but that does
>>> > not seem to be related at all. So probably the reproducibility is not
>>> > 100% but more random.
>>>
>>> Now I reproduced the bug even with 4.7-rc1 so it is older than 4.7. Will
>>> test further.
>>
>> It gets stranger and stranger - my old 4.7 image worked fine, freshly
>> compiled 4.7 exhibits the same problem.
>>
>> Toolchain has not changed, that I know for sure.
>>
>> What may have changed is kernel .config. My old conf was with whatever I
>> had during 4.7. Then I upgraded to 4.8-rc3 and then 4.8 and selected
>> values for "make oldconfig" new entries. Then went back to 4.7-rc1 and
>> then to 4.7 with this config, answering quiestion about new options when
>> any appeared. Diff is not available since I do not have the old configs
>> archived.
>>
>> Any ideas where to continue from here?
> Probably, You can do fresh system installation if possible.
> Any way, I will try to reproduce with 4.7 and 4.8 kernel versions.
> Will let you know my response in 1-2 days.
We are unable to reproduce with Intel system. we tried with both 4.7
and 4.8 kernel versions.
We are trying to get one SPARC system. We will let you know once we
are done with reproducing with SPARC system.
>>
>>>
>>> >
>>> >
>>> > 4c5773f9f5462dcb372857813918bbfe8c0cdcdd is the first bad commit
>>> > commit 4c5773f9f5462dcb372857813918bbfe8c0cdcdd
>>> > Author: Krzysztof Kozlowski 
>>> > Date:   Sat May 28 11:54:12 2016 +0200
>>> >
>>> > dt-bindings: clock: Add license and reformat Exynos5410 clock IDs
>>> >
>>> > Add license and copyrights (file introduced in 2014) to header with
>>> > Exynos5410 clock IDs. Additionally reformat it to improve readability.
>>> >
>>> > Signed-off-by: Krzysztof Kozlowski 
>>> > Acked-by: Stephen Boyd 
>>> > Reviewed-by: Javier Martinez Canillas 
>>> > Signed-off-by: Sylwester Nawrocki 
>>> >
>>> > :04 04 acbd432e11366a8eb8775942bc7b8caa476226e2 
>>> > 08e3a3f98c3d4fa2a93123c3f21b2847c06b4665 M  include
>>> >
>>> >
>>> > The whiole bisect log seems to dig around in unrelated places so at best
>>> > it just narrows the window by adding some known-bad data points.
>>> >
>>> > git bisect start
>>> > # good: [523d939ef98fd712632d93a5a2b588e477a7565e] Linux 4.7
>>> > git bisect good 523d939ef98fd712632d93a5a2b588e477a7565e
>>> > # bad: [ef0e1ea8856bed6ff8394d3dfe77f2cab487ecea] Merge tag 
>>> > 'arc-4.8-rc4-fixes' of 
>>> > git://git.kernel.org/pub/scm/linux/kernel/git/vgupta/arc
>>> > git bisect bad ef0e1ea8856bed6ff8394d3dfe77f2cab487ecea
>>> > # good: [e0b3f595d13b3e9ce9cdf53935e7f304c04b5b2b] affs ->d_compare(): 
>>> > don't bother with ->d_inode
>>> > git bisect good e0b3f595d13b3e9ce9cdf53935e7f304c04b5b2b
>>> > # bad: [77a87824ed676ca8ff8482e4157d3adb284fd381] 
>>> > clocksource/drivers/clps_711x: fixup for "ARM: clps711x:
>>> > git bisect bad 77a87824ed676ca8ff8482e4157d3adb284fd381
>>> > # bad: [27acbec338113a75b9d72aeb53149a3538031dda] Merge 
>>> > git://www.linux-watchdog.org/linux-watchdog
>>> > git bisect bad 27acbec338113a75b9d72aeb53149a3538031dda
>>> > # bad: [7f155c702677d057d03b192ce652311de5434697] Merge tag 
>>> > 'nfs-for-4.8-1' of git://git.linux-nfs.org/projects/trondmy/linux-nfs
>>> > git bisect bad 7f155c702677d057d03b192ce652311de5434697
>>> > # good: [797cee982eef9195736afc5e7f3b8f613c41d19a] Merge branch 
>>> > 'stable-4.8' of git://git.infradead.org/users/pcmoore/audit
>>> > git bisect good 797cee982eef9195736afc5e7f3b8f613c41d19a
>>> > # bad: [1056c9bd2702ea1bb79abf9bd1e78c578589d247] Merge tag 
>>> > 'clk-for-linus-4.8' of 
>>> > git://git.kernel.org/pub/scm/linux/kernel/git/clk/linux
>>> > git bisect bad 1056c9bd2702ea1bb79abf9bd1e78c578589d247
>>> > # bad: [1ff435d3571199a799ba6ccfe05544dcd21b9fb3] Merge branch 
>>> > 'clk-st-critical' into clk-next
>>> > git bisect bad 1ff435d3571199a799ba6ccfe05544dcd21b9fb3
>>> > # bad: [0e4504470667d355b53ca3c9802fdd2120c9f946] clk: samsung: 
>>> > exynos5433: Add CLK_IGNORE_UNUSED flag to PCIE device
>>> > git bisect bad 0e4504470667d355b53ca3c9802fdd2120c9f946
>>> > # bad: [880c81b3b6604a004d56b5975c8bed47276e8bf6] clk: samsung: 
>>> > exynos5440: Constify all clock initializers
>>> > git bisect bad 880c81b3b6604a004d56b5975c8bed47276e8bf6
>>> > # bad: [b3a96eed8e84780d300b79b58047ea277ba358b7] clk: samsung: 
>>> > exynos3250: Move platform driver and of_device_id to init section
>>> > git bisect bad b3a96eed8e84780d300b79b58047ea277ba358b7
>>> > # bad: [4528dd8ed477bf202bd33ee48d38d656672d37f8] dt-bindings: clock: Add 
>>> > watchdog and SSS clock IDs to Exynos5410
>>> > git bisect bad 4528dd8ed477bf202bd33ee48d38d656672d37f8
>>> > # bad: [5cd3535a27a7cf8fc4070b499d66e419e7e72b61] dt-bindings: clock: Add 
>>> > PWM and USB clock IDs to Exynos5410
>>> > git bisect bad 5cd3535a27a7cf8fc4070b499d66e419e7e72b61
>>>

Re: tg3 BUG: spinlock lockup suspected

2016-10-10 Thread Siva Reddy Kallam 
On Sun, Oct 9, 2016 at 12:35 AM, Meelis Roos  wrote:
>> > That did not go well - bisect found the following commit but that does
>> > not seem to be related at all. So probably the reproducibility is not
>> > 100% but more random.
>>
>> Now I reproduced the bug even with 4.7-rc1 so it is older than 4.7. Will
>> test further.
>
> It gets stranger and stranger - my old 4.7 image worked fine, freshly
> compiled 4.7 exhibits the same problem.
>
> Toolchain has not changed, that I know for sure.
>
> What may have changed is kernel .config. My old conf was with whatever I
> had during 4.7. Then I upgraded to 4.8-rc3 and then 4.8 and selected
> values for "make oldconfig" new entries. Then went back to 4.7-rc1 and
> then to 4.7 with this config, answering quiestion about new options when
> any appeared. Diff is not available since I do not have the old configs
> archived.
>
> Any ideas where to continue from here?
Probably, You can do fresh system installation if possible.
Any way, I will try to reproduce with 4.7 and 4.8 kernel versions.
Will let you know my response in 1-2 days.
>
>>
>> >
>> >
>> > 4c5773f9f5462dcb372857813918bbfe8c0cdcdd is the first bad commit
>> > commit 4c5773f9f5462dcb372857813918bbfe8c0cdcdd
>> > Author: Krzysztof Kozlowski 
>> > Date:   Sat May 28 11:54:12 2016 +0200
>> >
>> > dt-bindings: clock: Add license and reformat Exynos5410 clock IDs
>> >
>> > Add license and copyrights (file introduced in 2014) to header with
>> > Exynos5410 clock IDs. Additionally reformat it to improve readability.
>> >
>> > Signed-off-by: Krzysztof Kozlowski 
>> > Acked-by: Stephen Boyd 
>> > Reviewed-by: Javier Martinez Canillas 
>> > Signed-off-by: Sylwester Nawrocki 
>> >
>> > :04 04 acbd432e11366a8eb8775942bc7b8caa476226e2 
>> > 08e3a3f98c3d4fa2a93123c3f21b2847c06b4665 M  include
>> >
>> >
>> > The whiole bisect log seems to dig around in unrelated places so at best
>> > it just narrows the window by adding some known-bad data points.
>> >
>> > git bisect start
>> > # good: [523d939ef98fd712632d93a5a2b588e477a7565e] Linux 4.7
>> > git bisect good 523d939ef98fd712632d93a5a2b588e477a7565e
>> > # bad: [ef0e1ea8856bed6ff8394d3dfe77f2cab487ecea] Merge tag 
>> > 'arc-4.8-rc4-fixes' of 
>> > git://git.kernel.org/pub/scm/linux/kernel/git/vgupta/arc
>> > git bisect bad ef0e1ea8856bed6ff8394d3dfe77f2cab487ecea
>> > # good: [e0b3f595d13b3e9ce9cdf53935e7f304c04b5b2b] affs ->d_compare(): 
>> > don't bother with ->d_inode
>> > git bisect good e0b3f595d13b3e9ce9cdf53935e7f304c04b5b2b
>> > # bad: [77a87824ed676ca8ff8482e4157d3adb284fd381] 
>> > clocksource/drivers/clps_711x: fixup for "ARM: clps711x:
>> > git bisect bad 77a87824ed676ca8ff8482e4157d3adb284fd381
>> > # bad: [27acbec338113a75b9d72aeb53149a3538031dda] Merge 
>> > git://www.linux-watchdog.org/linux-watchdog
>> > git bisect bad 27acbec338113a75b9d72aeb53149a3538031dda
>> > # bad: [7f155c702677d057d03b192ce652311de5434697] Merge tag 
>> > 'nfs-for-4.8-1' of git://git.linux-nfs.org/projects/trondmy/linux-nfs
>> > git bisect bad 7f155c702677d057d03b192ce652311de5434697
>> > # good: [797cee982eef9195736afc5e7f3b8f613c41d19a] Merge branch 
>> > 'stable-4.8' of git://git.infradead.org/users/pcmoore/audit
>> > git bisect good 797cee982eef9195736afc5e7f3b8f613c41d19a
>> > # bad: [1056c9bd2702ea1bb79abf9bd1e78c578589d247] Merge tag 
>> > 'clk-for-linus-4.8' of 
>> > git://git.kernel.org/pub/scm/linux/kernel/git/clk/linux
>> > git bisect bad 1056c9bd2702ea1bb79abf9bd1e78c578589d247
>> > # bad: [1ff435d3571199a799ba6ccfe05544dcd21b9fb3] Merge branch 
>> > 'clk-st-critical' into clk-next
>> > git bisect bad 1ff435d3571199a799ba6ccfe05544dcd21b9fb3
>> > # bad: [0e4504470667d355b53ca3c9802fdd2120c9f946] clk: samsung: 
>> > exynos5433: Add CLK_IGNORE_UNUSED flag to PCIE device
>> > git bisect bad 0e4504470667d355b53ca3c9802fdd2120c9f946
>> > # bad: [880c81b3b6604a004d56b5975c8bed47276e8bf6] clk: samsung: 
>> > exynos5440: Constify all clock initializers
>> > git bisect bad 880c81b3b6604a004d56b5975c8bed47276e8bf6
>> > # bad: [b3a96eed8e84780d300b79b58047ea277ba358b7] clk: samsung: 
>> > exynos3250: Move platform driver and of_device_id to init section
>> > git bisect bad b3a96eed8e84780d300b79b58047ea277ba358b7
>> > # bad: [4528dd8ed477bf202bd33ee48d38d656672d37f8] dt-bindings: clock: Add 
>> > watchdog and SSS clock IDs to Exynos5410
>> > git bisect bad 4528dd8ed477bf202bd33ee48d38d656672d37f8
>> > # bad: [5cd3535a27a7cf8fc4070b499d66e419e7e72b61] dt-bindings: clock: Add 
>> > PWM and USB clock IDs to Exynos5410
>> > git bisect bad 5cd3535a27a7cf8fc4070b499d66e419e7e72b61
>> > # bad: [4c5773f9f5462dcb372857813918bbfe8c0cdcdd] dt-bindings: clock: Add 
>> > license and reformat Exynos5410 clock IDs
>> > git bisect bad 4c5773f9f5462dcb372857813918bbfe8c0cdcdd
>> > # first bad commit:

Re: tg3 BUG: spinlock lockup suspected

2016-10-10 Thread Siva Reddy Kallam 
On Sun, Oct 9, 2016 at 12:35 AM, Meelis Roos  wrote:
>> > That did not go well - bisect found the following commit but that does
>> > not seem to be related at all. So probably the reproducibility is not
>> > 100% but more random.
>>
>> Now I reproduced the bug even with 4.7-rc1 so it is older than 4.7. Will
>> test further.
>
> It gets stranger and stranger - my old 4.7 image worked fine, freshly
> compiled 4.7 exhibits the same problem.
>
> Toolchain has not changed, that I know for sure.
>
> What may have changed is kernel .config. My old conf was with whatever I
> had during 4.7. Then I upgraded to 4.8-rc3 and then 4.8 and selected
> values for "make oldconfig" new entries. Then went back to 4.7-rc1 and
> then to 4.7 with this config, answering quiestion about new options when
> any appeared. Diff is not available since I do not have the old configs
> archived.
>
> Any ideas where to continue from here?
Probably, You can do fresh system installation if possible.
Any way, I will try to reproduce with 4.7 and 4.8 kernel versions.
Will let you know my response in 1-2 days.
>
>>
>> >
>> >
>> > 4c5773f9f5462dcb372857813918bbfe8c0cdcdd is the first bad commit
>> > commit 4c5773f9f5462dcb372857813918bbfe8c0cdcdd
>> > Author: Krzysztof Kozlowski 
>> > Date:   Sat May 28 11:54:12 2016 +0200
>> >
>> > dt-bindings: clock: Add license and reformat Exynos5410 clock IDs
>> >
>> > Add license and copyrights (file introduced in 2014) to header with
>> > Exynos5410 clock IDs. Additionally reformat it to improve readability.
>> >
>> > Signed-off-by: Krzysztof Kozlowski 
>> > Acked-by: Stephen Boyd 
>> > Reviewed-by: Javier Martinez Canillas 
>> > Signed-off-by: Sylwester Nawrocki 
>> >
>> > :04 04 acbd432e11366a8eb8775942bc7b8caa476226e2 
>> > 08e3a3f98c3d4fa2a93123c3f21b2847c06b4665 M  include
>> >
>> >
>> > The whiole bisect log seems to dig around in unrelated places so at best
>> > it just narrows the window by adding some known-bad data points.
>> >
>> > git bisect start
>> > # good: [523d939ef98fd712632d93a5a2b588e477a7565e] Linux 4.7
>> > git bisect good 523d939ef98fd712632d93a5a2b588e477a7565e
>> > # bad: [ef0e1ea8856bed6ff8394d3dfe77f2cab487ecea] Merge tag 
>> > 'arc-4.8-rc4-fixes' of 
>> > git://git.kernel.org/pub/scm/linux/kernel/git/vgupta/arc
>> > git bisect bad ef0e1ea8856bed6ff8394d3dfe77f2cab487ecea
>> > # good: [e0b3f595d13b3e9ce9cdf53935e7f304c04b5b2b] affs ->d_compare(): 
>> > don't bother with ->d_inode
>> > git bisect good e0b3f595d13b3e9ce9cdf53935e7f304c04b5b2b
>> > # bad: [77a87824ed676ca8ff8482e4157d3adb284fd381] 
>> > clocksource/drivers/clps_711x: fixup for "ARM: clps711x:
>> > git bisect bad 77a87824ed676ca8ff8482e4157d3adb284fd381
>> > # bad: [27acbec338113a75b9d72aeb53149a3538031dda] Merge 
>> > git://www.linux-watchdog.org/linux-watchdog
>> > git bisect bad 27acbec338113a75b9d72aeb53149a3538031dda
>> > # bad: [7f155c702677d057d03b192ce652311de5434697] Merge tag 
>> > 'nfs-for-4.8-1' of git://git.linux-nfs.org/projects/trondmy/linux-nfs
>> > git bisect bad 7f155c702677d057d03b192ce652311de5434697
>> > # good: [797cee982eef9195736afc5e7f3b8f613c41d19a] Merge branch 
>> > 'stable-4.8' of git://git.infradead.org/users/pcmoore/audit
>> > git bisect good 797cee982eef9195736afc5e7f3b8f613c41d19a
>> > # bad: [1056c9bd2702ea1bb79abf9bd1e78c578589d247] Merge tag 
>> > 'clk-for-linus-4.8' of 
>> > git://git.kernel.org/pub/scm/linux/kernel/git/clk/linux
>> > git bisect bad 1056c9bd2702ea1bb79abf9bd1e78c578589d247
>> > # bad: [1ff435d3571199a799ba6ccfe05544dcd21b9fb3] Merge branch 
>> > 'clk-st-critical' into clk-next
>> > git bisect bad 1ff435d3571199a799ba6ccfe05544dcd21b9fb3
>> > # bad: [0e4504470667d355b53ca3c9802fdd2120c9f946] clk: samsung: 
>> > exynos5433: Add CLK_IGNORE_UNUSED flag to PCIE device
>> > git bisect bad 0e4504470667d355b53ca3c9802fdd2120c9f946
>> > # bad: [880c81b3b6604a004d56b5975c8bed47276e8bf6] clk: samsung: 
>> > exynos5440: Constify all clock initializers
>> > git bisect bad 880c81b3b6604a004d56b5975c8bed47276e8bf6
>> > # bad: [b3a96eed8e84780d300b79b58047ea277ba358b7] clk: samsung: 
>> > exynos3250: Move platform driver and of_device_id to init section
>> > git bisect bad b3a96eed8e84780d300b79b58047ea277ba358b7
>> > # bad: [4528dd8ed477bf202bd33ee48d38d656672d37f8] dt-bindings: clock: Add 
>> > watchdog and SSS clock IDs to Exynos5410
>> > git bisect bad 4528dd8ed477bf202bd33ee48d38d656672d37f8
>> > # bad: [5cd3535a27a7cf8fc4070b499d66e419e7e72b61] dt-bindings: clock: Add 
>> > PWM and USB clock IDs to Exynos5410
>> > git bisect bad 5cd3535a27a7cf8fc4070b499d66e419e7e72b61
>> > # bad: [4c5773f9f5462dcb372857813918bbfe8c0cdcdd] dt-bindings: clock: Add 
>> > license and reformat Exynos5410 clock IDs
>> > git bisect bad 4c5773f9f5462dcb372857813918bbfe8c0cdcdd
>> > # first bad commit: [4c5773f9f5462dcb372857813918bbfe8c0cdcdd] 
>> > dt-bindings: clock: Add license and reformat Exynos5410 clock IDs
>> >
>> >
>> > >
>> > > [   74.123859]

Re: tg3 BUG: spinlock lockup suspected

2016-10-08 Thread Meelis Roos 
> > That did not go well - bisect found the following commit but that does 
> > not seem to be related at all. So probably the reproducibility is not 
> > 100% but more random.
> 
> Now I reproduced the bug even with 4.7-rc1 so it is older than 4.7. Will 
> test further.

It gets stranger and stranger - my old 4.7 image worked fine, freshly 
compiled 4.7 exhibits the same problem.

Toolchain has not changed, that I know for sure.

What may have changed is kernel .config. My old conf was with whatever I 
had during 4.7. Then I upgraded to 4.8-rc3 and then 4.8 and selected 
values for "make oldconfig" new entries. Then went back to 4.7-rc1 and 
then to 4.7 with this config, answering quiestion about new options when 
any appeared. Diff is not available since I do not have the old configs 
archived.

Any ideas where to continue from here?

> 
> > 
> > 
> > 4c5773f9f5462dcb372857813918bbfe8c0cdcdd is the first bad commit
> > commit 4c5773f9f5462dcb372857813918bbfe8c0cdcdd
> > Author: Krzysztof Kozlowski 
> > Date:   Sat May 28 11:54:12 2016 +0200
> > 
> > dt-bindings: clock: Add license and reformat Exynos5410 clock IDs
> > 
> > Add license and copyrights (file introduced in 2014) to header with
> > Exynos5410 clock IDs. Additionally reformat it to improve readability.
> > 
> > Signed-off-by: Krzysztof Kozlowski 
> > Acked-by: Stephen Boyd 
> > Reviewed-by: Javier Martinez Canillas 
> > Signed-off-by: Sylwester Nawrocki 
> > 
> > :04 04 acbd432e11366a8eb8775942bc7b8caa476226e2 
> > 08e3a3f98c3d4fa2a93123c3f21b2847c06b4665 M  include
> > 
> > 
> > The whiole bisect log seems to dig around in unrelated places so at best 
> > it just narrows the window by adding some known-bad data points.
> > 
> > git bisect start
> > # good: [523d939ef98fd712632d93a5a2b588e477a7565e] Linux 4.7
> > git bisect good 523d939ef98fd712632d93a5a2b588e477a7565e
> > # bad: [ef0e1ea8856bed6ff8394d3dfe77f2cab487ecea] Merge tag 
> > 'arc-4.8-rc4-fixes' of 
> > git://git.kernel.org/pub/scm/linux/kernel/git/vgupta/arc
> > git bisect bad ef0e1ea8856bed6ff8394d3dfe77f2cab487ecea
> > # good: [e0b3f595d13b3e9ce9cdf53935e7f304c04b5b2b] affs ->d_compare(): 
> > don't bother with ->d_inode
> > git bisect good e0b3f595d13b3e9ce9cdf53935e7f304c04b5b2b
> > # bad: [77a87824ed676ca8ff8482e4157d3adb284fd381] 
> > clocksource/drivers/clps_711x: fixup for "ARM: clps711x:
> > git bisect bad 77a87824ed676ca8ff8482e4157d3adb284fd381
> > # bad: [27acbec338113a75b9d72aeb53149a3538031dda] Merge 
> > git://www.linux-watchdog.org/linux-watchdog
> > git bisect bad 27acbec338113a75b9d72aeb53149a3538031dda
> > # bad: [7f155c702677d057d03b192ce652311de5434697] Merge tag 'nfs-for-4.8-1' 
> > of git://git.linux-nfs.org/projects/trondmy/linux-nfs
> > git bisect bad 7f155c702677d057d03b192ce652311de5434697
> > # good: [797cee982eef9195736afc5e7f3b8f613c41d19a] Merge branch 
> > 'stable-4.8' of git://git.infradead.org/users/pcmoore/audit
> > git bisect good 797cee982eef9195736afc5e7f3b8f613c41d19a
> > # bad: [1056c9bd2702ea1bb79abf9bd1e78c578589d247] Merge tag 
> > 'clk-for-linus-4.8' of 
> > git://git.kernel.org/pub/scm/linux/kernel/git/clk/linux
> > git bisect bad 1056c9bd2702ea1bb79abf9bd1e78c578589d247
> > # bad: [1ff435d3571199a799ba6ccfe05544dcd21b9fb3] Merge branch 
> > 'clk-st-critical' into clk-next
> > git bisect bad 1ff435d3571199a799ba6ccfe05544dcd21b9fb3
> > # bad: [0e4504470667d355b53ca3c9802fdd2120c9f946] clk: samsung: exynos5433: 
> > Add CLK_IGNORE_UNUSED flag to PCIE device
> > git bisect bad 0e4504470667d355b53ca3c9802fdd2120c9f946
> > # bad: [880c81b3b6604a004d56b5975c8bed47276e8bf6] clk: samsung: exynos5440: 
> > Constify all clock initializers
> > git bisect bad 880c81b3b6604a004d56b5975c8bed47276e8bf6
> > # bad: [b3a96eed8e84780d300b79b58047ea277ba358b7] clk: samsung: exynos3250: 
> > Move platform driver and of_device_id to init section
> > git bisect bad b3a96eed8e84780d300b79b58047ea277ba358b7
> > # bad: [4528dd8ed477bf202bd33ee48d38d656672d37f8] dt-bindings: clock: Add 
> > watchdog and SSS clock IDs to Exynos5410
> > git bisect bad 4528dd8ed477bf202bd33ee48d38d656672d37f8
> > # bad: [5cd3535a27a7cf8fc4070b499d66e419e7e72b61] dt-bindings: clock: Add 
> > PWM and USB clock IDs to Exynos5410
> > git bisect bad 5cd3535a27a7cf8fc4070b499d66e419e7e72b61
> > # bad: [4c5773f9f5462dcb372857813918bbfe8c0cdcdd] dt-bindings: clock: Add 
> > license and reformat Exynos5410 clock IDs
> > git bisect bad 4c5773f9f5462dcb372857813918bbfe8c0cdcdd
> > # first bad commit: [4c5773f9f5462dcb372857813918bbfe8c0cdcdd] dt-bindings: 
> > clock: Add license and reformat Exynos5410 clock IDs
> > 
> > 
> > > 
> > > [   74.123859] tg3.c:v3.137 (May 11, 2014)
> > > [   74.123880] PCI: Enabling device: (:00:02.0), cmd 2
> > > [   74.315794] tg3 :00:02.0 (unnamed net_device) (uninitialized): 
> > > Cannot get nvram

Re: tg3 BUG: spinlock lockup suspected

2016-10-08 Thread Meelis Roos 
> > That did not go well - bisect found the following commit but that does 
> > not seem to be related at all. So probably the reproducibility is not 
> > 100% but more random.
> 
> Now I reproduced the bug even with 4.7-rc1 so it is older than 4.7. Will 
> test further.

It gets stranger and stranger - my old 4.7 image worked fine, freshly 
compiled 4.7 exhibits the same problem.

Toolchain has not changed, that I know for sure.

What may have changed is kernel .config. My old conf was with whatever I 
had during 4.7. Then I upgraded to 4.8-rc3 and then 4.8 and selected 
values for "make oldconfig" new entries. Then went back to 4.7-rc1 and 
then to 4.7 with this config, answering quiestion about new options when 
any appeared. Diff is not available since I do not have the old configs 
archived.

Any ideas where to continue from here?

> 
> > 
> > 
> > 4c5773f9f5462dcb372857813918bbfe8c0cdcdd is the first bad commit
> > commit 4c5773f9f5462dcb372857813918bbfe8c0cdcdd
> > Author: Krzysztof Kozlowski 
> > Date:   Sat May 28 11:54:12 2016 +0200
> > 
> > dt-bindings: clock: Add license and reformat Exynos5410 clock IDs
> > 
> > Add license and copyrights (file introduced in 2014) to header with
> > Exynos5410 clock IDs. Additionally reformat it to improve readability.
> > 
> > Signed-off-by: Krzysztof Kozlowski 
> > Acked-by: Stephen Boyd 
> > Reviewed-by: Javier Martinez Canillas 
> > Signed-off-by: Sylwester Nawrocki 
> > 
> > :04 04 acbd432e11366a8eb8775942bc7b8caa476226e2 
> > 08e3a3f98c3d4fa2a93123c3f21b2847c06b4665 M  include
> > 
> > 
> > The whiole bisect log seems to dig around in unrelated places so at best 
> > it just narrows the window by adding some known-bad data points.
> > 
> > git bisect start
> > # good: [523d939ef98fd712632d93a5a2b588e477a7565e] Linux 4.7
> > git bisect good 523d939ef98fd712632d93a5a2b588e477a7565e
> > # bad: [ef0e1ea8856bed6ff8394d3dfe77f2cab487ecea] Merge tag 
> > 'arc-4.8-rc4-fixes' of 
> > git://git.kernel.org/pub/scm/linux/kernel/git/vgupta/arc
> > git bisect bad ef0e1ea8856bed6ff8394d3dfe77f2cab487ecea
> > # good: [e0b3f595d13b3e9ce9cdf53935e7f304c04b5b2b] affs ->d_compare(): 
> > don't bother with ->d_inode
> > git bisect good e0b3f595d13b3e9ce9cdf53935e7f304c04b5b2b
> > # bad: [77a87824ed676ca8ff8482e4157d3adb284fd381] 
> > clocksource/drivers/clps_711x: fixup for "ARM: clps711x:
> > git bisect bad 77a87824ed676ca8ff8482e4157d3adb284fd381
> > # bad: [27acbec338113a75b9d72aeb53149a3538031dda] Merge 
> > git://www.linux-watchdog.org/linux-watchdog
> > git bisect bad 27acbec338113a75b9d72aeb53149a3538031dda
> > # bad: [7f155c702677d057d03b192ce652311de5434697] Merge tag 'nfs-for-4.8-1' 
> > of git://git.linux-nfs.org/projects/trondmy/linux-nfs
> > git bisect bad 7f155c702677d057d03b192ce652311de5434697
> > # good: [797cee982eef9195736afc5e7f3b8f613c41d19a] Merge branch 
> > 'stable-4.8' of git://git.infradead.org/users/pcmoore/audit
> > git bisect good 797cee982eef9195736afc5e7f3b8f613c41d19a
> > # bad: [1056c9bd2702ea1bb79abf9bd1e78c578589d247] Merge tag 
> > 'clk-for-linus-4.8' of 
> > git://git.kernel.org/pub/scm/linux/kernel/git/clk/linux
> > git bisect bad 1056c9bd2702ea1bb79abf9bd1e78c578589d247
> > # bad: [1ff435d3571199a799ba6ccfe05544dcd21b9fb3] Merge branch 
> > 'clk-st-critical' into clk-next
> > git bisect bad 1ff435d3571199a799ba6ccfe05544dcd21b9fb3
> > # bad: [0e4504470667d355b53ca3c9802fdd2120c9f946] clk: samsung: exynos5433: 
> > Add CLK_IGNORE_UNUSED flag to PCIE device
> > git bisect bad 0e4504470667d355b53ca3c9802fdd2120c9f946
> > # bad: [880c81b3b6604a004d56b5975c8bed47276e8bf6] clk: samsung: exynos5440: 
> > Constify all clock initializers
> > git bisect bad 880c81b3b6604a004d56b5975c8bed47276e8bf6
> > # bad: [b3a96eed8e84780d300b79b58047ea277ba358b7] clk: samsung: exynos3250: 
> > Move platform driver and of_device_id to init section
> > git bisect bad b3a96eed8e84780d300b79b58047ea277ba358b7
> > # bad: [4528dd8ed477bf202bd33ee48d38d656672d37f8] dt-bindings: clock: Add 
> > watchdog and SSS clock IDs to Exynos5410
> > git bisect bad 4528dd8ed477bf202bd33ee48d38d656672d37f8
> > # bad: [5cd3535a27a7cf8fc4070b499d66e419e7e72b61] dt-bindings: clock: Add 
> > PWM and USB clock IDs to Exynos5410
> > git bisect bad 5cd3535a27a7cf8fc4070b499d66e419e7e72b61
> > # bad: [4c5773f9f5462dcb372857813918bbfe8c0cdcdd] dt-bindings: clock: Add 
> > license and reformat Exynos5410 clock IDs
> > git bisect bad 4c5773f9f5462dcb372857813918bbfe8c0cdcdd
> > # first bad commit: [4c5773f9f5462dcb372857813918bbfe8c0cdcdd] dt-bindings: 
> > clock: Add license and reformat Exynos5410 clock IDs
> > 
> > 
> > > 
> > > [   74.123859] tg3.c:v3.137 (May 11, 2014)
> > > [   74.123880] PCI: Enabling device: (:00:02.0), cmd 2
> > > [   74.315794] tg3 :00:02.0 (unnamed net_device) (uninitialized): 
> > > Cannot get nvram lock, tg3_nvram_init failed
> > > [   74.656152] tg3 :00:02.0 eth0: Tigon3 [partno(none) rev 2003] 
> >

Re: tg3 BUG: spinlock lockup suspected

2016-10-08 Thread Meelis Roos 
> On Sat, Oct 8, 2016 at 10:15 PM, Meelis Roos  wrote:
> >> That did not go well - bisect found the following commit but that does
> >> not seem to be related at all. So probably the reproducibility is not
> >> 100% but more random.
> >
> > Now I reproduced the bug even with 4.7-rc1 so it is older than 4.7. Will
> > test further.
> >
> Thanks for reporting this. We will look into this.
> Any specific steps to reproduce this?

I just boot up my Sun Fire V210 and I get the warning during bootup. Net 
is working fine after that. Config below.

#
# Automatically generated file; DO NOT EDIT.
# Linux/sparc64 4.7.0 Kernel Configuration
#
CONFIG_64BIT=y
CONFIG_SPARC=y
# CONFIG_SPARC32 is not set
CONFIG_SPARC64=y
CONFIG_ARCH_DEFCONFIG="arch/sparc/configs/sparc64_defconfig"
CONFIG_ARCH_PROC_KCORE_TEXT=y
CONFIG_IOMMU_HELPER=y
CONFIG_STACKTRACE_SUPPORT=y
CONFIG_LOCKDEP_SUPPORT=y
CONFIG_ARCH_HIBERNATION_POSSIBLE=y
CONFIG_AUDIT_ARCH=y
CONFIG_HAVE_SETUP_PER_CPU_AREA=y
CONFIG_NEED_PER_CPU_EMBED_FIRST_CHUNK=y
CONFIG_NEED_PER_CPU_PAGE_FIRST_CHUNK=y
CONFIG_MMU=y
CONFIG_NEED_DMA_MAP_STATE=y
CONFIG_NEED_SG_DMA_LENGTH=y
CONFIG_ARCH_SUPPORTS_DEBUG_PAGEALLOC=y
CONFIG_PGTABLE_LEVELS=4
CONFIG_DEFCONFIG_LIST="/lib/modules/$UNAME_RELEASE/.config"
CONFIG_CONSTRUCTORS=y
CONFIG_IRQ_WORK=y

#
# General setup
#
CONFIG_INIT_ENV_ARG_LIMIT=32
CONFIG_CROSS_COMPILE=""
# CONFIG_COMPILE_TEST is not set
CONFIG_LOCALVERSION=""
CONFIG_LOCALVERSION_AUTO=y
CONFIG_DEFAULT_HOSTNAME="(none)"
CONFIG_SWAP=y
CONFIG_SYSVIPC=y
CONFIG_SYSVIPC_SYSCTL=y
CONFIG_POSIX_MQUEUE=y
CONFIG_POSIX_MQUEUE_SYSCTL=y
CONFIG_CROSS_MEMORY_ATTACH=y
CONFIG_FHANDLE=y
# CONFIG_USELIB is not set
# CONFIG_AUDIT is not set
CONFIG_HAVE_ARCH_AUDITSYSCALL=y

#
# IRQ subsystem
#
CONFIG_GENERIC_IRQ_SHOW=y
CONFIG_IRQ_PREFLOW_FASTEOI=y
CONFIG_GENERIC_MSI_IRQ=y
CONFIG_SPARSE_IRQ=y
CONFIG_GENERIC_CLOCKEVENTS=y

#
# Timers subsystem
#
CONFIG_TICK_ONESHOT=y
CONFIG_NO_HZ_COMMON=y
# CONFIG_HZ_PERIODIC is not set
CONFIG_NO_HZ_IDLE=y
# CONFIG_NO_HZ_FULL is not set
CONFIG_NO_HZ=y
CONFIG_HIGH_RES_TIMERS=y

#
# CPU/Task time and stats accounting
#
CONFIG_TICK_CPU_ACCOUNTING=y
# CONFIG_VIRT_CPU_ACCOUNTING_GEN is not set
# CONFIG_BSD_PROCESS_ACCT is not set
CONFIG_TASKSTATS=y
CONFIG_TASK_DELAY_ACCT=y
CONFIG_TASK_XACCT=y
CONFIG_TASK_IO_ACCOUNTING=y

#
# RCU Subsystem
#
CONFIG_TREE_RCU=y
# CONFIG_RCU_EXPERT is not set
CONFIG_SRCU=y
# CONFIG_TASKS_RCU is not set
CONFIG_RCU_STALL_COMMON=y
# CONFIG_TREE_RCU_TRACE is not set
# CONFIG_RCU_EXPEDITE_BOOT is not set
# CONFIG_BUILD_BIN2C is not set
# CONFIG_IKCONFIG is not set
CONFIG_LOG_BUF_SHIFT=17
CONFIG_LOG_CPU_MAX_BUF_SHIFT=12
CONFIG_NMI_LOG_BUF_SHIFT=13
CONFIG_CGROUPS=y
CONFIG_PAGE_COUNTER=y
CONFIG_MEMCG=y
CONFIG_MEMCG_SWAP=y
CONFIG_MEMCG_SWAP_ENABLED=y
CONFIG_BLK_CGROUP=y
CONFIG_DEBUG_BLK_CGROUP=y
CONFIG_CGROUP_WRITEBACK=y
CONFIG_CGROUP_SCHED=y
CONFIG_FAIR_GROUP_SCHED=y
CONFIG_CFS_BANDWIDTH=y
CONFIG_RT_GROUP_SCHED=y
CONFIG_CGROUP_PIDS=y
CONFIG_CGROUP_FREEZER=y
CONFIG_CGROUP_HUGETLB=y
CONFIG_CPUSETS=y
CONFIG_PROC_PID_CPUSET=y
CONFIG_CGROUP_DEVICE=y
CONFIG_CGROUP_CPUACCT=y
# CONFIG_CGROUP_PERF is not set
# CONFIG_CGROUP_DEBUG is not set
# CONFIG_CHECKPOINT_RESTORE is not set
CONFIG_NAMESPACES=y
CONFIG_UTS_NS=y
CONFIG_IPC_NS=y
# CONFIG_USER_NS is not set
CONFIG_PID_NS=y
CONFIG_NET_NS=y
# CONFIG_SCHED_AUTOGROUP is not set
# CONFIG_SYSFS_DEPRECATED is not set
# CONFIG_RELAY is not set
# CONFIG_BLK_DEV_INITRD is not set
CONFIG_CC_OPTIMIZE_FOR_PERFORMANCE=y
# CONFIG_CC_OPTIMIZE_FOR_SIZE is not set
CONFIG_SYSCTL=y
CONFIG_ANON_INODES=y
CONFIG_HAVE_UID16=y
CONFIG_SYSCTL_EXCEPTION_TRACE=y
CONFIG_BPF=y
# CONFIG_EXPERT is not set
CONFIG_UID16=y
CONFIG_MULTIUSER=y
CONFIG_SGETMASK_SYSCALL=y
CONFIG_SYSFS_SYSCALL=y
# CONFIG_SYSCTL_SYSCALL is not set
CONFIG_KALLSYMS=y
CONFIG_KALLSYMS_ALL=y
# CONFIG_KALLSYMS_ABSOLUTE_PERCPU is not set
CONFIG_KALLSYMS_BASE_RELATIVE=y
CONFIG_PRINTK=y
CONFIG_PRINTK_NMI=y
CONFIG_BUG=y
CONFIG_ELF_CORE=y
CONFIG_BASE_FULL=y
CONFIG_FUTEX=y
CONFIG_EPOLL=y
CONFIG_SIGNALFD=y
CONFIG_TIMERFD=y
CONFIG_EVENTFD=y
# CONFIG_BPF_SYSCALL is not set
CONFIG_SHMEM=y
CONFIG_AIO=y
CONFIG_ADVISE_SYSCALLS=y
CONFIG_USERFAULTFD=y
CONFIG_PCI_QUIRKS=y
CONFIG_MEMBARRIER=y
# CONFIG_EMBEDDED is not set
CONFIG_HAVE_PERF_EVENTS=y
CONFIG_PERF_USE_VMALLOC=y

#
# Kernel Performance Events And Counters
#
CONFIG_PERF_EVENTS=y
# CONFIG_DEBUG_PERF_USE_VMALLOC is not set
CONFIG_VM_EVENT_COUNTERS=y
CONFIG_SLUB_DEBUG=y
# CONFIG_COMPAT_BRK is not set
# CONFIG_SLAB is not set
CONFIG_SLUB=y
CONFIG_SLUB_CPU_PARTIAL=y
# CONFIG_SYSTEM_DATA_VERIFICATION is not set
# CONFIG_PROFILING is not set
CONFIG_HAVE_OPROFILE=y
# CONFIG_KPROBES is not set
CONFIG_JUMP_LABEL=y
# CONFIG_STATIC_KEYS_SELFTEST is not set
# CONFIG_UPROBES is not set
CONFIG_HAVE_64BIT_ALIGNED_ACCESS=y
CONFIG_HAVE_KPROBES=y
CONFIG_HAVE_KRETPROBES=y
CONFIG_HAVE_NMI=y
CONFIG_HAVE_NMI_WATCHDOG=y
CONFIG_HAVE_ARCH_TRACEHOOK=y
CONFIG_GENERIC_SMP_IDLE_THREAD=y
CONFIG_HAVE_DMA_API_DEBUG=y
CONFIG_HAVE_ARCH_JUMP_LABEL=y

Re: tg3 BUG: spinlock lockup suspected

2016-10-08 Thread Meelis Roos 
> On Sat, Oct 8, 2016 at 10:15 PM, Meelis Roos  wrote:
> >> That did not go well - bisect found the following commit but that does
> >> not seem to be related at all. So probably the reproducibility is not
> >> 100% but more random.
> >
> > Now I reproduced the bug even with 4.7-rc1 so it is older than 4.7. Will
> > test further.
> >
> Thanks for reporting this. We will look into this.
> Any specific steps to reproduce this?

I just boot up my Sun Fire V210 and I get the warning during bootup. Net 
is working fine after that. Config below.

#
# Automatically generated file; DO NOT EDIT.
# Linux/sparc64 4.7.0 Kernel Configuration
#
CONFIG_64BIT=y
CONFIG_SPARC=y
# CONFIG_SPARC32 is not set
CONFIG_SPARC64=y
CONFIG_ARCH_DEFCONFIG="arch/sparc/configs/sparc64_defconfig"
CONFIG_ARCH_PROC_KCORE_TEXT=y
CONFIG_IOMMU_HELPER=y
CONFIG_STACKTRACE_SUPPORT=y
CONFIG_LOCKDEP_SUPPORT=y
CONFIG_ARCH_HIBERNATION_POSSIBLE=y
CONFIG_AUDIT_ARCH=y
CONFIG_HAVE_SETUP_PER_CPU_AREA=y
CONFIG_NEED_PER_CPU_EMBED_FIRST_CHUNK=y
CONFIG_NEED_PER_CPU_PAGE_FIRST_CHUNK=y
CONFIG_MMU=y
CONFIG_NEED_DMA_MAP_STATE=y
CONFIG_NEED_SG_DMA_LENGTH=y
CONFIG_ARCH_SUPPORTS_DEBUG_PAGEALLOC=y
CONFIG_PGTABLE_LEVELS=4
CONFIG_DEFCONFIG_LIST="/lib/modules/$UNAME_RELEASE/.config"
CONFIG_CONSTRUCTORS=y
CONFIG_IRQ_WORK=y

#
# General setup
#
CONFIG_INIT_ENV_ARG_LIMIT=32
CONFIG_CROSS_COMPILE=""
# CONFIG_COMPILE_TEST is not set
CONFIG_LOCALVERSION=""
CONFIG_LOCALVERSION_AUTO=y
CONFIG_DEFAULT_HOSTNAME="(none)"
CONFIG_SWAP=y
CONFIG_SYSVIPC=y
CONFIG_SYSVIPC_SYSCTL=y
CONFIG_POSIX_MQUEUE=y
CONFIG_POSIX_MQUEUE_SYSCTL=y
CONFIG_CROSS_MEMORY_ATTACH=y
CONFIG_FHANDLE=y
# CONFIG_USELIB is not set
# CONFIG_AUDIT is not set
CONFIG_HAVE_ARCH_AUDITSYSCALL=y

#
# IRQ subsystem
#
CONFIG_GENERIC_IRQ_SHOW=y
CONFIG_IRQ_PREFLOW_FASTEOI=y
CONFIG_GENERIC_MSI_IRQ=y
CONFIG_SPARSE_IRQ=y
CONFIG_GENERIC_CLOCKEVENTS=y

#
# Timers subsystem
#
CONFIG_TICK_ONESHOT=y
CONFIG_NO_HZ_COMMON=y
# CONFIG_HZ_PERIODIC is not set
CONFIG_NO_HZ_IDLE=y
# CONFIG_NO_HZ_FULL is not set
CONFIG_NO_HZ=y
CONFIG_HIGH_RES_TIMERS=y

#
# CPU/Task time and stats accounting
#
CONFIG_TICK_CPU_ACCOUNTING=y
# CONFIG_VIRT_CPU_ACCOUNTING_GEN is not set
# CONFIG_BSD_PROCESS_ACCT is not set
CONFIG_TASKSTATS=y
CONFIG_TASK_DELAY_ACCT=y
CONFIG_TASK_XACCT=y
CONFIG_TASK_IO_ACCOUNTING=y

#
# RCU Subsystem
#
CONFIG_TREE_RCU=y
# CONFIG_RCU_EXPERT is not set
CONFIG_SRCU=y
# CONFIG_TASKS_RCU is not set
CONFIG_RCU_STALL_COMMON=y
# CONFIG_TREE_RCU_TRACE is not set
# CONFIG_RCU_EXPEDITE_BOOT is not set
# CONFIG_BUILD_BIN2C is not set
# CONFIG_IKCONFIG is not set
CONFIG_LOG_BUF_SHIFT=17
CONFIG_LOG_CPU_MAX_BUF_SHIFT=12
CONFIG_NMI_LOG_BUF_SHIFT=13
CONFIG_CGROUPS=y
CONFIG_PAGE_COUNTER=y
CONFIG_MEMCG=y
CONFIG_MEMCG_SWAP=y
CONFIG_MEMCG_SWAP_ENABLED=y
CONFIG_BLK_CGROUP=y
CONFIG_DEBUG_BLK_CGROUP=y
CONFIG_CGROUP_WRITEBACK=y
CONFIG_CGROUP_SCHED=y
CONFIG_FAIR_GROUP_SCHED=y
CONFIG_CFS_BANDWIDTH=y
CONFIG_RT_GROUP_SCHED=y
CONFIG_CGROUP_PIDS=y
CONFIG_CGROUP_FREEZER=y
CONFIG_CGROUP_HUGETLB=y
CONFIG_CPUSETS=y
CONFIG_PROC_PID_CPUSET=y
CONFIG_CGROUP_DEVICE=y
CONFIG_CGROUP_CPUACCT=y
# CONFIG_CGROUP_PERF is not set
# CONFIG_CGROUP_DEBUG is not set
# CONFIG_CHECKPOINT_RESTORE is not set
CONFIG_NAMESPACES=y
CONFIG_UTS_NS=y
CONFIG_IPC_NS=y
# CONFIG_USER_NS is not set
CONFIG_PID_NS=y
CONFIG_NET_NS=y
# CONFIG_SCHED_AUTOGROUP is not set
# CONFIG_SYSFS_DEPRECATED is not set
# CONFIG_RELAY is not set
# CONFIG_BLK_DEV_INITRD is not set
CONFIG_CC_OPTIMIZE_FOR_PERFORMANCE=y
# CONFIG_CC_OPTIMIZE_FOR_SIZE is not set
CONFIG_SYSCTL=y
CONFIG_ANON_INODES=y
CONFIG_HAVE_UID16=y
CONFIG_SYSCTL_EXCEPTION_TRACE=y
CONFIG_BPF=y
# CONFIG_EXPERT is not set
CONFIG_UID16=y
CONFIG_MULTIUSER=y
CONFIG_SGETMASK_SYSCALL=y
CONFIG_SYSFS_SYSCALL=y
# CONFIG_SYSCTL_SYSCALL is not set
CONFIG_KALLSYMS=y
CONFIG_KALLSYMS_ALL=y
# CONFIG_KALLSYMS_ABSOLUTE_PERCPU is not set
CONFIG_KALLSYMS_BASE_RELATIVE=y
CONFIG_PRINTK=y
CONFIG_PRINTK_NMI=y
CONFIG_BUG=y
CONFIG_ELF_CORE=y
CONFIG_BASE_FULL=y
CONFIG_FUTEX=y
CONFIG_EPOLL=y
CONFIG_SIGNALFD=y
CONFIG_TIMERFD=y
CONFIG_EVENTFD=y
# CONFIG_BPF_SYSCALL is not set
CONFIG_SHMEM=y
CONFIG_AIO=y
CONFIG_ADVISE_SYSCALLS=y
CONFIG_USERFAULTFD=y
CONFIG_PCI_QUIRKS=y
CONFIG_MEMBARRIER=y
# CONFIG_EMBEDDED is not set
CONFIG_HAVE_PERF_EVENTS=y
CONFIG_PERF_USE_VMALLOC=y

#
# Kernel Performance Events And Counters
#
CONFIG_PERF_EVENTS=y
# CONFIG_DEBUG_PERF_USE_VMALLOC is not set
CONFIG_VM_EVENT_COUNTERS=y
CONFIG_SLUB_DEBUG=y
# CONFIG_COMPAT_BRK is not set
# CONFIG_SLAB is not set
CONFIG_SLUB=y
CONFIG_SLUB_CPU_PARTIAL=y
# CONFIG_SYSTEM_DATA_VERIFICATION is not set
# CONFIG_PROFILING is not set
CONFIG_HAVE_OPROFILE=y
# CONFIG_KPROBES is not set
CONFIG_JUMP_LABEL=y
# CONFIG_STATIC_KEYS_SELFTEST is not set
# CONFIG_UPROBES is not set
CONFIG_HAVE_64BIT_ALIGNED_ACCESS=y
CONFIG_HAVE_KPROBES=y
CONFIG_HAVE_KRETPROBES=y
CONFIG_HAVE_NMI=y
CONFIG_HAVE_NMI_WATCHDOG=y
CONFIG_HAVE_ARCH_TRACEHOOK=y
CONFIG_GENERIC_SMP_IDLE_THREAD=y
CONFIG_HAVE_DMA_API_DEBUG=y
CONFIG_HAVE_ARCH_JUMP_LABEL=y

Re: tg3 BUG: spinlock lockup suspected

2016-10-08 Thread Siva Reddy Kallam 
On Sat, Oct 8, 2016 at 10:15 PM, Meelis Roos  wrote:
>> That did not go well - bisect found the following commit but that does
>> not seem to be related at all. So probably the reproducibility is not
>> 100% but more random.
>
> Now I reproduced the bug even with 4.7-rc1 so it is older than 4.7. Will
> test further.
>
Thanks for reporting this. We will look into this.
Any specific steps to reproduce this?
>>
>>
>> 4c5773f9f5462dcb372857813918bbfe8c0cdcdd is the first bad commit
>> commit 4c5773f9f5462dcb372857813918bbfe8c0cdcdd
>> Author: Krzysztof Kozlowski 
>> Date:   Sat May 28 11:54:12 2016 +0200
>>
>> dt-bindings: clock: Add license and reformat Exynos5410 clock IDs
>>
>> Add license and copyrights (file introduced in 2014) to header with
>> Exynos5410 clock IDs. Additionally reformat it to improve readability.
>>
>> Signed-off-by: Krzysztof Kozlowski 
>> Acked-by: Stephen Boyd 
>> Reviewed-by: Javier Martinez Canillas 
>> Signed-off-by: Sylwester Nawrocki 
>>
>> :04 04 acbd432e11366a8eb8775942bc7b8caa476226e2 
>> 08e3a3f98c3d4fa2a93123c3f21b2847c06b4665 M  include
>>
>>
>> The whiole bisect log seems to dig around in unrelated places so at best
>> it just narrows the window by adding some known-bad data points.
>>
>> git bisect start
>> # good: [523d939ef98fd712632d93a5a2b588e477a7565e] Linux 4.7
>> git bisect good 523d939ef98fd712632d93a5a2b588e477a7565e
>> # bad: [ef0e1ea8856bed6ff8394d3dfe77f2cab487ecea] Merge tag 
>> 'arc-4.8-rc4-fixes' of 
>> git://git.kernel.org/pub/scm/linux/kernel/git/vgupta/arc
>> git bisect bad ef0e1ea8856bed6ff8394d3dfe77f2cab487ecea
>> # good: [e0b3f595d13b3e9ce9cdf53935e7f304c04b5b2b] affs ->d_compare(): don't 
>> bother with ->d_inode
>> git bisect good e0b3f595d13b3e9ce9cdf53935e7f304c04b5b2b
>> # bad: [77a87824ed676ca8ff8482e4157d3adb284fd381] 
>> clocksource/drivers/clps_711x: fixup for "ARM: clps711x:
>> git bisect bad 77a87824ed676ca8ff8482e4157d3adb284fd381
>> # bad: [27acbec338113a75b9d72aeb53149a3538031dda] Merge 
>> git://www.linux-watchdog.org/linux-watchdog
>> git bisect bad 27acbec338113a75b9d72aeb53149a3538031dda
>> # bad: [7f155c702677d057d03b192ce652311de5434697] Merge tag 'nfs-for-4.8-1' 
>> of git://git.linux-nfs.org/projects/trondmy/linux-nfs
>> git bisect bad 7f155c702677d057d03b192ce652311de5434697
>> # good: [797cee982eef9195736afc5e7f3b8f613c41d19a] Merge branch 'stable-4.8' 
>> of git://git.infradead.org/users/pcmoore/audit
>> git bisect good 797cee982eef9195736afc5e7f3b8f613c41d19a
>> # bad: [1056c9bd2702ea1bb79abf9bd1e78c578589d247] Merge tag 
>> 'clk-for-linus-4.8' of 
>> git://git.kernel.org/pub/scm/linux/kernel/git/clk/linux
>> git bisect bad 1056c9bd2702ea1bb79abf9bd1e78c578589d247
>> # bad: [1ff435d3571199a799ba6ccfe05544dcd21b9fb3] Merge branch 
>> 'clk-st-critical' into clk-next
>> git bisect bad 1ff435d3571199a799ba6ccfe05544dcd21b9fb3
>> # bad: [0e4504470667d355b53ca3c9802fdd2120c9f946] clk: samsung: exynos5433: 
>> Add CLK_IGNORE_UNUSED flag to PCIE device
>> git bisect bad 0e4504470667d355b53ca3c9802fdd2120c9f946
>> # bad: [880c81b3b6604a004d56b5975c8bed47276e8bf6] clk: samsung: exynos5440: 
>> Constify all clock initializers
>> git bisect bad 880c81b3b6604a004d56b5975c8bed47276e8bf6
>> # bad: [b3a96eed8e84780d300b79b58047ea277ba358b7] clk: samsung: exynos3250: 
>> Move platform driver and of_device_id to init section
>> git bisect bad b3a96eed8e84780d300b79b58047ea277ba358b7
>> # bad: [4528dd8ed477bf202bd33ee48d38d656672d37f8] dt-bindings: clock: Add 
>> watchdog and SSS clock IDs to Exynos5410
>> git bisect bad 4528dd8ed477bf202bd33ee48d38d656672d37f8
>> # bad: [5cd3535a27a7cf8fc4070b499d66e419e7e72b61] dt-bindings: clock: Add 
>> PWM and USB clock IDs to Exynos5410
>> git bisect bad 5cd3535a27a7cf8fc4070b499d66e419e7e72b61
>> # bad: [4c5773f9f5462dcb372857813918bbfe8c0cdcdd] dt-bindings: clock: Add 
>> license and reformat Exynos5410 clock IDs
>> git bisect bad 4c5773f9f5462dcb372857813918bbfe8c0cdcdd
>> # first bad commit: [4c5773f9f5462dcb372857813918bbfe8c0cdcdd] dt-bindings: 
>> clock: Add license and reformat Exynos5410 clock IDs
>>
>>
>> >
>> > [   74.123859] tg3.c:v3.137 (May 11, 2014)
>> > [   74.123880] PCI: Enabling device: (:00:02.0), cmd 2
>> > [   74.315794] tg3 :00:02.0 (unnamed net_device) (uninitialized): 
>> > Cannot get nvram lock, tg3_nvram_init failed
>> > [   74.656152] tg3 :00:02.0 eth0: Tigon3 [partno(none) rev 2003] 
>> > (PCI:66MHz:64-bit) MAC address 00:03:ba:0a:f3:85
>> > [   74.656160] tg3 :00:02.0 eth0: attached PHY is 5704 
>> > (10/100/1000Base-T Ethernet) (WireSpeed[1], EEE[0])
>> > [   74.656167] tg3 :00:02.0 eth0: RXcsums[1] LinkChgREG[0] MIirq[0] 
>> > ASF[0] TSOcap[1]
>> > [   74.656172] tg3 :00:02.0 eth0: dma_rwctrl[763f] dma_mask[32-bit]
>> > [   74.656322] PCI: Enabling device: (:00:02.1), cmd 2
>> > [

Re: tg3 BUG: spinlock lockup suspected

2016-10-08 Thread Siva Reddy Kallam 
On Sat, Oct 8, 2016 at 10:15 PM, Meelis Roos  wrote:
>> That did not go well - bisect found the following commit but that does
>> not seem to be related at all. So probably the reproducibility is not
>> 100% but more random.
>
> Now I reproduced the bug even with 4.7-rc1 so it is older than 4.7. Will
> test further.
>
Thanks for reporting this. We will look into this.
Any specific steps to reproduce this?
>>
>>
>> 4c5773f9f5462dcb372857813918bbfe8c0cdcdd is the first bad commit
>> commit 4c5773f9f5462dcb372857813918bbfe8c0cdcdd
>> Author: Krzysztof Kozlowski 
>> Date:   Sat May 28 11:54:12 2016 +0200
>>
>> dt-bindings: clock: Add license and reformat Exynos5410 clock IDs
>>
>> Add license and copyrights (file introduced in 2014) to header with
>> Exynos5410 clock IDs. Additionally reformat it to improve readability.
>>
>> Signed-off-by: Krzysztof Kozlowski 
>> Acked-by: Stephen Boyd 
>> Reviewed-by: Javier Martinez Canillas 
>> Signed-off-by: Sylwester Nawrocki 
>>
>> :04 04 acbd432e11366a8eb8775942bc7b8caa476226e2 
>> 08e3a3f98c3d4fa2a93123c3f21b2847c06b4665 M  include
>>
>>
>> The whiole bisect log seems to dig around in unrelated places so at best
>> it just narrows the window by adding some known-bad data points.
>>
>> git bisect start
>> # good: [523d939ef98fd712632d93a5a2b588e477a7565e] Linux 4.7
>> git bisect good 523d939ef98fd712632d93a5a2b588e477a7565e
>> # bad: [ef0e1ea8856bed6ff8394d3dfe77f2cab487ecea] Merge tag 
>> 'arc-4.8-rc4-fixes' of 
>> git://git.kernel.org/pub/scm/linux/kernel/git/vgupta/arc
>> git bisect bad ef0e1ea8856bed6ff8394d3dfe77f2cab487ecea
>> # good: [e0b3f595d13b3e9ce9cdf53935e7f304c04b5b2b] affs ->d_compare(): don't 
>> bother with ->d_inode
>> git bisect good e0b3f595d13b3e9ce9cdf53935e7f304c04b5b2b
>> # bad: [77a87824ed676ca8ff8482e4157d3adb284fd381] 
>> clocksource/drivers/clps_711x: fixup for "ARM: clps711x:
>> git bisect bad 77a87824ed676ca8ff8482e4157d3adb284fd381
>> # bad: [27acbec338113a75b9d72aeb53149a3538031dda] Merge 
>> git://www.linux-watchdog.org/linux-watchdog
>> git bisect bad 27acbec338113a75b9d72aeb53149a3538031dda
>> # bad: [7f155c702677d057d03b192ce652311de5434697] Merge tag 'nfs-for-4.8-1' 
>> of git://git.linux-nfs.org/projects/trondmy/linux-nfs
>> git bisect bad 7f155c702677d057d03b192ce652311de5434697
>> # good: [797cee982eef9195736afc5e7f3b8f613c41d19a] Merge branch 'stable-4.8' 
>> of git://git.infradead.org/users/pcmoore/audit
>> git bisect good 797cee982eef9195736afc5e7f3b8f613c41d19a
>> # bad: [1056c9bd2702ea1bb79abf9bd1e78c578589d247] Merge tag 
>> 'clk-for-linus-4.8' of 
>> git://git.kernel.org/pub/scm/linux/kernel/git/clk/linux
>> git bisect bad 1056c9bd2702ea1bb79abf9bd1e78c578589d247
>> # bad: [1ff435d3571199a799ba6ccfe05544dcd21b9fb3] Merge branch 
>> 'clk-st-critical' into clk-next
>> git bisect bad 1ff435d3571199a799ba6ccfe05544dcd21b9fb3
>> # bad: [0e4504470667d355b53ca3c9802fdd2120c9f946] clk: samsung: exynos5433: 
>> Add CLK_IGNORE_UNUSED flag to PCIE device
>> git bisect bad 0e4504470667d355b53ca3c9802fdd2120c9f946
>> # bad: [880c81b3b6604a004d56b5975c8bed47276e8bf6] clk: samsung: exynos5440: 
>> Constify all clock initializers
>> git bisect bad 880c81b3b6604a004d56b5975c8bed47276e8bf6
>> # bad: [b3a96eed8e84780d300b79b58047ea277ba358b7] clk: samsung: exynos3250: 
>> Move platform driver and of_device_id to init section
>> git bisect bad b3a96eed8e84780d300b79b58047ea277ba358b7
>> # bad: [4528dd8ed477bf202bd33ee48d38d656672d37f8] dt-bindings: clock: Add 
>> watchdog and SSS clock IDs to Exynos5410
>> git bisect bad 4528dd8ed477bf202bd33ee48d38d656672d37f8
>> # bad: [5cd3535a27a7cf8fc4070b499d66e419e7e72b61] dt-bindings: clock: Add 
>> PWM and USB clock IDs to Exynos5410
>> git bisect bad 5cd3535a27a7cf8fc4070b499d66e419e7e72b61
>> # bad: [4c5773f9f5462dcb372857813918bbfe8c0cdcdd] dt-bindings: clock: Add 
>> license and reformat Exynos5410 clock IDs
>> git bisect bad 4c5773f9f5462dcb372857813918bbfe8c0cdcdd
>> # first bad commit: [4c5773f9f5462dcb372857813918bbfe8c0cdcdd] dt-bindings: 
>> clock: Add license and reformat Exynos5410 clock IDs
>>
>>
>> >
>> > [   74.123859] tg3.c:v3.137 (May 11, 2014)
>> > [   74.123880] PCI: Enabling device: (:00:02.0), cmd 2
>> > [   74.315794] tg3 :00:02.0 (unnamed net_device) (uninitialized): 
>> > Cannot get nvram lock, tg3_nvram_init failed
>> > [   74.656152] tg3 :00:02.0 eth0: Tigon3 [partno(none) rev 2003] 
>> > (PCI:66MHz:64-bit) MAC address 00:03:ba:0a:f3:85
>> > [   74.656160] tg3 :00:02.0 eth0: attached PHY is 5704 
>> > (10/100/1000Base-T Ethernet) (WireSpeed[1], EEE[0])
>> > [   74.656167] tg3 :00:02.0 eth0: RXcsums[1] LinkChgREG[0] MIirq[0] 
>> > ASF[0] TSOcap[1]
>> > [   74.656172] tg3 :00:02.0 eth0: dma_rwctrl[763f] dma_mask[32-bit]
>> > [   74.656322] PCI: Enabling device: (:00:02.1), cmd 2
>> > [   74.845325] tg3 :00:02.1 (unnamed net_device) (uninitialized): 
>> > Cannot get nvram lock, tg3_nvram_init failed
>>

Re: tg3 BUG: spinlock lockup suspected

2016-10-08 Thread Meelis Roos 
> That did not go well - bisect found the following commit but that does 
> not seem to be related at all. So probably the reproducibility is not 
> 100% but more random.

Now I reproduced the bug even with 4.7-rc1 so it is older than 4.7. Will 
test further.

> 
> 
> 4c5773f9f5462dcb372857813918bbfe8c0cdcdd is the first bad commit
> commit 4c5773f9f5462dcb372857813918bbfe8c0cdcdd
> Author: Krzysztof Kozlowski 
> Date:   Sat May 28 11:54:12 2016 +0200
> 
> dt-bindings: clock: Add license and reformat Exynos5410 clock IDs
> 
> Add license and copyrights (file introduced in 2014) to header with
> Exynos5410 clock IDs. Additionally reformat it to improve readability.
> 
> Signed-off-by: Krzysztof Kozlowski 
> Acked-by: Stephen Boyd 
> Reviewed-by: Javier Martinez Canillas 
> Signed-off-by: Sylwester Nawrocki 
> 
> :04 04 acbd432e11366a8eb8775942bc7b8caa476226e2 
> 08e3a3f98c3d4fa2a93123c3f21b2847c06b4665 M  include
> 
> 
> The whiole bisect log seems to dig around in unrelated places so at best 
> it just narrows the window by adding some known-bad data points.
> 
> git bisect start
> # good: [523d939ef98fd712632d93a5a2b588e477a7565e] Linux 4.7
> git bisect good 523d939ef98fd712632d93a5a2b588e477a7565e
> # bad: [ef0e1ea8856bed6ff8394d3dfe77f2cab487ecea] Merge tag 
> 'arc-4.8-rc4-fixes' of 
> git://git.kernel.org/pub/scm/linux/kernel/git/vgupta/arc
> git bisect bad ef0e1ea8856bed6ff8394d3dfe77f2cab487ecea
> # good: [e0b3f595d13b3e9ce9cdf53935e7f304c04b5b2b] affs ->d_compare(): don't 
> bother with ->d_inode
> git bisect good e0b3f595d13b3e9ce9cdf53935e7f304c04b5b2b
> # bad: [77a87824ed676ca8ff8482e4157d3adb284fd381] 
> clocksource/drivers/clps_711x: fixup for "ARM: clps711x:
> git bisect bad 77a87824ed676ca8ff8482e4157d3adb284fd381
> # bad: [27acbec338113a75b9d72aeb53149a3538031dda] Merge 
> git://www.linux-watchdog.org/linux-watchdog
> git bisect bad 27acbec338113a75b9d72aeb53149a3538031dda
> # bad: [7f155c702677d057d03b192ce652311de5434697] Merge tag 'nfs-for-4.8-1' 
> of git://git.linux-nfs.org/projects/trondmy/linux-nfs
> git bisect bad 7f155c702677d057d03b192ce652311de5434697
> # good: [797cee982eef9195736afc5e7f3b8f613c41d19a] Merge branch 'stable-4.8' 
> of git://git.infradead.org/users/pcmoore/audit
> git bisect good 797cee982eef9195736afc5e7f3b8f613c41d19a
> # bad: [1056c9bd2702ea1bb79abf9bd1e78c578589d247] Merge tag 
> 'clk-for-linus-4.8' of git://git.kernel.org/pub/scm/linux/kernel/git/clk/linux
> git bisect bad 1056c9bd2702ea1bb79abf9bd1e78c578589d247
> # bad: [1ff435d3571199a799ba6ccfe05544dcd21b9fb3] Merge branch 
> 'clk-st-critical' into clk-next
> git bisect bad 1ff435d3571199a799ba6ccfe05544dcd21b9fb3
> # bad: [0e4504470667d355b53ca3c9802fdd2120c9f946] clk: samsung: exynos5433: 
> Add CLK_IGNORE_UNUSED flag to PCIE device
> git bisect bad 0e4504470667d355b53ca3c9802fdd2120c9f946
> # bad: [880c81b3b6604a004d56b5975c8bed47276e8bf6] clk: samsung: exynos5440: 
> Constify all clock initializers
> git bisect bad 880c81b3b6604a004d56b5975c8bed47276e8bf6
> # bad: [b3a96eed8e84780d300b79b58047ea277ba358b7] clk: samsung: exynos3250: 
> Move platform driver and of_device_id to init section
> git bisect bad b3a96eed8e84780d300b79b58047ea277ba358b7
> # bad: [4528dd8ed477bf202bd33ee48d38d656672d37f8] dt-bindings: clock: Add 
> watchdog and SSS clock IDs to Exynos5410
> git bisect bad 4528dd8ed477bf202bd33ee48d38d656672d37f8
> # bad: [5cd3535a27a7cf8fc4070b499d66e419e7e72b61] dt-bindings: clock: Add PWM 
> and USB clock IDs to Exynos5410
> git bisect bad 5cd3535a27a7cf8fc4070b499d66e419e7e72b61
> # bad: [4c5773f9f5462dcb372857813918bbfe8c0cdcdd] dt-bindings: clock: Add 
> license and reformat Exynos5410 clock IDs
> git bisect bad 4c5773f9f5462dcb372857813918bbfe8c0cdcdd
> # first bad commit: [4c5773f9f5462dcb372857813918bbfe8c0cdcdd] dt-bindings: 
> clock: Add license and reformat Exynos5410 clock IDs
> 
> 
> > 
> > [   74.123859] tg3.c:v3.137 (May 11, 2014)
> > [   74.123880] PCI: Enabling device: (:00:02.0), cmd 2
> > [   74.315794] tg3 :00:02.0 (unnamed net_device) (uninitialized): 
> > Cannot get nvram lock, tg3_nvram_init failed
> > [   74.656152] tg3 :00:02.0 eth0: Tigon3 [partno(none) rev 2003] 
> > (PCI:66MHz:64-bit) MAC address 00:03:ba:0a:f3:85
> > [   74.656160] tg3 :00:02.0 eth0: attached PHY is 5704 
> > (10/100/1000Base-T Ethernet) (WireSpeed[1], EEE[0])
> > [   74.656167] tg3 :00:02.0 eth0: RXcsums[1] LinkChgREG[0] MIirq[0] 
> > ASF[0] TSOcap[1]
> > [   74.656172] tg3 :00:02.0 eth0: dma_rwctrl[763f] dma_mask[32-bit]
> > [   74.656322] PCI: Enabling device: (:00:02.1), cmd 2
> > [   74.845325] tg3 :00:02.1 (unnamed net_device) (uninitialized): 
> > Cannot get nvram lock, tg3_nvram_init failed
> > [   75.184539] tg3 :00:02.1 eth1: Tigon3 [partno(none) rev 2003] 
> > (PCI:66MHz:64-bit) MAC address

Re: tg3 BUG: spinlock lockup suspected

2016-10-08 Thread Meelis Roos 
> That did not go well - bisect found the following commit but that does 
> not seem to be related at all. So probably the reproducibility is not 
> 100% but more random.

Now I reproduced the bug even with 4.7-rc1 so it is older than 4.7. Will 
test further.

> 
> 
> 4c5773f9f5462dcb372857813918bbfe8c0cdcdd is the first bad commit
> commit 4c5773f9f5462dcb372857813918bbfe8c0cdcdd
> Author: Krzysztof Kozlowski 
> Date:   Sat May 28 11:54:12 2016 +0200
> 
> dt-bindings: clock: Add license and reformat Exynos5410 clock IDs
> 
> Add license and copyrights (file introduced in 2014) to header with
> Exynos5410 clock IDs. Additionally reformat it to improve readability.
> 
> Signed-off-by: Krzysztof Kozlowski 
> Acked-by: Stephen Boyd 
> Reviewed-by: Javier Martinez Canillas 
> Signed-off-by: Sylwester Nawrocki 
> 
> :04 04 acbd432e11366a8eb8775942bc7b8caa476226e2 
> 08e3a3f98c3d4fa2a93123c3f21b2847c06b4665 M  include
> 
> 
> The whiole bisect log seems to dig around in unrelated places so at best 
> it just narrows the window by adding some known-bad data points.
> 
> git bisect start
> # good: [523d939ef98fd712632d93a5a2b588e477a7565e] Linux 4.7
> git bisect good 523d939ef98fd712632d93a5a2b588e477a7565e
> # bad: [ef0e1ea8856bed6ff8394d3dfe77f2cab487ecea] Merge tag 
> 'arc-4.8-rc4-fixes' of 
> git://git.kernel.org/pub/scm/linux/kernel/git/vgupta/arc
> git bisect bad ef0e1ea8856bed6ff8394d3dfe77f2cab487ecea
> # good: [e0b3f595d13b3e9ce9cdf53935e7f304c04b5b2b] affs ->d_compare(): don't 
> bother with ->d_inode
> git bisect good e0b3f595d13b3e9ce9cdf53935e7f304c04b5b2b
> # bad: [77a87824ed676ca8ff8482e4157d3adb284fd381] 
> clocksource/drivers/clps_711x: fixup for "ARM: clps711x:
> git bisect bad 77a87824ed676ca8ff8482e4157d3adb284fd381
> # bad: [27acbec338113a75b9d72aeb53149a3538031dda] Merge 
> git://www.linux-watchdog.org/linux-watchdog
> git bisect bad 27acbec338113a75b9d72aeb53149a3538031dda
> # bad: [7f155c702677d057d03b192ce652311de5434697] Merge tag 'nfs-for-4.8-1' 
> of git://git.linux-nfs.org/projects/trondmy/linux-nfs
> git bisect bad 7f155c702677d057d03b192ce652311de5434697
> # good: [797cee982eef9195736afc5e7f3b8f613c41d19a] Merge branch 'stable-4.8' 
> of git://git.infradead.org/users/pcmoore/audit
> git bisect good 797cee982eef9195736afc5e7f3b8f613c41d19a
> # bad: [1056c9bd2702ea1bb79abf9bd1e78c578589d247] Merge tag 
> 'clk-for-linus-4.8' of git://git.kernel.org/pub/scm/linux/kernel/git/clk/linux
> git bisect bad 1056c9bd2702ea1bb79abf9bd1e78c578589d247
> # bad: [1ff435d3571199a799ba6ccfe05544dcd21b9fb3] Merge branch 
> 'clk-st-critical' into clk-next
> git bisect bad 1ff435d3571199a799ba6ccfe05544dcd21b9fb3
> # bad: [0e4504470667d355b53ca3c9802fdd2120c9f946] clk: samsung: exynos5433: 
> Add CLK_IGNORE_UNUSED flag to PCIE device
> git bisect bad 0e4504470667d355b53ca3c9802fdd2120c9f946
> # bad: [880c81b3b6604a004d56b5975c8bed47276e8bf6] clk: samsung: exynos5440: 
> Constify all clock initializers
> git bisect bad 880c81b3b6604a004d56b5975c8bed47276e8bf6
> # bad: [b3a96eed8e84780d300b79b58047ea277ba358b7] clk: samsung: exynos3250: 
> Move platform driver and of_device_id to init section
> git bisect bad b3a96eed8e84780d300b79b58047ea277ba358b7
> # bad: [4528dd8ed477bf202bd33ee48d38d656672d37f8] dt-bindings: clock: Add 
> watchdog and SSS clock IDs to Exynos5410
> git bisect bad 4528dd8ed477bf202bd33ee48d38d656672d37f8
> # bad: [5cd3535a27a7cf8fc4070b499d66e419e7e72b61] dt-bindings: clock: Add PWM 
> and USB clock IDs to Exynos5410
> git bisect bad 5cd3535a27a7cf8fc4070b499d66e419e7e72b61
> # bad: [4c5773f9f5462dcb372857813918bbfe8c0cdcdd] dt-bindings: clock: Add 
> license and reformat Exynos5410 clock IDs
> git bisect bad 4c5773f9f5462dcb372857813918bbfe8c0cdcdd
> # first bad commit: [4c5773f9f5462dcb372857813918bbfe8c0cdcdd] dt-bindings: 
> clock: Add license and reformat Exynos5410 clock IDs
> 
> 
> > 
> > [   74.123859] tg3.c:v3.137 (May 11, 2014)
> > [   74.123880] PCI: Enabling device: (:00:02.0), cmd 2
> > [   74.315794] tg3 :00:02.0 (unnamed net_device) (uninitialized): 
> > Cannot get nvram lock, tg3_nvram_init failed
> > [   74.656152] tg3 :00:02.0 eth0: Tigon3 [partno(none) rev 2003] 
> > (PCI:66MHz:64-bit) MAC address 00:03:ba:0a:f3:85
> > [   74.656160] tg3 :00:02.0 eth0: attached PHY is 5704 
> > (10/100/1000Base-T Ethernet) (WireSpeed[1], EEE[0])
> > [   74.656167] tg3 :00:02.0 eth0: RXcsums[1] LinkChgREG[0] MIirq[0] 
> > ASF[0] TSOcap[1]
> > [   74.656172] tg3 :00:02.0 eth0: dma_rwctrl[763f] dma_mask[32-bit]
> > [   74.656322] PCI: Enabling device: (:00:02.1), cmd 2
> > [   74.845325] tg3 :00:02.1 (unnamed net_device) (uninitialized): 
> > Cannot get nvram lock, tg3_nvram_init failed
> > [   75.184539] tg3 :00:02.1 eth1: Tigon3 [partno(none) rev 2003] 
> > (PCI:66MHz:64-bit) MAC address 00:03:ba:0a:f3:86
> > [   75.184546] tg3 :00:02.1 eth1: attached PHY is 5704 
> > (10/100/1000Base-T

Re: tg3 BUG: spinlock lockup suspected

2016-10-08 Thread Meelis Roos 
> I am testing 4.8 on my sparcs and got this on Sun V210 (sparc64). This 
> is reproducible. 4.8.0-rc3-00013 did not have this problem, will bisect 
> when I get some time.

That did not go well - bisect found the following commit but that does 
not seem to be related at all. So probably the reproducibility is not 
100% but more random.


4c5773f9f5462dcb372857813918bbfe8c0cdcdd is the first bad commit
commit 4c5773f9f5462dcb372857813918bbfe8c0cdcdd
Author: Krzysztof Kozlowski 
Date:   Sat May 28 11:54:12 2016 +0200

dt-bindings: clock: Add license and reformat Exynos5410 clock IDs

Add license and copyrights (file introduced in 2014) to header with
Exynos5410 clock IDs. Additionally reformat it to improve readability.

Signed-off-by: Krzysztof Kozlowski 
Acked-by: Stephen Boyd 
Reviewed-by: Javier Martinez Canillas 
Signed-off-by: Sylwester Nawrocki 

:04 04 acbd432e11366a8eb8775942bc7b8caa476226e2 
08e3a3f98c3d4fa2a93123c3f21b2847c06b4665 M  include


The whiole bisect log seems to dig around in unrelated places so at best 
it just narrows the window by adding some known-bad data points.

git bisect start
# good: [523d939ef98fd712632d93a5a2b588e477a7565e] Linux 4.7
git bisect good 523d939ef98fd712632d93a5a2b588e477a7565e
# bad: [ef0e1ea8856bed6ff8394d3dfe77f2cab487ecea] Merge tag 'arc-4.8-rc4-fixes' 
of git://git.kernel.org/pub/scm/linux/kernel/git/vgupta/arc
git bisect bad ef0e1ea8856bed6ff8394d3dfe77f2cab487ecea
# good: [e0b3f595d13b3e9ce9cdf53935e7f304c04b5b2b] affs ->d_compare(): don't 
bother with ->d_inode
git bisect good e0b3f595d13b3e9ce9cdf53935e7f304c04b5b2b
# bad: [77a87824ed676ca8ff8482e4157d3adb284fd381] 
clocksource/drivers/clps_711x: fixup for "ARM: clps711x:
git bisect bad 77a87824ed676ca8ff8482e4157d3adb284fd381
# bad: [27acbec338113a75b9d72aeb53149a3538031dda] Merge 
git://www.linux-watchdog.org/linux-watchdog
git bisect bad 27acbec338113a75b9d72aeb53149a3538031dda
# bad: [7f155c702677d057d03b192ce652311de5434697] Merge tag 'nfs-for-4.8-1' of 
git://git.linux-nfs.org/projects/trondmy/linux-nfs
git bisect bad 7f155c702677d057d03b192ce652311de5434697
# good: [797cee982eef9195736afc5e7f3b8f613c41d19a] Merge branch 'stable-4.8' of 
git://git.infradead.org/users/pcmoore/audit
git bisect good 797cee982eef9195736afc5e7f3b8f613c41d19a
# bad: [1056c9bd2702ea1bb79abf9bd1e78c578589d247] Merge tag 'clk-for-linus-4.8' 
of git://git.kernel.org/pub/scm/linux/kernel/git/clk/linux
git bisect bad 1056c9bd2702ea1bb79abf9bd1e78c578589d247
# bad: [1ff435d3571199a799ba6ccfe05544dcd21b9fb3] Merge branch 
'clk-st-critical' into clk-next
git bisect bad 1ff435d3571199a799ba6ccfe05544dcd21b9fb3
# bad: [0e4504470667d355b53ca3c9802fdd2120c9f946] clk: samsung: exynos5433: Add 
CLK_IGNORE_UNUSED flag to PCIE device
git bisect bad 0e4504470667d355b53ca3c9802fdd2120c9f946
# bad: [880c81b3b6604a004d56b5975c8bed47276e8bf6] clk: samsung: exynos5440: 
Constify all clock initializers
git bisect bad 880c81b3b6604a004d56b5975c8bed47276e8bf6
# bad: [b3a96eed8e84780d300b79b58047ea277ba358b7] clk: samsung: exynos3250: 
Move platform driver and of_device_id to init section
git bisect bad b3a96eed8e84780d300b79b58047ea277ba358b7
# bad: [4528dd8ed477bf202bd33ee48d38d656672d37f8] dt-bindings: clock: Add 
watchdog and SSS clock IDs to Exynos5410
git bisect bad 4528dd8ed477bf202bd33ee48d38d656672d37f8
# bad: [5cd3535a27a7cf8fc4070b499d66e419e7e72b61] dt-bindings: clock: Add PWM 
and USB clock IDs to Exynos5410
git bisect bad 5cd3535a27a7cf8fc4070b499d66e419e7e72b61
# bad: [4c5773f9f5462dcb372857813918bbfe8c0cdcdd] dt-bindings: clock: Add 
license and reformat Exynos5410 clock IDs
git bisect bad 4c5773f9f5462dcb372857813918bbfe8c0cdcdd
# first bad commit: [4c5773f9f5462dcb372857813918bbfe8c0cdcdd] dt-bindings: 
clock: Add license and reformat Exynos5410 clock IDs


> 
> [   74.123859] tg3.c:v3.137 (May 11, 2014)
> [   74.123880] PCI: Enabling device: (:00:02.0), cmd 2
> [   74.315794] tg3 :00:02.0 (unnamed net_device) (uninitialized): Cannot 
> get nvram lock, tg3_nvram_init failed
> [   74.656152] tg3 :00:02.0 eth0: Tigon3 [partno(none) rev 2003] 
> (PCI:66MHz:64-bit) MAC address 00:03:ba:0a:f3:85
> [   74.656160] tg3 :00:02.0 eth0: attached PHY is 5704 (10/100/1000Base-T 
> Ethernet) (WireSpeed[1], EEE[0])
> [   74.656167] tg3 :00:02.0 eth0: RXcsums[1] LinkChgREG[0] MIirq[0] 
> ASF[0] TSOcap[1]
> [   74.656172] tg3 :00:02.0 eth0: dma_rwctrl[763f] dma_mask[32-bit]
> [   74.656322] PCI: Enabling device: (:00:02.1), cmd 2
> [   74.845325] tg3 :00:02.1 (unnamed net_device) (uninitialized): Cannot 
> get nvram lock, tg3_nvram_init failed
> [   75.184539] tg3 :00:02.1 eth1: Tigon3 [partno(none) rev 2003] 
> (PCI:66MHz:64-bit) MAC address 00:03:ba:0a:f3:86
> [   75.184546] tg3 :00:02.1 eth1: attached PHY is 5704 (10/100/1000Base-T 
> Ethernet)

Re: tg3 BUG: spinlock lockup suspected

2016-10-08 Thread Meelis Roos 
> I am testing 4.8 on my sparcs and got this on Sun V210 (sparc64). This 
> is reproducible. 4.8.0-rc3-00013 did not have this problem, will bisect 
> when I get some time.

That did not go well - bisect found the following commit but that does 
not seem to be related at all. So probably the reproducibility is not 
100% but more random.


4c5773f9f5462dcb372857813918bbfe8c0cdcdd is the first bad commit
commit 4c5773f9f5462dcb372857813918bbfe8c0cdcdd
Author: Krzysztof Kozlowski 
Date:   Sat May 28 11:54:12 2016 +0200

dt-bindings: clock: Add license and reformat Exynos5410 clock IDs

Add license and copyrights (file introduced in 2014) to header with
Exynos5410 clock IDs. Additionally reformat it to improve readability.

Signed-off-by: Krzysztof Kozlowski 
Acked-by: Stephen Boyd 
Reviewed-by: Javier Martinez Canillas 
Signed-off-by: Sylwester Nawrocki 

:04 04 acbd432e11366a8eb8775942bc7b8caa476226e2 
08e3a3f98c3d4fa2a93123c3f21b2847c06b4665 M  include


The whiole bisect log seems to dig around in unrelated places so at best 
it just narrows the window by adding some known-bad data points.

git bisect start
# good: [523d939ef98fd712632d93a5a2b588e477a7565e] Linux 4.7
git bisect good 523d939ef98fd712632d93a5a2b588e477a7565e
# bad: [ef0e1ea8856bed6ff8394d3dfe77f2cab487ecea] Merge tag 'arc-4.8-rc4-fixes' 
of git://git.kernel.org/pub/scm/linux/kernel/git/vgupta/arc
git bisect bad ef0e1ea8856bed6ff8394d3dfe77f2cab487ecea
# good: [e0b3f595d13b3e9ce9cdf53935e7f304c04b5b2b] affs ->d_compare(): don't 
bother with ->d_inode
git bisect good e0b3f595d13b3e9ce9cdf53935e7f304c04b5b2b
# bad: [77a87824ed676ca8ff8482e4157d3adb284fd381] 
clocksource/drivers/clps_711x: fixup for "ARM: clps711x:
git bisect bad 77a87824ed676ca8ff8482e4157d3adb284fd381
# bad: [27acbec338113a75b9d72aeb53149a3538031dda] Merge 
git://www.linux-watchdog.org/linux-watchdog
git bisect bad 27acbec338113a75b9d72aeb53149a3538031dda
# bad: [7f155c702677d057d03b192ce652311de5434697] Merge tag 'nfs-for-4.8-1' of 
git://git.linux-nfs.org/projects/trondmy/linux-nfs
git bisect bad 7f155c702677d057d03b192ce652311de5434697
# good: [797cee982eef9195736afc5e7f3b8f613c41d19a] Merge branch 'stable-4.8' of 
git://git.infradead.org/users/pcmoore/audit
git bisect good 797cee982eef9195736afc5e7f3b8f613c41d19a
# bad: [1056c9bd2702ea1bb79abf9bd1e78c578589d247] Merge tag 'clk-for-linus-4.8' 
of git://git.kernel.org/pub/scm/linux/kernel/git/clk/linux
git bisect bad 1056c9bd2702ea1bb79abf9bd1e78c578589d247
# bad: [1ff435d3571199a799ba6ccfe05544dcd21b9fb3] Merge branch 
'clk-st-critical' into clk-next
git bisect bad 1ff435d3571199a799ba6ccfe05544dcd21b9fb3
# bad: [0e4504470667d355b53ca3c9802fdd2120c9f946] clk: samsung: exynos5433: Add 
CLK_IGNORE_UNUSED flag to PCIE device
git bisect bad 0e4504470667d355b53ca3c9802fdd2120c9f946
# bad: [880c81b3b6604a004d56b5975c8bed47276e8bf6] clk: samsung: exynos5440: 
Constify all clock initializers
git bisect bad 880c81b3b6604a004d56b5975c8bed47276e8bf6
# bad: [b3a96eed8e84780d300b79b58047ea277ba358b7] clk: samsung: exynos3250: 
Move platform driver and of_device_id to init section
git bisect bad b3a96eed8e84780d300b79b58047ea277ba358b7
# bad: [4528dd8ed477bf202bd33ee48d38d656672d37f8] dt-bindings: clock: Add 
watchdog and SSS clock IDs to Exynos5410
git bisect bad 4528dd8ed477bf202bd33ee48d38d656672d37f8
# bad: [5cd3535a27a7cf8fc4070b499d66e419e7e72b61] dt-bindings: clock: Add PWM 
and USB clock IDs to Exynos5410
git bisect bad 5cd3535a27a7cf8fc4070b499d66e419e7e72b61
# bad: [4c5773f9f5462dcb372857813918bbfe8c0cdcdd] dt-bindings: clock: Add 
license and reformat Exynos5410 clock IDs
git bisect bad 4c5773f9f5462dcb372857813918bbfe8c0cdcdd
# first bad commit: [4c5773f9f5462dcb372857813918bbfe8c0cdcdd] dt-bindings: 
clock: Add license and reformat Exynos5410 clock IDs


> 
> [   74.123859] tg3.c:v3.137 (May 11, 2014)
> [   74.123880] PCI: Enabling device: (:00:02.0), cmd 2
> [   74.315794] tg3 :00:02.0 (unnamed net_device) (uninitialized): Cannot 
> get nvram lock, tg3_nvram_init failed
> [   74.656152] tg3 :00:02.0 eth0: Tigon3 [partno(none) rev 2003] 
> (PCI:66MHz:64-bit) MAC address 00:03:ba:0a:f3:85
> [   74.656160] tg3 :00:02.0 eth0: attached PHY is 5704 (10/100/1000Base-T 
> Ethernet) (WireSpeed[1], EEE[0])
> [   74.656167] tg3 :00:02.0 eth0: RXcsums[1] LinkChgREG[0] MIirq[0] 
> ASF[0] TSOcap[1]
> [   74.656172] tg3 :00:02.0 eth0: dma_rwctrl[763f] dma_mask[32-bit]
> [   74.656322] PCI: Enabling device: (:00:02.1), cmd 2
> [   74.845325] tg3 :00:02.1 (unnamed net_device) (uninitialized): Cannot 
> get nvram lock, tg3_nvram_init failed
> [   75.184539] tg3 :00:02.1 eth1: Tigon3 [partno(none) rev 2003] 
> (PCI:66MHz:64-bit) MAC address 00:03:ba:0a:f3:86
> [   75.184546] tg3 :00:02.1 eth1: attached PHY is 5704 (10/100/1000Base-T 
> Ethernet) (WireSpeed[1], EEE[0])
> [   75.184551] tg3 :00:02.1 eth1: RXcsums[1] LinkChgREG[0] MIirq[0] 
> ASF[0]