From owner-freebsd-proliant@FreeBSD.ORG  Tue Jan 20 09:35:57 2009
Return-Path: <owner-freebsd-proliant@FreeBSD.ORG>
Delivered-To: freebsd-proliant@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 170A11065782
	for <freebsd-proliant@freebsd.org>;
	Tue, 20 Jan 2009 09:35:57 +0000 (UTC)
	(envelope-from bounces@nabble.com)
Received: from kuber.nabble.com (kuber.nabble.com [216.139.236.158])
	by mx1.freebsd.org (Postfix) with ESMTP id E4A4A8FC1B
	for <freebsd-proliant@freebsd.org>;
	Tue, 20 Jan 2009 09:35:56 +0000 (UTC)
	(envelope-from bounces@nabble.com)
Received: from isper.nabble.com ([192.168.236.156])
	by kuber.nabble.com with esmtp (Exim 4.63)
	(envelope-from <bounces@nabble.com>) id 1LPD1Y-0003Eu-Ck
	for freebsd-proliant@freebsd.org; Tue, 20 Jan 2009 01:35:56 -0800
Message-ID: <21559788.post@talk.nabble.com>
Date: Tue, 20 Jan 2009 01:35:56 -0800 (PST)
From: Vyacheslav Druzhinin <dvg@tjc.ru>
To: freebsd-proliant@freebsd.org
In-Reply-To: <21539842.post@talk.nabble.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Nabble-From: dvg@tjc.ru
References: <21539842.post@talk.nabble.com>
Subject: Re: DL160g5p strange problem with the system console
X-BeenThere: freebsd-proliant@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "Technical discussion of FreeBSD on HP ProLiant server platforms."
	<freebsd-proliant.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-proliant>, 
	<mailto:freebsd-proliant-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-proliant>
List-Post: <mailto:freebsd-proliant@freebsd.org>
List-Help: <mailto:freebsd-proliant-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-proliant>, 
	<mailto:freebsd-proliant-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 20 Jan 2009 09:35:57 -0000


Hi,

I didn't pay attension on these messages in dmesg. I think it must be
important

Jan 19 15:07:31 newmail kernel: atkbdc0: <Keyboard controller (i8042)> at
port 0x60,0x64 on isa0
Jan 19 15:07:31 newmail kernel: atkbd0: <AT Keyboard> irq 1 on atkbdc0
Jan 19 15:07:31 newmail kernel: atkbd: unable to set the command byte.
Jan 19 15:07:31 newmail kernel: kbd0 at atkbd0
Jan 19 15:07:31 newmail kernel: atkbd0: [GIANT-LOCKED]
Jan 19 15:07:31 newmail kernel: atkbd0: [ITHREAD]
Jan 19 15:07:31 newmail kernel: psm0: unable to set the command byte.

I googled the same errors occur on  IBM e345 server, the hint was to use usb
keyboard. I haven't one. I'll try to search for a usb keyboard later.

One more thing... all the distros I tried before was AMD64, right now I'm
booting from i386 RELEASE 7.0 ... and it's just works!! What a mess!!

ukbd0: <ServerEngines SE USB Device, class0/0, rev 1.10/0.01, addr 2> on
uhub0 kbd0 at ukbd0
ums0: <ServerEngines SE USB Device, class0/0, rev 1.10/0.01, addr 2> on
uhub0

It's awful but I can't use i386, I lose 4Gb of RAM of the total amount of
8Gb RAM. :(
Is it possible to fix AMD64 drivers for that usb devices?

WBR,
Vyacheslav.

-- 
View this message in context: http://www.nabble.com/DL160g5p-strange-problem-with-the-system-console-tp21539842p21559788.html
Sent from the freebsd-proliant mailing list archive at Nabble.com.