Re: Thread overran stack, or stack corrupted on 3.13.0

2014-02-19 Thread Dave Chinner
On Wed, Feb 05, 2014 at 02:19:32PM -0800, David Rientjes wrote: > On Thu, 6 Feb 2014, Andrew Vagin wrote: > > > [532284.563576] BUG: unable to handle kernel paging request at > > 35c83420 > > [532284.564086] IP: [] cpuacct_charge+0x97/0x1e0 > > [532284.564086] PGD 116369067 PUD 116368067

Re: Thread overran stack, or stack corrupted on 3.13.0

2014-02-05 Thread David Rientjes
On Thu, 6 Feb 2014, Andrew Vagin wrote: > [532284.563576] BUG: unable to handle kernel paging request at > 35c83420 > [532284.564086] IP: [] cpuacct_charge+0x97/0x1e0 > [532284.564086] PGD 116369067 PUD 116368067 PMD 0 > [532284.564086] Thread overran stack, or stack corrupted > [532284.5

Re: Thread overran stack, or stack corrupted on 3.13.0

2014-02-05 Thread Andrew Vagin
On Wed, Feb 05, 2014 at 01:23:45PM -0800, David Rientjes wrote: > On Wed, 5 Feb 2014, Andrew Vagin wrote: ... > > You've clipped the most interesting part of the trace, we don't know what > was calling mempool_alloc() and must have used a ton of stack. Sorry. You can find the full trace bellow

Re: Thread overran stack, or stack corrupted on 3.13.0

2014-02-05 Thread David Rientjes
On Wed, 5 Feb 2014, Andrew Vagin wrote: > [532284.563576] BUG: unable to handle kernel paging request at > 35c83420 > [532284.564086] IP: [] cpuacct_charge+0x97/0x1e0 > [532284.564086] PGD 116369067 PUD 116368067 PMD 0 > [532284.564086] Thread overran stack, or stack corrupted > [532284.5

Thread overran stack, or stack corrupted on 3.13.0

2014-02-05 Thread Andrew Vagin
Hello All, My test server crashed a few days ago. The kernel was built from Linus' git without any additional changes. I don't know how to reproduce this bug. [532284.563576] BUG: unable to handle kernel paging request at 35c83420 [532284.564086] IP: [] cpuacct_charge+0x97/0x1e0 [532284.5