Date: Wed, 9 Jan 2019 09:50:17 +0100 From: Michel Bertrand <mpbertrand@gmail.com> To: freebsd-stable@freebsd.org Subject: Re: freebsd-stable Digest, Vol 805, Issue 2 Message-ID: <CAC9=dP9tBgtNUXa8gi8n0R0=GVZ5eiLrtKLSNCdHE%2BhBjdRZGQ@mail.gmail.com> In-Reply-To: <mailman.10.1546948800.23097.freebsd-stable@freebsd.org> References: <mailman.10.1546948800.23097.freebsd-stable@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
UNSUBSCRIBE Michel Bertrand http://www.crossroad.fr tel: 01 46 42 37 56 06 25 001 456 michel@crossroad.fr Le mar. 8 janv. 2019 =C3=A0 13:00, <freebsd-stable-request@freebsd.org> a = =C3=A9crit : > Send freebsd-stable mailing list submissions to > freebsd-stable@freebsd.org > > To subscribe or unsubscribe via the World Wide Web, visit > https://lists.freebsd.org/mailman/listinfo/freebsd-stable > or, via email, send a message with subject or body 'help' to > freebsd-stable-request@freebsd.org > > You can reach the person managing the list at > freebsd-stable-owner@freebsd.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of freebsd-stable digest..." > Today's Topics: > > 1. Website Design and Development Solution... (Ina Smith) > 2. Re: APU2, legacy firmware 4.0.22, FreeBSD 12.0 hangs in boot > (Ruben) > 3. x86intrin.h not found after 10.4->11.2 upgrade (Morgan Reed) > 4. Re: FreeBSD 12 and Nocona (Marek Zarychta) > 5. Re: x86intrin.h not found after 10.4->11.2 upgrade (Morgan Reed) > 6. Re: FreeBSD 12 and Nocona (Stefan Bethke) > > > > ---------- Forwarded message ---------- > From: Ina Smith <ina.smith@acquire-web-position.com> > To: <freebsd-stable@freebsd.org> > Cc: > Bcc: > Date: Tue, 8 Jan 2019 02:23:03 +0530 > Subject: Website Design and Development Solution... > Hi, > > Greetings, > > Is your poor website design holding back your business? > > Are you struggling to figure out why you are not getting enough leads fro= m > your website? > > Let our experience help you create a website that is simple, unique and > professional! > > Should you be interested, let us know! Simply reply to this email with yo= ur > phone number and we will call you back. > > Looking forward to a prolific association! > > > > Thanks & Regards, > > Ina Smith > > Marketing Manager > > Head Office: San Jose, CA 95120 > > > > > > > > > > Disclaimer: We are using this domain for marketing. If you are intereste= d > and want to know about us, just reply to this email, if we have offended > you > by sending this to you by mistake, we apologize. Please reply "NO" or > "UNSUBSCRIBE" to this email if not interested, so that we shall add you t= o > our "Do Not Contact Again" list. > > > > > > > > > > > > > > > > ---------- Forwarded message ---------- > From: Ruben <mail@osfux.nl> > To: freebsd-stable@freebsd.org > Cc: > Bcc: > Date: Mon, 7 Jan 2019 22:43:11 +0100 > Subject: Re: APU2, legacy firmware 4.0.22, FreeBSD 12.0 hangs in boot > Hi, > > > On 1/5/19 6:40 PM, Ruben wrote: > > > > > Ill try updating an apu1 ( running 11.2 ) with its current (mainline) > > firmware to 12.0 one of these days as well. > > > I updated my apu1d4 from 11.2 to 12.0 (freebsd-update), no > strange/unexpected behaviour. > > The apu1d4 is running its "original" firmware I think (cant remember > having updated it) : > > =3D=3D=3D > > Build date: Apr 5 2014 > System memory size: 4592 MB > > Press F12 for boot menu. > > =3D=3D=3D > > Regards, > > Ruben > > > > > ---------- Forwarded message ---------- > From: Morgan Reed <morgan.s.reed@gmail.com> > To: freebsd-stable@freebsd.org > Cc: > Bcc: > Date: Tue, 8 Jan 2019 18:52:13 +1100 > Subject: x86intrin.h not found after 10.4->11.2 upgrade > Hi All, > > Finally got around to upgrading my NAS which was running FreeBSD 10= .4 > to a supported version (11.2). > > Ran into an issue when I came to do a portupgrade -a to update all my > installed ports, a number of the ports are failing with "x86intrin.h No > such file or directory", not sure what's going on there. > > I've updated my src tree just in case it was something that only got adde= d > in 11, no change. > > All the similar reports I found online were related to OLD versions of gc= c > (e.g. 4.3), which is not relevant since we're using clang (I assume > anyway), but I reinstalled llvm60 from package just in case, no change > again. > > An pointers would be greatly appreciated, thanks. > > Morgan > > > > > ---------- Forwarded message ---------- > From: Marek Zarychta <zarychtam@plan-b.pwste.edu.pl> > To: Stefan Bethke <stb@lassitu.de> > Cc: freebsd-stable@freebsd.org > Bcc: > Date: Tue, 8 Jan 2019 10:34:01 +0100 > Subject: Re: FreeBSD 12 and Nocona > > > W dniu 03.01.2019 o 14:13, Stefan Bethke pisze: > >> I have under supervision a few old servers running 11.2-STABLE. The > >> hardware is almost for retirement, but still in working condition. It'= s > >> all old Nocona NetBurst microarchitecture. I have recently tried do > >> upgrade OS two of them to 12.0-STABLE, but failed. When I use old > >> bootloader the boot freezes on blue highlighted "Booting" stage, when = I > >> tried to use 12 loader, it freezes earlier, on loading kernel modules. > >> The kernel was compiled from fresh sources for CPUTYPE?=3Dnocona. > >> 11.2-STABLE is fine with this optimization and the same kernel boots > >> fine on newer hardware. > >> > >> It is fair, that 11 EOL is expected September 30, 2021 and these serve= rs > >> will likely be retired before this date, but some questions arise: > >> > >> Is such old hardware still supported? Is it possible (how to) debug th= e > >> booting process? > > > > The first step is to try with known-good bits: can you boot these > machines off the 12.0 ISO or memstick images? Can you load your kernel an= d > modules with the loader from the ISO/memstick? Does GENERIC built without > any flags work? > > > > If any of these don=E2=80=99t work, try to be as specific as possible w= hen > reporting problems. For example, the exact make of mainboard (kenv output= ) > and the BIOS version, and any relevant BIOS settings are likely important > for problems regarding the loader. If the kernel and modules load, you ca= n > try a verbose boot to see better how far the kernel gets. > > > > I=E2=80=99d be really surprised if the CPUs themselves would cause trou= ble. > > > The first step is done. The affected hardware doesn't boot from official > 12.0-RELEASE CD either. Loader also freezes at the stage of loading > kernel modules. These servers are old Maxdata Platinum 500 and 3200. > Some time ago I have submitted dmesgs to NYC BUG dmesg repository[1][2]. > > Both configurations are fine with 11-STABLE, so I am not going to > upgrade them and I am replying only FYI. > > > [1] https://dmesgd.nycbug.org/index.cgi?do=3Dview&id=3D3790 > [2] https://dmesgd.nycbug.org/index.cgi?do=3Dview&id=3D4111 > > Regards, > > -- > Marek Zarychta > > > > > ---------- Forwarded message ---------- > From: Morgan Reed <morgan.s.reed@gmail.com> > To: freebsd-stable@freebsd.org > Cc: > Bcc: > Date: Tue, 8 Jan 2019 22:50:23 +1100 > Subject: Re: x86intrin.h not found after 10.4->11.2 upgrade > Just did a find across /usr for the file and it's definitely there so I'm > not sure why the compiler can't find it :/ > > # find /usr -name x86intrin.h > /usr/include/x86intrin.h > /usr/src/contrib/llvm/tools/clang/lib/Headers/x86intrin.h > > /usr/local/lib/gcc7/gcc/x86_64-portbld-freebsd11.2/7.4.0/include/x86intri= n.h > /usr/local/llvm60/lib/clang/6.0.1/include/x86intrin.h > /usr/lib/clang/6.0.0/include/x86intrin.h > > This system's been around the block (started out as 9.3 I think, had a fe= w > upgrades over the years) which would explain the gcc7 stuff. > > > On Tue, Jan 8, 2019 at 6:52 PM Morgan Reed <morgan.s.reed@gmail.com> > wrote: > > > Hi All, > > > > Finally got around to upgrading my NAS which was running FreeBSD > > 10.4 to a supported version (11.2). > > > > Ran into an issue when I came to do a portupgrade -a to update all my > > installed ports, a number of the ports are failing with "x86intrin.h No > > such file or directory", not sure what's going on there. > > > > I've updated my src tree just in case it was something that only got > added > > in 11, no change. > > > > All the similar reports I found online were related to OLD versions of > gcc > > (e.g. 4.3), which is not relevant since we're using clang (I assume > > anyway), but I reinstalled llvm60 from package just in case, no change > > again. > > > > An pointers would be greatly appreciated, thanks. > > > > Morgan > > > > > > > > > > -- > "They that can give up essential liberty to obtain a little temporary > safety deserve neither liberty nor safety." > -- Benjamin Franklin, 1759 > > > > > ---------- Forwarded message ---------- > From: Stefan Bethke <stb@lassitu.de> > To: Marek Zarychta <zarychtam@plan-b.pwste.edu.pl> > Cc: FreeBSD Stable <freebsd-stable@freebsd.org>, Warner Losh < > imp@freebsd.org>, Kyle Evans <kevans@freebsd.org>, Toomas Soome < > tsoome@freebsd.org> > Bcc: > Date: Tue, 8 Jan 2019 12:51:48 +0100 > Subject: Re: FreeBSD 12 and Nocona > Am 08.01.2019 um 10:34 schrieb Marek Zarychta < > zarychtam@plan-b.pwste.edu.pl>: > > W dniu 03.01.2019 o 14:13, Stefan Bethke pisze: > >>> I have under supervision a few old servers running 11.2-STABLE. The > >>> hardware is almost for retirement, but still in working condition. It= 's > >>> all old Nocona NetBurst microarchitecture. I have recently tried do > >>> upgrade OS two of them to 12.0-STABLE, but failed. When I use old > >>> bootloader the boot freezes on blue highlighted "Booting" stage, when= I > >>> tried to use 12 loader, it freezes earlier, on loading kernel modules= . > >>> The kernel was compiled from fresh sources for CPUTYPE?=3Dnocona. > >>> 11.2-STABLE is fine with this optimization and the same kernel boots > >>> fine on newer hardware. > >>> > >>> It is fair, that 11 EOL is expected September 30, 2021 and these > servers > >>> will likely be retired before this date, but some questions arise: > >>> > >>> Is such old hardware still supported? Is it possible (how to) debug t= he > >>> booting process? > >> > >> The first step is to try with known-good bits: can you boot these > machines off the 12.0 ISO or memstick images? Can you load your kernel an= d > modules with the loader from the ISO/memstick? Does GENERIC built without > any flags work? > >> > >> If any of these don=E2=80=99t work, try to be as specific as possible = when > reporting problems. For example, the exact make of mainboard (kenv output= ) > and the BIOS version, and any relevant BIOS settings are likely important > for problems regarding the loader. If the kernel and modules load, you ca= n > try a verbose boot to see better how far the kernel gets. > >> > >> I=E2=80=99d be really surprised if the CPUs themselves would cause tro= uble. > > > > > > The first step is done. The affected hardware doesn't boot from officia= l > > 12.0-RELEASE CD either. Loader also freezes at the stage of loading > > kernel modules. These servers are old Maxdata Platinum 500 and 3200. > > Some time ago I have submitted dmesgs to NYC BUG dmesg repository[1][2]= . > > > > Both configurations are fine with 11-STABLE, so I am not going to > > upgrade them and I am replying only FYI. > > > > > > [1] https://dmesgd.nycbug.org/index.cgi?do=3Dview&id=3D3790 < > https://dmesgd.nycbug.org/index.cgi?do=3Dview&id=3D3790>; > > [2] https://dmesgd.nycbug.org/index.cgi?do=3Dview&id=3D4111 < > https://dmesgd.nycbug.org/index.cgi?do=3Dview&id=3D4111>; > I think it would be great to get some input from someone familiar with th= e > new loader. I=E2=80=99ve cc=E2=80=99ed Warner, Kyle and Toomas, as they w= ere listed in the > quarterly status report. > > > Stefan > > -- > Stefan Bethke <stb@lassitu.de> Fon +49 151 14070811 > > > _______________________________________________ > freebsd-stable@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAC9=dP9tBgtNUXa8gi8n0R0=GVZ5eiLrtKLSNCdHE%2BhBjdRZGQ>