On, Fri Oct 21, 2016, Marcus von Appen wrote:
> Hi,
>
> -CURRENT as of r307731 seems to have some serious flaw with its build
> tool environment. Many ports fail to build with some error similar to
> the following (devel/apr1):
>
> cc -emit-llvm -fno-strict-aliasin
Hi,
-CURRENT as of r307731 seems to have some serious flaw with its build
tool environment. Many ports fail to build with some error similar to
the following (devel/apr1):
cc -emit-llvm -fno-strict-aliasing -pipe -march=native -DLIBICONV_PLUG
-fstack-protector -c -o .c.bco
cc: error: no input
gin
> > bacula::910:910::0:0:Bacula Daemon:/var/db/bacula:/usr/sbin/nologin
> > [...]
> >
> > Obviously, some ports install accounts but do not secure them as there is an
> > empty password.
>
> Are you certain that the ports didn't use "*" as crypte
ula Daemon:/var/db/bacula:/usr/sbin/nologin
|| [...]
||
|| Obviously, some ports install accounts but do not secure them as there is
|| an empty password.
||
|| I consider this not a feature, but a bug.
|
| Mmmm, I rewrote the user/group creation thingie a few months back, a bug
| may have crept in,
:/usr/sbin/nologin
saned::194:194::0:0:SANE Scanner Daemon:/nonexistent:/bin/sh
clamav::106:106::0:0:Clamav Antivirus:/nonexistent:/usr/sbin/nologin
bacula::910:910::0:0:Bacula Daemon:/var/db/bacula:/usr/sbin/nologin
[...]
Obviously, some ports install accounts but do not secure them as there is an
3:563::0:0:PulseAudio System User:/nonexistent:/usr/sbin/nologin
| saned::194:194::0:0:SANE Scanner Daemon:/nonexistent:/bin/sh
| clamav::106:106::0:0:Clamav Antivirus:/nonexistent:/usr/sbin/nologin
| bacula::910:910::0:0:Bacula Daemon:/var/db/bacula:/usr/sbin/nologin
| [...]
|
| Obviously, some por
pulse::563:563::0:0:PulseAudio System User:/nonexistent:/usr/sbin/nologin
saned::194:194::0:0:SANE Scanner Daemon:/nonexistent:/bin/sh
clamav::106:106::0:0:Clamav Antivirus:/nonexistent:/usr/sbin/nologin
bacula::910:910::0:0:Bacula Daemon:/var/db/bacula:/usr/sbin/nologin
[...]
Obviously, some ports
spect this is a bug in the check not the ports.
--
Daniel O'Connor
"The nice thing about standards is that there
are so many of them to choose from."
-- Andrew Tanenbaum
GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C
_
> On 11 Aug 2016, at 15:36, O'Connor, Daniel wrote:
> My clamav and pulse users have a password field of * - i.e. they're disabled
> (AND the shell is nologin)
>
> I suspect this is a bug in the check not the ports.
Sorry, I just saw your next email, please disreg
On Thu, 11 Aug 2016 15:29:03 +1000
Dewayne Geraghty wrote:
> Olivier,
> I've checked my 10.3Stable systems and they all have '*' as their password,
> which is consistent with /usr/ports/Mk/UIDs. You might like to check the
> age of the latter.
> Regards, Dewayne
ent:/usr/sbin/nologin
> saned::194:194::0:0:SANE Scanner Daemon:/nonexistent:/bin/sh
> clamav::106:106::0:0:Clamav Antivirus:/nonexistent:/usr/sbin/nologin
> bacula::910:910::0:0:Bacula Daemon:/var/db/bacula:/usr/sbin/nologin
> [...]
>
> Obviously, some ports install accounts but do
in
> pulse::563:563::0:0:PulseAudio System User:/nonexistent:/usr/sbin/nologin
> saned::194:194::0:0:SANE Scanner Daemon:/nonexistent:/bin/sh
> clamav::106:106::0:0:Clamav Antivirus:/nonexistent:/usr/sbin/nologin
> bacula::910:910::0:0:Bacula Daemon:/var/db/bacula:/usr/sbin/nologin
> [
:SANE Scanner Daemon:/nonexistent:/bin/sh
clamav::106:106::0:0:Clamav Antivirus:/nonexistent:/usr/sbin/nologin
bacula::910:910::0:0:Bacula Daemon:/var/db/bacula:/usr/sbin/nologin
[...]
Obviously, some ports install accounts but do not secure them as there is an
empty password.
I consider this not a
>> Are you sure the portsnap process finished successfully? It appears to
>> be trying to use the FreeBSD 9.x/10.x syntax for adding the dependencies
>> of dialog4ports, rather than the 11.x method.
>>
>
> Nope the opposite :)
>
> dialog4ports uses bsd.prog.mk, somehow his make ends up using the
On 2016-07-01 10:56, Larry Baird wrote:
> I recently installed FreebSD current using a snapshot ISO. I then used svnlite
> to bring FreeBSD source up to date. I then used portsnap fetch extract to
> bring my ports tree up todate. I was surprised I got errors doing 'make
> config
I recently installed FreebSD current using a snapshot ISO. I then used svnlite
to bring FreeBSD source up to date. I then used portsnap fetch extract to
bring my ports tree up todate. I was surprised I got errors doing 'make config'
for a port. I assumed it was a transitory problem. I ha
On Wed, 30 Mar 2016, Aleksander Alekseev wrote:
CPUTYPE?=native
CFLAGS+=-O2 -pipe
CXXFLAGS+=-O2 -pipe
These will bite with no provocation, and prevent ports that want to
set their own flags from using them.
Frankly as a rule of thumb I prefer binary packages. But how would you
recommend to
will keep you in
touch.
Thanks a lot everyone for your help!
>> CPUTYPE?=native
>> CFLAGS+=-O2 -pipe
>> CXXFLAGS+=-O2 -pipe
> These will bite with no provocation, and prevent ports that want to
> set their own flags from using them.
Frankly as a rule of thumb I prefe
On Tue, 29 Mar 2016, Aleksander Alekseev wrote:
Do you still have your old make.conf for comparison?
Sure. Current make.conf:
```
CPUTYPE?=native
CFLAGS+=-O2 -pipe
CXXFLAGS+=-O2 -pipe
These will bite with no provocation, and prevent ports that want to set
their own flags from using them
On Mon, 28 Mar 2016, Aleksander Alekseev wrote:
I think I realized what's going on. I probably rebuilded the world on
two different machines but forgot to do it on this one. I will
re-check this and report results a bit later.
OK, here is a problem. I can't upgrade the world because of compile
On 29 Mar 2016, at 15:53, Aleksander Alekseev wrote:
>
>> For some reason, your build does not pick up the __alloc_size defines
>> from sys/cdefs.h. You will have to figure out which cdefs.h your
>> build is including, and check whether that is in sync with the rest
>> of your source tree.
>
>
> Do you still have your old make.conf for comparison?
Sure. Current make.conf:
```
CPUTYPE?=native
CFLAGS+=-O2 -pipe
CXXFLAGS+=-O2 -pipe
```
Old make.conf:
```
CC=/usr/bin/clang
CXX=/usr/bin/clang++
CPP=/usr/bin/clang-cpp
CPUTYPE?=native
CFLAGS+=-O2 -pipe
CXXFLAGS+=-O2 -pipe
```
Just re-check
On Tue, 29 Mar 2016 16:53:18 +0300
Aleksander Alekseev wrote:
> > For some reason, your build does not pick up the __alloc_size
> > defines from sys/cdefs.h. You will have to figure out which
> > cdefs.h your build is including, and check whether that is in sync
> > with the rest of your source
> For some reason, your build does not pick up the __alloc_size defines
> from sys/cdefs.h. You will have to figure out which cdefs.h your
> build is including, and check whether that is in sync with the rest
> of your source tree.
I removed CC, CXX and CPP lines from /etc/make.conf and it solved
On 29 Mar 2016, at 11:38, Aleksander Alekseev wrote:
>
> OK, here is what I did so far.
>
> First I booted with 10.2 kernel (it's always good to have a backup).
> Now I have 10.2 kernel and world. After that I installed clang38 using
> ports (and discovered a b
OK, here is what I did so far.
First I booted with 10.2 kernel (it's always good to have a backup).
Now I have 10.2 kernel and world. After that I installed clang38 using
ports (and discovered a bug #208375 in a process).
> Don't try to build world with ports clang, it's not
OK, here is what I did so far.
First I booted with 10.2 kernel (it's always good to have a backup).
Now I have 10.2 kernel and world. After that I installed clang38 using
ports (and discovered a bug #208375 in a process).
> Don't try to build world with ports clang, it's not
clang-3.9 and it solved my problem with CLang I mentioned before).
>
> Thoughts?
Don't try to build world with ports clang, it's not yet supported (at
least not officially, and without jumping through some flaming hoops).
Just use the compiler in the base system.
If all that d
reproduces with both CLang 3.6 and new CLang compiled
> > manually from trunk (I created symlinks clang++-3.9 and clang-cpp-3.9
> > to clang-3.9 and it solved my problem with CLang I mentioned before).
> >
> > Thoughts?
> >
>
> I see that you're using cla
> to clang-3.9 and it solved my problem with CLang I mentioned before).
>
> Thoughts?
>
I see that you're using clang36 from ports. Right now clang38 is
what's being used in 11-CURRENT. I don't know whether it will
help, but you could try installing clang38 from por
> I think I realized what's going on. I probably rebuilded the world on
> two different machines but forgot to do it on this one. I will
> re-check this and report results a bit later.
OK, here is a problem. I can't upgrade the world because of compile
errors I mentioned before:
http://lpaste.net
> It used to be FreeBSD 10.2 but I rebuilded and reinstall kernel and
> world from CURRENT according to Handbook instructions. I have exact
> steps recorded in case it would help. I hope such way of upgrading
> FreeBSD is correct?
I think I realized what's going on. I probably rebuilded the world
On Mon, 28 Mar 2016 08:47:35 +0300
Aleksander Alekseev wrote:
> > What's the output of these commands?:
> >
> > freebsd-version
> > uname -r
> > uname -a
> > grep "define __FreeBSD_version" /usr/include/sys/param.h
> >
>
> $ freebsd-version
> 10.2-RELEASE
>
> $ uname -r
> 11.0-CURRENT
>
>
> What's the output of these commands?:
>
> freebsd-version
> uname -r
> uname -a
> grep "define __FreeBSD_version" /usr/include/sys/param.h
>
$ freebsd-version
10.2-RELEASE
$ uname -r
11.0-CURRENT
$ uname -a
FreeBSD portege 11.0-CURRENT FreeBSD 11.0-CURRENT #0 r297287: Sat Mar
26 12:36:04 MSK
D project a
> bit by reporting them.
>
> Today I noticed that I can't install anything from ports any longer:
>
> ```
> $ cd /usr/ports/*/evince
> $ sudo make -DBATCH configure
>
> make: "/usr/ports/Mk/bsd.port.mk" line 1162: UNAME_r (11.0-CURRENT)
Hello
I'm using FreeBSD CURRENT because of recent improvements in area of
Intel GPUs support in this branch. Also there is a hope that by using
CURRENT I can discover some bugs and contribute to FreeBSD project a
bit by reporting them.
Today I noticed that I can't install anything from
On 12/31/15 2:13 AM, Matthias Apitz wrote:
> El día Wednesday, December 30, 2015 a las 03:39:11PM +0100, Matthias Apitz
> escribió:
>
>>> # pkg info
>>> dialog4ports-0.1.5_2 Console Interface to configure ports
>>> pkg-1.6.2
El día Wednesday, December 30, 2015 a las 03:39:11PM +0100, Matthias Apitz
escribió:
> > # pkg info
> > dialog4ports-0.1.5_2 Console Interface to configure ports
> > pkg-1.6.2 Package manager
> > poudriere-devel-3.1.99.20151204 Po
El día Wednesday, December 30, 2015 a las 03:22:46PM +0100, Matthias Apitz
escribió:
>
> Hello,
>
> I run into the following problem:
>
> # poudriere version
> 3.2-pre
>
> (installed from ports)
>
> # pkg info
> dialog4ports-0.1.5_2 Console Inte
Hello,
I run into the following problem:
# poudriere version
3.2-pre
(installed from ports)
# pkg info
dialog4ports-0.1.5_2 Console Interface to configure ports
pkg-1.6.2 Package manager
poudriere-devel-3.1.99.20151204 Port build and test system
# uname -a
o! wow!
-a
On 10 November 2015 at 16:05, Yuri wrote:
> I would like to present two new ports:
> * RetroArch: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=204347
> * RetroArch core-pack:
> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=204452
>
> RetroArch allows
I would like to present two new ports:
* RetroArch: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=204347
* RetroArch core-pack:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=204452
RetroArch allows to play many older game titles with one simple UI,
using different cores (plugins) to
t
> port when it should just be a link to the current gcc default.
This is the direction I'm working towards by establishing lang/gccX-devel
ports (for snapshots) in addition to ang/gccX ports (for releases).
> BTW, perhaps it’s time to bump the default gcc to gcc49? ;).
Absolutel
Hi Gerald;
> Il giorno 08/nov/2015, alle ore 19:00, Gerald Pfeifer ha
> scritto:
>
> On Tue, 13 Oct 2015, Justin Hibbits wrote:
>> As Antoine mentioned, the problem is that lang/gcc does not have this
>> patch. USE_GCC uses lang/gcc, not lang/gcc48. So lang/gcc needs to
>> be updated.
>
> I
On Tue, 13 Oct 2015, Justin Hibbits wrote:
> As Antoine mentioned, the problem is that lang/gcc does not have this
> patch. USE_GCC uses lang/gcc, not lang/gcc48. So lang/gcc needs to
> be updated.
I have (finally) managed to steal the team, kicked off testing,
and plan on committing the patches
On 10/13/2015 9:59 AM, Justin Hibbits wrote:
Hi Pedro,
...
As Antoine mentioned, the problem is that lang/gcc does not have this
patch. USE_GCC uses lang/gcc, not lang/gcc48. So lang/gcc needs to
be updated.
I see now.
FWIW, I installed gcc48 and then I added USE_GCC= yes to the port.
Tha
Hi Pedro,
On Tue, Oct 13, 2015 at 9:18 AM, Pedro Giffuni wrote:
> Hi;
>
> On 10/12/2015 8:28 PM, Justin Hibbits wrote:
>>
>> Hi Pedro,
>>
>> ...
>> This is on powerpc64. I see the patch has been there for 16 months, but
>> for some reason, the /usr/local/bin/gcc48 doesn't contain the patch. I r
Hi;
On 10/12/2015 8:28 PM, Justin Hibbits wrote:
Hi Pedro,
...
This is on powerpc64. I see the patch has been there for 16 months,
but for some reason, the /usr/local/bin/gcc48 doesn't contain the
patch. I ran `strings` on the binary, and it has the following string:
%{fstack-protector|fs
On Mon, Oct 12, 2015 at 8:46 PM, Pedro Giffuni wrote:
>> All I can say is building with USE_GCC=yes, I see the following error:
>>
>> g++48: error: unrecognized command line option '-fstack-protector-strong'
>>
>> This is using the latest gcc48 in ports (
:
The default ports gcc for USE_GCC is still 4.8, which does not
support
-fstack-protector-strong. This breaks several ports including
(from
my poudriere run): libfpx and qt4-sqlite3-plugin.
- Justin
r288669 only applies to base. It was tested with an exp-run and
there were
no
failures so
On 10/12/2015 3:33 PM, Justin Hibbits wrote:
Hi Pedro,
On Mon, Oct 12, 2015 at 3:28 PM, Pedro Giffuni wrote:
Hi again;
On 12/10/2015 03:16 p.m., Pedro Giffuni wrote:
Hello;
On 12/10/2015 02:56 p.m., Justin Hibbits wrote:
The default ports gcc for USE_GCC is still 4.8, which does not
:
The default ports gcc for USE_GCC is still 4.8, which does not support
-fstack-protector-strong. This breaks several ports including (from
my poudriere run): libfpx and qt4-sqlite3-plugin.
- Justin
r288669 only applies to base. It was tested with an exp-run and there were
no
failures so this is
On Mon, Oct 12, 2015 at 4:16 PM, Pedro Giffuni wrote:
> Hello;
>
> On 12/10/2015 02:56 p.m., Justin Hibbits wrote:
>>
>> The default ports gcc for USE_GCC is still 4.8, which does not support
>> -fstack-protector-strong. This breaks several ports including (from
>&
Hi Pedro,
On Mon, Oct 12, 2015 at 3:28 PM, Pedro Giffuni wrote:
> Hi again;
>
> On 12/10/2015 03:16 p.m., Pedro Giffuni wrote:
>>
>> Hello;
>>
>> On 12/10/2015 02:56 p.m., Justin Hibbits wrote:
>>>
>>> The default ports gcc for USE_GCC is stil
Hi again;
On 12/10/2015 03:16 p.m., Pedro Giffuni wrote:
Hello;
On 12/10/2015 02:56 p.m., Justin Hibbits wrote:
The default ports gcc for USE_GCC is still 4.8, which does not support
-fstack-protector-strong. This breaks several ports including (from
my poudriere run): libfpx and qt4-sqlite3
Hello;
On 12/10/2015 02:56 p.m., Justin Hibbits wrote:
The default ports gcc for USE_GCC is still 4.8, which does not support
-fstack-protector-strong. This breaks several ports including (from
my poudriere run): libfpx and qt4-sqlite3-plugin.
- Justin
r288669 only applies to base. It was
The default ports gcc for USE_GCC is still 4.8, which does not support
-fstack-protector-strong. This breaks several ports including (from
my poudriere run): libfpx and qt4-sqlite3-plugin.
- Justin
___
freebsd-current@freebsd.org mailing list
https
John-Mark,
with all the due respect I have to invoke the forest-vs-trees argument here:
- it is established that in the knote() loop the current knote member of the
klist can be removed
- it's a fact that getting a pointer to a next element from a removed element is
an illegal operation
- FOREAC
On 1 September 2015 at 15:01, John-Mark Gurney wrote:
>
> But I would ask you to respect my maintainership of the code... Just
> because you get paid to work on FreeBSD full time does not mean you
> get to run roughshod over other people's work and force them to work
> on your time frame... Other
Konstantin Belousov wrote this message on Tue, Sep 01, 2015 at 21:44 +0300:
> On Tue, Sep 01, 2015 at 11:24:06AM -0700, John-Mark Gurney wrote:
> > Andriy Gapon wrote this message on Thu, Aug 27, 2015 at 23:21 +0300:
> > > On 27/08/2015 21:09, John-Mark Gurney wrote:
> > > > Andriy Gapon wrote this
On Tue, Sep 01, 2015 at 11:24:06AM -0700, John-Mark Gurney wrote:
> Andriy Gapon wrote this message on Thu, Aug 27, 2015 at 23:21 +0300:
> > On 27/08/2015 21:09, John-Mark Gurney wrote:
> > > Andriy Gapon wrote this message on Thu, Aug 27, 2015 at 10:21 +0300:
> > >> On 27/08/2015 02:36, John-Mark
Andriy Gapon wrote this message on Thu, Aug 27, 2015 at 23:21 +0300:
> On 27/08/2015 21:09, John-Mark Gurney wrote:
> > Andriy Gapon wrote this message on Thu, Aug 27, 2015 at 10:21 +0300:
> >> On 27/08/2015 02:36, John-Mark Gurney wrote:
> >>> We should/cannot get here w/ an empty list. If we do,
On 08/23/15 22:54, Konstantin Belousov wrote:
> On Sun, Aug 23, 2015 at 12:08:16PM +0300, Konstantin Belousov wrote:
>> On Sun, Aug 23, 2015 at 09:54:28AM +0300, Andriy Gapon wrote:
>>> On 12/08/2015 17:11, Lawrence Stewart wrote:
On 08/07/15 07:33, Pawel Pekala wrote:
> Hi K.,
>
>
On 08/27/15 17:15, Don Lewis wrote:
> On 27 Aug, Don Lewis wrote:
>> On 27 Aug, Lawrence Stewart wrote:
>>> On 08/27/15 09:36, John-Mark Gurney wrote:
Andriy Gapon wrote this message on Sun, Aug 23, 2015 at 09:54 +0300:
> On 12/08/2015 17:11, Lawrence Stewart wrote:
>> On 08/07/15 07:3
On 27/08/2015 23:21, Andriy Gapon wrote:
>> > First off, that can't be r286922, per:
>> > https://svnweb.freebsd.org/base/stable/10/sys/kern/kern_event.c?annotate=286922
>> >
>> > line 1964 is blank... The line of code above should be at line 1884,
>> > so not sure what is wrong here...
> No, it
On Thu, Aug 27, 2015 at 11:09:45AM -0700, John-Mark Gurney wrote:
> Andriy Gapon wrote this message on Thu, Aug 27, 2015 at 10:21 +0300:
> > On 27/08/2015 02:36, John-Mark Gurney wrote:
> > > We should/cannot get here w/ an empty list. If we do, then there is
> > > something seriously wrong... Th
On 27/08/2015 21:09, John-Mark Gurney wrote:
> Andriy Gapon wrote this message on Thu, Aug 27, 2015 at 10:21 +0300:
>> On 27/08/2015 02:36, John-Mark Gurney wrote:
>>> We should/cannot get here w/ an empty list. If we do, then there is
>>> something seriously wrong... The current kn (which we mus
Andriy Gapon wrote this message on Thu, Aug 27, 2015 at 10:21 +0300:
> On 27/08/2015 02:36, John-Mark Gurney wrote:
> > We should/cannot get here w/ an empty list. If we do, then there is
> > something seriously wrong... The current kn (which we must have as we
> > are here) MUST be on the list,
On Thu, Aug 27, 2015 at 10:21:47AM +0300, Andriy Gapon wrote:
> On 27/08/2015 02:36, John-Mark Gurney wrote:
> > We should/cannot get here w/ an empty list. If we do, then there is
> > something seriously wrong... The current kn (which we must have as we
> > are here) MUST be on the list, but as
On 27 Aug, Lawrence Stewart wrote:
> On 08/27/15 09:36, John-Mark Gurney wrote:
>> Andriy Gapon wrote this message on Sun, Aug 23, 2015 at 09:54 +0300:
>>> On 12/08/2015 17:11, Lawrence Stewart wrote:
On 08/07/15 07:33, Pawel Pekala wrote:
> Hi K.,
>
> On 2015-08-06 12:33 -0700, "K
On 27/08/2015 02:36, John-Mark Gurney wrote:
> We should/cannot get here w/ an empty list. If we do, then there is
> something seriously wrong... The current kn (which we must have as we
> are here) MUST be on the list, but as you just showed, there are no
> knotes on the list.
>
> Can you get m
On 27 Aug, Don Lewis wrote:
> On 27 Aug, Lawrence Stewart wrote:
>> On 08/27/15 09:36, John-Mark Gurney wrote:
>>> Andriy Gapon wrote this message on Sun, Aug 23, 2015 at 09:54 +0300:
On 12/08/2015 17:11, Lawrence Stewart wrote:
> On 08/07/15 07:33, Pawel Pekala wrote:
>> Hi K.,
>>
On 08/27/15 09:36, John-Mark Gurney wrote:
> Andriy Gapon wrote this message on Sun, Aug 23, 2015 at 09:54 +0300:
>> On 12/08/2015 17:11, Lawrence Stewart wrote:
>>> On 08/07/15 07:33, Pawel Pekala wrote:
Hi K.,
On 2015-08-06 12:33 -0700, "K. Macy" wrote:
> Is this still happeni
Konstantin Belousov wrote this message on Mon, Aug 24, 2015 at 11:10 +0300:
> On Sun, Aug 23, 2015 at 10:35:44PM -0700, John-Mark Gurney wrote:
> > Konstantin Belousov wrote this message on Sun, Aug 23, 2015 at 15:54 +0300:
> > > if (kev->flags & EV_ADD)
> > > - tkn = knote_alloc(waitok);
Andriy Gapon wrote this message on Sun, Aug 23, 2015 at 09:54 +0300:
> On 12/08/2015 17:11, Lawrence Stewart wrote:
> > On 08/07/15 07:33, Pawel Pekala wrote:
> >> Hi K.,
> >>
> >> On 2015-08-06 12:33 -0700, "K. Macy" wrote:
> >>> Is this still happening?
> >>
> >> Still crashes:
> >
> > +1 for m
Hi Konstantin,
On 2015-08-23 15:54 +0300, Konstantin Belousov
wrote:
>After looking at your data closely, I think you are right. The panic
>occurs when the exit1(9) does KNOTE_LOCKED(NOTE_EXIT). This is the
>only case in the tree where filter uses knlist_remove_inevent() to
>detach processed no
On Sun, Aug 23, 2015 at 10:35:44PM -0700, John-Mark Gurney wrote:
> Konstantin Belousov wrote this message on Sun, Aug 23, 2015 at 15:54 +0300:
> > if (kev->flags & EV_ADD)
> > - tkn = knote_alloc(waitok); /* prevent waiting with locks */
> > + /*
> > +* Pre
On 23/08/2015 15:54, Konstantin Belousov wrote:
> After looking at your data closely, I think you are right. The panic
> occurs when the exit1(9) does KNOTE_LOCKED(NOTE_EXIT). This is the
> only case in the tree where filter uses knlist_remove_inevent() to detach
> processed note, so indeed the s
Konstantin Belousov wrote this message on Sun, Aug 23, 2015 at 15:54 +0300:
> On Sun, Aug 23, 2015 at 12:08:16PM +0300, Konstantin Belousov wrote:
> > On Sun, Aug 23, 2015 at 09:54:28AM +0300, Andriy Gapon wrote:
> > > On 12/08/2015 17:11, Lawrence Stewart wrote:
> > > > On 08/07/15 07:33, Pawel Pe
On Sun, Aug 23, 2015 at 12:08:16PM +0300, Konstantin Belousov wrote:
> On Sun, Aug 23, 2015 at 09:54:28AM +0300, Andriy Gapon wrote:
> > On 12/08/2015 17:11, Lawrence Stewart wrote:
> > > On 08/07/15 07:33, Pawel Pekala wrote:
> > >> Hi K.,
> > >>
> > >> On 2015-08-06 12:33 -0700, "K. Macy" wrote:
On Sun, Aug 23, 2015 at 09:54:28AM +0300, Andriy Gapon wrote:
> On 12/08/2015 17:11, Lawrence Stewart wrote:
> > On 08/07/15 07:33, Pawel Pekala wrote:
> >> Hi K.,
> >>
> >> On 2015-08-06 12:33 -0700, "K. Macy" wrote:
> >>> Is this still happening?
> >>
> >> Still crashes:
> >
> > +1 for me runni
On 12/08/2015 17:11, Lawrence Stewart wrote:
> On 08/07/15 07:33, Pawel Pekala wrote:
>> Hi K.,
>>
>> On 2015-08-06 12:33 -0700, "K. Macy" wrote:
>>> Is this still happening?
>>
>> Still crashes:
>
> +1 for me running r286617
Here is another +1 with r286922.
I can add a couple of bits of debuggi
On 8/12/15 7:11 AM, Lawrence Stewart wrote:
> On 08/07/15 07:33, Pawel Pekala wrote:
>> Hi K.,
>>
>> On 2015-08-06 12:33 -0700, "K. Macy" wrote:
>>> Is this still happening?
>>
>> Still crashes:
>
> +1 for me running r286617
>
r286510 has been stable in the package build cluster. r286593 is sta
On 08/07/15 07:33, Pawel Pekala wrote:
> Hi K.,
>
> On 2015-08-06 12:33 -0700, "K. Macy" wrote:
>> Is this still happening?
>
> Still crashes:
+1 for me running r286617
Cheers,
Lawrence
___
freebsd-current@freebsd.org mailing list
http://lists.freebs
On 8/10/15 2:47 PM, Pawel Pekala wrote:
> Hi Mateusz,
>
> On 2015-08-06 23:44 +0200, Mateusz Guzik wrote:
>> Sorry, I completely forgot about this.
>>
>> Can you please modify debug flags in your kernel config file to be
>> "-O0 -g3" and reproduce with that? This should allow kgdb to obtain
>> fu
Hi Mateusz,
On 2015-08-06 23:44 +0200, Mateusz Guzik wrote:
>Sorry, I completely forgot about this.
>
>Can you please modify debug flags in your kernel config file to be
>"-O0 -g3" and reproduce with that? This should allow kgdb to obtain
>full info (along with exact rash site for inspection) wit
On Thu, Aug 06, 2015 at 11:33:28PM +0200, Pawel Pekala wrote:
> Hi K.,
>
> On 2015-08-06 12:33 -0700, "K. Macy" wrote:
> >Is this still happening?
>
> Still crashes:
>
> Thu Aug 6 23:22:05 CEST 2015
>
> FreeBSD blaviken.slowicza.org 11.0-CURRENT FreeBSD 11.0-CURRENT #50 r286370:
> Thu Aug 6
Hi K.,
On 2015-08-06 12:33 -0700, "K. Macy" wrote:
>Is this still happening?
Still crashes:
Thu Aug 6 23:22:05 CEST 2015
FreeBSD blaviken.slowicza.org 11.0-CURRENT FreeBSD 11.0-CURRENT #50 r286370:
Thu Aug 6 19:55:29 CEST 2015
r...@blaviken.slowicza.org:/usr/obj/hdd/src/sys/GENERIC am
Is this still happening?
On Jul 15, 2015 1:41 PM, "Pawel Pekala" wrote:
> Hi John-Mark,
>
> On 2015-07-15 11:05 -0700, John-Mark Gurney wrote:
> >Please repost the entire panic message, and the back trace w/o X
> >running... Also, if you could share the core and kernel w/ me (you can
> >email m
Hi John-Mark,
On 2015-07-15 11:05 -0700, John-Mark Gurney wrote:
>Please repost the entire panic message, and the back trace w/o X
>running... Also, if you could share the core and kernel w/ me (you can
>email me directly if you'd like), that'd help.
Fatal trap 9: general protection fault while
ests were done with X running yes. Today I did same test with all
> services commented out in rc.conf (including X) and did get same result.
> Poudriere causes kernel panic always in the same spot:
>
> [00:00:39] >> Calculating ports order and dependencies
Please repost the en
nd did get same result.
Poudriere causes kernel panic always in the same spot:
[00:00:39] >> Calculating ports order and dependencies
--
pozdrawiam / with regards
Paweł Pękala
___
freebsd-current@freebsd.org mailing list
http://lists.f
i
>> >>
>> >> I'm getting 100% reproducible kernel crash while trying build
>> >> ports with poudriere on my system. This started to show up about
>> >> 2-3 weeks ago. I upgrade my system on weekly basis usually on
>> >> saturday. Her
Pawel Pekala wrote this message on Mon, Jul 13, 2015 at 23:12 +0200:
> Let me know if you need more details.
Were you running X at the time of the crash? and if so, can you try
to reproduce w/o X running? It's hard to know if the panic (and you
didn't include the panic string) is due to kern_eve
Pawel Pekala wrote this message on Tue, Jul 14, 2015 at 22:47 +0200:
> On 2015-07-13 23:28 +0200, Mateusz Guzik wrote:
> >On Mon, Jul 13, 2015 at 11:12:05PM +0200, Pawel Pekala wrote:
> >> Hi
> >>
> >> I'm getting 100% reproducible kernel crash while try
Hi Mateusz,
On 2015-07-13 23:28 +0200, Mateusz Guzik wrote:
>On Mon, Jul 13, 2015 at 11:12:05PM +0200, Pawel Pekala wrote:
>> Hi
>>
>> I'm getting 100% reproducible kernel crash while trying build ports
>> with poudriere on my system. This started to show up abou
Hi Mateusz,
On 2015-07-13 23:28 +0200, Mateusz Guzik wrote:
>On Mon, Jul 13, 2015 at 11:12:05PM +0200, Pawel Pekala wrote:
>> Hi
>>
>> I'm getting 100% reproducible kernel crash while trying build ports
>> with poudriere on my system. This started to show up abou
On Mon, Jul 13, 2015 at 11:12:05PM +0200, Pawel Pekala wrote:
> Hi
>
> I'm getting 100% reproducible kernel crash while trying build ports
> with poudriere on my system. This started to show up about 2-3 weeks
> ago. I upgrade my system on weekly basis usually on saturday
Hi
I'm getting 100% reproducible kernel crash while trying build ports
with poudriere on my system. This started to show up about 2-3 weeks
ago. I upgrade my system on weekly basis usually on saturday.
Here's backtrace:
(kgdb) bt
#0 doadump (textdump=1) at pcpu.h:221
#1 0x8
On 04/21/15 12:43, Bryan Drewery wrote:
On 4/5/2015 2:10 PM, Pedro Giffuni wrote:
I don't know if someone is keeping up-to-date packages for -current
but I will hold the headers update for a while to help such cases.
We build head packages _at least_ once a week. Currently we always
update t
301 - 400 of 1651 matches
Mail list logo
