Voc� est� recebendo a Nota Fiscal Eletr�nica n�mero 525156 - [ 222188259 ]
___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Netmap LOR
Here's the backtrace: lock order reversal: (sleepable after non-sleepable) 1st 0xf8002a914840 vm object (vm object) @ /usr/src/sys/vm/vm_fault.c:361 2nd 0x822bf9c8 (&nm_mem)->nm_mtx ((&nm_mem)->nm_mtx) @ /usr/src/sys/dev/netmap/netmap_mem2.c:490 stack backtrace: #0 0x80bb3790 at witness_debugger+0x70 #1 0x80bb3684 at witness_checkorder+0xe54 #2 0x80b5f132 at _sx_xlock+0x72 #3 0x8075c43d at netmap_mem2_ofstophys+0x2d #4 0x80759a2b at netmap_dev_pager_fault+0x3b #5 0x80e8b991 at dev_pager_getpages+0x61 #6 0x80eb440a at vm_pager_get_pages+0x4a #7 0x80e98210 at vm_fault_hold+0x780 #8 0x80e97a48 at vm_fault+0x78 #9 0x81028745 at trap_pfault+0x115 #10 0x81027dd2 at trap+0x342 #11 0x81008981 at calltrap+0x8 Thanks, -- Shawn Webb HardenedBSD GPG Key ID: 0x6A84658F52456EEE GPG Key Fingerprint: 2ABA B6BD EF6A F486 BE89 3D9E 6A84 658F 5245 6EEE signature.asc Description: PGP signature
Re: why 100 packages are evil
On Mon, Apr 25, 2016 at 1:22 AM, David Chisnall wrote: > On 25 Apr 2016, at 06:48, Gerrit Kühn wrote: > > > >> Yes. It will be replaced by 'pkg upgrade' -- as far as I know, that's > >> the plan for 11.0-RELEASE. > > > > Hm... I never had any troubles with freebsd-update, it always "just > > worked" for me. OTOH, I remember having several issues with pkg, > requiring > > to fix databases manually and so on. > > There are two kinds of issues with freebsd-update: > > The first is fairly common: it’s slow and creates a lot of files. If you > read the forums, you’ll find a lot of issues about this. Updates from one > patchlevel to the next are pretty straightforward, but on both the VMs that > I use for FreeBSD and a slow AMD machine with ZFS it takes around an hour > (sometimes more) for freebsd-update to jump one major release. After that, > it takes pkg a minute or two to update the 2-3GB of packages that need > upgrading. Minor releases can often take tens of minutes on these system. > > The many files issue can cause inode exhaustion. One one machine, I just > checked and have 20K files in /var/db/freebsd-update/files. If you’re > using UFS for /var, it’s fairly easy for freebsd-update to run out of > inodes. Trying to recover a FreeBSD system that can no longer create files > in /var is not the most fun uses of my time. > > The second issue is that it sometimes just fails to work. I have twice > had freebsd-update manage to become confused about versions and install a > kernel that couldn’t read the filesystem. I’ve had similar confusion where > (on a box that I administer mostly via the network and where physical > access is a pain) had it install a version of ifconfig from an older > userland than the kernel. These are all on machines where freebsd-update > has been responsible for every upgrade after the initial install from CD. > Most depressingly, it spends ages doing checksums of every file in the > system, determines that they don’t match the expected ones, and then > installs the wrong one anyway. > > I have been using the testing versions of pkg on most FreeBSD machines > since it became available. Since pkg 1.0 was released, I have had far > fewer issues with pkg than with freebsd-update and almost all of those were > to do with poor information in the ports tree and the rest were either UI > or performance issues. We have a lot tighter control over the packaging > metadata for the base system. > > David > I have to agree with this. freebsd-update works pretty well. I have only been burned by it once. (The same ifconfig issue.) I had a number of issues, none disastrous, but painful to fix, with pkg in the early days. Some were probably PBCAK due to lack of familiarity with the tool. Others were bugs in early versions. Since 1.3 came out, I have had no problems at all with pkg other than packages that were not available due to vulnerabilities. Most were either linux-c6 packages (which never sent o get fixed) and ports depending on ffmpeg that include a specific ffmpeg distribution. At this point, I am quite comfortable with the idea of using pkg for the base system, though I will be very, very nervous about it for a while. -- Kevin Oberman, Part time kid herder and retired Network Engineer E-mail: rkober...@gmail.com PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683 ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: New rc.d scripts on current
On Mon, Apr 25, 2016 at 09:31:32AM -0300, Otacílio wrote:
> Em 25/04/2016 06:50, Maurizio Vairani escreveu:
> > 2016-04-24 21:26 GMT+02:00 Lars Engels :
> >
> >> On Sun, Apr 24, 2016 at 08:33:11AM -0700, Manfred Antar wrote:
> >>> Updated /etc yesterday via mergemaster.
> >>> Now I’m getting this on reboot. Everything seems to be working alright.
> >>>
> >>> eval: disk: not found
> >>> eval: disk: not found
> >>> eval: ${GELI ...}: Bad substitutio
> >>> FreeBSD/amd64 (pozo.com) (ttyu0)
> >>>
> >>> login:
> >>>
> >>> Not sure if it is error or new feature.
> >>>
> >>> Manfred
> >> It was my fault. the geli2 rc script had the description text in the
> >> "name" variable.
> >>
> > I am receiving this message too:
> >
> > /etc/rc.d/ccd: descConcatenated disks setup:not found
> >
> > Regards,
> > Maurizio
> > ___
> > freebsd-current@freebsd.org mailing list
> > https://lists.freebsd.org/mailman/listinfo/freebsd-current
> > To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
> I'm receiving
>
> eval: disk: not found
> eval: disk: not found
>
> on beaglebone black also. r298522
The fix was r298550
But you can just rename the second "name" variable definition with
"desc".
pgpJE85MpMCbt.pgp
Description: PGP signature
Re: New rc.d scripts on current
Em 25/04/2016 06:50, Maurizio Vairani escreveu:
2016-04-24 21:26 GMT+02:00 Lars Engels :
On Sun, Apr 24, 2016 at 08:33:11AM -0700, Manfred Antar wrote:
Updated /etc yesterday via mergemaster.
Now I’m getting this on reboot. Everything seems to be working alright.
eval: disk: not found
eval: disk: not found
eval: ${GELI ...}: Bad substitutio
FreeBSD/amd64 (pozo.com) (ttyu0)
login:
Not sure if it is error or new feature.
Manfred
It was my fault. the geli2 rc script had the description text in the
"name" variable.
I am receiving this message too:
/etc/rc.d/ccd: descConcatenated disks setup:not found
Regards,
Maurizio
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
I'm receiving
eval: disk: not found
eval: disk: not found
on beaglebone black also. r298522
[]'s
-Otacílio
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: New rc.d scripts on current
On Mon, Apr 25, 2016 at 11:50:53AM +0200, Maurizio Vairani wrote:
> 2016-04-24 21:26 GMT+02:00 Lars Engels :
>
> > On Sun, Apr 24, 2016 at 08:33:11AM -0700, Manfred Antar wrote:
> > > Updated /etc yesterday via mergemaster.
> > > Now I’m getting this on reboot. Everything seems to be working alright.
> > >
> > > eval: disk: not found
> > > eval: disk: not found
> > > eval: ${GELI ...}: Bad substitutio
> > > FreeBSD/amd64 (pozo.com) (ttyu0)
> > >
> > > login:
> > >
> > > Not sure if it is error or new feature.
> > >
> > > Manfred
> >
> > It was my fault. the geli2 rc script had the description text in the
> > "name" variable.
> >
>
> I am receiving this message too:
>
> /etc/rc.d/ccd: descConcatenated disks setup:not found
That was also fixed yesterday.
pgptcEKpGwVF_.pgp
Description: PGP signature
Re: New rc.d scripts on current
2016-04-24 21:26 GMT+02:00 Lars Engels :
> On Sun, Apr 24, 2016 at 08:33:11AM -0700, Manfred Antar wrote:
> > Updated /etc yesterday via mergemaster.
> > Now I’m getting this on reboot. Everything seems to be working alright.
> >
> > eval: disk: not found
> > eval: disk: not found
> > eval: ${GELI ...}: Bad substitutio
> > FreeBSD/amd64 (pozo.com) (ttyu0)
> >
> > login:
> >
> > Not sure if it is error or new feature.
> >
> > Manfred
>
> It was my fault. the geli2 rc script had the description text in the
> "name" variable.
>
I am receiving this message too:
/etc/rc.d/ccd: descConcatenated disks setup:not found
Regards,
Maurizio
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: why 100 packages are evil
On 25 Apr 2016, at 06:48, Gerrit Kühn wrote: > >> Yes. It will be replaced by 'pkg upgrade' -- as far as I know, that's >> the plan for 11.0-RELEASE. > > Hm... I never had any troubles with freebsd-update, it always "just > worked" for me. OTOH, I remember having several issues with pkg, requiring > to fix databases manually and so on. There are two kinds of issues with freebsd-update: The first is fairly common: it’s slow and creates a lot of files. If you read the forums, you’ll find a lot of issues about this. Updates from one patchlevel to the next are pretty straightforward, but on both the VMs that I use for FreeBSD and a slow AMD machine with ZFS it takes around an hour (sometimes more) for freebsd-update to jump one major release. After that, it takes pkg a minute or two to update the 2-3GB of packages that need upgrading. Minor releases can often take tens of minutes on these system. The many files issue can cause inode exhaustion. One one machine, I just checked and have 20K files in /var/db/freebsd-update/files. If you’re using UFS for /var, it’s fairly easy for freebsd-update to run out of inodes. Trying to recover a FreeBSD system that can no longer create files in /var is not the most fun uses of my time. The second issue is that it sometimes just fails to work. I have twice had freebsd-update manage to become confused about versions and install a kernel that couldn’t read the filesystem. I’ve had similar confusion where (on a box that I administer mostly via the network and where physical access is a pain) had it install a version of ifconfig from an older userland than the kernel. These are all on machines where freebsd-update has been responsible for every upgrade after the initial install from CD. Most depressingly, it spends ages doing checksums of every file in the system, determines that they don’t match the expected ones, and then installs the wrong one anyway. I have been using the testing versions of pkg on most FreeBSD machines since it became available. Since pkg 1.0 was released, I have had far fewer issues with pkg than with freebsd-update and almost all of those were to do with poor information in the ports tree and the rest were either UI or performance issues. We have a lot tighter control over the packaging metadata for the base system. David smime.p7s Description: S/MIME cryptographic signature
Re: why 100 packages are evil
On 25/04/2016 08:39, Miroslav Lachman wrote: Gerrit Kühn wrote on 04/25/2016 07:48: On Sat, 23 Apr 2016 18:52:32 +0100 Matthew Seaman wrote about Re: why 100 packages are evil: MS> > Is freebsd-update going away as result of the new packaging ? Yes. It will be replaced by 'pkg upgrade' -- as far as I know, that's the plan for 11.0-RELEASE. Hm... I never had any troubles with freebsd-update, it always "just worked" for me. OTOH, I remember having several issues with pkg, requiring to fix databases manually and so on. I had many issues with freebsd-update in the past so the last year I converted all machines back to "installkernel & installworld" from NFS mounted build server. It is faster and predictable than freebsd-update (in my case). I hope that pkg upgrade will be good replacement one day. But I don't think it is good enough right now. Miroslav Lachman As another useless datapoint - I've not had any real issues with freebsd-update and I've been using it since 6.x, same with pkg(ng) after the initial bugs were ironed out, this is on 30-40 production servers. ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: why 100 packages are evil
Gerrit Kühn wrote on 04/25/2016 07:48: On Sat, 23 Apr 2016 18:52:32 +0100 Matthew Seaman wrote about Re: why 100 packages are evil: MS> > Is freebsd-update going away as result of the new packaging ? Yes. It will be replaced by 'pkg upgrade' -- as far as I know, that's the plan for 11.0-RELEASE. Hm... I never had any troubles with freebsd-update, it always "just worked" for me. OTOH, I remember having several issues with pkg, requiring to fix databases manually and so on. I had many issues with freebsd-update in the past so the last year I converted all machines back to "installkernel & installworld" from NFS mounted build server. It is faster and predictable than freebsd-update (in my case). I hope that pkg upgrade will be good replacement one day. But I don't think it is good enough right now. Miroslav Lachman ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
