https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=210884
Gleb Smirnoff changed:
What|Removed |Added
Assignee|freebsd-bugs@FreeBSD.org|gleb...@freebsd.org
--- Comment #3
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=210884
Gleb Smirnoff changed:
What|Removed |Added
Status|Open|In Progress
--- Comment #38 from G
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=210884
--- Comment #37 from Larry Rosenman ---
(In reply to Shawn Webb from comment #36)
Same here. Looks good:
borg.lerctr.org ~ $ uptime
12:31PM up 2 days, 15:15, 1 users, load averages: 6.79, 5.84, 6.01
borg.lerctr.org ~ $ uname -a
FreeBSD bo
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=210884
--- Comment #36 from Shawn Webb ---
Reverting r302350 works for me.
--
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://li
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=210884
--- Comment #35 from Larry Rosenman ---
so far, with the kernel from the build log I posted:
borg.lerctr.org ~ $ w
9:30PM up 1 day, 14 mins, 1 users, load averages: 4.96, 5.96, 5.80
USER TTY FROM
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=210884
--- Comment #34 from Alexander Kabaev ---
It does not help to disable ipv6 if ipv4 is affected as well.
Please to try to revert r302350.
--
You are receiving this mail because:
You are the assignee for the bug.
___
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=210884
--- Comment #33 from Shawn Webb ---
I just disabled IPv6 on the VM and still get the panic.
--
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=210884
Shawn Webb changed:
What|Removed |Added
CC||shawn.w...@hardenedbsd.org
--- Commen
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=210884
Konstantin Belousov changed:
What|Removed |Added
CC||k...@freebsd.org
--- Comment
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=210884
Kubilay Kocak changed:
What|Removed |Added
Status|New |Open
Flags|
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=210884
--- Comment #29 from Larry Rosenman ---
now we wait some more
--
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.fr
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=210884
--- Comment #28 from Larry Rosenman ---
Created attachment 172272
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=172272&action=edit
build log
reeBSD 11.0-ALPHA6 (VT-LER) #9 r302379M: Fri Jul 8 21:13:03 CDT 2016
--
You are rec
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=210884
--- Comment #27 from Larry Rosenman ---
kernel recompile in the works
--
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=210884
--- Comment #26 from Larry Rosenman ---
Created attachment 172268
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=172268&action=edit
svn diff
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=210884
--- Comment #25 from Alexander Kabaev ---
This is most definitely a callout that never run and was never scheduled, just
as I suspected. I'd say I am still not believing you about reverting that
change.
Please give me your svn diff and clea
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=210884
--- Comment #24 from Larry Rosenman ---
borg.lerctr.org /var/crash # kgdb -c vmcore.last /boot/kernel/kernel
GNU gdb 6.1.1 [FreeBSD]
Copyright 2004 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public Lice
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=210884
--- Comment #23 from Alexander Kabaev ---
If, after all, you do panic after really, really, really reverting the change,
please print lle->lle_timer from in_lltable_free_entry context.
In above command sequence do not forget 'svn diff' to
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=210884
--- Comment #22 from Larry Rosenman ---
I did:
cd /usr/src
svn merge -c -302350 .
nohup make buildworld -j 20 buildkernel >make.k.out 2>&1
make installkernel
shutdown -r now
this is with bdrewery's meta-mode stuff.
--
You are receiving
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=210884
--- Comment #21 from Alexander Kabaev ---
Somehow bugzilla eats comments?
--
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
http
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=210884
--- Comment #19 from Alexander Kabaev ---
Please do check again that you run the kernel with the change reverted. I'll
allow myself not to believe you since reverting _does_ fix the panic here and
it is a reliable one.
--
You are receivin
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=210884
--- Comment #20 from Alexander Kabaev ---
Please do check again that you run the kernel with the change reverted. I'll
allow myself not to believe you since reverting _does_ fix the panic here and
it is a reliable one.
--
You are receivin
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=210884
--- Comment #18 from Larry Rosenman ---
That latest crash is post revert of 302350
--
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=210884
--- Comment #17 from Larry Rosenman ---
Created attachment 172266
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=172266&action=edit
post revert crash on boot :(
--
You are receiving this mail because:
You are the assignee for t
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=210884
--- Comment #16 from Larry Rosenman ---
Done. Now we wait :)
--
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.fr
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=210884
--- Comment #15 from Alexander Kabaev ---
Just revert the change and do not apply my diff
--
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org m
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=210884
--- Comment #14 from Larry Rosenman ---
So, should I do the revert of 302350 AND apply your patch or just apply your
patch? I've already reverted 302081.
--
You are receiving this mail because:
You are the assignee for the bug.
_
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=210884
--- Comment #13 from Alexander Kabaev ---
One more comment: the patch addresses only one instance of callout_stop use and
is not enough to cover all possible panics, ipv6 is being one example.
--
You are receiving this mail because:
You a
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=210884
--- Comment #12 from Alexander Kabaev ---
I suggest trying to revert https://svnweb.freebsd.org/changeset/base/302350
also, I suspect this is the commit that introduced the behaviour.
--
You are receiving this mail because:
You are the as
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=210884
Alexander Kabaev changed:
What|Removed |Added
CC||k...@freebsd.org
--- Comment #1
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=210884
--- Comment #10 from Larry Rosenman ---
Created attachment 172217
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=172217&action=edit
crash after revert
That apparently DID NOT help. See the core.txt I uploaded.
--
You are rece
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=210884
--- Comment #9 from Larry Rosenman ---
I got 2 more crashes this afternoon. I'll see if reverting r302081 helps.
I have core.txt's and vmcores from these as well.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=210884
--- Comment #8 from Larry Rosenman ---
(In reply to Mark Johnston from comment #7)
It's been random enough that I don't know if it would help or not :(
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=210884
Mark Johnston changed:
What|Removed |Added
CC||ma...@freebsd.org
--- Comment #7 f
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=210884
--- Comment #6 from Larry Rosenman ---
(In reply to Ivan Klymenko from comment #5)
That runs automatically, and produces the aforementioned core.txt's
--
You are receiving this mail because:
You are the assignee for the bug.
_
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=210884
Ivan Klymenko changed:
What|Removed |Added
CC||fi...@ukr.net
--- Comment #5 from
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=210884
--- Comment #4 from Larry Rosenman ---
I attached the core.txt files from my 2 crashes. I *DO* have the vmcore's
available if a dev wants to look.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=210884
--- Comment #3 from Larry Rosenman ---
Created attachment 172202
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=172202&action=edit
Crash #2
--
You are receiving this mail because:
You are the assignee for the bug.
_
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=210884
--- Comment #2 from Larry Rosenman ---
Created attachment 172201
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=172201&action=edit
crash #1
--
You are receiving this mail because:
You are the assignee for the bug.
_
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=210884
--- Comment #1 from Larry Rosenman ---
I have 2 vmcore's from similar panics.
--
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=210884
Bug ID: 210884
Summary: panic: bogus refcnt 0 on lle 0xf80004608c00
Product: Base System
Version: 11.0-CURRENT
Hardware: Any
OS: Any
Status: New
40 matches
Mail list logo
