From owner-freebsd-amd64@FreeBSD.ORG  Tue Nov 14 21:09:31 2006
Return-Path: <owner-freebsd-amd64@FreeBSD.ORG>
X-Original-To: freebsd-amd64@freebsd.org
Delivered-To: freebsd-amd64@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 524B116A407;
	Tue, 14 Nov 2006 21:09:31 +0000 (UTC)
	(envelope-from raymond@sundland.com)
Received: from mail.omnimx.net (mail.omnimx.net [64.235.254.12])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 1437443D58;
	Tue, 14 Nov 2006 21:09:31 +0000 (GMT)
	(envelope-from raymond@sundland.com)
Received: from [10.0.1.35] (pool-70-111-92-130.nwrk.east.verizon.net
	[70.111.92.130]) by mail.omnimx.net (Postfix) with ESMTP
	id 57F991704B; Tue, 14 Nov 2006 13:09:28 -0800 (PST)
Message-ID: <455A3079.6010800@sundland.com>
Date: Tue, 14 Nov 2006 16:09:13 -0500
From: "Raymond T. Sundland" <raymond@sundland.com>
User-Agent: Mail/News 3.0a1 (Macintosh/20060315)
MIME-Version: 1.0
To: John Baldwin <jhb@freebsd.org>
References: <003301c70754$56143280$8478020a@medco.com>
	<200611131552.14987.jhb@freebsd.org> <45592F08.40205@sundland.com>
	<200611141252.00756.jhb@freebsd.org>
In-Reply-To: <200611141252.00756.jhb@freebsd.org>
Content-Type: text/plain; charset=ISO-8859-15; format=flowed
Content-Transfer-Encoding: 7bit
X-Content-Filtered-By: Mailman/MimeDel 2.1.5
Cc: freebsd-amd64@freebsd.org
Subject: Re: FW: IPMI kernel module errors on 6.x
X-BeenThere: freebsd-amd64@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Porting FreeBSD to the AMD64 platform <freebsd-amd64.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-amd64>,
	<mailto:freebsd-amd64-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-amd64>
List-Post: <mailto:freebsd-amd64@freebsd.org>
List-Help: <mailto:freebsd-amd64-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-amd64>,
	<mailto:freebsd-amd64-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 14 Nov 2006 21:09:31 -0000

Hi John,

I don't see any of the additional messages that should be output by 
KCS_DEBUG.  I see the code (ifdef's) everywhere, but I don't actually 
see the output.  is this something that should be in dmesg or 
elsewhere?  I even removed the ifdef's to see if the output would be 
displayed in the dmesg without the check, and I see nothing.  I also 
tried loading the module with kldload -v.



John Baldwin wrote:
> On Monday 13 November 2006 21:50, Raymond T. Sundland wrote:
>   
>> This is the output with KCS_DEBUG enabled:
>>
>>     ipmi0: <IPMI System Interface> on isa0
>>     ipmi0: KCS mode found at mem 0xca2 alignment 0x4 on isa
>>     ipmi0: KCS: initial state: 00
>>     ipmi0: KCS: Failed to start write
>>     ipmi0: KCS Error retry exhausted
>>     ipmi0: KCS: Failed to start write
>>     ipmi0: KCS Error retry exhausted
>>     ipmi0: KCS: Failed to start write
>>     ipmi0: KCS Error retry exhausted
>>     ipmi0: Timed out waiting for GET_DEVICE_ID
>>     
>
> Hmmm.  It appears to not be working at all.  You can add more printf's in 
> kcs_start_write() and kcs_error() to see exactly which conditions are 
> failing.  If the status byte was just always stuck as 0x00 kcs_error() should 
> succeed, so it is doing something.
>
>   
>> John Baldwin wrote:
>>     
>>> On Monday 13 November 2006 13:48, Raymond Sundland wrote:
>>>   
>>>       
>>>> I sent this to -questions earlier, but thought I would get a more 
>>>>         
> complete
>   
>>>> response from either -hackers or -amd64.
>>>>     
>>>>         
>>> Try enabling KCS_DEBUG in sys/dev/ipmi/ipmi_kcs.c and save the output to a 
>>> file (it will be a lot!).
>>>
>>>   
>>>       
>
>