Date: Fri, 26 Sep 2008 19:50:17 -0700 From: Jeremy Chadwick <koitsu@FreeBSD.org> To: Christian Laursen <xi@borderworlds.dk> Cc: freebsd-stable@freebsd.org Subject: Re: 7.1-PRERELEASE freezes Message-ID: <20080927025017.GA40195@icarus.home.lan> In-Reply-To: <ygfabdu6fpu.fsf@dominion.borderworlds.dk> References: <ygfabdu6fpu.fsf@dominion.borderworlds.dk>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Sep 26, 2008 at 06:21:01PM +0200, Christian Laursen wrote: > I decided to give 7.1-PRERELEASE a try on one of my machines to find > out if there might be any problems I should be aware of. > > I quickly ran into problems. After a while the system freezes > completely. It seems to be somehow related to the load of the machine > as it doesn't seem to happen when it is idle. I built a kernel with > software watchdog enabled and enabled watchdog which had the nice > effect of turning the freeze into a panic. Hopefully that will be of > some help. > > I first encountered the problem using SCHED_ULE and then tried if > SCHED_4BSD made any difference. But the freeze happens with either > scheduler. > > I have disabled xorg and the nvidia driver but that doesn't help > either. I can cut down on various other stuff too, but first I hope > that someone here have a more educated guess about what could be the > cause of the freezes. > > I have placed the backtraces from the most recent crashes as well as > the demsg output from the most recent boot at this URL: > http://borderworlds.dk/~xi/7.1-PRERELEASE.freeze.txt > > My kernel config is also included. > > #0 doadump () at pcpu.h:196 > #1 0xc05abd03 in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:418 > #2 0xc05abeff in panic (fmt=Variable "fmt" is not available.) at /usr/src/sys/kern/kern_shutdown.c:572 > #3 0xc0570d18 in hardclock (usermode=0, pc=3231434181) at /usr/src/sys/kern/kern_clock.c:642 > #4 0xc07d194f in clkintr (frame=0xe38e1c68) at /usr/src/sys/i386/isa/clock.c:164 > #5 0xc07c0465 in intr_execute_handlers (isrc=0xc0866700, frame=0xe38e1c68) at /usr/src/sys/i386/i386/intr_machdep.c:366 > #6 0xc07d0fa8 in atpic_handle_intr (vector=0, frame=0xe38e1c68) at /usr/src/sys/i386/isa/atpic.c:596 > #7 0xc07bbf41 in Xatpic_intr0 () at atpic_vector.s:62 > #8 0xc09bc5c5 in acpi_cpu_c1 () at /usr/src/sys/modules/acpi/acpi/../../../i386/acpica/acpi_machdep.c:550 > #9 0xc09b54f4 in acpi_cpu_idle () at /usr/src/sys/modules/acpi/acpi/../../../dev/acpica/acpi_cpu.c:945 > #10 0xc07c35b6 in cpu_idle () at /usr/src/sys/i386/i386/machdep.c:1183 > #11 0xc05c9275 in sched_idletd (dummy=0x0) at /usr/src/sys/kern/sched_4bsd.c:1429 > #12 0xc05895d6 in fork_exit (callout=0xc05c9260 <sched_idletd>, arg=0x0, frame=0xe38e1d38) at /usr/src/sys/kern/kern_fork.c:804 > #13 0xc07bbf10 in fork_trampoline () at /usr/src/sys/i386/i386/exception.s:264 > A couple generic things, although I think jhb@ might be able to figure out what's going on here: 1) Is this machine running the latest BIOS available? 2) Are you running powerd(8) on this box? 3) Does disabling ACPI (it's a menu option when booting) help? 4) Does removing "device cpufreq" help? -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB |
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20080927025017.GA40195>