https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=255745
--- Comment #3 from John Grafton ---
(In reply to Ulrich Spörlein from comment #2)
I just opened it this morning from an overnight sleep and it worked as
expected. It only has an uptime of 3 hours, however. I'll leave it open for
the day
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=255659
tech-li...@zyxst.net changed:
What|Removed |Added
Severity|Affects Only Me |Affects Some People
--
You
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=255749
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=255775
Mark Linimon changed:
What|Removed |Added
Assignee|b...@freebsd.org|i...@freebsd.org
--
You are receiv
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=255685
Pietro Cerutti changed:
What|Removed |Added
Severity|Affects Only Me |Affects Some People
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=255759
Mark Linimon changed:
What|Removed |Added
Assignee|b...@freebsd.org|u...@freebsd.org
Component
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=255309
Mark Linimon changed:
What|Removed |Added
Assignee|b...@freebsd.org|n...@freebsd.org
Keywords
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=251615
Mark Linimon changed:
What|Removed |Added
Assignee|b...@freebsd.org|m...@freebsd.org
--
You are receiv
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=251363
Mark Linimon changed:
What|Removed |Added
Assignee|b...@freebsd.org|f...@freebsd.org
--
You are receiv
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=247417
Mark Linimon changed:
What|Removed |Added
Assignee|b...@freebsd.org|multime...@freebsd.org
Ke
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=242212
Mark Linimon changed:
What|Removed |Added
Assignee|b...@freebsd.org|i...@freebsd.org
--- Comment #11 fr
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=238735
Mark Linimon changed:
What|Removed |Added
Assignee|b...@freebsd.org|r...@freebsd.org
Keywords
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=253868
Ceri Davies changed:
What|Removed |Added
CC||c...@freebsd.org
Assignee|
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=255745
--- Comment #4 from John Grafton ---
The laptop failed to resume the first time I attempted to close and then open
the lid after leaving it open for 4 hours. So it failed to resume properly
after an uptime of ~7 hours.
--
You are receivi
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=21
cy...@freebsdfoundation.org changed:
What|Removed |Added
CC||cy...@freebsdfoundatio
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=253483
Teran McKinney changed:
What|Removed |Added
CC||seg...@go-beyond.org
--- Comment
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=255798
Bug ID: 255798
Summary: sort: Does not handle files starting with +
Product: Base System
Version: CURRENT
Hardware: Any
OS: Any
Status: New
Severity
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=255799
Bug ID: 255799
Summary: ffs crash on ufs file system
Product: Base System
Version: 13.0-RELEASE
Hardware: amd64
OS: Any
Status: New
Severity: Affect
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=255799
--- Comment #1 from doc...@doctor.nl2k.ab.ca ---
Created attachment 224857
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=224857&action=edit
info file
vmcore.1 file in 1.1GB
--
You are receiving this mail because:
You are the a
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=255799
Mark Linimon changed:
What|Removed |Added
Assignee|b...@freebsd.org|f...@freebsd.org
--
You are receiv
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=255745
--- Comment #5 from John Grafton ---
The laptop just failed to resume after an uptime of 4 hours.
--
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freeb
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=255685
Kristof Provost changed:
What|Removed |Added
CC||k...@freebsd.org
--- Comment #2
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=236371
Jung-uk Kim changed:
What|Removed |Added
CC||j...@freebsd.org
See Also|
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=255698
--- Comment #5 from Eugene M. Kim ---
Hi Konstantin, thank you for fixing this! I rebuilt my world and the dltest
program now outputs this:
dlerror()=0x8002227f0 ()
dlerror()=0x0
dlopen(/foobar.so, RTLD_NOW)=0x0
dlerror()=0x8002227f0 (Can
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=255698
--- Comment #6 from Eugene M. Kim ---
As for the dlsym() case you asked, I must have been mistaken, because I myself
could not reproduce the case (before the world build). Program used:
#include
#include
#include
#define PRINT_DLERROR
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=255698
--- Comment #7 from Konstantin Belousov ---
The following should fix the initial dlerror() state.
diff --git a/libexec/rtld-elf/rtld_lock.c b/libexec/rtld-elf/rtld_lock.c
index 94e931c2f760..e501c03f0722 100644
--- a/libexec/rtld-elf/rtld_
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=255499
Kirk McKusick changed:
What|Removed |Added
CC||mckus...@freebsd.org
--- Comment #
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=251906
--- Comment #36 from commit-h...@freebsd.org ---
A commit in branch stable/13 references this bug:
URL:
https://cgit.FreeBSD.org/src/commit/?id=6fa8a157705debef78e86de378f8a929207d62dc
commit 6fa8a157705debef78e86de378f8a929207d62dc
Author
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=251906
Robert Wing changed:
What|Removed |Added
Resolution|--- |FIXED
Status|In Progress
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=253483
--- Comment #4 from Graham Perrin ---
There should be a corresponding documentation bug with regard to the misleading
statement at https://www.freebsd.org/where/#choose-image
--
You are receiving this mail because:
You are the assignee fo
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=255616
Robert Wing changed:
What|Removed |Added
CC||r...@freebsd.org
--- Comment #1 from
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=255798
Tatsuki Makino changed:
What|Removed |Added
CC||tatsuki_mak...@hotmail.com
--- Co
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=255685
--- Comment #3 from Pietro Cerutti ---
I was able to fix the connectivity problem between jails (and host) by setting
the jails on a dedicated interface:
## /etc/rc.conf
cloned_interfaces="${cloned_interfaces} lo1"
## /etc/pf.conf
JAIL_IF
33 matches
Mail list logo