Date: Sat, 13 Jan 2001 13:54:58 +1100 From: Kal Torak <kaltorak@quake.com.au> To: FreeBSD-stable <freebsd-stable@freebsd.org> Subject: [Fwd: Interesting plight (top/ps problem)] Message-ID: <3A5FC382.D163DFEA@quake.com.au>
next in thread | raw e-mail | index | archive | help
"Duane H. Hesser" wrote: > > The "top/ps" problem is discussed and answered in the mailing list > archives. I found the discussion after having the same problem > after an upgrade from 3.x to 4.2. > > The problem occurs if the kernel is booted directly from the second > stage boot, rather than from the boot loader. It appears that the > boot loader performs some initialization which is not otherwise > done. A source patch is included which purports to fix this. I > recall installing the patch, but I've never tested it. The patch > has never been committed, either because it is not robust, or > because no one has taken ownership. Perhaps no PR has been > submitted. > > To the original poster: you can verify that this is (or is not) > the problem simply by calling /boot/loader from the "boot:" prompt. > If that works, just change /boot.config to call /boot/loader rather > than /kernel. > > If you want the patch, you should be able to find it in the stable > or hacker list archives somewhere in the last couple of months > (lookfor "nlist", "loader", "kvm" ...). If you can't find it, I > can probably paw thru my disks to find it, but the workaround is > so easy that I haven't bothered to try the patch. > > It is possible that you have some *other* problem related to > out-of-sync kernel/world, as has been suggested, but if you're in > a position to reboot, this solution is easy to try, and it did the > trick for me. You might want to check /boot.config first, to make > sure that you're skipping the third boot stage. If it says something > like "da(0,a)/kernel" change the "/kernel" to "/boot/loader". If > it already says "/boot/loader"...never mind. > > FWIW, a quick search of mailing list archives is always a good idea > when a problem like this appears. > > On 12-Jan-01 Kal Torak wrote: > > Erich Zigler wrote: > >> > >> A couple days ago I was mentioning about my ps and top problems. Well at the > >> advice of a FreeBSD user I went and installed the bin distribution for > >> 4.2-RELEASE rebooted with the 4.2-RELEASE kernel and everything was golden. > >> I could ps and top and kill I was one happy guy. > >> > >> Well I cvsup'ed my source tree, and went through the process as is outlined > >> in /usr/src/UPDATING of updating my source tree to 4.2-STABLE. I finish this > >> procedure, and ps and top fail to work. > >> > >> What is wrong? > >> > >> Why will it work on 4.2-RELEASE but not 4.2-STABLE? > > > > This just doesnt make ANY sense... > > If you really did follow the instructions everything SHOULD work fine, > > I have cvsup'd many times and so long as you do it by the UPDATING file > > I have never had any problems (besides new/changed driver issues)... > > > > It seems to me that something MUST be out of synch... > > Make sure your stable-supfile is getting everything... > > Do the install in single user mode if your not already... > > Clean out /usr/obj before a build, some of the files you may > > need to allow deleting on with the chflags command... > > > > You are specifying what kernel to build right? > > make buildkernel KERNEL=GENERIC > > unless you have a custom kernel then specify that... > > > > If you are doing all this, you should try removing all of the > > /usr/src and /usr/obj and remove the cvsup logs and get everything > > again... > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-stable" in the body of the message > > > > -------------- > Duane H. Hesser > dhh@androcles.com 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?3A5FC382.D163DFEA>