Re: cannot build i386 12.0-RELEASE kernel on -current

On Wed, 2018-12-12 at 19:33 +0300, Yuri Pankov wrote: > Henry Vogt wrote: > > > > Hi, > > > > my build machine (FreeBSD:13:amd64 r341429) builds world/kernel ok > > for amd64, world for i386 ok, but fails 'make buildkernel' for > > i386: > > > > -- snip > > > > ... > > > > --- if_vte.o --- >

Re: Composite PCI devices in FreeBSD (mfd in Linux)

On Mon, 2018-12-10 at 14:42 -0500, Anthony Jenkins wrote: > On 12/10/18 1:26 PM, John Baldwin wrote: > > > > On 12/10/18 9:00 AM, Anthony Jenkins wrote: > > > > > > Hi all, > > > > > > I'm trying to port an Intel PCI I2C controller from Linux to > > > FreeBSD. > > > Linux represents this device

Re: pkg-base noise

On Tue, 2018-12-11 at 11:40 -0700, Sean Bruno wrote: > make[8]: "/home/sbruno/bsd/fbsd_head/share/mk/bsd.files.mk" line 92: > warning: duplicate script for target "_testsFILESINS_cleanup.ksh" > ignored > make[8]: "/home/sbruno/bsd/fbsd_head/share/mk/bsd.files.mk" line 92: > warning: using previous

Re: Composite PCI devices in FreeBSD (mfd in Linux)

On Wed, 2018-12-19 at 14:35 -0500, Anthony Jenkins wrote: > On 12/19/18 10:41 AM, Anthony Jenkins wrote: > > > > [snip] > > > > I'm not feeling too confident about the condition of the FreeBSD > > ig4  > > driver; the PCI attach code was calling pci_alloc_msi() wrong, > > passing  > > a pointer

Re: Boot loader stuck after first stage upgrading 11.2 to 12.0-RC2

On Tue, 2018-12-04 at 21:51 +0200, Toomas Soome via freebsd-stable wrote: > > > > > On 4 Dec 2018, at 19:59, Mark Martinec > i> wrote: > > > > > > > > > > > > > 2018-11-29 18:43, Toomas Soome wrote: > > > > > > > > > > I just did push biosdisk updates to stable/12, I wonder if > > > > > you

Re: toolchain(s) for universe kernels

On Mon, 2018-11-19 at 11:55 -0600, Eric van Gyzen wrote: > I want to > > make MAKE_JUST_KERNELS=1 universe > > but it seems that I need a toolchain first.  There are multiple > toolchain-ish make targets.  If I start with an empty obj, which > toolchain target(s) should I build? > > Eric

Re: r342378 fails sometimes on boot mounting root (error 2)

On Fri, 2018-12-28 at 15:54 +0100, Matthias Apitz wrote: > Hello, > > I've setup a new r342378 (December 23) for amd64 onto an external > disk > with this procedure: > > # grep da0 /var/log/messages > ... > Dec 28 14:20:01 c720-r314251 kernel: da0 at umass-sim0 bus 0 scbus1 > target 0 lun 0 >

Re: How to hotplug a PCI device (such as VF) on FreeBSD

On Mon, 2019-03-25 at 08:49 +, Hongxiong Xian (Wicresoft North America Ltd) wrote: > Hi, > > I'm looking for a way to refresh the pci device list. > In Linux, we can remove a particular pci device, and then after > preforming a "rescan" the device will appear again. > For example,

Re: r343567 aka PAE vs non-PAE merge breaks i386 freebsd

On Thu, 2019-02-28 at 11:06 -0800, Conrad Meyer wrote: > On Thu, Feb 28, 2019 at 10:32 AM Steve Kargl > wrote: > > This is interesting as well. Does this mean that amd64 is now > > the only tier 1 platform and all other architectures are after > > thoughts? > > This has been the de facto truth

Re: What is evdev and autoloading?

On Sun, 2019-02-17 at 16:24 -0800, Steve Kargl wrote: > On Sun, Feb 17, 2019 at 03:04:41PM -0800, Mark Millard wrote: > > > > > > On 2019-Feb-17, at 10:03, Steve Kargl > troutmask.apl.washington.edu> wrote: > > > > Anyone have insight into what evdev is? There appears to > > be no manual

Re: What is evdev and autoloading?

On Mon, 2019-02-18 at 08:50 -0800, Steve Kargl wrote: > On Mon, Feb 18, 2019 at 09:11:14AM -0700, Warner Losh wrote: > > > > You do know these constant complaints about people trying to make > > things > > better is demoralizing and counter productive. > > > > You do realize some of the emails

