https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=225813
Conrad Meyer changed:
What|Removed |Added
Status|New |Closed
Resolution|---
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=207910
--- Comment #4 from commit-h...@freebsd.org ---
A commit references this bug:
Author: eadler
Date: Sun Feb 11 07:04:48 UTC 2018
New revision: 329121
URL: https://svnweb.freebsd.org/changeset/base/329121
Log:
MFC r308926:
Add Intel Ato
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=207910
Eitan Adler changed:
What|Removed |Added
Resolution|--- |FIXED
Status|In Progress
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=225813
Conrad Meyer changed:
What|Removed |Added
Resolution|--- |FIXED
Status|New
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=225813
Conrad Meyer changed:
What|Removed |Added
Resolution|--- |FIXED
Status|New
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219000
--- Comment #3 from commit-h...@freebsd.org ---
A commit references this bug:
Author: kevans
Date: Sun Feb 11 02:27:52 UTC 2018
New revision: 329114
URL: https://svnweb.freebsd.org/changeset/base/329114
Log:
MFC Loader Fixes 2017q3: r320
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=225450
--- Comment #15 from Pablo Ruiz ---
And, finally if I move the while(1) just after the mtx_unlock_spin call, like
this:
diff --git a/sys/x86/x86/mp_x86.c b/sys/x86/x86/mp_x86.c
index 1c257d87e58..04975dd8a2e 100644
--- a/sys/x86/x86/mp_x86
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=225450
--- Comment #14 from Pablo Ruiz ---
I've tried moving the while loop a bit down at mp_x86, and I got a db prompt
too:
diff --git a/sys/x86/x86/mp_x86.c b/sys/x86/x86/mp_x86.c
index 3cca61ca72e..1c257d87e58 100644
--- a/sys/x86/x86/mp_x86.c
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=225450
--- Comment #13 from Pablo Ruiz ---
Hi again,
Adding the following patch:
diff --git a/sys/x86/x86/mp_x86.c b/sys/x86/x86/mp_x86.c
index 7cc02d663bf..3cca61ca72e 100644
--- a/sys/x86/x86/mp_x86.c
+++ b/sys/x86/x86/mp_x86.c
@@ -925,6 +925,
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=225813
Conrad Meyer changed:
What|Removed |Added
CC||c...@freebsd.org
--- Comment #1 fro
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=225450
--- Comment #12 from Pablo Ruiz ---
Hi,
Here is the output from building with:
options KTR_COMPILE=KTR_PROC
options KTR_MASK=KTR_PROC
options KTR_VERBOSE
...
OK boot kernel.test -v
/boot/kernel.test/kernel text=0x16f3170 data=0xb66748+0
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=15
--- Comment #3 from commit-h...@freebsd.org ---
A commit references this bug:
Author: kevans
Date: Sun Feb 11 02:27:52 UTC 2018
New revision: 329114
URL: https://svnweb.freebsd.org/changeset/base/329114
Log:
MFC Loader Fixes 2017q3: r320
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=225450
--- Comment #11 from John Baldwin ---
Hmm, I don't know why the previous simple lock didn't help. One other possible
thing to try is placing 'while (1);' infinite loop in the init_secondary_tail()
function in sys/x86/x86/mp_x86.c and movin
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=225584
--- Comment #85 from m...@sentex.net ---
(In reply to Konstantin Belousov from comment #84)
(gdb) thread 4
[Switching to thread 4 (LWP 101503 of process 43500)]
#0 _umtx_op_err () at /usr/src/lib/libthr/arch/amd64/amd64/_umtx_op_err.S:37
3
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=225813
Bug ID: 225813
Summary: [geom][patch] gpart does not recognise Apple APFS
partition type
Product: Base System
Version: CURRENT
Hardware: amd64
OS: Any
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=225584
--- Comment #84 from Konstantin Belousov ---
(In reply to mike from comment #83)
It is yet another (different) lock leakage. Please switch to the Thread 4 (LWP
101503) and from the frame 1 do "print *mtx".
--
You are receiving this mail
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=225584
--- Comment #83 from m...@sentex.net ---
Created attachment 190490
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=190490&action=edit
process that is hung in usem state
with libc path and python linked to debug libs
--
You are r
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=114468
Jamie Landeg-Jones changed:
What|Removed |Added
CC||ja...@catflap.org
--- Comment
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=57045
fernando.apesteg...@gmail.com changed:
What|Removed |Added
CC||fernando.apesteguia@g
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=225584
--- Comment #82 from Konstantin Belousov ---
(In reply to mike from comment #81)
I can't say anything without debug info. Start with the backtraces, as usual.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212318
--- Comment #13 from Ben RUBSON ---
Can't your fuse program simply use fuse_unmount(mountpoint, NULL) instead of
fuse_unmount_compat22(mountpoint) ?
(as we did here : https://github.com/vgough/encfs/pull/293)
--
You are receiving this mai
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212318
w.schwarzenf...@utanet.at changed:
What|Removed |Added
CC||w.schwarzenf...@utanet.a
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=225584
--- Comment #81 from m...@sentex.net ---
(In reply to Konstantin Belousov from comment #79)
> BTW, if using the patch from the comment 59, is the hang reproducible ?
I got it to hang on RELENG_11 just now. Perhaps its some combo of the CP
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=225584
--- Comment #80 from m...@sentex.net ---
(In reply to Konstantin Belousov from comment #79)
re: patch 59
I will apply it by itself and try again
patch -p1 < p.59
Hmm... Looks like a unified diff to me...
The text leading up to this was:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=225584
--- Comment #79 from Konstantin Belousov ---
BTW, if using the patch from the comment 59, is the hang reproducible ?
--
You are receiving this mail because:
You are the assignee for the bug.
___
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=225584
--- Comment #78 from Konstantin Belousov ---
(In reply to Ed Maste from comment #77)
Ok. It could be a consequence of the discovered issue occuring in other code
fragment, it can be something else.
So I can wait for some AMD comments. Or
26 matches
Mail list logo
