From root@sentry.granch.com  Wed Oct  4 07:37:41 2000
Return-Path: <root@sentry.granch.com>
Received: from sentry.granch.com (sentry.granch.com [212.109.197.55])
	by hub.freebsd.org (Postfix) with ESMTP id EE14037B66C
	for <FreeBSD-gnats-submit@freebsd.org>; Wed,  4 Oct 2000 07:37:29 -0700 (PDT)
Received: (from root@localhost)
	by sentry.granch.com (8.9.3/8.9.3) id SAA00375;
	Wed, 4 Oct 2000 18:58:49 +0700 (NOVST)
Message-Id: <200010041158.SAA00375@sentry.granch.com>
Date: Wed, 4 Oct 2000 18:58:49 +0700 (NOVST)
From: System Administartor <root@sentry.granch.com>
Reply-To: root@sentry.granch.com
To: FreeBSD-gnats-submit@freebsd.org
Subject: Proc size mismatch
X-Send-Pr-Version: 3.2

>Number:         21753
>Category:       kern
>Synopsis:       Proc size mismatch
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    freebsd-bugs
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Wed Oct 04 07:40:04 PDT 2000
>Closed-Date:    Wed Oct 4 08:00:18 PDT 2000
>Last-Modified:  Wed Oct  4 23:20:01 PDT 2000
>Originator:     System Administartor
>Release:        FreeBSD 4.1.1-STABLE i386
>Organization:
Granch Ltd.
>Environment:

	FreeBSD 4.1.1-STABLE,Genuine PIII, 192 RAM, M/b ASUS P3B-F, HDD 6Gb
        FreeBSD 4.1.1-STABLE,AMD K6-2 350, 64 RAM, M/b ATC i430TX, HDD 10Gb

>Description:

	After install new kernel, which was CVSed recently, at 30 Sep 2000,
        ps says "Proc size mismatch (32736 total, 1048 chunks)"

>How-To-Repeat:

	CVS new kernel.
        Install.
        Reboot.
        See this message...

>Fix:

	Return to 4.1-RELEASE kernel code


