From owner-freebsd-stable  Wed Oct 11 08:35:06 1995
Return-Path: owner-stable
Received: (from root@localhost)
          by freefall.freebsd.org (8.6.12/8.6.6) id IAA10930
          for stable-outgoing; Wed, 11 Oct 1995 08:35:06 -0700
Received: from ns1.win.net (ns1.win.net [204.215.209.3])
          by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id IAA10924
          for <stable@freebsd.org>; Wed, 11 Oct 1995 08:35:03 -0700
Received: (from bugs@localhost) by ns1.win.net (8.6.11/8.6.9) id LAA09946 for stable@freebsd.org; Wed, 11 Oct 1995 11:40:17 -0400
From: Mark Hittinger <bugs@ns1.win.net>
Message-Id: <199510111540.LAA09946@ns1.win.net>
Subject: kill the messenger
To: stable@freebsd.org
Date: Wed, 11 Oct 1995 11:40:16 -0400 (EDT)
X-Mailer: ELM [version 2.4 PL23]
Content-Type: text
Content-Length: 801       
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.

Regards,

Mark Hittinger
Internet Manager
WinNET Communications, Inc.
bugs@win.net