From owner-freebsd-questions@FreeBSD.ORG Wed Mar 21 14:21:45 2007 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id EFCD416A400 for ; Wed, 21 Mar 2007 14:21:44 +0000 (UTC) (envelope-from xfb52@dial.pipex.com) Received: from smtp-out4.blueyonder.co.uk (smtp-out4.blueyonder.co.uk [195.188.213.7]) by mx1.freebsd.org (Postfix) with ESMTP id 7C56D13C4EA for ; Wed, 21 Mar 2007 14:21:44 +0000 (UTC) (envelope-from xfb52@dial.pipex.com) Received: from [172.23.170.146] (helo=anti-virus03-09) by smtp-out4.blueyonder.co.uk with smtp (Exim 4.52) id 1HU1h9-0005FZ-7n; Wed, 21 Mar 2007 14:21:43 +0000 Received: from [62.31.10.181] (helo=[192.168.0.2]) by asmtp-out1.blueyonder.co.uk with esmtp (Exim 4.52) id 1HU1h8-00012y-00; Wed, 21 Mar 2007 14:21:42 +0000 Message-ID: <46013F75.2060508@dial.pipex.com> Date: Wed, 21 Mar 2007 14:21:41 +0000 From: Alex Zbyslaw User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-GB; rv:1.7.13) Gecko/20061205 X-Accept-Language: en MIME-Version: 1.0 To: abhishek singh References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-questions@freebsd.org Subject: Re: Kernel error X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 21 Mar 2007 14:21:45 -0000 abhishek singh wrote: > Hey > > I am getting this " kernel: sis0: Applying short cable fix (reg=e8)" > kernel > error in /var/log/messages what it does mean .I am using FreeBSD 5.4. You can ignore it; it an advisory message only. The chipset used for sis0 needs some different parameters if you use a short cable - I believe these come from the manufacturer. In fact, with an sis0 chipset I always get this message even when using a cable which I believe is not "short", but everything works just fine. I'm sure that google would tell you more. Unless you have actual ethernet errors (e.g. as shown by "netstat -i -I sis0") then ignore it. --Alex