https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=225771
Mark Linimon changed:
What|Removed |Added
Assignee|freebsd-bugs@FreeBSD.org|freebsd-...@freebsd.org
K
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=225775
--- Comment #2 from Ed Maste ---
It is because lld collects read-only contents into a separate segment, for
example:
% readelf -l zfsloader.sym
Elf file type is EXEC (Executable file)
Entry point 0x0
There are 5 program headers, starting
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=225782
--- Comment #1 from Conrad Meyer ---
If this is also true on CURRENT, it looks like a buggy BIOS. Your BIOS isn't
reporting P-states via ACPI or you would see a second positive number instead
of "/-1". It's possible the BIOS bug also brea
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=206420
m...@luckie.org.nz changed:
What|Removed |Added
CC||m...@luckie.org.nz
--- Comment
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=225782
Bug ID: 225782
Summary: Ryzen: unable to set cpu freq
Product: Base System
Version: 11.1-STABLE
Hardware: Any
OS: Any
Status: New
Severity: Affects
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=225775
--- Comment #1 from Andriy Gapon ---
Just curious, why the boot code may need more than two segments.
It would be interesting to see readelf or objdump output for zfsloader.bin.
--
You are receiving this mail because:
You are the assignee
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=224825
--- Comment #12 from D. Ebdrup ---
Turns out it was a lot less effort to reset the ME password, so in case any
additional information needs to be had, I can provide it easily.
--
You are receiving this mail because:
You are the assignee f
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=225778
Bug ID: 225778
Summary: ntpd fails to stay running
Product: Base System
Version: 11.1-RELEASE
Hardware: amd64
OS: Any
Status: New
Severity: Affects
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=225775
Bug ID: 225775
Summary: btxld does not handle input with other than 2 PT_LOAD
segments
Product: Base System
Version: CURRENT
Hardware: Any
OS: Any
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=224825
D. Ebdrup changed:
What|Removed |Added
CC||debd...@gmail.com
--- Comment #11 from
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=225584
--- Comment #62 from Konstantin Belousov ---
(In reply to mike from comment #61)
Do not consider it a fix. I do not have any explanation what is going on
there.
--
You are receiving this mail because:
You are the assignee for the bug.
__
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=225584
--- Comment #61 from m...@sentex.net ---
(In reply to Konstantin Belousov from comment #59)
Its managed 22 builds now without issue. Prior, I could only do 10 at most. I
have a separate RELENG_11 box as well. I take it the same patch will
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=225771
Bug ID: 225771
Summary: [icmp] members of icmpstat are still u_long, why not
uint64_t?
Product: Base System
Version: CURRENT
Hardware: Any
OS: Any
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=225584
--- Comment #60 from m...@sentex.net ---
(In reply to Konstantin Belousov from comment #59)
I have to confess, I might have borked the previous patch and left the while
loop commented out :( I have made sure its right this time. Five build
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=225692
--- Comment #9 from Conrad Meyer ---
(In reply to jkerian+freebsdbugs from comment #8)
I believe it is an automated tool, but bapt knows much more about this process
than I do.
--
You are receiving this mail because:
You are the assignee
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=225692
--- Comment #8 from jkerian+freebsdb...@gmail.com ---
(In reply to Conrad Meyer from comment #7)
Is UTF-8.src pulled from CLDR in some scripted way? Or is that a custom file?
If custom, I have other codepoints that should probably be added
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=225584
--- Comment #59 from Konstantin Belousov ---
(In reply to mike from comment #58)
Lets try a slight variation.
diff --git a/lib/libc/stdio/_flock_stub.c b/lib/libc/stdio/_flock_stub.c
index 069ed64c4e9..935bf18b529 100644
--- a/lib/libc/std
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=225584
--- Comment #58 from m...@sentex.net ---
Created attachment 190431
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=190431&action=edit
with while loop patch
funlockfile 0x80146caa0 0x80c83b800 0x0
Bus error (core dumped)
--
You a
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=225584
--- Comment #57 from Konstantin Belousov ---
(In reply to mike from comment #56)
Yes, that was already handled. And, the hang there is the whole system hang.
Please apply this debugging patch and try reproduce the issue one more time.
di
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=159665
j...@berklix.com changed:
What|Removed |Added
CC||j...@berklix.com
--- Comment #8
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=225762
Bug ID: 225762
Summary: diff truncate function name with --show-function-line
Product: Base System
Version: CURRENT
Hardware: Any
OS: Any
Status: New
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=225584
--- Comment #56 from m...@sentex.net ---
(In reply to Konstantin Belousov from comment #55)
The DragonFly commit mentioned here
http://gitweb.dragonflybsd.org/dragonfly.git/commitdiff/b48dd28447fc8ef62fbc963accd301557fd9ac20
But I FreeBSD al
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=225584
--- Comment #55 from Konstantin Belousov ---
(In reply to mike from comment #53)
The article you linked does not provide any useful information. Nobody knows
why this knob helped.
That said, I am both disappointed and relieved that the pa
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=225584
--- Comment #54 from m...@sentex.net ---
Created attachment 190430
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=190430&action=edit
latest backtrace post kernel patch
--
You are receiving this mail because:
You are the assignee
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=225584
--- Comment #53 from m...@sentex.net ---
(In reply to Konstantin Belousov from comment #52)
No luck. It survived a lot of builds, but still dumped core
funlockfile 0x80146ce48 0x80bcd1500 0x0
Bus error (core dumped)
BTW, DragonFly and L
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=225584
--- Comment #52 from Konstantin Belousov ---
Created attachment 190428
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=190428&action=edit
Disable RDFSBASE on zens.
This is a pure guess based on the _impression_ I get from looking
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=225584
--- Comment #51 from Konstantin Belousov ---
(In reply to mike from comment #50)
It is not the abort line that was printed for the core analyzed. I expect that
the first address printed is 0x80146cd10.
--
You are receiving this mail beca
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=225755
Bug ID: 225755
Summary: Panic after make core
Product: Base System
Version: 11.1-RELEASE
Hardware: amd64
OS: Any
Status: New
Severity: Affects Only
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=218517
Eugene Grosbein changed:
What|Removed |Added
Status|Closed |Open
Resolution|Unable t
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=218517
Eugene Grosbein changed:
What|Removed |Added
Assignee|freebsd-bugs@FreeBSD.org|freebsd-...@freebsd.org
--
You
30 matches
Mail list logo