https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213903
Mateusz Guzik changed:
What|Removed |Added
Status|Open|Closed
Resolution|---
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213903
Rodney W. Grimes changed:
What|Removed |Added
CC|sta...@freebsd.org |
--- Comment #57 from Rodney
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213903
Mark Millard changed:
What|Removed |Added
CC|
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213903
muxx@gmail.com changed:
What|Removed |Added
CC||muxx@gmail.com
---
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213903
--- Comment #53 from Chris Collins ---
Both patches in this PR have fixed my kernel panic issues on 11.0
I tested the debug patch which didnt aim to fix but did as a side affect, and I
tested the later patch.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213903
Mateusz Guzik changed:
What|Removed |Added
Flags|mfc-stable10?, |mfc-stable10-,
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213903
--- Comment #50 from commit-h...@freebsd.org ---
A commit references this bug:
Author: mjg
Date: Tue Jul 11 03:45:48 UTC 2017
New revision: 320885
URL: https://svnweb.freebsd.org/changeset/base/320885
Log:
Remove waiters check from the
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213903
--- Comment #49 from Ben Woods ---
I am running FreeBSD 12-CURRENT r319025 without any patches and can confirm the
crashes do not occur for me anymore on my FreeNAS mini. Thanks for your help
with this!
--
You are
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213903
--- Comment #48 from Mateusz Guzik ---
Thanks for testing. I'll commit the patch later today with few other
modifications.
That said, I expect the problem to be gone on head starting with r313270 and on
stable/11
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213903
--- Comment #46 from Chris Collins ---
I would hope this makes it into RELEASE 11.1, would be disappointed if that was
released with a known problem. PFSense seem to have absolutely no motivation
to apply the
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213903
Kubilay Kocak changed:
What|Removed |Added
Flags||mfc-stable10?,
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213903
--- Comment #44 from Cassiano Peixoto ---
(In reply to Mateusz Guzik from comment #43)
Ok patch applied. I'll let you know the results.
Thanks.
--
You are receiving this mail because:
You are the assignee for
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213903
--- Comment #43 from Mateusz Guzik ---
Yes, apply the patch to a clean tree. Thanks.
--
You are receiving this mail because:
You are the assignee for the bug.
___
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213903
Mark Linimon changed:
What|Removed |Added
Keywords||patch
--
You
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213903
--- Comment #39 from Mateusz Guzik ---
Can someone who runs into the problem on stable/10 test the following please:
https://people.freebsd.org/~mjg/patches/rwlock-unlock.diff
--
You are receiving this mail because:
You
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213903
--- Comment #38 from Chris Collins ---
(In reply to Mateusz Guzik from comment #35)
Just to let you know my pfsense unit affected by this issue does not have an
atom cpu.
It has a celeron N3150 cpu.
--
You
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213903
--- Comment #37 from Cassiano Peixoto ---
(In reply to Mateusz Guzik from comment #35)
Mateusz,
Yes i realized many changes has been made on 11-STABLE related to this issue. I
think it could be fixed as well.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213903
--- Comment #36 from Franco Fichtner ---
You can use https://github.com/opnsense/src/commit/6b79b52c.patch on stable/10,
it was verified working on 11.0.
Cheers,
Franco
--
You are receiving this mail because:
You
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213903
--- Comment #35 from Mateusz Guzik ---
Hi there, sorry for late reply. This somehow fell through the cracks.
First of all there is no kernel bug per se that I can see, rather a bug in the
atom cpu which started
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213903
--- Comment #34 from Cassiano Peixoto ---
(In reply to Mateusz Guzik from comment #26)
Dear Mateusz,
Please, Can you confirm if it has been fixed in last STABLE? I've seen some
commits but i'm no sure.
Thanks.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213903
--- Comment #33 from Chris Collins ---
I have applied your patch now Mateusz on 11-p10 so will report back if it
works.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213903
chrysa...@chrysalisnet.org changed:
What|Removed |Added
CC|
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213903
--- Comment #31 from Cassiano Peixoto ---
Hi Mateusz,
After some time i had a server with FreeBSD 11-p1 crashed with your patch
applied.
See bellow:
(kgdb) list *0x80b317ac
0x80b317ac is in
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213903
--- Comment #30 from Cassiano Peixoto ---
Hi Mateusz,
Any update about this issue?
Thanks.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213903
--- Comment #29 from Ben Woods ---
(In reply to Mateusz Guzik from comment #26)
I have been running with the patch with no crashes.
If you would like me to confirm whether the issue is still in CURRENT, I will
have
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213903
--- Comment #28 from Cassiano Peixoto ---
(In reply to Cassiano Peixoto from comment #27)
Hi Mateusz, any news about this issue?
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213903
--- Comment #27 from Cassiano Peixoto ---
(In reply to Mateusz Guzik from comment #26)
Hi Mateuz, i can confirm only on stable/10. Maybe someone else can confirm it
to you. After the patch is running 13 days
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213903
--- Comment #26 from Mateusz Guzik ---
So, can I please get confirmation that the problem is still present in current
and still present in stable/11 past r315395? There were several changes which
could have make the
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213903
--- Comment #25 from Mateusz Guzik ---
I'm working on an update on this, likely will be ready tomorrow.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213903
--- Comment #23 from Ben Woods ---
I have also been running a week with this patch, with no more crashes. It
appears to have solved it - thank you!
--
You are receiving this mail because:
You are the assignee for
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213903
--- Comment #22 from Cassiano Peixoto ---
(In reply to Franco Fichtner from comment #21)
Hi Franco, i agree with you. Now it's 6 days with no crashing anymore. Mateusz,
can you take a look please?
--
You are
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213903
--- Comment #21 from Franco Fichtner ---
This was only supposed to print further debug output, but something in here is
probably responsible for fixing it as it touches the same lines as r301157
that's been known to
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213903
--- Comment #20 from Cassiano Peixoto ---
Hi guys,
After i applied Mateusz's patch it stopped crashing (2 days with no crash). So
it seems worked. Mateusz are you planning to commit it?
Thank you for your
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213903
--- Comment #19 from Scott Larson ---
(In reply to Cassiano Peixoto from comment #15)
Tossing in that I've been seeing this panic on stock kernel 11.0-p8 machines
running on Atom C2750s. The failure shown by kgdb output
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213903
--- Comment #18 from Cassiano Peixoto ---
(In reply to Cassiano Peixoto from comment #17)
Hi Mateusz,
I got another customer to try. Can i apply this patch and only replace the
kernel or do i need to replace
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213903
--- Comment #17 from Cassiano Peixoto ---
(In reply to Mateusz Guzik from comment #16)
Hi Mateusz,
Sorry but i can't try this patch, i had to rollback the old kernel to avoid
crashes. It's a production server
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213903
--- Comment #16 from Mateusz Guzik ---
Can you please reproduce with
https://people.freebsd.org/~mjg/patches/rwlock-debug-10.diff appliled on top.
E.g. like this:
cd /usr/src
fetch
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213903
--- Comment #15 from Cassiano Peixoto ---
(In reply to Franco Fichtner from comment #14)
Hi Franco,
Here it is:
FreeBSD 10.3-STABLE #4: Mon Feb 6 09:29:52 BRST 2017
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213903
--- Comment #14 from Franco Fichtner ---
Hi Cassiano,
What's your output of uname -v?
Can you make sure to include a backtrace here from ddb? type "bt" at the prompt
when the panic happens. It may be related but not
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213903
--- Comment #13 from Cassiano Peixoto ---
(In reply to Franco Fichtner from comment #12)
Hi Franco,
I don't know exactly which svn version i'm using, because when i run uname -a
it doesn't show me. But anyway i
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213903
--- Comment #12 from Franco Fichtner ---
r301157 was backported to 10-STABLE, but 10.3 is unaffected. There is no
10.3-STABLE. Which one did you mean?
>From our experience r301157 is the bad commit as the panics
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213903
Cassiano Peixoto changed:
What|Removed |Added
CC|
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213903
--- Comment #10 from Mateusz Guzik ---
turnstile of NULL value and the queue of 1 are consistent with the previous
core showing the lock value being that of the curthread.
Can you please reproduce with this
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213903
--- Comment #9 from Ben Woods ---
(In reply to Franco Fichtner from comment #7)
Indeed, my CPU is one of these. I am experiencing this on a FreeNAS mini bought
from IxSystems.
Some details from my dmesg:
CPU:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213903
--- Comment #8 from Ben Woods ---
(In reply to John Baldwin from comment #6)
> In kgdb, can you go up to the frame that faulted (13) and print out 'ts' and
> 'queue'?
Apologies for the delay in replying, I had
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213903
--- Comment #7 from Franco Fichtner ---
So far we haven't heard back from users regarding the debug info. But we have a
suspect:
https://lists.freebsd.org/pipermail/freebsd-current/2015-November/058122.html
Some CPU
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213903
John Baldwin changed:
What|Removed |Added
CC||j...@freebsd.org
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213903
--- Comment #5 from Franco Fichtner ---
Thank you. A public call for testing will be out today based on your diff. :)
Cheers,
Franco
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213903
Mateusz Guzik changed:
What|Removed |Added
CC||m...@freebsd.org
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213903
--- Comment #3 from Franco Fichtner ---
We have over a dozen user reports on this collected in two weeks, some with
daily crashes. Trying to bring in a developer now...
--
You are receiving this mail because:
You
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213903
--- Comment #2 from Ben Woods ---
I still experience the issue about 2-3 times a month. Not sure how to
investigate further...
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213903
Shawn Webb changed:
What|Removed |Added
CC|
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213903
Ben Woods changed:
What|Removed |Added
CC|
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213903
Bug ID: 213903
Summary: Kernel crashes from turnstile_broadcast
(/usr/src/sys/kern/subr_turnstile.c:837)
Product: Base System
Version: CURRENT
Hardware: Any
54 matches
Mail list logo