Re: tg3 BUG: spinlock lockup suspected

> 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

Re: tg3 BUG: spinlock lockup suspected

> 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

Re: tg3 BUG: spinlock lockup suspected

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. >> >>

Re: tg3 BUG: spinlock lockup suspected

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

Re: tg3 BUG: spinlock lockup suspected

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

Re: tg3 BUG: spinlock lockup suspected

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. >>>

Re: tg3 BUG: spinlock lockup suspected

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

Re: tg3 BUG: spinlock lockup suspected

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

Re: tg3 BUG: spinlock lockup suspected

> > 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

Re: tg3 BUG: spinlock lockup suspected

> > 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

Re: tg3 BUG: spinlock lockup suspected

> 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

Re: tg3 BUG: spinlock lockup suspected

> 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

Re: tg3 BUG: spinlock lockup suspected

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

Re: tg3 BUG: spinlock lockup suspected

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.

Re: tg3 BUG: spinlock lockup suspected

> 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. > > >

Re: tg3 BUG: spinlock lockup suspected

> 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. > > >

Re: tg3 BUG: spinlock lockup suspected

> 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

Re: tg3 BUG: spinlock lockup suspected

> 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