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
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
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
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
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
-
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, but as
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 can not be
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 must have
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... The
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:33, Pawel Pekala
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 2015-08-06 12:33
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 km...@freebsd.org wrote:
Is this still happening?
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. Macy km...@freebsd.org
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 2015-08-06 12:33
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 you
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 me a
Hi Konstantin,
On 2015-08-23 15:54 +0300, Konstantin Belousov kostik...@gmail.com
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
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 km...@freebsd.org wrote:
Is this still happening?
Still crashes:
+1 for me running
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); /*
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
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 */
+ /*
+* Prevent
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 km...@freebsd.org 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
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 km...@freebsd.org wrote:
Is this still happening?
Still crashes:
+1 for me running r286617
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 km...@freebsd.org wrote:
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 Pekala
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 km...@freebsd.org wrote:
Is this still happening?
Still crashes:
+1 for me running r286617
r286510 has been stable in the package build cluster. r286593 is
On 08/07/15 07:33, Pawel Pekala wrote:
Hi K.,
On 2015-08-06 12:33 -0700, K. Macy km...@freebsd.org wrote:
Is this still happening?
Still crashes:
+1 for me running r286617
Cheers,
Lawrence
___
freebsd-current@freebsd.org mailing list
Hi Mateusz,
On 2015-08-06 23:44 +0200, Mateusz Guzik mjgu...@gmail.com 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
On 8/10/15 2:47 PM, Pawel Pekala wrote:
Hi Mateusz,
On 2015-08-06 23:44 +0200, Mateusz Guzik mjgu...@gmail.com 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
Hi K.,
On 2015-08-06 12:33 -0700, K. Macy km...@freebsd.org 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
On Thu, Aug 06, 2015 at 11:33:28PM +0200, Pawel Pekala wrote:
Hi K.,
On 2015-08-06 12:33 -0700, K. Macy km...@freebsd.org 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
Is this still happening?
On Jul 15, 2015 1:41 PM, Pawel Pekala pa...@freebsd.org wrote:
Hi John-Mark,
On 2015-07-15 11:05 -0700, John-Mark Gurney j...@funkthat.com wrote:
Please repost the entire panic message, and the back trace w/o X
running... Also, if you could share the core and kernel
Pawel Pekala wrote this message on Wed, Jul 15, 2015 at 17:46 +0200:
On 2015-07-14 15:38 -0700, John-Mark Gurney j...@funkthat.com wrote:
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?
Hi John-Mark,
On 2015-07-15 11:05 -0700, John-Mark Gurney j...@funkthat.com 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
Hi John-Mark,
On 2015-07-14 15:38 -0700, John-Mark Gurney j...@funkthat.com wrote:
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
Hi John-Mark,
On 2015-07-14 15:27 -0700, John-Mark Gurney j...@funkthat.com wrote:
Pawel Pekala wrote this message on Tue, Jul 14, 2015 at 22:47 +0200:
On 2015-07-13 23:28 +0200, Mateusz Guzik mjgu...@gmail.com wrote:
On Mon, Jul 13, 2015 at 11:12:05PM +0200, Pawel Pekala wrote:
Hi
I'm
Hi Mateusz,
On 2015-07-13 23:28 +0200, Mateusz Guzik mjgu...@gmail.com 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 about 2-3 weeks
ago. I
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
Pawel Pekala wrote this message on Tue, Jul 14, 2015 at 22:47 +0200:
On 2015-07-13 23:28 +0200, Mateusz Guzik mjgu...@gmail.com 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
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.
Here's backtrace:
(kgdb)
Hi Mateusz,
On 2015-07-13 23:28 +0200, Mateusz Guzik mjgu...@gmail.com 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 about 2-3 weeks
ago. I
41 matches
Mail list logo