Re: kernel build dies with "unknown option"

On Wed, 2019-02-13 at 18:29 -0500, Robert Huff wrote: > On a system running: > > FreeBSD 13.0-CURRENT r343080 16 Jan 2019 amd64 > > I updated the source tree as of midnight US Eastern time, then > ran buildworld. That completed successfully. > Then: > > huff@jerusalem> make

Re: problem building dev/e1000

On Fri, 2019-02-15 at 12:32 -0700, Warner Losh wrote: > On Fri, Feb 15, 2019 at 12:17 PM Ian Lepore wrote: > > > On Fri, 2019-02-15 at 10:53 -0800, Enji Cooper wrote: > > > > [...] > > > > > > HO Eric! > > > > > > iflib was a recen

Re: problem building dev/e1000

On Fri, 2019-02-15 at 10:53 -0800, Enji Cooper wrote: > > On Feb 15, 2019, at 10:46, Eric Joyner wrote: > > > > ifdi_if.h is a system generated interface file that network drivers > > that depend on iflib use. It's generated from ifdi_if.m in sys/net. > > > > My guess is that you don't have

Re: Inability to build FreeBSD-current amd64

On Wed, 2019-05-15 at 19:26 +, Thomas Mueller wrote: > from tech-lists: > > > What do you do before buildworld? > > > > I'll rm -rf /usr/obj and /var/cache/ccache [1], create them again, > > then in > > /usr/src I'll do this: > > make -j32 cleanworld && make -j32 cleandir && make

Re: Inability to build FreeBSD-current amd64

On Wed, 2019-05-15 at 23:23 +, Thomas Mueller wrote: > What do most FreeBSD users who rebuild system from source do > regarding WITH_CLANG_EXTRAS in /etc/src.conf ? > > I have WITH_CLANG_EXTRAS=yes in /etc/src.conf and wonder if that > could be screwing my build. > > Build seems to stumble

Re: error: yacc.h: No such file or directory

