Re: Makefile Problem of FreeBSD-Current

On Sun, May 11, 2014 at 11:14 AM, Warner Losh wrote: > > From UPDATING: > > 20140505: > /etc/src.conf now affects only builds of the FreeBSD src tree. In > the > past, it affected all builds that used the bsd.*.mk files. The old > behavior was a bug, but people may have re

Re: Makefile Problem of FreeBSD-Current

On Sun, May 11, 2014 at 9:39 AM, Sean Bruno wrote: > On Sun, 2014-05-11 at 20:49 +0800, bycn82 wrote: > > As you can see below . it still did not find the src.opts.mk > > > > > > root@FB10Head:/usr/src/sbin/ipfw # make > > make: "/usr/src/sbin/ipfw/Makefile" line 3: Could not find src.opts.mk > >

Re: delete-old issue with src.opts.mk

On Sat, May 10, 2014 at 3:54 PM, Warner Losh wrote: > > On May 10, 2014, at 9:45 AM, Thomas Hoffmann wrote: > > > The other night I built a new -CURRENT at r265728. At delete-old it asked > > me if I wanted to "remove /usr/share/mk/src.opts.mk?" I said yes. >

delete-old issue with src.opts.mk

The other night I built a new -CURRENT at r265728. At delete-old it asked me if I wanted to "remove /usr/share/mk/src.opts.mk?" I said yes. Subsequently an upgrade attempt for virtualbox-ose-4.3.10_1 failed with a "missing src.opts.mk " error. Last night I built a new -CURRENT a

Re: ZFS bug or feature

In /boot/loader.conf: kern.geom.label.disk_ident.enable=0 will disable the use of disk ids. -Tom ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-uns

Re: make delete-old/delete-old-libs issue after r264673 build

On Sat, Apr 19, 2014 at 9:29 PM, Warner Losh wrote: > > bad mk files? > jkim@ resolved this for me w/ r264674. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "free

Re: make delete-old/delete-old-libs issue after r264673 build

On Sat, Apr 19, 2014 at 2:27 AM, Jung-uk Kim wrote: > On 2014-04-19 02:14:58 -0400, Thomas Hoffmann wrote: > > On Sat, Apr 19, 2014 at 1:05 AM, Jung-uk Kim > <mailto:j...@freebsd.org>> wrote: > > > > On 2014-04-18 23:46:46 -0400, Thomas Hoffmann wrote: >

Re: make delete-old/delete-old-libs issue after r264673 build

On Sat, Apr 19, 2014 at 1:05 AM, Jung-uk Kim wrote: > On 2014-04-18 23:46:46 -0400, Thomas Hoffmann wrote: > > After building at -CURRENT amd64 r264673, I got the following > > errors running 'make delete-old' and 'make delete-old-libs': > ... > > This

make delete-old/delete-old-libs issue after r264673 build

After building at -CURRENT amd64 r264673, I got the following errors running 'make delete-old' and 'make delete-old-libs': # make delete-old make[2]: "/usr/share/mk/bsd.opts.mk" line 239: Could not find bsd.mkopt.mk make[2]: "/usr/share/mk/bsd.opts.mk" line 262: Malformed conditional (${MK_LIBPTH

Re: r264391 breaks buildworld for -CURRENT amd64

On Sun, Apr 13, 2014 at 2:24 AM, Nathan Whitehorn wrote: > Thanks for the report. It should be fixed now. Apologies for the breakage! > -Nathan Thanks for the fix. No apology necessary. Any bump(s) related to getting efi boot for amd64 working in HEAD get a free pass with me! -Tom _

r264391 breaks buildworld for -CURRENT amd64

Reference: http://docs.freebsd.org/cgi/getmsg.cgi?fetch=9766061+0+current/svn-src-head An attempt to make buildworld on -CURRENT amd64 at r264394 failed with the following error: ===> lib/liby (depend) --- sys.depend__D --- make[6]: make[6]: don't know how to make reloc.c. Stop make[6]: stopped

Newcons with Nvidia

The newcons wiki page shows that newcons with Nvidia as UNKNOWN. That may or may not change after this report. I'm running -CURRENT r263278 amd64 with an Nvidia GeForce 8800M GTS using the nv driver from x11-drivers/xorg-driver. I built/booted a newcons kernel, applied the vidcontrol-for-vt-2014-0

