From owner-freebsd-mobile@freebsd.org Wed Mar 2 00:11:19 2016 Return-Path: Delivered-To: freebsd-mobile@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id ED6A9ABFEDD for ; Wed, 2 Mar 2016 00:11:18 +0000 (UTC) (envelope-from johannes@brilliantservice.co.jp) Received: from mail-vk0-x235.google.com (mail-vk0-x235.google.com [IPv6:2607:f8b0:400c:c05::235]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id AC575119A for ; Wed, 2 Mar 2016 00:11:18 +0000 (UTC) (envelope-from johannes@brilliantservice.co.jp) Received: by mail-vk0-x235.google.com with SMTP id e185so185555236vkb.1 for ; Tue, 01 Mar 2016 16:11:18 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=brilliantservice-co-jp.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=XEh99uESLezjPDA5PCgpq/SKU5/4BG+2c/SLoO0LmME=; b=vUw7GLnPKHS1pU+ZIMPTljzf6wUC7BTMYvtY4QriHaS4iLHLTHkgtGfVsOmZRdJ2HI JPDaO5uy4YNjh9rMh5P7oZpvNmP6gQAGnUvkEzCpHJxwNoRSOgwY73T4OblnomXA9hMe b+GTaBERZDYnogY03FxIFmafxklfY3ev8SeneNMwn/pmkS33gShaadpGT5lBC8NK+4aM xWNKEKumiLlNQ6g+Tr/JtDVVevp2zvZsw09wINd2O5cu0TRnkReliXQCyBSDlQu9QH6C 2IFtUm4KE97VFPM4X8TNhnwMRbrHVocSn3zgBBsDL+gCqGA6uMSgf1mjyOdNzVA9m30R bdhg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=XEh99uESLezjPDA5PCgpq/SKU5/4BG+2c/SLoO0LmME=; b=TLJSERg7WWT0xcZGtube77nArS1HposmFbGA2nOFMEHnFwHDRWStXMX3W0MFyGRZai pmjQtmVElpv6UcUGG6sucUIoHsJYBGVky6AXwqRnZqEax1o/SZ0VACtyfZeX06181mzf na3HthH8I89aKgNzJapSitD/2quq5HzyPcNiyawiy52sVh+iSOGmlugxn0d98/aXRT/6 3ljBSR0gKPxD3zo4wrSW6c9+hI3Gry8zm1vwB8LB3MR4L4mhgnsS5mHQX/tqNEIxevIV JLrELnRe0XqBzFsEE1eP4Fz1iVyY6NnMZ1C9dnZHVvT8pi2CGDBQnNKQkf41TQr8ZReD XahQ== X-Gm-Message-State: AD7BkJJ83KdKr12ekKR5/SITzKBGaUSL618EDeBHB/HJzDAi+WXH5ueTlaVNJso5hxyqFR/ztoWOR7dIs+AgI1sNWPYEoVNmH9v2qq1duxRg20BYsgVDdjryZ+QaLZsGEPvmrGXqjzqWV/NLajKu3lhnXg== X-Received: by 10.31.16.218 with SMTP id 87mr18377113vkq.105.1456877477406; Tue, 01 Mar 2016 16:11:17 -0800 (PST) MIME-Version: 1.0 Received: by 10.159.36.197 with HTTP; Tue, 1 Mar 2016 16:11:02 -0800 (PST) In-Reply-To: <00A3C4F0-AEEE-4341-9D5C-3810A9A08EA3@xcllnt.net> References: <4E9118B0-FC9F-444F-B277-3E5BAE75C723@xcllnt.net> <20160227172039.F26318@sola.nimnet.asn.au> <00A3C4F0-AEEE-4341-9D5C-3810A9A08EA3@xcllnt.net> From: "Lundberg, Johannes" Date: Tue, 1 Mar 2016 16:11:02 -0800 Message-ID: Subject: Re: hint.uart.1 in device.hints causes freeze at boot To: Marcel Moolenaar Cc: Ian Smith , Warner Losh , "freebsd-mobile@freebsd.org" , "freebsd-embedded@freebsd.org" Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.20 X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Mar 2016 00:11:19 -0000 Hi Marcel Switching to PCI does not help the halting boot, only disabling UART1 does. I'm working with UART0 (in PCI mode with Adafruit cable) to get serial console output but all I get is garbage (question marks with filled elliptic background) from BIOS. When kernel is loaded output stops. Where did you get this info? hw.uart.console=3D"mm:0xd0810000,br:115200,rs:2,xo:44236800 The only info I can find is that this address is for the sound chip(?).. Even though HDMI is working out of the box it would be nice to also have serial console for when you don't wanna carry around a big monitor... On Sat, Feb 27, 2016 at 9:22 AM, Marcel Moolenaar wrote= : > > On Feb 27, 2016, at 5:54 AM, Lundberg, Johannes < > johannes@brilliantservice.co.jp> wrote: > > >though I've no clue why or how that should cause a boot failure? > > Verbose logging don't give any clues either.. It just stops. > > > On the Atom SoC I have, you can configure the UARTs as PCI or ACPI device= s. > They work as PCI devices but required better support for memory mapped lo= w- > level consoles in x86. If configured as ACPI (supposedly compatible), the= y > just > don=E2=80=99t work. I belief FreeBSD would just hang when configured as A= CPI, but > I=E2=80=99m > foggy on that detail. > > Key is that they we=E2=80=99re trimmed-down UARTs (3-wire functionality) = and thus > weird > beasts... > > Johannes: If your BIOS has the same capability, try switching. PCI mode i= s > well > supported in FreeBSD, though requires something like the following in you= r > loader.conf: > > hw.uart.console=3D"mm:0xd0810000,br:115200,rs:2,xo:44236800 > > This tells the uart(4) driver that the device is memory mapped (at I/O > address 0xd0810000, uses 32-bit register access and has a non-standard > clock input of 44236800 (=3D44Mhz). > > -- > Marcel Moolenaar > marcel@xcllnt.net > > --=20 =3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D= -=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D- =E7=A7=98=E5=AF=86=E4=BF=9D=E6=8C=81=E3=81=AB=E3=81=A4=E3=81=84=E3=81=A6=EF= =BC=9A=E3=81=93=E3=81=AE=E9=9B=BB=E5=AD=90=E3=83=A1=E3=83=BC=E3=83=AB=E3=81= =AF=E3=80=81=E5=90=8D=E5=AE=9B=E4=BA=BA=E3=81=AB=E9=80=81=E4=BF=A1=E3=81=97= =E3=81=9F=E3=82=82=E3=81=AE=E3=81=A7=E3=81=82=E3=82=8A=E3=80=81=E7=A7=98=E5= =8C=BF=E7=89=B9=E6=A8=A9=E3=81=AE=E5=AF=BE=E8=B1=A1=E3=81=A8=E3=81=AA=E3=82= =8B=E6=83=85=E5=A0=B1=E3=82=92=E5=90=AB=E3=82=93=E3=81=A7=E3=81=84=E3=81=BE= =E3=81=99=E3=80=82 =E3=82=82=E3=81=97=E3=80=81=E5=90=8D=E5=AE=9B=E4=BA=BA=E4=BB=A5=E5=A4=96=E3= =81=AE=E6=96=B9=E3=81=8C=E5=8F=97=E4=BF=A1=E3=81=95=E3=82=8C=E3=81=9F=E5=A0= =B4=E5=90=88=E3=80=81=E3=81=93=E3=81=AE=E3=83=A1=E3=83=BC=E3=83=AB=E3=81=AE= =E7=A0=B4=E6=A3=84=E3=80=81=E3=81=8A=E3=82=88=E3=81=B3=E3=81=93=E3=81=AE=E3= =83=A1=E3=83=BC=E3=83=AB=E3=81=AB=E9=96=A2=E3=81=99=E3=82=8B=E4=B8=80=E5=88= =87=E3=81=AE=E9=96=8B=E7=A4=BA=E3=80=81 =E8=A4=87=E5=86=99=E3=80=81=E9=85=8D=E5=B8=83=E3=80=81=E3=81=9D=E3=81=AE=E4= =BB=96=E3=81=AE=E5=88=A9=E7=94=A8=E3=80=81=E3=81=BE=E3=81=9F=E3=81=AF=E8=A8= =98=E8=BC=89=E5=86=85=E5=AE=B9=E3=81=AB=E5=9F=BA=E3=81=A5=E3=81=8F=E3=81=84= =E3=81=8B=E3=81=AA=E3=82=8B=E8=A1=8C=E5=8B=95=E3=82=82=E3=81=95=E3=82=8C=E3= =81=AA=E3=81=84=E3=82=88=E3=81=86=E3=81=8A=E9=A1=98=E3=81=84=E7=94=B3=E3=81= =97=E4=B8=8A=E3=81=92=E3=81=BE=E3=81=99=E3=80=82 --- CONFIDENTIALITY NOTE: The information in this email is confidential and intended solely for the addressee. Disclosure, copying, distribution or any other action of use of this email by person other than intended recipient, is prohibited. If you are not the intended recipient and have received this email in error, please destroy the original message. From owner-freebsd-mobile@freebsd.org Wed Mar 2 00:45:36 2016 Return-Path: Delivered-To: freebsd-mobile@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 103A9ABDCB3; Wed, 2 Mar 2016 00:45:36 +0000 (UTC) (envelope-from marcel@xcllnt.net) Received: from mail.xcllnt.net (mail.xcllnt.net [50.0.150.214]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id CE314122D; Wed, 2 Mar 2016 00:45:35 +0000 (UTC) (envelope-from marcel@xcllnt.net) Received: from [10.1.254.16] (cerberus.brkt.com [208.185.168.138]) (authenticated bits=0) by mail.xcllnt.net (8.15.2/8.15.2) with ESMTPSA id u220jPPZ067537 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 1 Mar 2016 16:45:25 -0800 (PST) (envelope-from marcel@xcllnt.net) Subject: Re: hint.uart.1 in device.hints causes freeze at boot Mime-Version: 1.0 (Mac OS X Mail 9.2 \(3112\)) Content-Type: multipart/signed; boundary="Apple-Mail=_972C3F82-C4BC-4950-8943-6305D0563A64"; protocol="application/pgp-signature"; micalg=pgp-sha512 X-Pgp-Agent: GPGMail 2.6b2 From: Marcel Moolenaar In-Reply-To: Date: Tue, 1 Mar 2016 16:45:19 -0800 Cc: Ian Smith , Warner Losh , "freebsd-mobile@freebsd.org" , "freebsd-embedded@freebsd.org" Message-Id: References: <4E9118B0-FC9F-444F-B277-3E5BAE75C723@xcllnt.net> <20160227172039.F26318@sola.nimnet.asn.au> <00A3C4F0-AEEE-4341-9D5C-3810A9A08EA3@xcllnt.net> To: "Lundberg, Johannes" X-Mailer: Apple Mail (2.3112) X-Content-Filtered-By: Mailman/MimeDel 2.1.20 X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Mar 2016 00:45:36 -0000 --Apple-Mail=_972C3F82-C4BC-4950-8943-6305D0563A64 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 > On Mar 1, 2016, at 4:11 PM, Lundberg, Johannes = wrote: >=20 > Hi Marcel >=20 > Switching to PCI does not help the halting boot, only disabling UART1 = does. >=20 > I'm working with UART0 (in PCI mode with Adafruit cable) to get serial = console output but all I get is garbage (question marks with filled = elliptic background) from BIOS. When kernel is loaded output stops. >=20 > Where did you get this info? > hw.uart.console=3D"mm:0xd0810000,br:115200,rs:2,xo:44236800 >=20 > The only info I can find is that this address is for the sound = chip(?).. The address may be different for you. It=E2=80=99s dependent on the = devices that you have enabled in the BIOS. If you can boot FreeBSD and login to it, dmesg(8) will tell you what address to use. -- Marcel Moolenaar marcel@xcllnt.net --Apple-Mail=_972C3F82-C4BC-4950-8943-6305D0563A64 Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=signature.asc Content-Type: application/pgp-signature; name=signature.asc Content-Description: Message signed with OpenPGP using GPGMail -----BEGIN PGP SIGNATURE----- Comment: GPGTools - https://gpgtools.org iQIcBAEBCgAGBQJW1jefAAoJEIda8t8f0tjjQJ8P+wZUoAeJ2CYXQTV1HPLxdMFF Um1M4SspJQG7G4Bipr2MXQjCLZMbPoDktjfIhspRRAo+Qts0I5nBYzVIFrHN4ZpW AQOiz6hLLazPtNE9Kq47IWmTibKXQseJR/F38E1UZ2IKWy2VWFbid9kWBktwX+xm MQ5fh/sCEms79BqiCXJhCzi5TNECWQ7yMJMEsQTtC2lVNsh7n95eY/+AyPwGJ3i4 IuGHOhYD00bEU3NjrWvFJFgPZPZEyvb+iu2ysdeo0A5yeM96gyc5YuIFiCTLva1A UCkAYa6VyCC3x1Z1B0dgI64d1Omg651wLjhLKHgEDoH9MsUkY1OKDIebK6pIf1pz g+eF98ygUeiyJISfilbhRub2CVimGEPTOaKDCbjV1e95ftBLsXSRJ1r5SnCZuqbW 11Kowkmu255EXWa8SnBocFBAA6lvdvnp4rvZttesOpk/Qra4jHdIyFhHJpYaqhgi T82tUEpsPY/qoX3EBuN2ITasMvOL8skfNMH1ogYtTbNw+dG93hXPGl1PazlVqN2o ILXMF3SMrjsVJWO6/ncRY9XTF36ZD+qNj7RtU6oceR5fbRorJBBp2f4KYEi86rrM BE9vEqos4Hz8YhrCkmv+OX3wtbmDtL5MnUWd/yo1Lq4jBX/y51symbgLNUOnlGIV 6Z85UTfPuN11n7YMpp3N =qwXR -----END PGP SIGNATURE----- --Apple-Mail=_972C3F82-C4BC-4950-8943-6305D0563A64-- From owner-freebsd-mobile@freebsd.org Wed Mar 2 01:29:18 2016 Return-Path: Delivered-To: freebsd-mobile@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C7613AC0242; Wed, 2 Mar 2016 01:29:18 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from bigwig.baldwin.cx (bigwig.baldwin.cx [IPv6:2001:470:1f11:75::1]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id A53D819CB; Wed, 2 Mar 2016 01:29:18 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from ralph.baldwin.cx (c-73-231-226-104.hsd1.ca.comcast.net [73.231.226.104]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id A415DB990; Tue, 1 Mar 2016 20:29:17 -0500 (EST) From: John Baldwin To: freebsd-current@freebsd.org Cc: Warner Losh , Marcel Moolenaar , "Lundberg, Johannes" , "freebsd-embedded@freebsd.org" , "freebsd-mobile@freebsd.org" Subject: Re: hint.uart.1 in device.hints causes freeze at boot Date: Tue, 01 Mar 2016 17:19:34 -0800 Message-ID: <21207070.KlEgumgKTW@ralph.baldwin.cx> User-Agent: KMail/4.14.3 (FreeBSD/10.2-STABLE; KDE/4.14.3; amd64; ; ) In-Reply-To: References: <4E9118B0-FC9F-444F-B277-3E5BAE75C723@xcllnt.net> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (bigwig.baldwin.cx); Tue, 01 Mar 2016 20:29:17 -0500 (EST) X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Mar 2016 01:29:18 -0000 On Friday, February 26, 2016 11:08:37 PM Warner Losh wrote: > On Fri, Feb 26, 2016 at 6:49 PM, Marcel Moolenaar wrote: > > Any reason not to add .disabled=1 to all the entries that are there, > with the possible exception of uart.0? At least for i386 and amd64? > Bonus points for writing code that filters those out when there's > no ACPI. While PNPBIOS could also supply this info, I doubt that you > could find hardware that has pnpbios data and not ACPI data except > maybe some of the soekris boxes to test against. > > Better still would be to split the current GENERIC.hints into two bits. > One that was strictly for legacy (!ACPI and !PNPBIOS) situations, and > one that we always load. There look to be at least a couple of hints > that are universally relevant still. I might have a 200MHz pentium I > can test this with... If there was an easy way to load a new hints file we could ship a /boot/legacy.hints and have a note in the handbook / FAQ about using it if needed. We could even have smarts in the loader to suck it in perhaps if !ACPI and !PnPBIOS. > As near as I can tell, only the following are relevant: > hint.fd.0.at="fdc0" > hint.fd.0.drive="0" > hint.fd.1.at="fdc0" > hint.fd.1.drive="1" > hint.acpi_throttle.0.disabled="1" > hint.p4tcc.0.disabled="1" hint.sc.0.at is relevant if you want to use sc(4) instead of vt(4). For a long time I've booted machines that only had that hint. The npx.0 hint used to matter (but no longer does). I think we should definitely trim the hints file for amd64. amd64 pretty much mandates ACPI. For i386 I would be fine with a the legacy.hints route even if it wasn't automagical but something you had to manually load. The only thing about the hints that is still somewhat useful on x86 is enabling serial console (though boot -h and/or console=comconsole already does that) and enabling remote GDB. (hint.uart.1.flags=0x80 is shorter and doesn't require remembering random I/O port addresses like the hw.uart route for GDB.) -- John Baldwin