From owner-freebsd-questions Wed Dec 27 16:13:43 1995 Return-Path: owner-questions Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id QAA27089 for questions-outgoing; Wed, 27 Dec 1995 16:13:43 -0800 (PST) Received: from peedub.gj.org (ns035.munich.netsurf.de [194.64.166.35]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id QAA27083 for ; Wed, 27 Dec 1995 16:13:20 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by peedub.gj.org (8.7.3/8.6.9) with SMTP id BAA01193; Thu, 28 Dec 1995 01:08:42 GMT Message-Id: <199512280108.BAA01193@peedub.gj.org> X-Authentication-Warning: peedub.gj.org: Host localhost [127.0.0.1] didn't use HELO protocol To: M C Wong Cc: freebsd-questions@freebsd.org Subject: Re: [2.1R] pager error [2] ? Reply-To: Gary Jennejohn In-reply-to: Your message of "Thu, 28 Dec 1995 10:03:56 EDT." <199512272304.AA266655455@relay.hp.com> Date: Thu, 28 Dec 1995 01:08:41 +0000 From: Gary Jennejohn Sender: owner-questions@freebsd.org Precedence: bulk M C Wong writes: > >> > Follow up to my previous mail, here are more logs observerd : >> > >> > > lespoir:/local/home/wongm 124 > Dec 26 13:56:50 lespoir last message >> > > repeated 126 times >> > > Dec 26 13:56:52 lespoir /kernel: aha0: Invalid bus phase/sequence >> > > Dec 26 13:56:50 lespoir last message repeated 126 times >> > > Dec 26 13:56:52 lespoir /kernel: aha0: Invalid bus phase/sequence >> > > Dec 26 13:56:52 lespoir /kernel: vnode_pager_input: I/O read error >> > > Dec 26 13:56:52 lespoir /kernel: vnode_pager_input: I/O read error >> > > Dec 26 13:56:52 lespoir /kernel: vm_fault: pager input (probably hardwar >e) error, PID 1553 failure >> > > Dec 26 13:56:52 lespoir /kernel: vm_fault: pager input (probably hardwar >e) error, PID 1553 failure >> > > Dec 26 13:56:53 lespoir /kernel: Linux-emul(1204): syslog() not supporte >d (BSD sigreturn) >> > > Dec 26 13:56:53 lespoir /kernel: Linux-emul(1204): syslog() not supporte >d (BSD sigreturn) >> > >> > > [4] EMT trap linux-netscape >> > >> > I am mostly concerned with the "(probably hardware) error" problem. Does a >nyone >> > have a clue ? >> > this looks sort of like a problem I starting seeing when I switched to a P-100. Turns out that my SCSI cable was just a little too long. This only manifested itself when there was very heavy SCSI traffic (make world). The faster processor brought this to light, I never saw it with a 486DX2-66. Check out your cables. --- Gary Jennejohn Home - Gary.Jennejohn@munich.netsurf.de Work - gjennejohn@frt.dec.com