Re: File not found in ftp repository

On Sun, Mar 16, 2014 at 11:56 PM, Nilton Jose Rizzo wrote: > Em Mon, 17 Mar 2014 00:03:29 -0300, Nilton Jose Rizzo escreveu > > Em Sun, 16 Mar 2014 11:31:58 -0400, Thomas Hoffmann escreveu > > > On Sun, Mar 16, 2014 at 9:38 AM, Nilton Jose Rizzo >wrote: > > > >

Re: File not found in ftp repository

On Sun, Mar 16, 2014 at 9:38 AM, Nilton Jose Rizzo wrote: > root@valfenda:/home2/rizzo # wget > > ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/distfiles/xfce4/xfce4-equake-plugin-1.3.4.tar.bz2 > --2014-03-16 10:34:32-- > > ftp://ftp.freebsd.org/pub/FreeBSD/ports/distfiles/xfce4/xfce4-equake-plugin-1.3.

Re: [PATCH] PCI bus number management

On Thu, Feb 6, 2014 at 2:47 PM, Thomas Hoffmann wrote: > On Thu, Feb 6, 2014 at 2:37 PM, John Baldwin wrote: > >> I have a patch to teach the PCI bus code and PCI-PCI bridge driver to >> manage >> PCI bus numbers. The approach is somewhat similar to how NEW_PCIB >&

Re: [PATCH] PCI bus number management

On Thu, Feb 6, 2014 at 2:37 PM, John Baldwin wrote: > I have a patch to teach the PCI bus code and PCI-PCI bridge driver to > manage > PCI bus numbers. The approach is somewhat similar to how NEW_PCIB manages > I/O > windows for briges. Each bridge creates an rman to manage the bus numbers > fo

Re: libelf.so.1 missing after -CURRENT update

On Sat, Feb 1, 2014 at 3:55 PM, Glen Barber wrote: > On Sat, Feb 01, 2014 at 03:52:32PM -0500, Thomas Hoffmann wrote: > > Did my weekly update of -CURRENT today to r261350 from r261236. After the > > upgrade when I tried to run 'pkg' I got the error: > > > >

libelf.so.1 missing after -CURRENT update

Did my weekly update of -CURRENT today to r261350 from r261236. After the upgrade when I tried to run 'pkg' I got the error: libelf.so.1 required by libpkg.so.1 So, I reinstalled 'pkg', which fixed the problem. Then I ran pkg_libchk to see if any other libs were missing and got: glib -2.36.3_1:

Re: Problem updating bootcode on ZFS on root system with MBR

On Sun, Jan 26, 2014 at 3:46 AM, Scot Hetzel wrote: > On Tue, Jan 21, 2014 at 3:11 PM, Thomas Hoffmann wrote: > > On Tue, Jan 21, 2014 at 10:47 AM, Andriy Gapon wrote: > > > >> on 21/01/2014 13:18 Andrey V. Elsukov said the following: > >> > On

Re: lock order reversals w/ backtrace

On Fri, Jan 24, 2014 at 11:47 PM, Thomas Hoffmann wrote: > On Fri, Jan 24, 2014 at 9:52 AM, Thomas Hoffmann wrote: > >> On Thu, Jan 23, 2014 at 11:49 AM, Hans Petter Selasky < >> hans.petter.sela...@bitfrost.no> wrote: >> >>> Hi, >>> >

Re: lock order reversals w/ backtrace

On Fri, Jan 24, 2014 at 9:52 AM, Thomas Hoffmann wrote: > On Thu, Jan 23, 2014 at 11:49 AM, Hans Petter Selasky < > hans.petter.sela...@bitfrost.no> wrote: > >> Hi, >> >> Can you see if you can snap some keywords of the backtraces, like usb_xxx >> us

Re: lock order reversals w/ backtrace

On Thu, Jan 23, 2014 at 11:49 AM, Hans Petter Selasky < hans.petter.sela...@bitfrost.no> wrote: > Hi, > > Can you see if you can snap some keywords of the backtraces, like usb_xxx > usbdx_xxx cam scsi or something like that. > > Else I believe there are some sysctl options to prevent the final r

