https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=246629
--- Comment #1 from Ozkan KIRIK ---
There is no problem FreeBSD 12.1-p5
Latest SVN base/stable/12 kernel produces this problem.
--
You are receiving this mail because:
You are the assignee for the bug.
___
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=246626
--- Comment #1 from Ozkan KIRIK ---
There is no problem FreeBSD 12.1-p5
Latest SVN base/stable/12 kernel produces this problem.
--
You are receiving this mail because:
You are the assignee for the bug.
___
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=246660
Mark Linimon changed:
What|Removed |Added
Assignee|b...@freebsd.org|n...@freebsd.org
--
You are receiv
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=246670
--- Comment #5 from Jan Beich ---
(In reply to Conrad Meyer from comment #1)
> In the C locale, some UTF-8 characters are not representable.
Indeed. Why bsdtar(1) only errors out when built statically? QEMU_EMULATING
builds use native-xtoo
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=246670
--- Comment #4 from Danilo G. Baio ---
(In reply to Conrad Meyer from comment #3)
Right. Should I move it to ports (emulators/qemu-user-static) ?
--
You are receiving this mail because:
You are the assignee for the bug.
_
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=246670
--- Comment #3 from Conrad Meyer ---
Seems like a problem with QEMU_EMULATING.
--
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=246670
--- Comment #2 from Danilo G. Baio ---
(In reply to Conrad Meyer from comment #1)
It just happens under QEMU_EMULATING, default system.
--
You are receiving this mail because:
You are the assignee for the bug.
___
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=246670
Conrad Meyer changed:
What|Removed |Added
CC||c...@freebsd.org
--- Comment #1 fro
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=246670
Bug ID: 246670
Summary: bsdtar: Fails to extract (UTF-8) under QEMU_EMULATING
Product: Base System
Version: Unspecified
Hardware: arm64
OS: Any
Status: New
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=246630
--- Comment #12 from Conrad Meyer ---
Beats me; I think dim@ might have more of a clue. You or dim@ probably have
better channels for inquiring further. :-)
--
You are receiving this mail because:
You are the assignee for the bug.
__
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=246630
--- Comment #11 from Ed Maste ---
(In reply to Conrad Meyer from comment #9)
Perhaps this is compiler nondeterminism introduced in Clang 10?
--
You are receiving this mail because:
You are the assignee for the bug.
___
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=246630
--- Comment #10 from Ed Maste ---
Here is where the interesting parts start - I've rearranged the diff -/+ to
make it easier to see where differences exist:
│ - 43c803:4c 63 c2movslq %edx,%r8
│ + 43c803:4c 63 da
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=246630
--- Comment #9 from Conrad Meyer ---
So clearly register selection is non-deterministic for some reason. Perhaps
some optimization pass runs for a non-deterministic amount of time or % of
system memory, and scaling -j impacts that?
--
Yo
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=246630
--- Comment #8 from Conrad Meyer ---
First code-size change is shortly afterwards:
│ - 43c83e:45 31 c0xor%r8d,%r8d
│ - 43c841:44 8a 3bmov(%rbx),%r15b
│ + 43c83e:45 31 db
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=246630
--- Comment #7 from Conrad Meyer ---
Diff seems to start here (I reordered lines for clarity):
│ @@ -63992,183658 +63992,183673 @@
...
│ - 43c7b5:49 89 cdmov%rcx,%r13
│ + 43c7b5:49 89 cfmov
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=246630
--- Comment #6 from Fabian Keil ---
I uploaded the whole compressed diff to:
https://www.fabiankeil.de/tmp/FreeBSD-11.4-BETA2-amd64-r361067-rescue-cp.diff.gz
(33 MB)
--
You are receiving this mail because:
You are the assignee for the bug
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=246630
--- Comment #5 from Ed Maste ---
Ah, the early differences are just different offsets due to later changes,
│ - 40024a:e8 21 94 69 00 callq 0xa99670
│ + 40024a:e8 a1 93 69 00 callq 0xa995f0
Do you have somewh
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=246630
--- Comment #4 from Fabian Keil ---
I'm always compiling with -j2.
Once I noticed the issue using completely different machines I
reproduced it with bhyve changing only the core number.
--
You are receiving this mail because:
You are the
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=246630
--- Comment #3 from Fabian Keil ---
Created attachment 214763
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=214763&action=edit
First 600 lines of the text section difference
--
You are receiving this mail because:
You are the
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=246630
--- Comment #2 from Ed Maste ---
diffoscope should disassemble the .text sections and compare the result; would
you be able to extract and post a few dozen lines from where .text diverges?
Is this unaffected by -j? Are there other differen
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=246656
--- Comment #3 from commit-h...@freebsd.org ---
A commit references this bug:
Author: cem
Date: Fri May 22 15:30:14 UTC 2020
New revision: 361385
URL: https://svnweb.freebsd.org/changeset/base/361385
Log:
ctime.3: Use ASCII asterisks for
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=246656
Conrad Meyer changed:
What|Removed |Added
Resolution|--- |FIXED
Status|New
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=246656
--- Comment #2 from Conrad Meyer ---
Hmm, roff(7):
Special Characters
Special characters are used to encode special glyphs ...
Sequences begin with the escape character ‘\’ followed by
either an open-parenthesis ‘(’ for t
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=246656
Conrad Meyer changed:
What|Removed |Added
CC||c...@freebsd.org
--- Comment #1 fro
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=246494
Ed Maste changed:
What|Removed |Added
Assignee|b...@freebsd.org|ema...@freebsd.org
--
You are receivin
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=246660
Bug ID: 246660
Summary: Sporadic LACP Lagg Flap
Product: Base System
Version: 12.1-STABLE
Hardware: Any
OS: Any
Status: New
Severity: Affects Some P
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=246660
nones...@longcount.org changed:
What|Removed |Added
Hardware|Any |amd64
--
You are receivin
Passez au travers du stress et retrouvez l'énergie du coeur !
Pour vous aider à traverser les épreuves et à éviter le sur-stress, suivez
gratuitement les ateliers web conférence de Christine Angelard, Nathalie Augot
et Antoinette Layoun.
JE M'INSCRIS GRACIEUSEMENT AUX ATELIERS DE MON CHOIX
B
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=246552
--- Comment #5 from Greg V ---
(In reply to Dan Kotowski from comment #4)
Yes, "No valid device tree blob found" is *good*.
The loader probably should not scream so angrily about this when ACPI is
found..
I'll remove the hardcoded has_acp
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=194117
Andriy Gapon changed:
What|Removed |Added
Status|New |In Progress
Assignee|b...
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=194117
--- Comment #1 from commit-h...@freebsd.org ---
A commit references this bug:
Author: avg
Date: Fri May 22 11:20:25 UTC 2020
New revision: 361363
URL: https://svnweb.freebsd.org/changeset/base/361363
Log:
libprocstat: fix ZFS support
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213334
Andriy Gapon changed:
What|Removed |Added
Status|New |Closed
Resolution|---
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=246552
--- Comment #4 from Dan Kotowski ---
(In reply to Mark Millard from comment #3)
Layer 8 strikes again (forgot to use -v)
https://gist.github.com/agrajag9/bbb49048447510a128cb3304546e174b
Not sure if worth noting, but there's a warning ab
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=246656
Bug ID: 246656
Summary: Unicode asterisks in ctime(3) may not render correctly
Product: Documentation
Version: Latest
Hardware: Any
OS: Any
Status: New
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=246654
Bug ID: 246654
Summary: Intel i350 with igb vf driver and wrong vlan tag
Product: Base System
Version: 11.2-STABLE
Hardware: amd64
OS: Any
Status: New
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=234775
--- Comment #3 from Paul Floyd ---
(In reply to Conrad Meyer from comment #2)
Yes, this problem still exists on both i386 and amd64.
--
You are receiving this mail because:
You are the assignee for the bug.
__
37 matches
Mail list logo
