From owner-freebsd-arch Tue Feb 11 13:26:45 2003 Delivered-To: freebsd-arch@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B0D0937B401 for ; Tue, 11 Feb 2003 13:26:44 -0800 (PST) Received: from c001.snv.cp.net (h005.c001.snv.cp.net [209.228.32.119]) by mx1.FreeBSD.org (Postfix) with SMTP id B5C7643FA3 for ; Tue, 11 Feb 2003 13:26:43 -0800 (PST) (envelope-from kutulu@kutulu.org) Received: (cpmta 26344 invoked from network); 11 Feb 2003 13:26:42 -0800 Received: from 64.212.128.3 (HELO kutulu) by smtp.register-admin.com (209.228.32.119) with SMTP; 11 Feb 2003 13:26:42 -0800 X-Sent: 11 Feb 2003 21:26:42 GMT Message-ID: <00c101c2d214$45cff270$29330f0a@lcapps.educate.com> From: "Kutulu" To: Subject: SCHED_ULE and ps? Date: Tue, 11 Feb 2003 16:26:41 -0500 Organization: KutuluWare Software Services MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1106 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG (Sending this to arch@ cuz UPDATING said to) I just rebuilt my world/kernel with the new ULE scheduler and noticed this happening: root 36 0.0 0.0 0 12 ?? DL 31Dec69 0:00.86 (vnlru) root 37 0.0 0.0 0 12 ?? DL 31Dec69 0:08.40 (syncer) root 128 0.0 0.1 220 52 ?? Ss Mon01PM 0:00.00 adjkerntz -i root 214 0.0 0.4 1164 244 ?? Ss 6:02PM 0:00.45 /sbin/dhclient xl0 root 268 0.0 0.3 644 208 ?? Ss 6:02PM 0:07.38 /sbin/natd -config /usr/local/etc/natd.conf -n xl0 All of the processes in parens (I assume these are internal or system-level processes) show a timestamp of 0, as does /sbin/init itself. All other processes are showing the correct time, or something that looks reasonable. The only item I changed in my kernel config was to change the scheduler. I don't remember seeing this behavior with my previous kernel, which was built last week using the old scheduler, but I only ran it for a short time. I also checked the available 4.6 and 4.7 machines and they don't exhibit this behavior either. I did a complete buildworld and buildkernel, /bin/ps says it was built yesterday around the same time as the kernel, so I don't think there's a world/kernel sync issue here. I'm putting the 4BSD scheduler back to see if this helps, but has anyone else seen this issue? --Mike Edenfield To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message