Re: Fw: Lessons learned from source upgrade from FreeBSD i386 9.2 Stable to FreeBSD i386 10.0 Release.

On Thu, Jan 23, 2014 at 2:15 PM, Matthew Rezny wrote: > Forwarded because my attempt to reply on list was rejected by > heavy-handed and oblivious moderation: > > "The freebsd-current mailing list is for issues involving > FreeBSD-CURRENT, not FreeBSD-STABLE. Neither FreeBSD 9.x nor 10.x is > "c

Re: Lessons learned from source upgrade from FreeBSD i386 9.2 Stable to FreeBSD i386 10.0 Release.

On Thu, Jan 23, 2014 at 11:52 AM, Warren Block wrote: > On Thu, 23 Jan 2014, Kevin Oberman wrote: > > On Thu, Jan 23, 2014 at 7:47 AM, Thomas Hoffmann >> wrote: >> On Thu, Jan 23, 2014 at 9:56 AM, Warren Block >> wrote: >> > >> >

lock order reversals w/ backtrace

A few days ago I started running 11.0-CURRENT at r260971 for the first time. The last couple of times I shutdown my system I noticed 2 or 3 short "lock order reversal" messages with accompanying backtraces scroll by. Do these messages represent a problem that I should report or can I ignore them a

Re: Lessons learned from source upgrade from FreeBSD i386 9.2 Stable to FreeBSD i386 10.0 Release.

On Thu, Jan 23, 2014 at 9:56 AM, Warren Block wrote: > > > Using -DNOCLEAN with an existing /usr/obj can go even faster than ccache: > less than two minutes for a buildworld on my frequently updated i5/SSD > system, sometimes less than one minute. Can you elaborate on this, please? I always clea

Re: Problem updating bootcode on ZFS on root system with MBR

On Tue, Jan 21, 2014 at 10:47 AM, Andriy Gapon wrote: > on 21/01/2014 13:18 Andrey V. Elsukov said the following: > > On 21.01.2014 14:45, Andriy Gapon wrote: > What do I need to do to get the boot2 code written to /dev/ada0s1a? > >>> > >>> This will work only if ada0s1a isn't in use. The de

Problem updating bootcode on ZFS on root system with MBR

I am running 11.0-CURRENT (r260850) with zfs on root with MBR. After upgrading my 10.0-RELEASE (r260669) system to 11.0-CURRENT (r260850) my zpools reported that they needed to be upgraded. So, I upgraded my zpools and I am attempting to update the bootcode (as required). I managed to get the boot

Re: panic: mtx_lock_spin: recursed on non-recursive mutex uart_hwmtx...

On Mon, Jan 20, 2014 at 11:37 AM, Konstantin Belousov wrote: > On Mon, Jan 20, 2014 at 07:36:15AM -0800, David Wolfskill wrote: > > Jan 20 07:02:16 freebeast syslogd: exiting on signal 15 > > Waiting (max 60 seconds) for system process `vnlru' to stop...done > > Waiting (max 60 seconds) for system

Re: FreeBSD 10.0-RC3 Now Available

On Fri, Dec 27, 2013 at 12:15 PM, Scot Hetzel wrote: > The correct way to install/update ZFS Boot code on an MBR disk is: > > Install boot Manager (required on first install) > > # gpart bootcode -b /boot/boot0 ad0 > > Note: /boot/mbr could also be used if you are not multibooting > > Install ZFS

Re: FreeBSD 10.0-RC3 Now Available

AM, Warren Block wrote: > On Fri, 27 Dec 2013, Mathieu Arnold wrote: > > +--On 27 décembre 2013 10:28:07 -0500 Thomas Hoffmann >> wrote: >> | All the examples I've seen for updating bootcode assume GPT. If one has >> | MBR (as I do) and assuming the followi

Re: FreeBSD 10.0-RC3 Now Available

All the examples I've seen for updating bootcode assume GPT. If one has MBR (as I do) and assuming the following basic scheme: gpart show ada0 => 63 976773105 ada0 MBR (466G) 63 976773105 1 freebsd [active] (466G) gpart show ada0s1 =>0 976773105 ada0s1 BSD (