From owner-freebsd-questions@FreeBSD.ORG Tue Mar 13 08:30:19 2007 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 7CE0716A400 for ; Tue, 13 Mar 2007 08:30:17 +0000 (UTC) (envelope-from list@museum.rain.com) Received: from ns.umpquanet.com (ns.umpquanet.com [63.105.30.37]) by mx1.freebsd.org (Postfix) with ESMTP id 1CC6613C480 for ; Tue, 13 Mar 2007 08:30:16 +0000 (UTC) (envelope-from list@museum.rain.com) Received: from ns.umpquanet.com (localhost [127.0.0.1]) by ns.umpquanet.com (8.13.8/8.13.8) with ESMTP id l2D86C6P019834 for ; Tue, 13 Mar 2007 01:06:12 -0700 (PDT) (envelope-from list@museum.rain.com) Received: (from james@localhost) by ns.umpquanet.com (8.13.8/8.13.8/Submit) id l2D86Clx019833 for freebsd-questions@freebsd.org; Tue, 13 Mar 2007 01:06:12 -0700 (PDT) (envelope-from list@museum.rain.com) X-Authentication-Warning: ns.umpquanet.com: james set sender to list@museum.rain.com using -f Date: Tue, 13 Mar 2007 01:06:12 -0700 From: James Long To: freebsd-questions@freebsd.org Message-ID: <20070313080612.GA19177@ns.umpquanet.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.13 (2006-08-11) Subject: dmesg and GIANT-LOCK X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Mar 2007 08:30:19 -0000 With regard to the recent thread about looking for GIANT-LOCKs in dmesg, why would one system say: ns : 00:56:29 /home/james> uname -v ;dmesg | grep fxp FreeBSD 6.2-STABLE #0: Tue Feb 20 15:47:09 PST 2007 fxp0: port 0x2400-0x243f mem 0xc4fff000-0xc4ffffff,0xc4e00000-0xc4efffff irq 10 at device 2.0 on pci0 miibus0: on fxp0 fxp0: Ethernet address: 00:02:a5:0a:57:73 while a more recent build says: t30 : 00:56:19 /home/james> uname -v ;dmesg | grep fxp FreeBSD 6.2-STABLE #2: Thu Mar 8 08:23:11 PST 2007 fxp0: port 0x7400-0x743f mem 0xd0200000-0xd0200fff irq 11 at device 8.0 on pci2 miibus0: on fxp0 fxp0: Ethernet address: 00:09:6b:86:82:a6 fxp0: [GIANT-LOCKED] Is it just the difference in chipset/controller type that requires the fxp driver to use GIANT on the second machine, but not the first? I also note that on the first machine, irq 10 is solely assigned to fxp0. On t30, irq 11 is shared with a number of other devices. Dunno if that matters. Thanks!