https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=231195
patrice lab changed:
What|Removed |Added
Summary|unable to upgrade to|unable to freebsd-update to
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=231080
--- Comment #8 from Lawrence Stewart ---
I believe I may have hit this too the other day on a big iron server at $work
running GENERIC-NODEBUG r338290.
% sudo kgdb /boot/kernel/kernel /var/crash/vmcore.0
GNU gdb (GDB) 8.1.1 [GDB v8.1.1 fo
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=231212
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=231211
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=231212
Bug ID: 231212
Summary: `zfs destroy` a jail running buildworld causes
"ranlib: fatal: Failed to open 'libXXX.a'"
Product: Base System
Version: CURRENT
Hardware: Any
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=231211
Bug ID: 231211
Summary: [zfs] possible deadlock triggered by zfs test suite
Product: Base System
Version: CURRENT
Hardware: Any
OS: Any
Status: New
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=228448
Ed Maste changed:
What|Removed |Added
CC||ema...@freebsd.org
--- Comment #1 from
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=231193
Ian Lepore changed:
What|Removed |Added
Assignee|b...@freebsd.org|i...@freebsd.org
Status|N
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203349
Bug 203349 depends on bug 209072, which changed state.
Bug 209072 Summary: ACPI is disabled on arm64
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=209072
What|Removed |Added
---
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=231192
Mark Linimon changed:
What|Removed |Added
Assignee|b...@freebsd.org|n...@freebsd.org
Keywords
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=231193
Mark Linimon changed:
What|Removed |Added
CC||i...@freebsd.org
--- Comment #1 fro
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=231064
--- Comment #5 from Mark Johnston ---
It seems that the issue is really just that the EFI framebuffer is included as
ConventionalMemory in the EFI map. It seems to be excluded from the map on the
x86 EFI systems that I can easily check. A
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=231064
Mark Johnston changed:
What|Removed |Added
Assignee|b...@freebsd.org|ma...@freebsd.org
--
You are rece
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=231064
--- Comment #4 from Mark Johnston ---
(In reply to Andrew Turner from comment #3)
Indeed, that works around the panic. (I actually had to bump MAX_EXCNT for
this to work.) I'm not sure how best to handle this for 12.0 though.
--
You are
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=231080
--- Comment #7 from Sean Bruno ---
I've dropped the crashdump + kernel in my homedir on
freefall:~sbruno/igw0_crash.tgz
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=231080
Mark Johnston changed:
What|Removed |Added
CC||ma...@freebsd.org
Keywor
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=231190
--- Comment #3 from todd ---
Thank you very much, That seems to have deleted the file.. I never realized you
could force null args..
Cheers
--
You are receiving this mail because:
You are the assignee for the bug.
___
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=231080
--- Comment #6 from Sean Bruno ---
Created attachment 196917
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=196917&action=edit
Crash summary from igw0 (another Atom server) in the freebsd cluster
--
You are receiving this mail
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=231080
--- Comment #5 from Sean Bruno ---
Created attachment 196916
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=196916&action=edit
dmesg from atom servers that seem to be more likely to fall down
--
You are receiving this mail beca
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=231080
--- Comment #4 from Sean Bruno ---
I've had this happen at least 2 more times on these lower end machine (atom
class) in the freebsd cluster. This happens at svn 338340 but does not happen
at svn 88. That's not really "helpful" here,
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=231190
Conrad Meyer changed:
What|Removed |Added
CC||c...@freebsd.org
--- Comment #2 fro
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=231195
Bug ID: 231195
Summary: unable to upgrade to 11.1-RELEASE since june or august
Product: Base System
Version: 11.1-RELEASE
Hardware: Any
OS: Any
Status: New
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=231064
--- Comment #3 from Andrew Turner ---
You can try excluding that physical memory from the map by calling
arm_physmem_exclude_region from initarm. It takes the start address, length,
and the EXFLAG_NOALLOC flag, e.g. arm_physmem_exclude_regi
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=231193
Bug ID: 231193
Summary: ntpd peers stuck in INIT status when using local named
Product: Base System
Version: 11.2-RELEASE
Hardware: Any
OS: Any
Status: New
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=231192
Bug ID: 231192
Summary: cxl: nic does not work after reboot
Product: Base System
Version: 11.2-RELEASE
Hardware: Any
OS: Any
Status: New
Severity: A
25 matches
Mail list logo
