From owner-freebsd-current@FreeBSD.ORG Tue Feb 10 05:10:24 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5B801106566C for ; Tue, 10 Feb 2009 05:10:24 +0000 (UTC) (envelope-from bms@incunabulum.net) Received: from out1.smtp.messagingengine.com (out1.smtp.messagingengine.com [66.111.4.25]) by mx1.freebsd.org (Postfix) with ESMTP id 323FF8FC12 for ; Tue, 10 Feb 2009 05:10:24 +0000 (UTC) (envelope-from bms@incunabulum.net) Received: from compute2.internal (compute2.internal [10.202.2.42]) by out1.messagingengine.com (Postfix) with ESMTP id 62ED9290EA1 for ; Tue, 10 Feb 2009 00:10:23 -0500 (EST) Received: from heartbeat2.messagingengine.com ([10.202.2.161]) by compute2.internal (MEProxy); Tue, 10 Feb 2009 00:10:23 -0500 X-Sasl-enc: IMwuI2IVnP/zSO3tZ6zifxzDcH9dqEgWxy6oHDrbmrsV 1234242623 Received: from empiric.lon.incunabulum.net (82-35-112-254.cable.ubr07.dals.blueyonder.co.uk [82.35.112.254]) by mail.messagingengine.com (Postfix) with ESMTPSA id F034F2CBBC for ; Tue, 10 Feb 2009 00:10:22 -0500 (EST) Message-ID: <49910C3D.90709@incunabulum.net> Date: Tue, 10 Feb 2009 05:10:21 +0000 From: Bruce M Simpson User-Agent: Thunderbird 2.0.0.19 (X11/20090126) MIME-Version: 1.0 To: FreeBSD Current X-Enigmail-Version: 0.95.6 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: uart(4) not working in QEMU X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 10 Feb 2009 05:10:24 -0000 Hi, I have been trying to test my kernel code in QEMU as it saves a lot of time and effort. However, I have noticed since returning to my current project, that sio(4) was deprecated in favour of uart(4). Whilst I updated my kernel configs to reflect this, I've noticed a lot of problems with I/O and QEMU -- in particular, the kernel will log messages over uart(4) just fine, but when the kernel runs init, I can't get any I/O out of the uart(4) at all, apart from a single 'c' or 'F' character. The kernel continues to log messages OK to the uart0/ttyu0 device regardless of what's going on in userland. If I configure ttyv0 in the QEMU virtual machine up via /etc/ttys to run a getty there, I can get in, and see that the getty for ttyu0 is running. However, echo'ing or cat'ing data to /dev/ttyu0 won't work, even if I kill the getty process first. I just don't see anything appearing in my QEMU serial console. I've tried a lot of combinations of 3wire.115200 vs std.9600, boot.config options, loader.conf options, none of which have solved the problem (mostly working from the threads on this list from when the changes were made). I have also tried other bindings for the QEMU serial device -- e.g. tcp ports, nmdm(4), and always see the same effects. I do have INVARIANTS enabled -- could this be an issue? thanks, BMS