Date: Fri, 9 Aug 2002 21:51:25 -0500 From: FreeBSD Mailing Lists <freebsd@mail13.webintl.com> To: FreeBSD-STABLE@FreeBSD.ORG Subject: Re: panics after upgrading to -STABLE Aug 9, 2002 Message-ID: <0FAE6683-AC0C-11D6-A426-00039345F4BA@mail13.webintl.com> In-Reply-To: <20020810014138.GA354@laptop.lambertfam.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Could someone put the word out when this issue is fixed? This problem just hosed my web server after I forgot the prime directive: test on a non-critical machine. Albert On Friday, August 9, 2002, at 08:41 PM, Scott Lambert wrote: > I've been getting regular panics today after CVSuping and following the > UPDATING procedure. I think all of the panics are happening as various > network apps are tearing down their connections. I've had it trap while > in the kernel on the behalf of fetchmail, ppp, and nfsd (when I kill > -9'd > nfsd to try to make sure I wouldn't panic during a buildkernel, and > during > a shutdown.). > > This happened with both my LAPTOP kernel and the GENERIC kernel. > > Last kernel built before today : > Aug 9 11:55:25 laptop /kernel: FreeBSD 4.6-STABLE #25: Mon Aug 5 > 18:37:34 EDT 2002 > Aug 9 11:55:25 laptop /kernel: > root@laptop.lambertfam.org:/usr/obj/usr/src/sys/LAPTOP > > Kernel with problems : > Aug 9 15:39:09 laptop /kernel: FreeBSD 4.6-STABLE #26: Fri Aug 9 > 14:56:21 EDT 2002 > Aug 9 15:39:09 laptop /kernel: > root@laptop.lambertfam.org:/usr/obj/usr/src/sys/LAPTOP > > And I am now running a kernel, LAPTOP, built after cvsuping with > date=2002.08.09.00.00.00 > > I have survived a shutdown -r with this kernel and have now checked my > mail several times. On the basis of that, :-), I'm going to claim that > this kernel is ok. > > I suspect that the tcpip related changes today are to blame for my > problems. > > This is what happened on the first reload to the new kernel: > > Aug 9 15:39:19 laptop /kernel: Linux ELF exec handler installed > Aug 9 15:42:26 laptop /kernel: > Aug 9 15:42:26 laptop /kernel: > Aug 9 15:42:26 laptop /kernel: Fatal trap 12: page fault while in > kernel mode > Aug 9 15:42:26 laptop /kernel: fault virtual address = 0x0 > Aug 9 15:42:26 laptop /kernel: fault code = supervisor > read, page not present > Aug 9 15:42:26 laptop /kernel: instruction pointer = 0x8:0xc0181804 > Aug 9 15:42:26 laptop /kernel: stack pointer = > 0x10:0xc028d808 > Aug 9 15:42:26 laptop /kernel: frame pointer = > 0x10:0xc028d810 > Aug 9 15:42:26 laptop /kernel: code segment = base 0x0, > limit 0xfffff, type 0x1b > Aug 9 15:42:26 laptop /kernel: = DPL 0, pres 1, def32 1, gran 1 > Aug 9 15:42:26 laptop /kernel: processor eflags = interrupt > enabled, resume, IOPL = 0 > Aug 9 15:42:26 laptop /kernel: current process = Idle > Aug 9 15:42:26 laptop /kernel: interrupt mask = net > Aug 9 15:42:26 laptop /kernel: trap number = 12 > Aug 9 15:42:26 laptop /kernel: panic: page fault > Aug 9 15:42:26 laptop /kernel: > Aug 9 15:42:26 laptop /kernel: syncing disks... > Aug 9 15:42:26 laptop /kernel: > Aug 9 15:42:26 laptop /kernel: Fatal trap 12: page fault while in > kernel mode > Aug 9 15:42:26 laptop /kernel: fault virtual address = 0x30 > Aug 9 15:42:26 laptop /kernel: fault code = supervisor > read, page not present > Aug 9 15:42:26 laptop /kernel: instruction pointer = 0x8:0xc01e7cd4 > Aug 9 15:42:26 laptop /kernel: stack pointer = > 0x10:0xc028d628 > Aug 9 15:42:26 laptop /kernel: frame pointer = > 0x10:0xc028d630 > Aug 9 15:42:26 laptop /kernel: code segment = base 0x0, > limit 0xfffff, type 0x1b > Aug 9 15:42:26 laptop /kernel: = DPL 0, pres 1, def32 1, gran 1 > Aug 9 15:42:26 laptop /kernel: processor eflags = interrupt > enabled, resume, IOPL = 0 > Aug 9 15:42:26 laptop /kernel: current process = Idle > Aug 9 15:42:26 laptop /kernel: interrupt mask = net bio cam > Aug 9 15:42:26 laptop /kernel: trap number = 12 > Aug 9 15:42:26 laptop /kernel: panic: page fault > Aug 9 15:42:26 laptop /kernel: Uptime: 30s > Aug 9 15:42:26 laptop /kernel: Automatic reboot in 15 seconds - press > a key on the console to abort > Aug 9 15:42:26 laptop /kernel: Rebooting... > > This is the last trap, with the GENERIC kernel, before I got the > 2002.08.09.00.00.00 > LAPTOP kernel built. > > Aug 9 21:00:17 laptop syslogd: exiting on signal 15 > Aug 9 21:03:16 laptop /kernel: > Aug 9 21:03:16 laptop /kernel: > Aug 9 21:03:16 laptop /kernel: Fatal trap 12: page fault while in > kernel mode > Aug 9 21:03:16 laptop /kernel: fault virtual address = 0x0 > Aug 9 21:03:16 laptop /kernel: fault code = supervisor > read, page not present > Aug 9 21:03:16 laptop /kernel: instruction pointer = 0x8:0xc0204e38 > Aug 9 21:03:16 laptop /kernel: stack pointer = > 0x10:0xdac1ad8c > Aug 9 21:03:16 laptop /kernel: frame pointer = > 0x10:0xdac1ad94 > Aug 9 21:03:16 laptop /kernel: code segment = base 0x0, > limit 0xfffff, type 0x1b > Aug 9 21:03:16 laptop /kernel: = DPL 0, pres 1, def32 1, gran 1 > Aug 9 21:03:16 laptop /kernel: processor eflags = interrupt > enabled, resume, IOPL = 0 > Aug 9 21:03:16 laptop /kernel: current process = 118 (nfsd) > Aug 9 21:03:16 laptop /kernel: interrupt mask = net tty > Aug 9 21:03:16 laptop /kernel: trap number = 12 > Aug 9 21:03:16 laptop /kernel: panic: page fault > Aug 9 21:03:16 laptop /kernel: > Aug 9 21:03:16 laptop /kernel: syncing disks... 7 > Aug 9 21:03:16 laptop /kernel: done > Aug 9 21:03:16 laptop /kernel: Uptime: 15m24s > Aug 9 21:03:16 laptop /kernel: Automatic reboot in 15 seconds - press > a key on the console to abort > Aug 9 21:03:16 laptop /kernel: --> Press a key on the console to > reboot, > Aug 9 21:03:16 laptop /kernel: --> or switch off the system now. > Aug 9 21:03:16 laptop /kernel: Rebooting... > > Rather than copy and paste all of the dmesg and trap information into > this message, I'm going to upload my messages logs to : > > http://www.lambertfam.org/~lambert/laptop/messages/ > > This URL: > http://www.lambertfam.org/~lambert/laptop/ > > has all the gory details of the configuration of this system. > > The machine seems to be able to run as long as I want it to as long as I > don't hit the network. I have done three buildkernel with it while the > bad kernels were on it. Some network apps don't seem to bother it. I > was able to cvsup a couple of times. First to see if I had cvsuped mid > commit and secondly to back my tree up to midnight. > > -- > Scott Lambert KC5MLE Unix > SysAdmin > lambert@lambertfam.org > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?0FAE6683-AC0C-11D6-A426-00039345F4BA>