From owner-freebsd-stable@FreeBSD.ORG Fri Jun 17 16:27:22 2011 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4EB9E106567B for ; Fri, 17 Jun 2011 16:27:22 +0000 (UTC) (envelope-from jack.vogel@intel.com) Received: from mga09.intel.com (mga09.intel.com [134.134.136.24]) by mx1.freebsd.org (Postfix) with ESMTP id 2064A8FC1A for ; Fri, 17 Jun 2011 16:27:21 +0000 (UTC) Received: from orsmga001.jf.intel.com ([10.7.209.18]) by orsmga102.jf.intel.com with ESMTP; 17 Jun 2011 09:27:21 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="4.65,382,1304319600"; d="scan'208";a="16282670" Received: from orsmsx603.amr.corp.intel.com ([10.22.226.49]) by orsmga001.jf.intel.com with ESMTP; 17 Jun 2011 09:27:21 -0700 Received: from orsmsx605.amr.corp.intel.com (10.22.226.10) by orsmsx603.amr.corp.intel.com (10.22.226.49) with Microsoft SMTP Server (TLS) id 8.2.255.0; Fri, 17 Jun 2011 09:27:21 -0700 Received: from orsmsx508.amr.corp.intel.com ([10.22.226.46]) by orsmsx605.amr.corp.intel.com ([10.22.226.10]) with mapi; Fri, 17 Jun 2011 09:27:21 -0700 From: "Vogel, Jack" To: Bartosz Stec Date: Fri, 17 Jun 2011 09:27:20 -0700 Thread-Topic: Panic during kernel booting on HP Proliant DL180G6 and latest STABLE Thread-Index: Acws9Fw7xaBG0uQ7RxSO7c3SPO5KAgAFqBEg Message-ID: <1DB50624F8348F48840F2E2CF6040A9D018D22E697@orsmsx508.amr.corp.intel.com> References: <4DC6A277.4030801@it4pro.pl> <4DC6E23B.2040207@it4pro.pl> <4DC81E22.5030806@it4pro.pl> <4DCC3844.6070008@it4pro.pl> <4DCD1672.4020405@FreeBSD.org> <4DF1DC26.5010600@it4pro.pl> <20110610093728.GA39453@icarus.home.lan> <4DF1EB98.9080109@it4pro.pl> <1DB50624F8348F48840F2E2CF6040A9D018ACA75C7@orsmsx508.amr.corp.intel.com> <4DFB59A6.9030508@it4pro.pl> In-Reply-To: <4DFB59A6.9030508@it4pro.pl> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Cc: FreeBSD Stable , Jeremy Chadwick Subject: RE: Panic during kernel booting on HP Proliant DL180G6 and latest STABLE X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 17 Jun 2011 16:27:22 -0000 Yes, there have been a few times when I have seen something like this, and = issue when the driver is static and not when modulized. I have never been c= lear what to make of this. If anyone else here has any thoughts or enlighte= ning ideas I'd appreciate it. Also if it does not even happen when using th= e GENERIC config then it would be interesting to see the diff between that = and what does cause the panic. Regards, Jack -----Original Message----- From: Bartosz Stec [mailto:bartosz.stec@it4pro.pl]=20 Sent: Friday, June 17, 2011 6:42 AM To: Vogel, Jack Cc: Jeremy Chadwick; FreeBSD Stable Subject: Re: Panic during kernel booting on HP Proliant DL180G6 and latest = STABLE W dniu 2011-06-10 20:23, Vogel, Jack pisze: > Er, so what if you get rid of ZFS, does your panic go away? It doesn't r= eally matter what type adapter it is, the igb driver only requests standard= size clusters, so memory is getting trashed somewhere I suspect. > > Jack Well, from my observations about this issue (which could be very wrong=20 because my lack of knowledge about BSD kernel) I don't suspect igb=20 driver directly, but rather an order which kernel is processing stuff=20 related to MSIX and hardware (so I suppose that real cause of the=20 problem could be very hard to catch and repeat)? Here's why: 1. There's no panic when using GENERIC kernel. There's also nothing=20 unusual in my custom kernel (included in thread), neither in make.conf. 2. Before current build, panic was seen with igb driver included in=20 kernel, but no panic when using a module. Even better - no panic when=20 trying to load a module while igb driver is stil included in source. No=20 random memory corruption here - same scenario seen every boot with all=20 variants above. It's HP server with HP ECC memory by the way. 3. With current build kernel panics regardless if igb driver is a module=20 or included in kernel (unless i disable MSIX). But I found override - I=20 removed igb driver from kernel config, and a module from loader.conf.=20 Than booted in single user mode, and manually loaded igb driver. No=20 panic! Appareantly something gets wrong _only_ at boot time. --=20 Bartosz Stec