On Mon, Mar 06, 2006 at 12:08:16PM +0600, Pavel Gubin wrote: > On Mon, Mar 06, 2006 at 01:00:38AM -0500, Kris Kennaway wrote: > > On Mon, Mar 06, 2006 at 11:58:33AM +0600, Pavel Gubin wrote: > > > On Mon, Mar 06, 2006 at 12:48:24AM -0500, Kris Kennaway wrote: > > > > > I've got some machine which is almost idle and works now almost only > > > > > as dialup > > > > > server. The problem was that this machine was very stable under > > > > > 5.4-RELEASE, > > > > > but after upgrading (via buildworld/installworld) to 6.0-RELEASE-p4 > > > > > and then > > > > > to 6.1-PRERELEASE (4 days ago) the machine panices (uptime from an > > > > > hour to > > > > > a day or two). > > > > > > > > Are you using stale modules? > > > > > > No, there was full buildworld/buildkernel/installkernel/installworld > > > cycle, and now all files in /boot/kernel are dated 2-Mar-2006. > > > > > > > Those panic traces don't make much sense to me. > > > > > > Maybe I can do something else? Coredumps are on hand and can be digged > > > in > > > all directions :) > > > > What compiler flags are you using to build your kernel? > > The build was done with "make buildkernel KERNCONF=Fet", and seems that > /etc/make.conf does not contain variables that can have any effect on > compiler:
Strange. What does DDB say about the stack trace when it panics? Kris
pgpztxZ4n7iGr.pgp
Description: PGP signature
