RE: 3.8.4 kernel

2013-05-07 Thread Huang, Xiong
> > Joseph, if there's no hardware switch for the wireless on your G770, you can > probably still take wireless out of the picture by removing or renaming the > bcma module (look in /lib/modules/.../kernel/drivers/bcma/), then rebooting. > > Xiong, do you have a specific network manager-related t

Re: 3.8.4 kernel

2013-05-07 Thread Eric Dumazet
On Tue, 2013-05-07 at 09:20 -0700, Bjorn Helgaas wrote: > [+cc Eric because he made a change (69b08f62e17) that apparently > exposes driver bugs] > > On Mon, May 6, 2013 at 7:51 PM, Huang, Xiong wrote: > >> > > >> > Did this ever get resolved? > >> > >> I opened https://bugzilla.kernel.org/show_b

Re: 3.8.4 kernel

2013-05-07 Thread Bjorn Helgaas
[+cc Eric because he made a change (69b08f62e17) that apparently exposes driver bugs] On Mon, May 6, 2013 at 7:51 PM, Huang, Xiong wrote: >> > >> > Did this ever get resolved? >> >> I opened https://bugzilla.kernel.org/show_bug.cgi?id=57681 to keep track of >> this and attached the dmesg logs you

RE: 3.8.4 kernel

2013-05-06 Thread Huang, Xiong
> > > > Did this ever get resolved? > > I opened https://bugzilla.kernel.org/show_bug.cgi?id=57681 to keep track of > this and attached the dmesg logs you collected. If you have a chance, could > you > also collect and attach the output of "lspci -vv" > (any kernel is fine for this). > > I don'

Re: 3.8.4 kernel

2013-05-06 Thread Bjorn Helgaas
[+cc Xiong, Cloud, netdev since this looks like an atl1c issue] On Fri, Apr 26, 2013 at 3:33 PM, Bjorn Helgaas wrote: > On Wed, Mar 27, 2013 at 3:46 PM, Bjorn Helgaas wrote: >> On Wed, Mar 27, 2013 at 3:18 PM, Joseph A. Millikan >> wrote: >>> >>> We use Mint 11 32-bit and we've noticed with any

Re: 3.8.4 kernel

2013-04-26 Thread Bjorn Helgaas
On Wed, Mar 27, 2013 at 3:46 PM, Bjorn Helgaas wrote: > On Wed, Mar 27, 2013 at 3:18 PM, Joseph A. Millikan > wrote: >> >> We use Mint 11 32-bit and we've noticed with any kernel beyond 3.6.11, the >> Ethernet port stops responding to pings after 15 minutes and samba clients >> cease to receive d

Re: kernel 3.8.4 : kernel BUG at fs/locks.c:2093! part #2

2013-04-01 Thread Toralf Förster
On 03/29/2013 07:43 PM, J. Bruce Fields wrote: > For now, though, this should fix the bug. > > Thanks again for this testing. With this patch applied on top of 3.8.5 the bug could not be reproduced any longer (till now). @Dave Just Cc:'ed you for your trinity score card :-) -- MfG/Sincerely Tor

Re: kernel 3.8.4 : kernel BUG at fs/locks.c:2093! part #2

