From owner-freebsd-stable@FreeBSD.ORG Wed Feb 29 09:12:07 2012 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 954EE1065674; Wed, 29 Feb 2012 09:12:07 +0000 (UTC) (envelope-from admin@govital.net) Received: from mail.govital.net (mail.govital.net [209.183.5.10]) by mx1.freebsd.org (Postfix) with ESMTP id 3AA628FC0A; Wed, 29 Feb 2012 09:12:06 +0000 (UTC) Received: from govital.net (localhost [127.0.0.1]) by mail.govital.net (Postfix) with ESMTP id A51704BD55; Wed, 29 Feb 2012 03:54:02 -0500 (EST) From: "Chris Demers" To: Harry Newton ,Adrian Chadd Date: Wed, 29 Feb 2012 03:54:02 -0500 Message-Id: <20120229084249.M5878@govital.net> In-Reply-To: References: <1330459721.1023.15.camel@revolution.hippie.lan> X-Mailer: OpenWebMail 2.53 20080403 301 X-OriginatingIP: 216.8.180.103 (admin) MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 X-govital-MailScanner-Information: Please contact the ISP for more information X-MailScanner-ID: A51704BD55.A37BA X-govital-MailScanner: Found to be clean X-govital-MailScanner-From: admin@govital.net X-Spam-Status: No Cc: Ian Lepore , freebsd-stable@freebsd.org, jhb@freebsd.org Subject: Re: Regression between 9-RELEASE and 9-STABLE [PCIB ?] 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: Wed, 29 Feb 2012 09:12:07 -0000 Greetings Everyone, Along this same topic, I have also had a problem with 9-STABLE being unstable. I have been experiencing random kernel core dumps on a machine. I know the machine is fine, if i switch back to a set of disks running my previous 8-stable everything is fine. But with a current 9-STABLE as of last night even I get kernel panics. Can provide more details tomorrow, machine is currently panicked in the data center and need to go there in the morning to reboot. Hoping it gets fixed soon, want to start bringing the machine into production slowly, don't want to have to roll back to 9-release would rather see this fixed. But i believe it is a variation of the exact same problem that has been brought up here. Last panic it created a core file, hopefully it did again so i can debug it. On Tue, 28 Feb 2012 23:10:51 +0000, Harry Newton wrote > Adrian - thanks ! > > John, if you write me a shopping list of what information you think > useful, assuming you have time and inclination, I'll do my best > provide it. > > On 28 February 2012 23:04, Adrian Chadd wrote: > > A lot of the PCI bus enumeration and configuration code has changed. > > > > John's likely the best person to bring into this. He's been doing a > > lot of the PCI bus hacking and has found/fixed quite a few > > regressions. > > > > Good luck! > > > > > > > > Adrian > > > > > > On 28 February 2012 14:26, Harry Newton wrote: > >> Not really. Verbose suggests it completes the scan of the PCI to LPC > >> Bridge and PCI to PCI bridge. Comparing with a working verbose boot, > >> the next stage, which isn't reached, is HyperTransport Technology > >> Configuration. > >> > >> Trying BUS_DEBUG, I got a lot of this: > >> > >> device_add_child_ordered: 1813: (null) at pci with orer 0 as unit -1 > >> make_device: 1698: (null) at pci as unit -1 > >> > >> I neglected to say before: the machine's been running FreeBSD 7-STABLE > >> quite happily with no problems. > >> > >> - Harry > >> > >> > >> On 28 February 2012 20:08, Ian Lepore wrote: > >>> On Tue, 2012-02-28 at 19:15 +0000, Harry Newton wrote: > >>>> 9-RELEASE works fine. csup to 9-STABLE and make buildworld kernel etc > >>>> gives a system the hangs during the boot process. There are no error > >>>> messages during the part boot, and no panic. Last messages before hang > >>>> are: > >>>> > >>>> pcib0: port 0xcf8-0xcff on acpi0 > >>>> pci0: on pcib0 > >>>> > >>>> I am stumped about how to diagnose this, and would be _very_ grateful > >>>> for any suggestions. > >>>> > >>>> When it's hung I can't force a break to debugger (BREAK_TO_DEBUGGER) > >>>> in kern conf: I imagine I'm too early in the boot sequence. > >>>> > >>>> - Harry > >>>> > >>> > >>> I assume booting verbose doesn't provide any more clues?  I've sometimes > >>> gotten an extra clue from a hang during boot by building with option > >>> BUS_DEBUG.  Even if you don't suspect the newbus routines as directly > >>> being the problem, sometimes you get a bit more info about what was > >>> happening at the time of lockup. > >>> > >>> -- Ian > >>> > >>> > >> > >> > >> > >> -- > >> Harry Newton > >> _______________________________________________ > >> freebsd-stable@freebsd.org mailing list > >> http://lists.freebsd.org/mailman/listinfo/freebsd-stable > >> To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" > > -- > Harry Newton > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" > > -- > This message has been scanned for viruses and > dangerous content by MailScanner, and is > believed to be clean. -- Chris Demers admin@govital.net www.govital.net -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.