https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=275326
--- Comment #5 from yjqg ---
(In reply to yjqg from comment #0)
Due to the attachment filesize exceeding 1000k, failed to attached. Added later
at comment #4 .
--
You are receiving this mail because:
You are the assignee for the b
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=275326
--- Comment #4 from yjqg ---
Created attachment 246557
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=246557&action=edit
stack backtrace.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=275326
--- Comment #3 from yjqg ---
Upgrade Ventoy to the latest version 1.0.96 do not work, the same error.
dd the iso file to a new usb sticker, it boots ok.
Hopefully the iso installer can be used normally in ventoy, so the ventoy
toolbox
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=275326
Mark Linimon changed:
What|Removed |Added
Summary|14.0-RELEASE dvd1-iso |14.0-RELEASE dvd1-iso
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=275326
yjqg changed:
What|Removed |Added
Summary|14.0-RELEASE dvd iso used |14.0-RELEASE dvd1-iso
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=275326
--- Comment #2 from yjqg ---
Ventory 1.0.91 and the partition holding iso files is in exfat.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=275326
--- Comment #1 from yjqg ---
Created attachment 246556
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=246556&action=edit
screen recording.
Add screen recording.
--
You are receiving this mail because:
You are the assignee
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=275322
--- Comment #4 from Konstantin Belousov ---
[Both machines are on several days old stable/14]
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=275322
--- Comment #3 from Konstantin Belousov ---
I cannot reproduce this. For me it looks like this:
Breakpoint 1, main (argc=1, argv=0x7fffe5f8) at pr275322.c:14
14 in pr275322.c
(gdb) c
Continuing.
pid 99860 comm pr275322: signal 5 e
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=275326
Bug ID: 275326
Summary: 14.0-RELEASE dvd iso used in Ventory boot panic.
Product: Base System
Version: 14.0-RELEASE
Hardware: amd64
OS: Any
Status: New
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=275323
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=275323
Mark Linimon changed:
What|Removed |Added
Version|unspecified |14.0-RELEASE
Component|Bug
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=275322
--- Comment #2 from Cheyenne Wills ---
(In reply to Kyle Evans from comment #1)
I might be able to reduce the C code even more if needed.
Some background on how I stumbled on this.
I'm trying to debug some of my code (assembly) that uses
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=275322
Kyle Evans changed:
What|Removed |Added
CC||j...@freebsd.org,
|
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=275322
Bug ID: 275322
Summary: Improper handling of mxcsr register during debug
(gdb/lldb)
Product: Base System
Version: 14.0-RELEASE
Hardware: Any
OS: Any
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=262180
--- Comment #4 from f...@cantconnect.ru ---
(In reply to crest from comment #2)
> Where in your sequence of of commands did you attach to the jail?
"jail" command does this (create+attach).
--
You are receiving this mail because:
You are
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=262180
--- Comment #3 from f...@cantconnect.ru ---
(In reply to Graham Perrin from comment #1)
> Can you reproduce symptoms with a supported RELEASE?
Yes it still works on 14.0-RELEASE.
--
You are receiving this mail because:
You are the assig
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=275273
--- Comment #5 from d...@sunsaturn.com ---
I'm talking about production system running FreeBSD 14-RELEASE.
I just hate to see a sys admin spend hours setting up a system, put all the
notes in /etc/motd to have it all wiped out on him/her.
P
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=271677
Mike Karels changed:
What|Removed |Added
Status|New |Closed
Resolution|---
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=271677
--- Comment #12 from commit-h...@freebsd.org ---
A commit in branch stable/14 references this bug:
URL:
https://cgit.FreeBSD.org/src/commit/?id=3569e21f07147c8dd4bee82e5e7efe69c98edeb1
commit 3569e21f07147c8dd4bee82e5e7efe69c98edeb1
Author
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260841
Yasuhito FUTATSUKI changed:
What|Removed |Added
CC||freebsd-bug-report...@yf.bs
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=271607
Ed Maste changed:
What|Removed |Added
See Also||https://bugs.freebsd.org/bu
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=271607
Bug 271607 depends on bug 274502, which changed state.
Bug 274502 Summary: RELNOTES: document kern.vt.enable_bell=0 by default
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=274502
What|Removed |Added
-
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=275270
Mark Johnston changed:
What|Removed |Added
CC||ma...@freebsd.org
Stat
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=275295
Mark Linimon changed:
What|Removed |Added
Assignee|b...@freebsd.org|emulat...@freebsd.org
--
You are r
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=275048
Mark Johnston changed:
What|Removed |Added
Resolution|--- |FIXED
Status|In Progre
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=275286
Mark Johnston changed:
What|Removed |Added
Assignee|b...@freebsd.org|k...@freebsd.org
Statu
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=275306
Mark Linimon changed:
What|Removed |Added
Assignee|b...@freebsd.org|j...@freebsd.org
--
You are receiv
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=275308
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=275308
Mark Johnston changed:
What|Removed |Added
Status|New |Open
CC|
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=275308
--- Comment #1 from Ed Maste ---
It is possible that setting sysctl vfs.zfs.dmu_offset_next_sync=0 is a
short-term workaround and the fix is in
https://github.com/openzfs/zfs/pull/15571. There should be more clarity over
the next couple of
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=275295
--- Comment #2 from Ed Maste ---
Ah, more extensive change is required, note the XXX comment in
linux_faccessat2:
int
linux_faccessat2(struct thread *td, struct linux_faccessat2_args *args)
{
int flags, unsupported;
/* XXX
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=275295
Ed Maste changed:
What|Removed |Added
CC||ema...@freebsd.org
--- Comment #1 from
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=275308
Bug ID: 275308
Summary: potential ZFS data corruption
Product: Base System
Version: 14.0-RELEASE
Hardware: Any
OS: Any
Status: New
Severity: Affects
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=275306
Bug ID: 275306
Summary: 14.0-RELEASE: starting jail causes panic
Product: Base System
Version: 14.0-RELEASE
Hardware: amd64
OS: Any
Status: New
Seve
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=275273
matthias+freebsd+bugzi...@harz.de changed:
What|Removed |Added
CC||matthias+freebsd
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=275305
Bug ID: 275305
Summary: warning "-Wdeprecated-non-prototype" breaks build a
system with "WITH_OFED_EXTRA" option
Product: Base System
Version: 14.0-STABLE
Hardware: a
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=275296
Bug ID: 275296
Summary: security_daily_compat_var() in periodic.conf still
retained though should have been removed after 11
Product: Base System
Version: 15.0-CURRENT
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=275295
Bug ID: 275295
Summary: Linuxulator: faccessat2 unsupported flag 0x100
Product: Base System
Version: 14.0-STABLE
Hardware: Any
OS: Any
Status: New
S
39 matches
Mail list logo
