Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S266864AbUIORIp (ORCPT ); Wed, 15 Sep 2004 13:08:45 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S266626AbUIORIp (ORCPT ); Wed, 15 Sep 2004 13:08:45 -0400 Received: from sweetums.bluetronic.net ([24.199.150.42]:29899 "EHLO sweetums.bluetronic.net") by vger.kernel.org with ESMTP id S266845AbUIORBr (ORCPT ); Wed, 15 Sep 2004 13:01:47 -0400 Date: Wed, 15 Sep 2004 12:58:57 -0400 (EDT) From: Ricky Beam To: Jeff Garzik cc: Lee Revell , Zilvinas Valinskas , Erik Tews , linux-kernel mailing list Subject: Re: 2.6.9 rc2 freezing In-Reply-To: <414869AB.5070307@pobox.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1057 Lines: 27 On Wed, 15 Sep 2004, Jeff Garzik wrote: >Lee Revell wrote: >> Anyway, if you are running anything on your server that breaks under >> PREEMPT, it will break anyway as soon as you add another processor. > >Incorrect. The spinlock behavior is very different. Indeed. Enable PREEMPT (my default for some time now) and the machine will lockup after spewing pages of scheduling while atomic's. Disable PREEMPT and the machine is stable again: [jfbeam:pts/2{2}]gir:~/[12:55pm]:uname -a Linux gir 2.6.9-SMP-rc2+BK@1.1455 #71 SMP BK[20040914173940] Tue Sep 14 16:14:33 EDT 2004 i686 athlon i386 GNU/Linux [jfbeam:pts/2{2}]gir:~/[12:55pm]:uptime 12:55pm up 19:54, 2 users, load average: 0.01, 0.02, 0.00 [jfbeam:pts/2{2}]gir:~/[12:55pm]:grep ^proc /proc/cpuinfo processor : 0 processor : 1 --Ricky - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/