From owner-freebsd-bugs Thu Apr 13 22:30: 9 2000 Delivered-To: freebsd-bugs@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id A135337BE2F for ; Thu, 13 Apr 2000 22:30:04 -0700 (PDT) (envelope-from gnats@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.9.3/8.9.2) id WAA91989; Thu, 13 Apr 2000 22:30:04 -0700 (PDT) (envelope-from gnats@FreeBSD.org) Date: Thu, 13 Apr 2000 22:30:04 -0700 (PDT) Message-Id: <200004140530.WAA91989@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org Cc: From: Rahul Dhesi Subject: Re: kern/17122: crash due to: softdep_disk_write_com Reply-To: Rahul Dhesi Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The following reply was made to PR kern/17122; it has been noted by GNATS. From: Rahul Dhesi To: freebsd-gnats-submit@FreeBSD.org Cc: Subject: Re: kern/17122: crash due to: softdep_disk_write_com Date: Thu, 13 Apr 2000 22:27:52 -0700 I swapped machines, by moving the crash-prone OS configuration to a different box. Now only was I now using all different hardware, but also, the motherboard brand and SCSI host adaptor brand were now different. The crashes continued. Then I rebuilt the kernel omitting softupdates. The crashes stopped. The final conclusion is that the bug is probably either in softupdates or in the way it interacts with some other OS component. And the bug is probably triggered by the way the squid proxy cache does I/O. Rahul To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message