Re: [LTP] Re: [Dev] Re: Kernel Panic with LTP on 2.6.11-rc1 (was Re: LTP Results for 2.6.x and 2.4.x)
* Bryce Harrington ([EMAIL PROTECTED]) wrote: > Well, I'm not having much luck. strace isn't installed on the system > (and is giving errors when trying to compile it). Also, the ssh session > (and sshd) quits whenever I try running the following growfiles command > manually, so I'm having trouble replicating the kernel panic manually. Sounds very much like oom killer gone nuts. > # growfiles -W gf14 -b -e 1 -u -i 0 -L 20 -w -l -C 1 -T 10 glseek19 glseek19.2 > > Anyway, if anyone wants to investigate this further, I can provide > access to the machine (email me). Otherwise, I'm probably just going to > wait for -rc2 and see if the problem's still there. Wait no longer, it's here ;-) thanks, -chris -- Linux Security Modules http://lsm.immunix.org http://lsm.bkbits.net - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [LTP] Re: [Dev] Re: Kernel Panic with LTP on 2.6.11-rc1 (was Re: LTP Results for 2.6.x and 2.4.x)
On Fri, 21 Jan 2005, Bryce Harrington wrote: > On Fri, 21 Jan 2005, Chris Wright wrote: > > * Andrew Morton ([EMAIL PROTECTED]) wrote: > > > Bryce Harrington <[EMAIL PROTECTED]> wrote: > > > I am unable to find the oops trace amongst all that stuff. Help? > > > > > > (It would have been handy to include it in the bug report, actually) > > > > Yes, it would. Or at least some better granularity leading up to the > > problem. I ran growfiles locally on 2.6.11-rc-bk and didn't have any > > problem. Could you strace growfiles and see what it was doing when it > > killed the machine? > > Okay, I'll set up another run and try collecting that info. Is there > any other data that would be useful to collect while I'm at it? Well, I'm not having much luck. strace isn't installed on the system (and is giving errors when trying to compile it). Also, the ssh session (and sshd) quits whenever I try running the following growfiles command manually, so I'm having trouble replicating the kernel panic manually. # growfiles -W gf14 -b -e 1 -u -i 0 -L 20 -w -l -C 1 -T 10 glseek19 glseek19.2 Anyway, if anyone wants to investigate this further, I can provide access to the machine (email me). Otherwise, I'm probably just going to wait for -rc2 and see if the problem's still there. Thanks, Bryce - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [Dev] Re: Kernel Panic with LTP on 2.6.11-rc1 (was Re: LTP Results for 2.6.x and 2.4.x)
On Fri, 21 Jan 2005, Chris Wright wrote: > * Andrew Morton ([EMAIL PROTECTED]) wrote: > > Bryce Harrington <[EMAIL PROTECTED]> wrote: > > I am unable to find the oops trace amongst all that stuff. Help? > > > > (It would have been handy to include it in the bug report, actually) > > Yes, it would. Or at least some better granularity leading up to the > problem. I ran growfiles locally on 2.6.11-rc-bk and didn't have any > problem. Could you strace growfiles and see what it was doing when it > killed the machine? Okay, I'll set up another run and try collecting that info. Is there any other data that would be useful to collect while I'm at it? Bryce - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Kernel Panic with LTP on 2.6.11-rc1 (was Re: LTP Results for 2.6.x and 2.4.x)
On Fri, Jan 21, 2005 at 03:35:20PM -0800, Andrew Morton wrote: > I am unable to find the oops trace amongst all that stuff. Help? > (It would have been handy to include it in the bug report, actually) There was no oops. The panic() in oom_kill.c was triggered. -- wli - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [Dev] Re: Kernel Panic with LTP on 2.6.11-rc1 (was Re: LTP Results for 2.6.x and 2.4.x)
* Andrew Morton ([EMAIL PROTECTED]) wrote: > Bryce Harrington <[EMAIL PROTECTED]> wrote: > I am unable to find the oops trace amongst all that stuff. Help? > > (It would have been handy to include it in the bug report, actually) Yes, it would. Or at least some better granularity leading up to the problem. I ran growfiles locally on 2.6.11-rc-bk and didn't have any problem. Could you strace growfiles and see what it was doing when it killed the machine? thanks, -chris -- Linux Security Modules http://lsm.immunix.org http://lsm.bkbits.net - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Kernel Panic with LTP on 2.6.11-rc1 (was Re: LTP Results for 2.6.x and 2.4.x)
Bryce Harrington <[EMAIL PROTECTED]> wrote: > > cmdline="mkfifo gffifo18; growfiles -b -W gf13 -e 1 -u -i 0 -L 30 -I r > -r 1-4096 gffifo18" > contacts="" > analysis=exit > initiation_status="ok" > <<>> > growfiles(gf13): 17094 DEBUG1 Using random seed of 1106350453 > Kernel panic - not syncing: Out of memory and no killable processes... > > > The full output are available at these links: > > FAIL LTP 2.6.11-rc1 SuSE 9.0 2-way http://khack.osdl.org/stp/300213/ > FAIL LTP 2.6.11-rc1 SuSE 9.2 2-way http://khack.osdl.org/stp/300219/ > FAIL LTP 2.6.11-rc1 SuSE 9.2 1-way http://khack.osdl.org/stp/300209/ > > OK LTP 2.6.10 SuSE 9.2 2-way http://khack.osdl.org/stp/300230 > OK LTP 2.6.10 SuSE 9.0 2-way http://khack.osdl.org/stp/300229 > OK LTP 2.6.10 RH 9.02-way http://khack.osdl.org/stp/300228 > OK OPTS 2.6.11-rc1 RH 9.22-way http://khack.osdl.org/stp/300227 I am unable to find the oops trace amongst all that stuff. Help? (It would have been handy to include it in the bug report, actually) - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Kernel Panic with LTP on 2.6.11-rc1 (was Re: LTP Results for 2.6.x and 2.4.x)
On Tue, 18 Jan 2005, Bryce Harrington wrote: > Here's an updated summary of our LTP regression test runs against the > 2.6.x and 2.4.x kernels on RedHat 9.0: > > http://developer.osdl.org/bryce/ltp/ > > I've run into some issues with patch-2.6.11-rc1 and the latest LTP, but > will post numbers when I've sorted those out. Okay, it looks like there is a regression of Linux 2.6.11-rc1 on LTP. I've run a bunch of tests to narrow down and rule things out: * Other tests (e.g. open_posix) run ok on this kernel * This version of LTP is working fine on other kernels * Not a hardware problem; same issue occurs on all of our 2-ways * Not distro-dependent; problem occurs for me on RH 9.0, and SuSE 9.0 and 9.2 Here is the output from the test causing the panic: <<>> tag=gf13 stime=110659 cmdline="mkfifo gffifo18; growfiles -b -W gf13 -e 1 -u -i 0 -L 30 -I r -r 1-4096 gffifo18" contacts="" analysis=exit initiation_status="ok" <<>> growfiles(gf13): 17094 DEBUG1 Using random seed of 1106350453 Kernel panic - not syncing: Out of memory and no killable processes... The full output are available at these links: FAIL LTP 2.6.11-rc1 SuSE 9.0 2-way http://khack.osdl.org/stp/300213/ FAIL LTP 2.6.11-rc1 SuSE 9.2 2-way http://khack.osdl.org/stp/300219/ FAIL LTP 2.6.11-rc1 SuSE 9.2 1-way http://khack.osdl.org/stp/300209/ OK LTP 2.6.10 SuSE 9.2 2-way http://khack.osdl.org/stp/300230 OK LTP 2.6.10 SuSE 9.0 2-way http://khack.osdl.org/stp/300229 OK LTP 2.6.10 RH 9.02-way http://khack.osdl.org/stp/300228 OK OPTS 2.6.11-rc1 RH 9.22-way http://khack.osdl.org/stp/300227 These are all run on the December version of LTP (20041203). growfiles.c is in ltp-full-20041203/testcases/kernel/fs/doio. Bryce - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
LTP Results for 2.6.x and 2.4.x
Here's an updated summary of our LTP regression test runs against the 2.6.x and 2.4.x kernels on RedHat 9.0: http://developer.osdl.org/bryce/ltp/ Briefly, here are the numbers for the most recent kernels: Patch Name TestReq# LTP Ver CPUPASS FAIL WARN BROK --- linux-2.6.10 299759 20041105 2-way 2196 6 2 6 patch-2.6.10-rc3 299166 20041007 2-way 2199 6 2 6 patch-2.6.10-rc2 298746 20041007 2-way 2198 8 2 6 patch-2.6.10-rc1 298400 20041007 2-way 2198 6 2 6 Patch Name TestReq# LTP CPUPASS FAIL WARN BROK --- patch-2.4.29-rc3 300054 20041105 2-way 2210 3 2 3 patch-2.4.29-rc1 299873 20041105 2-way 2210 3 2 3 patch-2.4.29-pre2 299601 20041105 2-way 2210 3 2 3 patch-2.4.29-pre1 298976 20041007 2-way 2210 3 2 3 linux-2.4.28 298851 20041007 2-way 2210 3 2 3 A summary and a detailed report of the current failures on 2.6.10 is available at: http://khack.osdl.org/299759/results/FAIL_summary.txt http://developer.osdl.org/bryce/ltp/failrpt_299759_2.6.10.txt I've run into some issues with patch-2.6.11-rc1 and the latest LTP, but will post numbers when I've sorted those out. Bryce On Fri, 1 Oct 2004, Linus Torvalds wrote: > On Fri, 1 Oct 2004, Bryce Harrington wrote: > > > > madvise02 7 FAIL : madvise failed with wrong errno, expected > > errno = 22, got errno = 12 : Cannot allocate > > memory > >See: ltp/testcases/kernel/syscalls/madvise/madvise02.c > > Are you running this test on a 64-bit kernel with a 32-bit test > environment? This failure _looks_ that way, apparently because the > compatibility layer doesn't sign-extend "len". And quite frankly, > sign-extending it would be silly, although I think it would make the test > happy. > > Linus > - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
