Date: Tue, 14 Nov 2006 12:51:59 -0500 From: John Baldwin <jhb@freebsd.org> To: "Raymond T. Sundland" <raymond@sundland.com> Cc: freebsd-amd64@freebsd.org Subject: Re: FW: IPMI kernel module errors on 6.x Message-ID: <200611141252.00756.jhb@freebsd.org> In-Reply-To: <45592F08.40205@sundland.com> References: <003301c70754$56143280$8478020a@medco.com> <200611131552.14987.jhb@freebsd.org> <45592F08.40205@sundland.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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!). > > > > > -- John Baldwin
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200611141252.00756.jhb>