From owner-freebsd-current@FreeBSD.ORG Fri Nov 23 10:21:21 2007 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 217B616A46D for ; Fri, 23 Nov 2007 10:21:21 +0000 (UTC) (envelope-from frank@pinky.sax.de) Received: from post.frank-behrens.de (post.frank-behrens.de [82.139.255.138]) by mx1.freebsd.org (Postfix) with ESMTP id 5253E13C4E1 for ; Fri, 23 Nov 2007 10:21:20 +0000 (UTC) (envelope-from frank@pinky.sax.de) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=pinky.sax.de; h=from:to:date:mime-version:subject:in-reply-to:references:content-type:content-transfer-encoding:content-description; q=dns/txt; s=pinky1; t=1195813277; i=frank@pinky.sax.de; bh=6zhwItMikTVjbZzrS4uxmG49OKQDNxdSEidwvRB8S4s=; b=JbTHFQLGylZJXP1IQVfnVPZgQzcXHV4c15ugk77Df1jsWT7r35OsT6/BBACh7mYtwyDFzL/fF3PzhUoD5Y3aQA== Received: from [192.168.20.32] (sun.behrens [192.168.20.32]) by post.frank-behrens.de (8.14.2/8.14.1) with ESMTP-MSA id lANAKvSr003061 for ; Fri, 23 Nov 2007 11:20:57 +0100 (CET) (envelope-from frank@pinky.sax.de) Message-Id: <200711231020.lANAKvSr003061@post.frank-behrens.de> From: "Frank Behrens" To: freebsd-current@freebsd.org Date: Fri, 23 Nov 2007 11:20:57 +0100 MIME-Version: 1.0 Priority: normal In-reply-to: <200711221554.lAMFsRdS002781@post.frank-behrens.de> References: <20071122134146.B53707@maildrop.int.zabbadoz.net> X-mailer: Pegasus Mail for Windows (4.31, DE v4.31 R1) Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Content-description: Mail message body X-Hashcash: 1:24:071123:freebsd-current@freebsd.org::sBEVhrIZaPI4Q2+5:0000001AscJ Subject: Re: Can not boot 7.0-BETA3 with puc (was: Can not boot 7.0-BETA3 with IPSEC) 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: Fri, 23 Nov 2007 10:21:21 -0000 My in previous email described problem is not caused by IPSEC setup. I should have investigated this much better. :-( Thanks to Bjoern for his debugging hints. The 7.0-BETA3 seems to have a problem with puc(4) driver. When I enable the driver with kernel configuration device puc nodevice uart options COM_MULTIPORT I see the following effects: 1. The sio(4) does not attach as in RELENG_6 to the ports provided by puc(4) driver. In RELENG_7 it shows as puc0: port 0xdf00-0xdf1f,0xdec0-0xdedf mem 0xfe6f8000-0xfe6f8fff,0xfe6f7000-0xfe6f7fff irq 21 at device 13.0 on pci2 puc0: Reserved 0x20 bytes for rid 0x10 type 4 at 0xdf00 ioapic0: routing intpin 21 (PCI IRQ 21) to vector 54 puc0: [FILTER] sio0 on puc0 sio0: type 16550A, console sio0: [FILTER] sio1: reserved for low-level i/o where RELENG_6 shows puc0: port 0xdf00-0xdf1f,0xdec0-0xdedf mem 0xfe6f8000-0xfe6f8fff,0xfe6f7000-0xfe6f7fff irq 21 at device 13.0 on pci2 sio4: on puc0 sio4: type 16550A sio4: unable to activate interrupt in fast mode - using normal mode sio5: on puc0 sio5: type 16550A sio5: unable to activate interrupt in fast mode - using normal mode .... sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 sio0: type 16550A, console sio1: reserved for low-level i/o In RELENG_6 the sio0 and sio1 are the ports on motherboard, the ports on external card are mapped to sio4, sio5 and so on. In RELENG_7 the 1st port on external card seems to be mapped to sio0 and nothing else. In both cases the content of /boot/device.hints is: hint.sio.0.at="isa" hint.sio.0.port="0x3F8" hint.sio.0.flags="0x10" hint.sio.0.irq="4" hint.sio.1.at="isa" hint.sio.1.disabled="1" hint.sio.1.flags="0x40" hint.sio.1.port="0x2F8" hint.sio.1.irq="3" hint.sio.2.at="isa" hint.sio.2.disabled="1" hint.sio.2.port="0x3E8" hint.sio.2.irq="5" hint.sio.3.at="isa" hint.sio.3.disabled="1" hint.sio.3.port="0x2E8" hint.sio.3.irq="9" 2. The kernel boot is not completed, probably because serial console is remapped. I'll try to debug this problem further. Or does somebody have an explanation for this behaviour? Regards, Frank -- Frank Behrens, Osterwieck, Germany PGP-key 0x5B7C47ED on public servers available.