Re: 2.6.24-sha1: RIP [] iov_iter_advance+0x38/0x70

2008-02-25 Thread Nick Piggin
On Wednesday 20 February 2008 09:01, Alexey Dobriyan wrote: > On Tue, Feb 19, 2008 at 11:47:11PM +0300, wrote: > > > Are you reproducing it simply by running the > > > ftest03 binary directly from the shell? How many times between oopses? > > > It is multi-process but no threads, so races should

Re: 2.6.24-sha1: RIP [] iov_iter_advance+0x38/0x70

2008-02-19 Thread Alexey Dobriyan
On Tue, Feb 19, 2008 at 11:47:11PM +0300, wrote: > On Wed, Feb 13, 2008 at 03:42:02PM +1100, Nick Piggin wrote: > > On Wednesday 13 February 2008 11:17, Nick Piggin wrote: > > > On Wednesday 13 February 2008 09:27, Alexey Dobriyan wrote: > > > > > > It's a trivial dumb module which does nothing

Re: 2.6.24-sha1: RIP [] iov_iter_advance+0x38/0x70

2008-02-19 Thread Alexey Dobriyan
On Wed, Feb 13, 2008 at 03:42:02PM +1100, Nick Piggin wrote: > On Wednesday 13 February 2008 11:17, Nick Piggin wrote: > > On Wednesday 13 February 2008 09:27, Alexey Dobriyan wrote: > > > > It's a trivial dumb module which does nothing but loads and unloads. > > > I redid ftest03 later without

Re: 2.6.24-sha1: RIP [] iov_iter_advance+0x38/0x70

2008-02-19 Thread Kevin Coffman
On Feb 18, 2008 8:20 PM, Nick Piggin <[EMAIL PROTECTED]> wrote: > On Wednesday 13 February 2008 09:27, Alexey Dobriyan wrote: > > On Tue, Feb 12, 2008 at 02:04:30PM -0800, Andrew Morton wrote: > > Can you try this patch please? Sorry, I still see (only with DEBUG_PAGEALLOC enabled): kernel: BUG:

Re: 2.6.24-sha1: RIP [] iov_iter_advance+0x38/0x70

2008-02-18 Thread Nick Piggin
On Wednesday 13 February 2008 09:27, Alexey Dobriyan wrote: > On Tue, Feb 12, 2008 at 02:04:30PM -0800, Andrew Morton wrote: > > > [ 4057.31] Pid: 7035, comm: ftest03 Not tainted > > > 2.6.24-25f666300625d894ebe04bac2b4b3aadb907c861 #2 [ 4057.31] RIP: > > > 0010:[] [] > > >

Re: 2.6.24-sha1: RIP [] iov_iter_advance+0x38/0x70

2008-02-12 Thread Nick Piggin
On Wednesday 13 February 2008 11:17, Nick Piggin wrote: > On Wednesday 13 February 2008 09:27, Alexey Dobriyan wrote: > > It's a trivial dumb module which does nothing but loads and unloads. > > I redid ftest03 later without any suspicious activity and it oopsed the > > same way. > > Ah crap.

Re: 2.6.24-sha1: RIP [] iov_iter_advance+0x38/0x70

2008-02-12 Thread Nick Piggin
On Wednesday 13 February 2008 09:27, Alexey Dobriyan wrote: > On Tue, Feb 12, 2008 at 02:04:30PM -0800, Andrew Morton wrote: > > On Sun, 10 Feb 2008 17:00:31 +0300 > > > > Alexey Dobriyan <[EMAIL PROTECTED]> wrote: > > > This happened during LTP. FWIW, modprobe/rmmod trivial empty module > > >

Re: 2.6.24-sha1: RIP [] iov_iter_advance+0x38/0x70

2008-02-12 Thread Alexey Dobriyan
On Tue, Feb 12, 2008 at 02:04:30PM -0800, Andrew Morton wrote: > On Sun, 10 Feb 2008 17:00:31 +0300 > Alexey Dobriyan <[EMAIL PROTECTED]> wrote: > > > This happened during LTP. FWIW, modprobe/rmmod trivial empty module > > together with cat /proc/*/wchan and cat /proc/modules were also running. >

Re: 2.6.24-sha1: RIP [] iov_iter_advance+0x38/0x70

2008-02-12 Thread Andrew Morton
On Sun, 10 Feb 2008 17:00:31 +0300 Alexey Dobriyan <[EMAIL PROTECTED]> wrote: > This happened during LTP. FWIW, modprobe/rmmod trivial empty module > together with cat /proc/*/wchan and cat /proc/modules were also running. > > Box is E6400, much debugging is on, config below. > > > [

Re: 2.6.24-sha1: RIP [] iov_iter_advance+0x38/0x70

2008-02-10 Thread Alexey Dobriyan
On Sun, Feb 10, 2008 at 05:00:31PM +0300, wrote: > This happened during LTP. FWIW, modprobe/rmmod trivial empty module > together with cat /proc/*/wchan and cat /proc/modules were also running. > > Box is E6400, much debugging is on, config below. > > > [ 4057.31] BUG: unable to handle

2.6.24-sha1: RIP [] iov_iter_advance+0x38/0x70

2008-02-10 Thread Alexey Dobriyan
This happened during LTP. FWIW, modprobe/rmmod trivial empty module together with cat /proc/*/wchan and cat /proc/modules were also running. Box is E6400, much debugging is on, config below. [ 4057.31] BUG: unable to handle kernel paging request at 810101dbc008 [ 4057.31] IP: []