From owner-freebsd-stable Wed Oct 11 16:31:46 1995 Return-Path: owner-stable Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id QAA23370 for stable-outgoing; Wed, 11 Oct 1995 16:31:46 -0700 Received: from Root.COM (implode.Root.COM [198.145.90.17]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id QAA23365 for ; Wed, 11 Oct 1995 16:31:43 -0700 Received: from corbin.Root.COM (corbin [198.145.90.50]) by Root.COM (8.6.12/8.6.5) with ESMTP id QAA13142; Wed, 11 Oct 1995 16:31:42 -0700 Received: from localhost (localhost [127.0.0.1]) by corbin.Root.COM (8.6.12/8.6.5) with SMTP id QAA00927; Wed, 11 Oct 1995 16:31:36 -0700 Message-Id: <199510112331.QAA00927@corbin.Root.COM> To: Mark Hittinger cc: stable@freebsd.org Subject: Re: kill the messenger In-reply-to: Your message of "Wed, 11 Oct 95 11:40:16 EDT." <199510111540.LAA09946@ns1.win.net> From: David Greenman Reply-To: davidg@Root.COM Date: Wed, 11 Oct 1995 16:31:36 -0700 Sender: owner-stable@freebsd.org Precedence: bulk >Hey guys - some of 2.2's badness is bouncing down into 2.1 city. > >After I supped/built/rebooted on Oct 10 the following familiar problems >have surfaced on 2.1. > >1. Pci probe boot hangs on old EISA motherboards (printf's fix it) >2. Unusual file system corruption after a system hang >3. Unusual file system corruption after a panic induced by XFree312 >4. System hang with disk drive light on 100% >5. System hangs very often - within minutes after rebooting. > >All of these problems were noted on 2.2 early last month. 2.1 Kernels >before Oct10 did not exhibit these problems. > >I keep very up-to-date sup trees so these are very recent commits. > >2.1 must not be allowed to go gold with these recent commits intact. I appreciate the feedback, but I'm going to need a lot more information before I'll have any chance of narrowing down the problem. 1) What disk controller are you using? 2) What is the last SUP of -stable that worked without any trouble? 3) Are the problems all happening on the same (old EISA) machine, or are different problems happening on different machines? If the later, please associate the problems with the hardware configurations involved. The only significant things I've changed recently in -stable are pcibus.c and ncr.c. All other significant changes in the kernel were made last week. I'm using the NCR controller in two PCI machines here and have not seen any problems during my regression testing. Hmmm. The weird thing is that there have been relatively few changes to the kernel during the past few weeks - most of them were to recently added device drivers, and the rest were well-controlled bugfixes. I'll send you an older rev of sys/i386/isa/pcibus.c - it's the only thing I can think of that might cause the above problems. -DG