On Sat, 7 Oct 2006 01:36:24 +0200
"Jesper Juhl" <[email protected]> wrote:
> Hi,
>
> I've been using the this very simple script for a while to do test
> builds of the kernel :
>
>
> #!/bin/bash
>
> for i in $(seq 1 100); do
> nice make distclean
> while true; do
> nice make randconfig
> grep -q "CONFIG_EXPERIMENTAL=y" .config
> if [ $? -eq 1 ]; then
> break
> fi
> done
> cp .config config.${i}
> nice make -j3 > build.log.${i} 2>&1
> done
>
>
> Which has worked great in the past, but with recent kernels it has
> been a sure way to cause a complete lockup within 1 hour :-(
>
This is probably one of those nobody-but-you-can-reproduce-it things.
>
> The last kernel where I know for sure that it ran without problems is
> 2.6.17.13 .
> The first kernel where I know for sure it caused lockups is
> 2.6.18-git15 . I've also tested 2.6.18-git16, 2.6.18-git21 and
> 2.6.19-rc1-git2 and those 3 also lock up solid.
>
> The lockup usually happens within 30 minutes, but sometimes the box
> survives longer, but I've not seen it survive for more than 60 minutes
> at most.
> It doesn't seem to matter if I leave it alone just building kernels or
> if I use it for other purposes while building in the background - if
> anything, it seems to survive longer when I do other work while it
> builds.
>
> When the lockup happens the box just freezes and doesn't respond to
> anything at all. Sometimes I can reboot with alt+sysrq+b but sometimes
> not even that works.
If you can do sysrq-b then you can do sysrq-t, too?
Please ensure that you have all the CONFIG_DEBUG_* things set, apart from
PAGEALLOC.
> Here's exactely what I do, so you can try to reproduce :
>
> 1) boot my distro (Slackware 11.0) into runlevel 4 (multi-user with
> X), using kernel 2.6.19-rc1-git2 (or one of the other "known-bad"
> kernels).
>
> 2) Log in via kdm, and once I'm at my KDE desktop I start 'konsole'.
>
> 3) cd into a dir holding a fresh copy of the 2.6.19-rc1-git2 source
> and run the above script from a file named build-random.sh that I have
> placed in the root of the source dir and made executable.
>
> 4) wait for 0-60 minutes.
>
>
> After a reboot I find nothing in the logs, so I can't give you many
> hints on what goes wrong, unfortunately.
>
Once you've got the test set up and running, you can do the alt-ctl-F1
thing to take you out of X and into the vga console. I suggest you leave
it running that way, see if anything pops up when it hangs.
-
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/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]