On Tue, 2019-06-18 at 07:01 -0700, Enji Cooper wrote: > > On Jun 18, 2019, at 06:59, Enji Cooper > > wrote: > > > > > > > On Jun 18, 2019, at 06:53, Ian Lepore wrote: > > > > ... > > > > > Last Saturday, Bryan (cc'd) made a serie

Re: error: yacc.h: No such file or directory

On Tue, 2019-06-18 at 09:51 -0700, Bryan Drewery wrote: > On 6/18/2019 3:56 AM, Kubilay Kocak wrote: > > Have seen another report on Twitter yesterday. Didn't see a full > > build > > log, but theirs was had apparently without -j, apparently on June > > 14 > > sources: > > > > Error: > >

Re: sys/modules/sdio broken in .svn_revision 348842 'opt_cam.h' not found

On Tue, 2019-06-18 at 02:21 +0200, Julian H. Stacey wrote: > "Julian H. Stacey" wrote: > > "Bjoern A. Zeeb" wrote: > > > On 17 Jun 2019, at 10:37, Mark Linimon wrote: > > > > > > > On Mon, Jun 17, 2019 at 11:41:03AM +0200, Julian H. Stacey > > > > wrote: > > > > > svn_revision 348842 > > > > > >

Re: error: yacc.h: No such file or directory

> > > On Jun 18, 2019, at 06:59, Enji Cooper > > > > > > > > > > wrote: > > > > > > > > > > > > > > > > On Jun 18, 2019, at 06:53, Ian Lepore > > > > > > wrote: > > > > > > > > >

Re: error: yacc.h: No such file or directory

On Tue, 2019-06-18 at 06:45 -0700, Cy Schubert wrote: > On June 18, 2019 6:24:36 AM PDT, Michael Tuexen > wrote: > > > On 18. Jun 2019, at 12:56, Kubilay Kocak > > > wrote: > > > > > > On 18/06/2019 5:42 pm, Michael Tuexen wrote: > > > > Dear all, > > > > I'm trying to run > > > > sudo make

Re: lib/libgcc_s fails on make all after make world succeeds

On Sun, 2019-05-19 at 23:54 +0200, Dimitry Andric wrote: > On 19 May 2019, at 23:29, Julian H. Stacey wrote: > > > > Hi curr...@freebsd.org > > On current src/ on 2 boxes, I have seen the same break for a week > > or 2, > > lib/libgcc_s fails on make all after make world succeeds, > > Anyone

Re: FCP-101: obsolete driver removal planned for 2019-05-18

On Sun, 2019-05-12 at 10:45 -0700, Rodney W. Grimes wrote: > > 12.05.2019 8:21, Warner Losh wrote: > > > > > >> I've posted a review to remove obsolete 10 and 10/100 > > > Ethernet drivers > > > >> as previous approved in FCP-101. > > > >> The following drivers are slated for > > >

Re: ci.freebsd.org: powerpcspe build failing due to linker error in assembly code

On Mon, 2019-05-20 at 17:54 -0700, Enji Cooper wrote: > Hi, > The following build issue has been cropping up over the past 6 hours. > From https://ci.freebsd.org/job/FreeBSD-head-powerpcspe-build/11154/console : > > 12:49:01 /usr/src/stand/powerpc/kboot/kerneltramp.S: Assembler messages: >

Re: GPT boot has less features than legacy MBR-based one (Was: UEFI, loader.efi and /boot.config)

On Fri, 2019-01-18 at 21:24 +0300, Lev Serebryakov wrote: > On 18.01.2019 21:14, Toomas Soome wrote: > > > errm.. you press a key and enter device and or loader path. if it is not > > working - the code is there to be fixed. > > And loader looks to "bootme" attribute and try to boot from

Re: Question about 'gptzfsboot'

On Mon, 2019-04-29 at 10:33 -0400, Thomas Laus wrote: > > On 2019-04-28 22:27, Ian Lepore wrote: > > > > > > If you're using gptzfsboot, I guess you're using zfs? I just > > > fixed a > > > problem with probing disks for zfs volumes a few days ago > &

Re: Question about 'gptzfsboot'

On Mon, 2019-04-29 at 14:47 -0400, Thomas Laus wrote: > On 2019-04-29 14:27, Thomas Laus wrote: > > It was more than a broken console. All of the other 2 computers > > that I > > upgraded to r346885 were essentially 'dead'. I could not even > > remotely > > login to them via ssh. All of them

Re: Question about 'gptzfsboot'

On Sun, 2019-04-28 at 19:29 -0400, Thomas Laus wrote: > On 2019-04-28 08:07, Ronald Klop wrote: > > > > Is this the same as this? > > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=144234 > > > > The messages are similar. The boot process will normally proceed on > the > second or third

Re: random_sources_feed: rs_read for hardware device 'Intel Secure Key RNG' returned no entropy.

On Wed, 2019-05-08 at 19:13 +0300, Andrey V. Elsukov wrote: > Hi, > > today I updated one of my test machines and discovered that message > from > the subject periodically printed in the console. > > FreeBSD 13.0-CURRENT r347327=4f47587(svn_head) GENERIC-NODEBUG amd64 > FreeBSD clang version

Re: New format for binaries?

On Tue, 2019-07-09 at 10:51 +0400, Gleb Popov wrote: > On Tue, Jul 9, 2019 at 1:33 AM Unidef wrote: > > > Instead of just cc files*c -o file > > > > We can do > > > > cc files*. -o file.c > > > > And cpp file*cpp -o file.cpp > > > > We can hook it up to a MySQL or a neural database? A neural

Re: i2c bit banging timeout for SCL

On Mon, 2019-07-01 at 19:03 +0300, Andriy Gapon wrote: > iicbb driver has a hardcoded timeout that defines how long the driver waits > for > SCL line to go high after the driver releases it to float. Sometimes slaves > hold the line low until they are ready to continue with the communication. >

Re: i2c bit banging timeout for SCL

On Mon, 2019-07-01 at 11:25 -0600, Warner Losh wrote: > On Mon, Jul 1, 2019 at 11:14 AM Poul-Henning Kamp > > wrote: > > > > > In message < > > canczdfofbvmxptnel4goqxtvp6zd-xrtja4rmuo1racy0jd...@mail.gmail.com> > > , > > Warner Losh writes: > > > > > The only issue, really, is that

Re: HEADSUP: drm-current-kmod now installs sources

On Tue, 2019-08-13 at 14:58 -0700, John Baldwin wrote: > For developers this means even if you are doing testing on a box > that doesn't use DRM, you can install the package so that kernel > builds will try to compile it and hopefully spot KPI/KBI changes > before they land in the tree so that the

Re: HEADSUP: drm-current-kmod now installs sources

On Wed, 2019-08-14 at 12:00 -0700, John Baldwin wrote: > On 8/14/19 11:06 AM, Kyle Evans wrote: > > LOCAL_MODULES="" does seem like a sensible default when we're not > > building a native kernel. > > Unfortunately kern.post.mk has no way of knowing that as MACHINE_* > are already set to the

Re: HEADSUP: drm-current-kmod now installs sources

On Wed, 2019-08-14 at 13:59 -0600, Warner Losh wrote: > On Wed, Aug 14, 2019 at 1:56 PM Ian Lepore wrote: > > > On Wed, 2019-08-14 at 12:00 -0700, John Baldwin wrote: > > > On 8/14/19 11:06 AM, Kyle Evans wrote: > > > > LOCAL_MODULES="" d

Re: RFC: should lseek(SEEK_DATA/SEEK_HOLE) return ENOTTY?

On Sun, 2019-08-11 at 09:12 -0600, Alan Somers wrote: > On Sun, Aug 11, 2019 at 8:57 AM Ian Lepore wrote: > > > > On Sun, 2019-08-11 at 09:04 +0200, Gary Jennejohn wrote: > > > On Sun, 11 Aug 2019 02:03:10 + > > > Rick Macklem wrote: > > >

Re: RFC: should lseek(SEEK_DATA/SEEK_HOLE) return ENOTTY?

On Sun, 2019-08-11 at 09:04 +0200, Gary Jennejohn wrote: > On Sun, 11 Aug 2019 02:03:10 + > Rick Macklem wrote: > > > Hi, > > > > I've noticed that, if you do a lseek(SEEK_DATA/SEEK_HOLE) on a file > > that > > resides in a file system that does not support holes, ENOTTY is > > returned. >

Re: HEADSUP: drm-current-kmod now installs sources

On Wed, 2019-08-14 at 09:08 -0700, John Baldwin wrote: > On 8/13/19 3:17 PM, Ian Lepore wrote: > > On Tue, 2019-08-13 at 14:58 -0700, John Baldwin wrote: > > > For developers this means even if you are doing testing on a box > > > that doesn't use DRM, you can install

Re: HEADSUP: drm-current-kmod now installs sources

On Wed, 2019-08-14 at 19:55 +0200, Niclas Zeising wrote: > On 2019-08-14 19:23, Emmanuel Vadot wrote: > > On Wed, 14 Aug 2019 10:13:48 -0700 > > John Baldwin wrote: > > > > > On 8/14/19 9:22 AM, Ian Lepore wrote: > > > > This all sounds vaguely wrong,

Re: Lost user database after bungled upgrade

On Wed, 2019-08-28 at 18:09 -0400, Ryan Stone wrote: > Thanks for the hint; I wasn't aware of /var/backups. Unfortunately > fixing my user database at this point hasn't fixed pkg. I'm worried > that it has some bad data cached somewhere now. I tried restoring the > pkg databack from /var/backups

Re: Weird goings on with make::empty()

On Wed, 2019-09-04 at 09:33 -0500, Kyle Evans wrote: > On Wed, Sep 4, 2019 at 9:27 AM Enji Cooper > wrote: > > > > > > > On Sep 4, 2019, at 04:59, Poul-Henning Kamp > > > wrote: > > > > > > On: > > > > > >Repository Root: svn+ssh://repo.freebsd.org/base > > >Repository UUID:

Re: Source tree has many empty directories?

On Tue, 2019-09-10 at 21:41 +0200, Dimitry Andric wrote: > On 10 Sep 2019, at 20:14, Ian Lepore wrote: > > > > On Tue, 2019-09-10 at 11:01 -0600, Warner Losh wrote: > > > However, please do *NOT* remove the sys/*/compile directories. > > > > > > Warn

Re: Source tree has many empty directories?

On Tue, 2019-09-10 at 11:01 -0600, Warner Losh wrote: > However, please do *NOT* remove the sys/*/compile directories. > > Warner Uhhh... that's interesting. I just nuked one of those on my system yesterday, because it had been hanging around since 2013 and I had no idea what was -- I just

Re: head -r352274 buildkernel targetting armv7 failure: am335x/am335x_dmtpps.c:304:3: error: implicit declaration of function 'spinlock_enter' is invalid in C99 [-Werror,-Wimplicit-function-declaratio

On Sat, 2019-09-14 at 11:05 -0700, Mark Millard via freebsd-arm wrote: > After updating my amd64 context to head -r352274, > attempting an amd64->armv7 cross buildworld buildkernel > ended up failing with: > > > --- am335x_dmtpps.o --- > /usr/src/sys/arm/ti/am335x/am335x_dmtpps.c:304:3: error:

Re: ntpd segfaults on start

On Mon, 2019-09-09 at 09:30 -0700, Rodney W. Grimes wrote: > > On Sat, 2019-09-07 at 09:28 -0700, Cy Schubert wrote: > > > In message <20190907161749.gj2...@kib.kiev.ua>, Konstantin > > > Belousov writes: > > > > On Sat, Sep 07, 2019 at 08:45:21AM -0700, Cy Schubert wrote: > > > > > I've been able

Re: ntpd segfaults on start

On Sat, 2019-09-07 at 09:28 -0700, Cy Schubert wrote: > In message <20190907161749.gj2...@kib.kiev.ua>, Konstantin Belousov writes: > > On Sat, Sep 07, 2019 at 08:45:21AM -0700, Cy Schubert wrote: > > > I've been able to set the memlock rlimit as low as 20 MB. The issue is > > > letting it

Re: ntpd segfaults on start

On Mon, 2019-09-09 at 21:44 +0300, Konstantin Belousov wrote: > On Mon, Sep 09, 2019 at 12:13:24PM -0600, Ian Lepore wrote: > > On Mon, 2019-09-09 at 09:30 -0700, Rodney W. Grimes wrote: > > > > On Sat, 2019-09-07 at 09:28 -0700, Cy Schubert wrote: > > > >

Re: ntpd segfaults on start

On Mon, 2019-09-09 at 12:28 -0700, Cy Schubert wrote: > > > > On the other hand, the code execution times are not predictable if the > > process's pages can be paged out. Under severe load next instruction > > might take several seconds or even minutes to start. It is quite unlike > > the

Re: rc script: manual stop vs system shutdown

On Thu, 2019-08-01 at 21:14 +0300, Andriy Gapon wrote: > On 01/08/2019 19:12, Warner Losh wrote: > > > > > > On Thu, Aug 1, 2019, 10:53 AM Rodney W. Grimes > > mailto:freebsd-...@gndrsh.dnsmgr.net>> > > wrote: > > > > > > > > Is it possible in an rc script to distinguish between a

Re: filesystem mount problem

On Sun, 2019-07-21 at 15:07 -0400, AN wrote: > Hi: > > FreeBSD FreeBSD_13 13.0-CURRENT FreeBSD 13.0-CURRENT #102 r350187: > Sat Jul > 20 19:04:30 EDT 2019 > root@FreeBSD_13:/usr/obj/usr/src/amd64.amd64/sys/MYKERNEL amd64 > 1300036 > > I would appreciate some help with the following problem. >

Re: [package - head-i386-default][sysutils/lsof] Failed for lsof-4.93.2_2,8 in build

On Thu, 2019-07-25 at 13:13 -0500, Larry Rosenman wrote: > On 07/25/2019 1:10 pm, Alan Somers wrote: > > On Thu, Jul 25, 2019 at 12:05 PM Larry Rosenman > > wrote: > > > > > > Um Who broke this? > > > > > > /usr/src/sys/sys/refcount.h:65:12: error: use of undeclared > > > identifier > > >

Re: Booting anything after r352057 kills console

On Tue, 2019-09-24 at 14:32 -0400, Thomas Laus wrote: > On 2019-09-24 11:58, Pete Wright wrote: > > > > darn, and they didn't give you any additional information in the > > messages buffer, or generate a core file? > > > > There were no messages in the syslog and no other log that showed >

Re: Someone broke USB

On Sat, 2019-07-06 at 14:06 -0700, Steve Kargl wrote: > On Sat, Jul 06, 2019 at 10:50:59PM +0200, Hans Petter Selasky wrote: > > On 2019-07-06 21:41, Steve Kargl wrote: > > > On Sat, Jul 06, 2019 at 08:33:39PM +0200, Hans Petter Selasky > > > wrote: > > > > On 2019-07-06 20:23, Steve Kargl wrote:

Re: gpiobus: setting output value while in input mode

On Thu, 2019-10-24 at 17:04 +0300, Andriy Gapon wrote: > For a lack of a more specific mailing list (or my not being aware of it), > asking > here. > > gpioiic, a very simple driver, has this code: > === > static void >

Re: gpiobus: setting output value while in input mode

On Thu, 2019-10-24 at 19:01 +0300, Andriy Gapon wrote: > Also, if we universally implement GPIO_PIN_PRESET we still need to answer the > question. Because some consumer might still try to change an input, either by > mistake or for some reason, and we need a rule on how to handle that. Well,

Re: Best thread pool implementation for the base system?

On Thu, 2019-10-24 at 12:46 -0600, Alan Somers wrote: > I count 5 thread pool implementations in contrib: > * cddl/compat/opensolaris/misc/thread_pool.c > * contrib/apr-util/misc/apr_thread_pool.c > * contrib/llvm/lib/Support/ThreadPool.cpp > * contrib/openmp/runtime/src/kmp_tasking.cpp > *

Re: Reverting -current by date.

On Wed, 2019-11-20 at 09:38 -0800, bob prohaska wrote: > From time to time it would be handy to revert freebsd-current to > an older, well-behaved revision. > > Is there a mechanism for identifying revision numbers that > will at least compile and boot, by date? > > In my case buildworld seems

Re: Best way to print something from the kernel at 1s intervals?

On Fri, 2019-11-29 at 23:10 +0100, Peter Eriksson wrote: > I love dtrace, but I seriously doubt that it could be used it for > this. This is the absolutely last code that executes at kernel > shutdown/reboot. All other processes are terminated when this is > happening... > > Basically the code

Re: ZFS with 32-bit, non-x86 kernel

On Fri, 2019-10-04 at 13:27 -0600, Warner Losh wrote: > On Fri, Oct 4, 2019, 1:07 PM Dennis Clarke wrote: > > > On 10/4/19 10:05 AM, Andriy Gapon wrote: > > > > > > Does anyone use ZFS with a 32-bit kernel, that is also not i386 ? > > > If you do, could you please let me know? Along with uname

Re: OFWBUS: How does autoconfiguration work?

On Tue, 2020-02-04 at 19:09 +0530, Niteesh wrote: > I am working on an operating systems project at my university, which > currently > uses lazy driver initialization i.e. that is the drivers initialize the > hardware only > during the first invocation, for example, the UART hardware is

Re: OFWBUS: How does autoconfiguration work?

On Sun, 2020-02-02 at 10:02 +0530, Niteesh wrote: > I couldn't find anything useful for me, I need information about how the > hardware autoconfiguration works, not autoconf. > Then maybe you need to provide more details about what you're doing, what you've tried that isn't working, or

Re: btxld not found

On Tue, 2020-01-28 at 17:08 +0100, Nick Hibma wrote: > > On Tue, Jan 28, 2020, 4:57 AM Nick Hibma > > wrote: > > > On 28/01 /2020, at 12:39, Toomas Soome > > tso...@me.com>> wrote: > > > > > > > On 28. Jan 2020, at 13:36, Nick Hibma > > >

Re: bootstrap error with make buildworld

On Tue, 2020-02-18 at 14:16 +0100, Trond Endrestøl wrote: > On Tue, 18 Feb 2020 11:03+0100, Jochen Neumeister wrote: > > > Anyone got a tip to solve this problem? > > Otherwise I would unfortunately have to reinstall the server. My Poudriere > > Box > > runs on this server > > > > Am 17.02.20

Re: head -r356109 on 32-bit powerpc (old PowerMac): Memory modified after free during late-stage of boot, most recently used by bus-sc

On Sun, 2019-12-29 at 23:04 +0100, Hans Petter Selasky wrote: > On 2019-12-29 22:53, Mark Millard via freebsd-hackers wrote: > > 0xd2630510: at uma_zalloc_arg+0x1b4 > > 0xd2630540: at malloc+0xfc > > 0xd2630580: at alloc_bounce_pages+0x7c > > 0xd26305c0: at bus_dmamap_create+0x1e8 > > Do you know

Re: Any a.out users?

On Fri, 2020-03-13 at 13:04 -0400, Ed Maste wrote: > While looking at other things we came across ldconfig's a.out > support, > which hasn't been used by anything in the FreeBSD base system in ~2 > decades. > > I know there are (or at least recently were) folks using a.out > binaries on

Re: Any a.out users?

On Fri, 2020-03-13 at 13:34 -0400, Ed Maste wrote: > On Fri, 13 Mar 2020 at 13:22, Ian Lepore wrote: > > > > Could a.out support be a kernel config option that's off by > > default? > > Probably. That seems reasonable to me. > > > And could its presence be

Re: FYI: artifact-based head bisect and OPi+2e (an armv7): -r359311 fails to boot but -r359309 boots (kernel substitutions)

On Sun, 2020-03-29 at 09:44 -0700, Thomas Skibo wrote: > On Sun, Mar 29, 2020 at 12:29:00AM -0700, Mark Millard via freebsd- > arm wrote: > > While trying to update the head version > > in use I ran into boot hangups on the > > OrangePi+ 2e and did an approximate > > bisect of

Re: lock order reversal and poudriere

On Sat, 2020-05-02 at 20:36 +0200, Kurt Jaeger wrote: > Hi! > > > > > I am compiling some packages with poudriere on 13-current kernel. I > > > > noticed some strange messages printed into the terminal and dmesg: > > > > > > > > lock order reversal: > > > > > > [...] > > > > Are those the debug

Re: Plans for git (was: Please check the current beta git conversions)

On Wed, 2020-09-02 at 11:11 -0600, Warner Losh wrote: > On Wed, Sep 2, 2020 at 10:47 AM Steve Kargl < > s...@troutmask.apl.washington.edu> wrote: > > > On Wed, Sep 02, 2020 at 12:14:08PM -0400, Ed Maste wrote: > > > On Wed, 2 Sep 2020 at 02:31, Steve Kargl > > > wrote: > > > > > > > > > A short

Re: Plans for git (was: Please check the current beta git conversions)

On Wed, 2020-09-02 at 14:45 -0400, Dan Langille wrote: > On Wed, Sep 2, 2020, at 2:36 PM, Ian Lepore wrote: > > > Seriously, Warner? > > Yes, seriously. We are adults. Act accordingly. > > Don't be confused. I also thought the message he was replying to was out of

Re: Deprecating ftpd in the FreeBSD base system?

On Thu, 2020-09-17 at 12:49 -0700, John-Mark Gurney wrote: > Ian Lepore wrote this message on Thu, Sep 17, 2020 at 09:01 -0600: > > On Thu, 2020-09-17 at 18:43 +0400, Gleb Popov wrote: > > > On Thu, Sep 17, 2020 at 6:05 PM Cy Schubert < > > > cy.schub

Re: Deprecating ftpd in the FreeBSD base system?

On Thu, 2020-09-17 at 18:43 +0400, Gleb Popov wrote: > On Thu, Sep 17, 2020 at 6:05 PM Cy Schubert < > cy.schub...@cschubert.com> > wrote: > > > I've been advocating removing FTP (and HTTP) from libfetch as well. > > People > > should be using HTTPS only. > > > > Isn't this a bit too much? I

Re: efirtc + atrtc at the same time

On Mon, 2020-05-25 at 11:37 +0300, Andriy Gapon wrote: > I see that on my laptop both efirtc and atrtc get attached. > The latter is via an ACPI attachment: > efirtc0: > efirtc0: registered as a time-of-day clock, resolution 1.00s > atrtc0: port 0x70-0x71 on acpi0 > atrtc0: registered as a

Re: Undeletable files after kyua test runs

On Mon, 2020-06-29 at 21:08 +0200, Gordon Bergling wrote: > On Mon, Jun 29, 2020 at 11:58:47AM -0700, Rodney W. Grimes wrote: > > > On Mon, Jun 29, 2020 at 10:32:38AM -0700, Kevin Oberman wrote: > > > > On Mon, Jun 29, 2020 at 10:26 AM Gordon Bergling < > > > > g...@freebsd.org> wrote: > > > > > I

Re: В ответ на: vnc can't connect to socket

On Sun, 2020-06-21 at 19:54 +0200, Michael Tuexen wrote: > > On 21. Jun 2020, at 19:40, Ian Lepore wrote: > > > > On Sun, 2020-06-21 at 14:54 +0200, Michael Tuexen wrote: > > > > On 21. Jun 2020, at 14:28, Kostya Berger > > > > > > > &

Re: В ответ на: vnc can't connect to socket

On Sun, 2020-06-21 at 14:54 +0200, Michael Tuexen wrote: > > On 21. Jun 2020, at 14:28, Kostya Berger > > wrote: > > > > Ok, it turns out, it gives the previously mentioned error only if I > > use VNC server string 0.0.0.0:5900 (as I always did). in my VNC > > client.But when replaced

Re: rc.d/zpool runs before ada(4) attaches

On Tue, 2020-12-01 at 16:22 +0100, Ronald Klop wrote: > > Van: Harry Schmalzbauer > Datum: dinsdag, 1 december 2020 12:51 > Aan: Ronald Klop , FreeBSD Current < > freebsd-current@freebsd.org> > Onderwerp: Re: rc.d/zpool runs before ada(4) attaches > > > > Am 01.12.2020 um 10:33 schrieb Ronald

Re: Panic after updating

On Wed, 2021-01-13 at 10:37 +0100, Jakob Alvermark wrote: > On 1/13/21 10:07 AM, Hans Petter Selasky wrote: > > > > > > Yes! That works! Thank you! > > > > > > > See: > > > > https://cgit.freebsd.org/src/commit/?id=bafb682656724d06045fa494efb83a4312036f1f > > > > > > > Nice! Thanks

Re: Panic after updating

n I got a different result, > > > > > > > so I > > > > > > > most likely did something wrong the first time. > > > > > > > > > > > > > > ff3468ac94597efdcbc56f372528dfc98b114dac is the first bad > > > > > > > commit > > > >

Re: Panic after updating

On Tue, 2021-01-12 at 19:56 +0100, Hans Petter Selasky wrote: > On 1/12/21 7:45 PM, Ian Lepore wrote: > > > > - for (int i = 0; i <= sc->sc_npins; i++) { > > > > + for (int i = 0; i != sc->sc_npins; i++) { > > > >

Re: Enabling AESNI by default

On Thu, 2020-12-31 at 14:09 -0800, Rodney W. Grimes wrote: > > We've had the AESNI module for quite a few years now, and it has > > not > > caused any problems. > > > > I am wondering if there are any objections to including it in > > GENERIC, > > so that users get the benefit without having to

Re: Files in /etc containing empty VCSId header

On Tue, 2021-06-08 at 15:11 -0700, Rodney W. Grimes wrote: > > On Tue, 8 Jun 2021 09:41:34 + > > Mark Linimon wrote: > > > > > On Mon, Jun 07, 2021 at 01:58:01PM -0600, Ian Lepore wrote: > > > > Sometimes it's a real interesting exercise to figure o

Re: Files in /etc containing empty VCSId header

On Mon, 2021-06-07 at 13:53 -0600, Warner Losh wrote: > On Mon, Jun 7, 2021 at 12:26 PM John Baldwin wrote: > > > On 5/20/21 9:37 AM, Michael Gmelin wrote: > > > Hi, > > > > > > After a binary update using freebsd-update, all files in /etc > > > contain > > > "empty" VCS Id headers, e.g., > > >

Re: Files in /etc containing empty VCSId header

On Wed, 2021-06-09 at 18:54 +1000, Peter Jeremy via freebsd-current wrote: > On 2021-Jun-08 17:13:45 -0600, Ian Lepore wrote: > > On Tue, 2021-06-08 at 15:11 -0700, Rodney W. Grimes wrote: > > > There is a command for that which does or use to do a pretty > > > decent

Re: Files in /etc containing empty VCSId header

On Tue, 2021-06-08 at 13:47 +0200, Gary Jennejohn wrote: > On Tue, 8 Jun 2021 09:41:34 + > Mark Linimon wrote: > > > On Mon, Jun 07, 2021 at 01:58:01PM -0600, Ian Lepore wrote: > > > Sometimes it's a real interesting exercise to figure out where a > > > file

Re: Rationalizing sed -i/-I (in-place editing) argument handling

On Mon, 2021-03-08 at 15:13 -0500, Ed Maste wrote: > A relatively minor but longstanding incompatibility between FreeBSD > and many other systems is the way sed handles backup files for > in-place editing -- sed's -I and -i options. GNU sed and other BSDs > accept an optional argument: -I.bak will

Re: Arm64 Tier 1 FreeBSD 13 Phones

On Sat, 2021-04-10 at 04:07 -0400, grarpamp wrote: > FreeBSD Phones... > > https://en.wikipedia.org/wiki/Librem_5 > NXP i.MX 8M Quad core Cortex-A53, 64bit ARM > > https://en.wikipedia.org/wiki/PinePhone > Allwinner A64 ARM Quad core Cortex-A53 > > https://www.youtube.com/watch?v=c32-QOrI4cw >

Re: I get odd time reports from poudriere on armv7 system, under a (non-debug) main [so: 14] FreeBSD.

On Sun, 2021-09-26 at 02:27 -0700, Mark Millard via freebsd-current wrote: > On 2021-Sep-25, at 23:25, Mark Millard wrote: > > > [...] > if (argc == 3 && strcmp(argv[2], "-nsec") == 0) > printf("%ld.%ld\n", ts.tv_sec, ts.tv_nsec); There are two problems with this, both

Re: PATH: /usr/local before or after /usr ?

On Fri, 2021-07-16 at 09:01 -0600, Alan Somers wrote: > FreeBSD has always placed /usr/local/X after /usr/X in the default PATH. > AFAICT that convention began with SVN revision 37 "Initial import of 386BSD > 0.1 othersrc/etc". Why is that? It would make sense to me that > /usr/local/X should

<    1   2   3   4   5