>Release-Note:
>Audit-Trail:
State-Changed-From-To: open->closed 
State-Changed-By: will 
State-Changed-When: Wed Oct 4 08:00:18 PDT 2000 
State-Changed-Why:  
You have to install updated binaries along with a new 
kernel if you updated sources.  Hence, you can't normally 
install a kernel built from newer sources and use it with 
a world based on older sources.  To really solve your 
problem, try running `make world'. 

http://www.freebsd.org/cgi/query-pr.cgi?pr=21753 

From: Peter Pentchev <roam@orbitel.bg>
To: System Administartor <root@sentry.granch.com>
Cc: FreeBSD-gnats-submit@freebsd.org
Subject: Re: kern/21753: Proc size mismatch
Date: Wed, 4 Oct 2000 18:01:46 +0300

 On Wed, Oct 04, 2000 at 06:58:49PM +0700, System Administartor wrote:
 > >Synopsis:       Proc size mismatch
 [snip]
 > 
 > >Description:
 > 
 > 	After install new kernel, which was CVSed recently, at 30 Sep 2000,
 >         ps says "Proc size mismatch (32736 total, 1048 chunks)"
 > 
 > >How-To-Repeat:
 > 
 > 	CVS new kernel.
 >         Install.
 >         Reboot.
 >         See this message...
 > 
 > >Fix:
 > 
 > 	Return to 4.1-RELEASE kernel code
 
 Wrong.
 
 Fix:
 	Always read /usr/src/UPDATING when rebuilding a kernel.
 
 <a quote from /usr/src/UPDATING>
 COMMON ITEMS:
 
         To build a kernel
         -----------------
         cd /usr/src
         # If you have not already done so, please buildworld here
         # You will also need to update your config file to 4.x.
 <end of quote>
 	
 	Always upgrade your whole system when upgrading your kernel -
 	there are almost certain to be changes in the system programs
 	as well, especially if some important kernel structures have
 	changed.
 
 G'luck,
 Peter
 
 -- 
 Hey, out there - is it *you* reading me, or is it someone else?
 

From: "Rashid N. Achilov" <shelton@sentry.granch.ru>
To: Peter Pentchev <roam@orbitel.bg>
Cc: FreeBSD-gnats-submit@freebsd.org
Subject: Re: kern/21753: Proc size mismatch
Date: Thu, 05 Oct 2000 12:58:29 +0700

 Peter Pentchev wrote:
 > 
 > On Wed, Oct 04, 2000 at 06:58:49PM +0700, System Administartor wrote:
 > > >Synopsis:       Proc size mismatch
 > [snip]
 > >
 > > >Description:
 > >
 > >       After install new kernel, which was CVSed recently, at 30 Sep 2000,
 > >         ps says "Proc size mismatch (32736 total, 1048 chunks)"
 > >
 > > >Fix:
 > >
 > >       Return to 4.1-RELEASE kernel code
 > 
 > Wrong.
 
 Right. At least for me :-) When I saw it, I got very surprised, and
 reboot from 4.1-RELEASE kernel fix this problem...
 
 > 
 >         Always upgrade your whole system when upgrading your kernel -
 >         there are almost certain to be changes in the system programs
 >         as well, especially if some important kernel structures have
 >         changed.
 > 
 
 I *REALLY* need rebuild hundred of there binaries, many of them didn't
 change?
 -- 
    With Best Regards.
    Rashid N. Achilov (RNA1-RIPE), Brainbench ID: 28514
    Granch Ltd. lead engineer, e-mail: achilov@granch.ru
    tel/fax (383-2) 24-2363
 

From: Peter Pentchev <roam@orbitel.bg>
To: achilov@granch.ru
Cc: FreeBSD-gnats-submit@freebsd.org
Subject: Re: kern/21753: Proc size mismatch
Date: Thu, 5 Oct 2000 09:11:36 +0300

 On Thu, Oct 05, 2000 at 12:58:29PM +0700, Rashid N. Achilov wrote:
 > Peter Pentchev wrote:
 > > 
 > > On Wed, Oct 04, 2000 at 06:58:49PM +0700, System Administartor wrote:
 > > > >Synopsis:       Proc size mismatch
 > > [snip]
 > > >
 > > > >Description:
 > > >
 > > >       After install new kernel, which was CVSed recently, at 30 Sep 2000,
 > > >         ps says "Proc size mismatch (32736 total, 1048 chunks)"
 > > >
 > > > >Fix:
 > > >
 > > >       Return to 4.1-RELEASE kernel code
 > > 
 > > Wrong.
 > 
 > Right. At least for me :-) When I saw it, I got very surprised, and
 > reboot from 4.1-RELEASE kernel fix this problem...
 
 This is a workaround, not a fix.  A workaround, as in it lets you
 continue with your *old* binaries and your *old* kernel, which of course
 are in sync.  It does not 'fix' the problem as in let you make use
 of the new features introduced in FreeBSD with the changes.
 
 > > 
 > >         Always upgrade your whole system when upgrading your kernel -
 > >         there are almost certain to be changes in the system programs
 > >         as well, especially if some important kernel structures have
 > >         changed.
 > > 
 > 
 > I *REALLY* need rebuild hundred of there binaries, many of them didn't
 > change?
 
 Well, there is always make -DNOCLEAN buildworld, which leaves all of
 the /usr/obj tree intact (well, most of it, anyway :), and recompiles
 only the programs that have changed.  If this should fail, then you
 must rebuild the whole thing - but this only happens very rarely, when
 major changes have been introduced.
 
 Ah, and yes, judging from personal experience, it's better to run
 mergemaster *before* the world build, so it can update make.conf *and*
 the mtree files - this takes care of the case when a new directory
 has been introduced in the tree and the build falls over for lack of
 dependencies :)
 
 G'luck,
 Peter
 
 -- 
 I am not the subject of this sentence.
 
>Unformatted:
