Date: Fri, 19 Apr 2002 08:14:47 -0600 (MDT) From: Randy Smith <randys@amigo.net> To: Andy Farkas <andyf@speednet.com.au> Cc: freebsd-isp@freebsd.org Subject: Re: Clarification of kernel log in messages Message-ID: <20020419081023.K2170-100000@stalker.amigo.net> In-Reply-To: <Pine.BSF.4.33.0204191224330.71410-100000@backup.af.speednet.com.au>
index | next in thread | previous in thread | raw e-mail
Andy, This machine has been in production for two and a half years. So, I would be surprised if it is the cable. -- Randy Smith Amigo.Net Systems Administrator 1-719-589-6100 x 4185 http://www.amigo.net/ On Fri, 19 Apr 2002, Andy Farkas wrote: > Date: Fri, 19 Apr 2002 12:27:42 +1000 (EST) > From: Andy Farkas <andyf@speednet.com.au> > To: Randy Smith <randys@amigo.net> > Subject: Re: Clarification of kernel log in messages > > On Thu, 18 Apr 2002, Randy Smith wrote: > > > I would feel a bit unconfortable about it. Maybe even a _lot_ > > > unconfortable. It's a should-not-occur situation, and may be > > > your first inkling of an impending failure. That's me wearing > > > my 37-years-as-a-mainframe-system-programmer hat, but I think > > > the situation translates well from one arena to the other. > > > > What could cause that, other than impending hardware failure? What can I > > do to monitor this and/or track down the problem? (Hardware is not my thing, > > generally.) > > > > Thanks for the input. > > > > Randy > > > > It *could* be a flaky scsi cable. You never said if this was a new system > or an established one - if its new, you could just now be seeing cable > probs... > > -- > > :{ andyf@speednet.com.au > > Andy Farkas > System Administrator > Speednet Communications > http://www.speednet.com.au/ > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the messagehelp
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020419081023.K2170-100000>