2013-03-29 Thread J. Bruce Fields
On Wed, Mar 27, 2013 at 05:57:27PM -0400, J. Bruce Fields wrote: > On Wed, Mar 27, 2013 at 10:35:12PM +0100, Toralf Förster wrote: > > On 03/26/2013 03:46 PM, J. Bruce Fields wrote: > > > Can you run with test patches? > > > > applied - today I got a warning instead a bug at the host kernel (3.8.4

Re: kernel 3.8.4 : kernel BUG at fs/locks.c:2093! part #2

2013-03-27 Thread J. Bruce Fields
On Wed, Mar 27, 2013 at 10:35:12PM +0100, Toralf Förster wrote: > On 03/26/2013 03:46 PM, J. Bruce Fields wrote: > > Can you run with test patches? > > applied - today I got a warning instead a bug at the host kernel (3.8.4): Excellent! Thanks, I think I see the bug now --b. > 2013-03-27T2

Re: 3.8.4 kernel

2013-03-27 Thread Bjorn Helgaas
On Wed, Mar 27, 2013 at 3:18 PM, Joseph A. Millikan wrote: > > We use Mint 11 32-bit and we've noticed with any kernel beyond 3.6.11, the > Ethernet port stops responding to pings after 15 minutes and samba clients > cease to receive data in realtime. I hope this is the correct place to > report

Re: kernel 3.8.4 : kernel BUG at fs/locks.c:2093! part #2

2013-03-27 Thread Toralf Förster
On 03/26/2013 03:46 PM, J. Bruce Fields wrote: > Can you run with test patches? applied - today I got a warning instead a bug at the host kernel (3.8.4): 2013-03-27T22:28:43.480+01:00 n22 kernel: [ cut here ] 2013-03-27T22:28:43.480+01:00 n22 kernel: WARNING: at fs/locks.

3.8.4 kernel

2013-03-27 Thread Joseph A. Millikan
We use Mint 11 32-bit and we've noticed with any kernel beyond 3.6.11, the Ethernet port stops responding to pings after 15 minutes and samba clients cease to receive data in realtime. I hope this is the correct place to report this as we received a nasty, sullen response when posted with th

Re: kernel 3.8.4 : kernel BUG at fs/locks.c:2093! part #2

2013-03-27 Thread J. Bruce Fields
On Wed, Mar 27, 2013 at 06:20:42PM +0100, Toralf Förster wrote: > On 03/26/2013 07:17 PM, J. Bruce Fields wrote: > > > > Bah, too bad. That patch was definitely not a fix, so there may be some > > race here. > > > >> What I get at the host is now : > >> > >> 2013-03-26T18:32:17.487+01:00 n22 ker

Re: kernel 3.8.4 : kernel BUG at fs/locks.c:2093! part #2

2013-03-27 Thread Toralf Förster
On 03/26/2013 07:17 PM, J. Bruce Fields wrote: > > Bah, too bad. That patch was definitely not a fix, so there may be some > race here. > >> What I get at the host is now : >> >> 2013-03-26T18:32:17.487+01:00 n22 kernel: [ cut here >> ] >> 2013-03-26T18:32:17.487+01:00 n

Re: kernel 3.8.4 : kernel BUG at fs/locks.c:2093! part #2

2013-03-26 Thread J. Bruce Fields
On Tue, Mar 26, 2013 at 06:46:31PM +0100, Toralf Förster wrote: > On 03/26/2013 03:46 PM, J. Bruce Fields wrote: > > Can you run with test patches? > > > > This just makes nfsd's fput calls synchronous so that we see in the > > backtrace who called them. > > Well - the patched 3.8.4 host kernel n

Re: kernel 3.8.4 : kernel BUG at fs/locks.c:2093! part #2

2013-03-26 Thread Toralf Förster
On 03/26/2013 03:46 PM, J. Bruce Fields wrote: > Can you run with test patches? > > This just makes nfsd's fput calls synchronous so that we see in the > backtrace who called them. Well - the patched 3.8.4 host kernel now survives the stress test of the UML system. What I get at the host is now

Re: kernel 3.8.4 : kernel BUG at fs/locks.c:2093! part #2

2013-03-26 Thread Al Viro
On Tue, Mar 26, 2013 at 10:46:40AM -0400, J. Bruce Fields wrote: > > fs/locks.c:2093 says that we did the final fput of a file that still had > > posix locks held on it. > > > > I can't see how that would happen, but admittedly the nfsd4 code here is > > much too complicated for its own good. > >

Re: kernel 3.8.4 : kernel BUG at fs/locks.c:2093! part #2

2013-03-26 Thread J. Bruce Fields
On Mon, Mar 25, 2013 at 06:01:43PM -0400, bfields wrote: > On Sun, Mar 24, 2013 at 06:02:39PM +0100, Toralf Förster wrote: > > The following bug was triggered twice under a stable 3.8.4 kernel if I > > export a NFS (v4) directory > > and mount it within a user mode linux

Re: kernel 3.8.4 : kernel BUG at fs/locks.c:2093! part #2

2013-03-25 Thread J. Bruce Fields
On Sun, Mar 24, 2013 at 06:02:39PM +0100, Toralf Förster wrote: > The following bug was triggered twice under a stable 3.8.4 kernel if I export > a NFS (v4) directory > and mount it within a user mode linux (running at the same system) and run > within that UML trinity >

kernel 3.8.4 : kernel BUG at fs/locks.c:2093! part #2

2013-03-24 Thread Toralf Förster
The following bug was triggered twice under a stable 3.8.4 kernel if I export a NFS (v4) directory and mount it within a user mode linux (running at the same system) and run within that UML trinity (16 UML trinity processes at a 4-core host CPU) with victim files+directories within that NFS

kernel 3.8.4 : kernel BUG at fs/locks.c:2093!

2013-03-24 Thread Toralf Förster
Observed it today at a 32 bit Gentoo Linux w/ kernel 3.8.4 : 2013-03-24T11:39:48.749+01:00 n22 kernel: [ cut here ] 2013-03-24T11:39:48.749+01:00 n22 kernel: kernel BUG at fs/locks.c:2093! 2013-03-24T11:39:48.749+01:00 n22 kernel: invalid opcode: [#1] SMP 2013-03-24T1