[Bug 250770] AWS EC2 system freezes up possibly associated with NFS (EFS)
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=250770 Bug ID: 250770 Summary: AWS EC2 system freezes up possibly associated with NFS (EFS) Product: Base System Version: 12.2-RELEASE Hardware: Any OS: Any Status: New Severity: Affects Some People Priority: --- Component: kern Assignee: b...@freebsd.org Reporter: r...@gusw.net I use light-weight small cloneable FreeBSD systems built from the basic AWS EC2 AMI, first with 12.0-RELEASE and just now re-built with 12.2-RELEASE version. The idea is to have a minimal system rootfs while the bulk of the system disk, the /usr tree, is mounted from EFS (NFSv4). The AMI out of the box for 12.0 required 8 GB system disk, and now for 12.2 it's 10 GB, if I can do it in 1 GB I have some significant cost savings in redundant EBS volumes while also an easier time to distribute application software updates to my worker and server farm. I have described the principle here: https://forums.freebsd.org/threads/amazon-aws-ec2-super-light-configuration.69084/ The problem is that no matter what I do, the system locks up after about 4 hours. And it's not a kernel panic, it's not associated with any error, and I cannot see it at all. Nothing on the console screenshot, nothing in the logs and nothing in the /var/log/messages upon force-stop & re-start. Moreover, AWS EC2 console thinks the system is up in its status check. But any attempt to do anything results in hangs. SSH connection hangs. telnet to port 22, no response at all (not even connection reset, etc.) just hangs. If I happen to be logged in on the system whatever shell command I am doing will just hang, unable to CTRL-C break out nor CTRL-Z to the background. Just hang. So I have nothing to show you. But I can provide anyone who wants to see it with a setup and would appreciate if someone would help out here. Here is my /etc/fstab: # Custom /etc/fstab for FreeBSD VM images /dev/gpt/rootfs /ufs rw 1 1 /dev/gpt/varfs /var ufs rw 1 1 fdesc/dev/fd fdescfs rw 0 0 proc /procprocfs rw 0 0 /usr /.usrnullfs rw 0 0 fs-xx.efs.us-x-x.amazonaws.com:/ /usr nfs rw,nfsv4,minorversion=1,oneopenown,rsize=1048576,wsize=1048576,hard,timeo=600,retrans=2,noresvport,late,bg 0 0 It is freezing up within around 4 hours, even just idling around doing nothing, and it doesn't seem like heavy work activity would accelerate the lock-up situation. Also doesn't depend on which instance type, specifically I have tried t3.nano, t3.micro, c5.large, m5a.large, it happens on all of them about the same time. -- You are receiving this mail because: You are the assignee for the bug. ___ 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"
[Bug 250770] AWS EC2 system freezes up possibly associated with NFS (EFS)
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=250770 Mark Linimon changed: What|Removed |Added CC||cperc...@freebsd.org Assignee|b...@freebsd.org|virtualizat...@freebsd.org -- You are receiving this mail because: You are the assignee for the bug. ___ 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"
[Bug 250755] 12.2-RELEASE i386 GENERIC kernel fails to load
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=250755
Dimitry Andric changed:
What|Removed |Added
CC||arichard...@freebsd.org
--- Comment #4 from Dimitry Andric ---
The bump to i686 was originally committed to head in base r353936, after base
r352030 bumped it to i586 at first. On 2020-01-07, so already 11 months ago,
this was all merged back to stable/12 in base r356460, as part of the clang
9.0.0 merge. Similarly, on 2020-05-05 for stable/11, in base r360658.
In any case, I have tried buiding stable/12 world with base r353936 and base
r352030 reverted, so effectively going back to i486 as default:
Index: contrib/llvm-project/clang/lib/Driver/ToolChains/Arch/X86.cpp
===
--- contrib/llvm-project/clang/lib/Driver/ToolChains/Arch/X86.cpp
(revision 367228)
+++ contrib/llvm-project/clang/lib/Driver/ToolChains/Arch/X86.cpp
(working copy)
@@ -94,7 +94,7 @@
switch (Triple.getOS()) {
case llvm::Triple::FreeBSD:
-return "i686";
+//return "i686"; FALLTHROUGH
case llvm::Triple::NetBSD:
case llvm::Triple::OpenBSD:
return "i486";
However, this leads to a -Werror problem again:
--- atomic.o ---
/usr/src/contrib/llvm-project/compiler-rt/lib/builtins/atomic.c:178:3: error:
large atomic operation may incur significant performance penalty
[-Werror,-Watomic-alignment]
LOCK_FREE_CASES();
^
/usr/src/contrib/llvm-project/compiler-rt/lib/builtins/atomic.c:160:9: note:
expanded from macro 'LOCK_FREE_CASES'
LOCK_FREE_ACTION(uint64_t);
\
^
/usr/src/contrib/llvm-project/compiler-rt/lib/builtins/atomic.c:176:21: note:
expanded from macro 'LOCK_FREE_ACTION'
*((type *)dest) = __c11_atomic_load((_Atomic(type) *)src, model);
\
^
1 error generated.
*** [atomic.o] Error code 1
Originally we have -Wno-atomic-alignment in libcompiler_rt's Makefile, but we
removed it base r364782, because:
> After base r364753, there should be no need to suppress -Watomic-alignment
> warnings anymore for compiler-rt's atomic.c. This occurred because the
> IS_LOCK_FREE_8 macro was not correctly defined to 0 for mips, and this
> caused the compiler to emit a runtime call to __atomic_is_lock_free(),
> and that triggers the warning.
However, the changes in base r364753 are not enough for this particular
warning. Alex, you also worked on these warnings upstream, right? I think we
could probably add __i386__ to the following line in
contrib/llvm-project/compiler-rt/lib/builtins/atomic.c to work around it
(optionally with a check if the target CPU is really < i586):
/// 32 bit MIPS and PowerPC don't support 8-byte lock_free atomics
#if defined(__mips__) || (!defined(__powerpc64__) && defined(__powerpc__))
--
You are receiving this mail because:
You are the assignee for the bug.
___
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"
[Bug 250755] 12.2-RELEASE i386 GENERIC kernel fails to load
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=250755 --- Comment #5 from p5b2e9...@t-online.de --- Meantime I tried this: make buildworld CPUTYPE=i586 and make buildkernel CPUTYPE=i586 both completed. But make installkernel CPUTYPE=i586 failed with *** Signal 4 Any hints please? -- You are receiving this mail because: You are the assignee for the bug. ___ 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"
[Bug 250755] 12.2-RELEASE i386 GENERIC kernel fails to load
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=250755 --- Comment #6 from Konstantin Belousov --- (In reply to Dimitry Andric from comment #4) I was just surprised that this change went into 12.x, at least without loud announcement. More, I suggest to take a look at https://www.freebsd.org/releases/12.2R/relnotes.html 11.1. Default CPUTYPE Change -- You are receiving this mail because: You are the assignee for the bug. ___ 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"
[Bug 249987] Lenovo X120e touchpad failing
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=249987 --- Comment #13 from Jason W. Bacon --- Maybe unrelated, but the X120e has always had an issue with starting the keyboard after cold boot. The keyboard does not respond until about 1 second after the first key is pressed. Any keystrokes entered within that first second are lost. -- You are receiving this mail because: You are the assignee for the bug. ___ 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"
[Bug 250777] Crash outside a Java machine SIGSEGV (0xb) at pc=0x000000080121c49a
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=250777 Bug ID: 250777 Summary: Crash outside a Java machine SIGSEGV (0xb) at pc=0x00080121c49a Product: Base System Version: CURRENT Hardware: amd64 OS: Any Status: New Severity: Affects Only Me Priority: --- Component: misc Assignee: b...@freebsd.org Reporter: bernard.beanco...@lilo.org Attachment #219276 text/plain mime type: Created attachment 219276 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=219276&action=edit error report file (the core dump is too big : 145551360 bytes) In an Oracle VM (VirtualBox 6.1), running FreeBSD13 uname -a FreeBSD freebsd13 13.0-CURRENT FreeBSD 13.0-CURRENT #0 e18fc94e525-c253475(main): Thu Oct 1 06:34:24 UTC 2020 r...@releng1.nyi.freebsd.org:/usr/obj/usr/src/amd64.amd64/sys/GENERIC amd64 zfs -V zfs-2.0.0-rc1_140_gab6a0e236 zfs-kmod-2.0.0-rc1_140_gab6a0e236 # # A fatal error has been detected by the Java Runtime Environment: # # SIGSEGV (0xb) at pc=0x00080121c49a, pid=2984, tid=0x00018726 # # JRE version: OpenJDK Runtime Environment (8.0_272-b10) (build 1.8.0_272-b10) # Java VM: OpenJDK 64-Bit Server VM (25.272-b10 mixed mode bsd-amd64 compressed oops) # Problematic frame: # C [libc.so.7+0x15d49a] unsigned long+0x10a # # Core dump written. Default location: /root/java.core # # An error report file with more information is saved as: # /root/hs_err_pid2984.log # # If you would like to submit a bug report, please visit: # https://bugs.freebsd.org/bugzilla/enter_bug.cgi?product=Ports%20%26%20Packages&component=Individual%20Port(s)&short_desc=java/openjdk8%3A%20 # The crash happened outside the Java Virtual Machine in native code. # See problematic frame for where to report the bug. # Abort (core dumped) -- You are receiving this mail because: You are the assignee for the bug. ___ 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"
[Bug 250777] java/openjdk8: crash outside a Java machine SIGSEGV (0xb) at pc=0x000000080121c49a
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=250777 Mark Linimon changed: What|Removed |Added Flags||maintainer-feedback?(java@F ||reeBSD.org) Summary|Crash outside a Java|java/openjdk8: crash |machine SIGSEGV (0xb) at|outside a Java machine |pc=0x00080121c49a |SIGSEGV (0xb) at ||pc=0x00080121c49a Component|misc|Individual Port(s) Product|Base System |Ports & Packages Assignee|b...@freebsd.org|ports-b...@freebsd.org Version|CURRENT |Latest CC||j...@freebsd.org -- You are receiving this mail because: You are the assignee for the bug. ___ 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"
[Bug 250780] net.pf.request_maxcount doesn't work in loader.conf after upgrade to 12.2
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=250780 Bug ID: 250780 Summary: net.pf.request_maxcount doesn't work in loader.conf after upgrade to 12.2 Product: Base System Version: 12.2-RELEASE Hardware: amd64 OS: Any Status: New Severity: Affects Some People Priority: --- Component: misc Assignee: b...@freebsd.org Reporter: nicola.dellu...@delluomo-morettin.com Hi, after I upgraded from 12.1-RELEASE to 12.2-RELEASE pf stopped working @reboot complaining my tables are > than the limit. In effect, by checking with sysctl, I found out that the custom limit set in /boot/loader.conf is not loaded anymore at reboot, so I fall back to defaults. If I set it manually from command line # sysctl net.pf.request_maxcount=30 # pfctl -f /etc/pf.conf everything works fine. Here's my loader.conf file. security.bsd.allow_destructive_dtrace=0 kern.geom.label.disk_ident.enable="0" kern.geom.label.gptid.enable="0" opensolaris_load="YES" zfs_load="YES" net.pf.request_maxcount=30 machdep.hyperthreading_allowed=0 cpu_microcode_load="YES" cpu_microcode_name="/boot/firmware/intel-ucode.bin" hw.mds_disable=1 -- You are receiving this mail because: You are the assignee for the bug. ___ 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"
[Bug 250780] net.pf.request_maxcount doesn't work in loader.conf after upgrade to 12.2
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=250780 Mark Linimon changed: What|Removed |Added Keywords||regression Assignee|b...@freebsd.org|p...@freebsd.org -- You are receiving this mail because: You are the assignee for the bug. ___ 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"
[Bug 250782] ports(7) manpage: ignored target 'configure' listed
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=250782 Bug ID: 250782 Summary: ports(7) manpage: ignored target 'configure' listed Product: Documentation Version: Latest Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: Manual Pages Assignee: b...@freebsd.org Reporter: tigersha...@gmail.com CC: d...@freebsd.org Under TARGETS, one of those listed no longer does anything, is ignored, and silently fails possibly for backward compatibility or due to an oversight. If not due to oversight the following two lines should be removed. configure Configure the port. Some ports will ask you questions during this stage. See INTERACTIVE and BATCH. In contrast, the TARGET below which does work, may benefit from adding mention of INTERACTIVE and BATCH if in fact there is intended to be no distinction between them other than only this target is functional. config Configure OPTIONS for this port using dialog4ports(1). -- You are receiving this mail because: You are the assignee for the bug. ___ 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"
[Bug 250783] ld segmentation fault
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=250783 Bug ID: 250783 Summary: ld segmentation fault Product: Base System Version: 12.1-STABLE Hardware: amd64 OS: Any Status: New Severity: Affects Some People Priority: --- Component: bin Assignee: b...@freebsd.org Reporter: nij...@gmail.com Attachment #219280 text/plain mime type: Created attachment 219280 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=219280&action=edit Log from failed build ld segfaults when trying to build `maturin` Python package ``` curl -LO https://files.pythonhosted.org/packages/35/e1/d6a9c170f925fb8f4f97d0bed27e2c43a5ba73d7f88a10ed63cd3f8f7968/maturin-0.8.3.tar.gz mkdir maturin cd mautrin tar xf ../maturin-0.8.3.tar.gz cargo rustc --bin maturin --manifest-path Cargo.toml -- -C link-arg=-s ``` ``` (gdb) bt #0 0x00f99607 in operator() () at /usr/src/contrib/llvm/tools/lld/ELF/MarkLive.cpp:207 #1 callback_fn<(lambda at /usr/src/contrib/llvm/tools/lld/ELF/MarkLive.cpp:194:18)>(void) () at /usr/src/contrib/llvm/include/llvm/ADT/STLExtras.h:126 #2 0x00f96363 in forEachSuccessor > () at /usr/src/contrib/llvm/tools/lld/ELF/MarkLive.cpp:97 #3 doGcSections > () at /usr/src/contrib/llvm/tools/lld/ELF/MarkLive.cpp:264 #4 markLive > () at /usr/src/contrib/llvm/tools/lld/ELF/MarkLive.cpp:312 #5 0x00f28de6 in link > () at /usr/src/contrib/llvm/tools/lld/ELF/Driver.cpp:1636 #6 0x00f1ed26 in main () at /usr/src/contrib/llvm/tools/lld/ELF/Driver.cpp:443 #7 0x00f1d619 in link () at /usr/src/contrib/llvm/tools/lld/ELF/Driver.cpp:103 #8 0x0106792b in main () at /usr/src/contrib/llvm/tools/lld/tools/lld/lld.cpp:129 ``` I'm not very well-versed in C++/rust but if I naively replace /usr/bin/ld with /usr/local/bin/ld from gcc9 the build seems to work I'm not sure if a core dump is helpful here, https://files.nickv.me/maturin-ld.lld.core.xz This is on a fresh VM from http://ftp.freebsd.org/pub/FreeBSD/snapshots/VM-IMAGES/ (with git, gcc9, rust, and python38) -- You are receiving this mail because: You are the assignee for the bug. ___ 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"
[Bug 250783] ld segmentation fault
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=250783 --- Comment #1 from Nick Venenga --- Here is a related conversation https://github.com/PyO3/maturin/issues/363 -- You are receiving this mail because: You are the assignee for the bug. ___ 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"
[Bug 250782] ports(7) manpage: ignored target 'configure' listed
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=250782 Mateusz Piotrowski <0...@freebsd.org> changed: What|Removed |Added CC||0...@freebsd.org Resolution|--- |Works As Intended Status|New |Closed --- Comment #1 from Mateusz Piotrowski <0...@freebsd.org> --- The configure target and the config target are not the same. Configure is for running "./configure" in as a part of the building process, while config is for selecting port options. It is true that the configure target is a no-op sometimes. Please look for HAS_CONFIGURE and GNU_CONFIGURE variables in the documentation. Cheers! -- You are receiving this mail because: You are the assignee for the bug. ___ 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"
[Bug 250784] integer divide fault in zfs_rmnode
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=250784 Bug ID: 250784 Summary: integer divide fault in zfs_rmnode Product: Base System Version: 12.2-RELEASE Hardware: amd64 OS: Any Status: New Severity: Affects Only Me Priority: --- Component: kern Assignee: b...@freebsd.org Reporter: stevenschlans...@gmail.com I recently upgraded to FreeBSD 12.2-RELEASE r366954 GENERIC amd64 and run plexmediaserver-plexpass-1.20.3.3483 Now I consistently receive a kernel panic soon after boot: Fatal trap 18: integer divide fault while in kernel mode cpuid = 11; apic id = 0b instruction pointer = 0x20:0x82963725 stack pointer = 0x28:0xfe009f78d480 frame pointer = 0x28:0xfe009f78d510 code segment= base 0x0, limit 0xf, type 0x1b = DPL 0, pres 1, long 1, def32 0, gran 1 processor eflags= interrupt enabled, resume, IOPL = 0 current process = 2247 (Plex Media Server) trap number = 18 panic: integer divide fault cpuid = 11 time = 1604252527 KDB: stack backtrace: #0 0x80c0a8f5 at kdb_backtrace+0x65 #1 0x80bbeb1b at vpanic+0x17b #2 0x80bbe993 at panic+0x43 #3 0x8108f911 at trap_fatal+0x391 #4 0x8108ed97 at trap+0x67 #5 0x81066f38 at calltrap+0x8 #6 0x82a148ce at zfs_rmnode+0x5e #7 0x82a35612 at zfs_freebsd_reclaim+0x42 #8 0x812482db at VOP_RECLAIM_APV+0x7b #9 0x80c8e376 at vgonel+0x216 #10 0x80c8e9c5 at vrecycle+0x45 #11 0x82a355bd at zfs_freebsd_inactive+0xd #12 0x812481ab at VOP_INACTIVE_APV+0x7b #13 0x80c8d0b0 at vinactive+0xf0 #14 0x80c8d5c8 at vputx+0x2b8 #15 0x80c9722c at kern_unlinkat+0x20c #16 0x810904c7 at amd64_syscall+0x387 #17 0x8106785e at fast_syscall_common+0xf8 Uptime: 1m27s I am not clear exactly which file is unlinked. Thank you for any assistance in resolving this situation, and let me know if I can provide additional information. -- You are receiving this mail because: You are the assignee for the bug. ___ 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"
[Bug 250711] atkbdc: No Keyboard on System76 lemur Pro laptop with 12.1 (11.4 Ok)
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=250711 --- Comment #11 from Vladimir Kondratyev --- FYI. If drm-kmod on 12-stable supports video card located on your laptop, you may want to add CometLake PCI IDs to I2C driver to get touchpad working under X. See r367230 (https://svnweb.freebsd.org/base?view=revision&revision=367230). Or wait for couple of weeks for MFC. If STABLE's drm-kmod version (4.16) is too old, then only choice is install current (or use scfb driver which does not support any acceleration) -- You are receiving this mail because: You are the assignee for the bug. ___ 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"
Problem reports for b...@freebsd.org that need special attention
To view an individual PR, use: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id). The following is a listing of current problems submitted by FreeBSD users, which need special attention. These represent problem reports covering all versions including experimental development code and obsolete releases. Status |Bug Id | Description +---+--- New |197876 | [devfs] an error in devfs leads to data loss and New |198797 | [PATCH] Added an option to install BSDstats to bs New |202362 | ntp: restore refclocks selection (10.2-RELEASE re New |202740 | vi/ex string substitution problem when there is m New |204097 | witness_initialize() does not perform bound check New |206336 | [patch] usr.sbin/freebsd-update allow proxy confi New |209213 | UEFI Loader shows only black screen with Nvidia G New |210804 | installerconfig - using ZFS create in custom scri New |223470 | freebsd-update: Cannot identify running kernel (/ New |230620 | "install -d" issue New |235085 | [PATCH] Option to make rc.d/sysctl more verbose ( Open| 71667 | [patch] cleanup of the usr.sbin/bootparamd code Open|182466 | [headers] [patch] make self-contained Open|183618 | [panic] Dell PowerEdge R620 -- PERC H710 Mini (mf Open|187015 | agpgart: Panic make_dev_credv: bad si_name (error Open|192573 | Add ps(1) option: Print process start time in sec Open|194925 | [pf] [ifconfig] interface group keywords do not w Open|197921 | scheduler: Allow non-migratable threads to bind t Open|206528 | Emulex LPe 16002 FC HBA Not Recognized by oce(4) Open|206649 | cyapa(4): Add common gestures for Cypress APA I2C Open|207248 | [patch] daemon(8): Add option to redirect stdout Open|207940 | stand/efi/boot1: Add boot partition selection Open|212608 | sockstat(1) and lsof(8) can not identity the owne Open|220246 | syslogd does not send RFC3164-conformant messages Open|221305 | Mouse cursor loss when moving cursor while loadin Open|221550 | kern.bootfile returns only /kernel on mips64 (ERL Open|221854 | makefs: Reject UFS labels that are too long to fi Open|222632 | connect(2) not available in capability mode Open|226893 | freebsd-update: Support patchlevel argument for f Open|231810 | [build] release always fails with "mkimg: partiti Open|233578 | Unprivileged local user can prevent other users l Open|233988 | freebsd-update: Improve progress output on termin Open|236718 | system panics with message: vm_fault_hold: fault Open|237287 | moused(8) ignores button release events in virtua Open|237924 | Possible infinite loop in function empty_aux_buff Open|237981 | cxgb(4): Driver doesn't work with latest (7.12) C Open|238183 | cam/scsi/scsi_sa.c: warnings issued by static ana Open|238486 | Possible buffer overflow bug in sc_allocate_keybo Open|238550 | Touchpad (via SMBus) not working: Synaptics (SYN1 Open|238638 | mfi: Remove unnecessary pointer printing in mfi.c Open|238837 | init: Remove P_SYSTEM flag from PID 1 to allow ea Open|241697 | i915kms: Kernel panic loading module on custom ke Open|242212 | usr.sbin/mergemaster/mergemaster.sh: There is no Open|244181 | unzip: Add passphrase and GLIBC build support Open|244838 | "bectl activate -t" does not honor the -t flag in Open|247132 | Fix build error: use of undeclared identifier 'cp Open|247301 | linuxkpi: panic: Assertion td->td_lkpi_task == NU Open|248352 | mfi(4): Remove RAID map sync functionality Open|248715 | dhclient: prepend domain-name-servers in dhclient 49 problems total for which you should take action. ___ 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"
[Bug 250783] ld segmentation fault
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=250783 Mark Linimon changed: What|Removed |Added Assignee|b...@freebsd.org|toolch...@freebsd.org -- You are receiving this mail because: You are the assignee for the bug. ___ 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"
[Bug 250784] integer divide fault in zfs_rmnode
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=250784 Mark Linimon changed: What|Removed |Added Assignee|b...@freebsd.org|f...@freebsd.org Keywords||panic, regression -- You are receiving this mail because: You are the assignee for the bug. ___ 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"
[Bug 250790] Kontol
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=250790 Bug ID: 250790 Summary: Kontol Product: Base System Version: 12.1-STABLE Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: gnu Assignee: b...@freebsd.org Reporter: ersonaggr...@gmail.com Attachment #219286 text/plain mime type: Created attachment 219286 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=219286&action=edit Kontol Xix -- You are receiving this mail because: You are the assignee for the bug. ___ 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"
[Bug 250790] Kontol
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=250790 Li-Wen Hsu changed: What|Removed |Added Status|New |Closed Component|gnu |Spam Assignee|b...@freebsd.org|bugmeis...@freebsd.org CC||lw...@freebsd.org Product|Base System |Other Resolution|--- |Not A Bug Version|12.1-STABLE |unspecified -- You are receiving this mail because: You are the assignee for the bug. ___ 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"
[Bug 250769] Freebsd kernel panic after upgrade to 12.2R when loading amdgpu
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=250769 Li-Wen Hsu changed: What|Removed |Added CC||lw...@freebsd.org See Also||https://bugs.freebsd.org/bu ||gzilla/show_bug.cgi?id=2507 ||00 Assignee|b...@freebsd.org|x...@freebsd.org Status|New |Open --- Comment #2 from Li-Wen Hsu --- Does build drm-kmod from ports help? Please refer to bug 250700 (comment #1) for more information. -- You are receiving this mail because: You are the assignee for the bug. ___ 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"
Научные публикации
___ 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"
[Bug 250580] VMware UEFI guests crash in virtual hardware after r366691
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=250580 hehon...@mail.com changed: What|Removed |Added CC||hehon...@mail.com --- Comment #5 from hehon...@mail.com --- Yes, this bug is not AMD-specific. I'm running FreeBSD 12.1 on an ESXi Server with an Intel Xeon E3-1230v3 CPU and after upgrading to 12.2 it failed to boot. Also, another virtual machine which is a FreeNAS 11.3 also breaks after upgrading to TrueNAS 12, which under the hood is also FreeBSD 12.2. Recently I found I can boot these 2 virtual machines by entering the EFI shell of VMware UEFI firmware before booting FreeBSD, just: i. Power ON the VM and immediately press the ESC button. ii. On the boot menu screen of VMware VM's firmware, press the arrow key to select "EFI Internal Shell (Unsupported option)" and press enter to confirm. iii. After seeing "Press ESC in 5 seconds to skip startup.nsh, any other key to continue." press a key other than ESC or just wait for the countdown. iv. Continue to boot FreeBSD as normal. May this detail helps to investigate the issue. -- You are receiving this mail because: You are the assignee for the bug. ___ 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"
