[Bug 235107] 'make buildworld' of 12.0-RELEASE sources fails in special circumstances
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=235107 --- Comment #15 from o...@oz42.eu --- I could perhaps want to enable a disabled feature again. But this is not the problem. The point is that 'make buildworld' even bootstraps its own compiler when necessary, but still depends on files outside of /usr/src that exist in /usr/src. *.h and lib* files for example. -- 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 231760] FreeBSD 12.0-ALPHA7 Installations Halts at ACPI on 4 different AMD Ryzen Laptops (HP, DELL, Huawei)
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=231760 --- Comment #10 from Rajesh --- (In reply to John Baldwin from comment #9) Hi John, Sorry for the delayed response. Please find the backtrace below when the BAR (0x24) is read pci_cfgregread: amd64 pci4.0.2 reg 0x24 bytes 0x1 pciereg_cfgread: pci4.0.2 reg 0x24 bytes 0x1 KDB: stack backtrace: db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame 0x826653f0 pciereg_cfgread() at pciereg_cfgread+0x5e/frame 0x82665430 AcpiOsReadPciConfiguration() at AcpiOsReadPciConfiguration+0x49/frame 0x82665460 AcpiEvAddressSpaceDispatch() at AcpiEvAddressSpaceDispatch+0x1f5/frame 0x826654d0 AcpiExAccessRegion() at AcpiExAccessRegion+0xa3/frame 0x82665520 AcpiExFieldDatumIo() at AcpiExFieldDatumIo+0xfb/frame 0x82665560 AcpiExExtractFromField() at AcpiExExtractFromField+0xe0/frame 0x826655d0 AcpiExReadDataFromField() at AcpiExReadDataFromField+0x125/frame 0x82665610 AcpiExResolveNodeToValue() at AcpiExResolveNodeToValue+0xe7/frame 0x82665660 AcpiExResolveToValue() at AcpiExResolveToValue+0x1d1/frame 0x826656a0 AcpiDsEvaluateNamePath() at AcpiDsEvaluateNamePath+0x78/frame 0x826656e0 AcpiDsExecEndOp() at AcpiDsExecEndOp+0x99/frame 0x82665720 AcpiPsParseLoop() at AcpiPsParseLoop+0x732/frame 0x826657a0 AcpiPsParseAml() at AcpiPsParseAml+0x80/frame 0x826657e0 AcpiPsExecuteMethod() at AcpiPsExecuteMethod+0x13c/frame 0x82665820 AcpiNsEvaluate() at AcpiNsEvaluate+0x1e7/frame 0x82665860 AcpiNsInitOneDevice() at AcpiNsInitOneDevice+0xe7/frame 0x82665890 AcpiNsWalkNamespace() at AcpiNsWalkNamespace+0xc3/frame 0x826658f0 AcpiNsInitializeDevices() at AcpiNsInitializeDevices+0x63/frame 0x82665950 AcpiInitializeObjects() at AcpiInitializeObjects+0x27/frame 0x82665970 acpi_attach() at acpi_attach+0x3d3/frame 0x82665a10 device_attach() at device_attach+0x3ec/frame 0x82665a60 bus_generic_attach() at bus_generic_attach+0x5c/frame 0x82665a90 device_attach() at device_attach+0x3ec/frame 0x82665ae0 bus_generic_new_pass() at bus_generic_new_pass+0x118/frame 0x82665b10 root_bus_configure() at root_bus_configure+0x77/frame 0x82665b40 configure() at configure+0x9/frame 0x82665b50 mi_startup() at mi_startup+0x118/frame 0x82665b70 btext() at btext+0x2c I am not able to get the acpidump properly. When I run "acpidump -t -d", it prints certain details in stdout and then hangs. Is there any known behavior like this with acpidump? -- 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 235831] [FEATURE REQUEST] [ZFS] Option to **non-destructively** import ZFS pool at checkpoint (i.e., keep the checkpoint)
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=235831 Bug ID: 235831 Summary: [FEATURE REQUEST] [ZFS] Option to **non-destructively** import ZFS pool at checkpoint (i.e., keep the checkpoint) Product: Base System Version: 11.2-RELEASE Hardware: Any OS: Any Status: New Severity: Affects Some People Priority: --- Component: kern Assignee: b...@freebsd.org Reporter: stil...@gmail.com The ZPOOL feature "zpool import --rewind-to-checkpoint POOLNAME" was recently added - thank you! But there's a slight omission which I hope is easy to add. Rewinding to a checkpoint is always a destructive act - the checkpoint is destroyed by the "import --rewind-to-checkpoint" command. If testing, it is extremely useful to [create checkpoint -> test -> rewind -> test -> rewind] multiple times, to compare the behaviour with different options. At present one has to re-checkpoint, but the recheckpoint loses the date. FEATURE REQUEST Is it possible to add a variant "--rewind-to-checkpoint-no-discard" or "--rewind-to-checkpoint -k" (for keep), that simply skips the call to destroy the checkpoint, after rewind + import has completed? EFFECT: It's possible to rewind to a checkpoint **without** destroying the checkpoint in the process. Thanks -- 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 223829] ZFS zpool status -D missing documentation in manpage
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=223829 Oleksandr Tymoshenko changed: What|Removed |Added Assignee|d...@freebsd.org |b...@freebsd.org CC||d...@freebsd.org Component|Documentation |Manual Pages Stilez changed: What|Removed |Added CC||stil...@gmail.com -- 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 235832] [FEATURE REQUEST] [ZFS] Add "-r" (recursive) option to zfs diff
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=235832 Bug ID: 235832 Summary: [FEATURE REQUEST] [ZFS] Add "-r" (recursive) option to zfs diff Product: Base System Version: 11.2-RELEASE Hardware: Any OS: Any Status: New Severity: Affects Many People Priority: --- Component: kern Assignee: b...@freebsd.org Reporter: stil...@gmail.com Imagine a zfs dataset (pool/mydata) with nested datasets (pool/mydata/subdataNNN). At present one can "snapshot -r pool/mydata" and it'l also snapshot all nested datasets, and I imagine most users with nested datasets would do this. But to check if anything has changed between snapshots, one cannot do "zfs diff -r pool/mydata". The option is missing. One has to diff each sub-dataset individually, which isn't intuitive or helpful. Could -r be added to zfs diff? -- 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 189827] [patch] sed(1) treats some absolute addr2 of `N' command as relative
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=189827 --- Comment #2 from hiroto.kagot...@gmail.com --- This problem was fixed by base r269302. Thanks and please close this PR. -- 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 189827] [patch] sed(1) treats some absolute addr2 of `N' command as relative
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=189827 Oleksandr Tymoshenko changed: What|Removed |Added Status|Open|Closed CC||go...@freebsd.org Resolution|--- |FIXED -- 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 235832] Add "-r" (recursive) option to zfs diff
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=235832 Kubilay Kocak changed: What|Removed |Added Severity|Affects Many People |Affects Some People Status|New |Open Keywords||feature, needs-patch Summary|[FEATURE REQUEST] [ZFS] Add |Add "-r" (recursive) option |"-r" (recursive) option to |to zfs diff |zfs diff| -- 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 230172] FreeBSD 11.2 fails to boot on Celeron J1900 after upgrade from 11.1
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230172 --- Comment #31 from j...@transactionware.com --- Some notes when 'vt' is used (some of this also in comments above): * Console output stops when the kernel starts booting. * If the boot is allowed to complete it is available via ssh. * /dev/ttyv* device entries are not present. * Loading /boot/modules/i915kms.ko makes the device entries appear and console output resumes. In my case this is on FreeBSD 12-p3 with port graphics/drm-fbsd12-kmod. * "kill -HUP 1" restarts getty processes and the console becomes usable. * If /boot/modules/i915kms.ko is loaded via kld_list in /etc/rc.conf, console output will resume once the module is loaded and the ttyv* getty processes will start correctly. -- 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 235792] cron(8) does not respect login.conf environment vars
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=235792 --- Comment #3 from Bob Bishop --- (In reply to andrew from comment #2) I've been around the block a few times also :-) I'm content to disagree on this, let's see what other people think. -- 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 235635] vt video corruption when switching from xserver to tty
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=235635 --- Comment #2 from Damien --- Additional Information: I can confirm that this only occurs when switching from X server to tty without shutting down X first. If X server is shut down, when the switch to the tty occurs, any corruption is now gone. Also, if the corruption persists due to X server being shut down forceably i.e. through kill etc., restarting X and then shutting it down gracefully prevents the corruption from being displayed when it X server terminates. It should be noted that no corruption is ever seen when the tty is switched to the active X server. -- 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 155439] [libkvm] [patch] Spurious error message kvm_nlist: No such file or directory
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=155439 longw...@incore.de changed: What|Removed |Added CC||longw...@incore.de Status|Open|Closed Resolution|--- |Overcome By Events -- 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 155441] [loader] [patch] Firewire support in loader is broken
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=155441 longw...@incore.de changed: What|Removed |Added CC||longw...@incore.de --- Comment #5 from longw...@incore.de --- The commit 342865 includes the first part of the original patch. Please can somebody explain whether something is wrong with the second part of the patch. -- 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 184691] [patch] getty(8): remove leftovers from COMPAT_43 removal, sync man page
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=184691 --- Comment #3 from Edward Tomasz Napierala --- The C parts might be committed; the reason I hadn't done so is that the way is structured, there's a bunch of hardcoded offsets, and I'd need to take a really close look to make sure they match. And we don't really gain much by committing it - as the PR says, it's just leftovers that don't hurt. -- 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 230172] FreeBSD 11.2 fails to boot on Celeron J1900 after upgrade from 11.1
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230172 --- Comment #32 from j...@transactionware.com --- My comments above were on a Tipro J1900 based touch screen system. I have also tested on a SuperMicro X10SBA; there the system hangs when loading i915kms.ko, and requires a power cycle. -- 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 230755] natd sends wrong sequence number when a retransmitted PASV packet comes in
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230755 Andrey V. Elsukov changed: What|Removed |Added CC||a...@freebsd.org, ||eu...@freebsd.org Assignee|b...@freebsd.org|i...@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 102834] [patch] mail(1) hangs on the sigsuspend system call in popen.c
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=102834 --- Comment #14 from longw...@incore.de --- The problem in this PR is the fact that in the functions wait_child() and free_child() of source popen.c the call of findchild() must be done after the call of the sigfunctions. For wait_child() this was solved with commit 236286. For free_child() this was solved together with some other changes in STABLE 10 and 11 but reverted because of another problem reported in PR 230196. For Stable 11 the following patch would be enough to close this PR: --- popen.c.orig2019-02-18 19:07:59.043267000 +0100 +++ popen.c 2019-02-18 19:09:25.226232000 +0100 @@ -359,12 +359,14 @@ free_child(int pid) { sigset_t nset, oset; - struct child *cp = findchild(pid); + struct child *cp; (void)sigemptyset(&nset); (void)sigaddset(&nset, SIGCHLD); (void)sigprocmask(SIG_BLOCK, &nset, &oset); + cp = findchild(pid); + if (cp->done) delchild(cp); else -- 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 103682] [patch] [request] nfsstat(1) should use %u instead of %d to display NFS stats
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=103682 Oleksandr Tymoshenko changed: What|Removed |Added Status|Open|Closed Resolution|--- |FIXED CC||go...@freebsd.org --- Comment #6 from Oleksandr Tymoshenko --- This was fixed in r304058 -- 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 235846] panic: pmap_demote_pde: firstpte and newpte map different physical addresses
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=235846 Bug ID: 235846 Summary: panic: pmap_demote_pde: firstpte and newpte map different physical addresses Product: Base System Version: CURRENT Hardware: Any OS: Any Status: New Keywords: panic, stress2 Severity: Affects Only Me Priority: --- Component: kern Assignee: b...@freebsd.org Reporter: p...@freebsd.org With FreeBSD 13.0-CURRENT #0 r344247: Mon Feb 18 07:56:47 CET 2019 I got: 20190218 18:41:14 all (127/614): callout_reset_on.sh panic: pmap_demote_pde: firstpte and newpte map different physical addresses cpuid = 9 time = 1550511727 KDB: stack backtrace: db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame 0xfe0182bcb460 vpanic() at vpanic+0x1b4/frame 0xfe0182bcb4c0 panic() at panic+0x43/frame 0xfe0182bcb520 pmap_demote_pde_locked() at pmap_demote_pde_locked+0xd4a/frame 0xfe0182bcb5d0 pmap_remove() at pmap_remove+0x457/frame 0xfe0182bcb640 vm_map_delete() at vm_map_delete+0x321/frame 0xfe0182bcb6b0 vm_map_remove() at vm_map_remove+0x81/frame 0xfe0182bcb6e0 pipeclose() at pipeclose+0x2e1/frame 0xfe0182bcb720 pipe_close() at pipe_close+0x60/frame 0xfe0182bcb750 _fdrop() at _fdrop+0x1a/frame 0xfe0182bcb770 closef() at closef+0x1ec/frame 0xfe0182bcb800 fdescfree_fds() at fdescfree_fds+0x8c/frame 0xfe0182bcb850 fdescfree() at fdescfree+0x39e/frame 0xfe0182bcb910 exit1() at exit1+0x4fe/frame 0xfe0182bcb980 sys_sys_exit() at sys_sys_exit+0xd/frame 0xfe0182bcb990 amd64_syscall() at amd64_syscall+0x291/frame 0xfe0182bcbab0 https://people.freebsd.org/~pho/stress/log/mark080.txt -- 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 235831] [FEATURE REQUEST] [ZFS] Option to **non-destructively** import ZFS pool at checkpoint (i.e., keep the checkpoint)
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=235831 Mark Linimon changed: What|Removed |Added Assignee|b...@freebsd.org|f...@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 235832] Add "-r" (recursive) option to zfs diff
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=235832 Mark Linimon changed: What|Removed |Added Assignee|b...@freebsd.org|f...@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 235015] unused variable shmsegptr in kern_shmdt_locked()
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=235015 Trev changed: What|Removed |Added CC|fbsdbu...@sentry.org| --- Comment #1 from Trev --- Just bitten by this bug myself in 12.0-R while making a custom kernel. -- 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 235846] panic: pmap_demote_pde: firstpte and newpte map different physical addresses
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=235846 --- Comment #1 from Mark Johnston --- Could you post the vmcore for this one? -- 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 235850] bectl(8): create should mention it creates from booted system without any other argument
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=235850 Bug ID: 235850 Summary: bectl(8): create should mention it creates from booted system without any other argument Product: Documentation Version: Latest Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: Manual Pages Assignee: b...@freebsd.org Reporter: l...@freebsd.org CC: d...@freebsd.org The bectl(8) manpage under the create option should echo the libbe(3) be_create wording to say that it populates the BE from the running system if no other arguments are given. It will be created from a snapshot of the currently booted boot environ- ment. -- 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 235846] panic: pmap_demote_pde: firstpte and newpte map different physical addresses
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=235846 --- Comment #2 from Peter Holm --- (In reply to Mark Johnston from comment #1) Sure. https://people.freebsd.org/~pho/kernel+vmcore.19.r344247.mercat1.txz -- 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 235852] panic: handle_written_filepage: not started
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=235852 Bug ID: 235852 Summary: panic: handle_written_filepage: not started Product: Base System Version: CURRENT Hardware: Any OS: Any Status: New Keywords: panic, stress2 Severity: Affects Only Me Priority: --- Component: kern Assignee: b...@freebsd.org Reporter: p...@freebsd.org This is a *very* old problem. The test scenario is FFS snapshot: 20190218 23:05:29 all (1/1): pageout.sh panic: handle_written_filepage: not started cpuid = 3 time = 1550527654 KDB: stack backtrace: db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame 0xfe00aa9482d0 vpanic() at vpanic+0x1b4/frame 0xfe00aa948330 panic() at panic+0x43/frame 0xfe00aa948390 handle_written_filepage() at handle_written_filepage+0x3e/frame 0xfe00aa948400 softdep_disk_write_complete() at softdep_disk_write_complete+0xdd/frame 0xfe00aa9484a0 bufdone() at bufdone+0x3bb/frame 0xfe00aa948520 ufs_strategy() at ufs_strategy+0x83/frame 0xfe00aa948550 VOP_STRATEGY_APV() at VOP_STRATEGY_APV+0x90/frame 0xfe00aa948570 bufstrategy() at bufstrategy+0x44/frame 0xfe00aa9485a0 bufwrite() at bufwrite+0x249/frame 0xfe00aa9485f0 ffs_syncvnode() at ffs_syncvnode+0x2ae/frame 0xfe00aa948670 ffs_fsync() at ffs_fsync+0x22/frame 0xfe00aa9486b0 VOP_FSYNC_APV() at VOP_FSYNC_APV+0x88/frame 0xfe00aa9486d0 ufs_remove() at ufs_remove+0xdf/frame 0xfe00aa948730 VOP_REMOVE_APV() at VOP_REMOVE_APV+0xac/frame 0xfe00aa948750 kern_unlinkat() at kern_unlinkat+0x1e7/frame 0xfe00aa948990 amd64_syscall() at amd64_syscall+0x291/frame 0xfe00aa948ab0 https://people.freebsd.org/~pho/stress/log/pageout-4.txt https://people.freebsd.org/~pho/kernel+vmcore.20.r344247.mercat1.txz -- 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 235853] Add danish translation to INDEX.keymaps/INDEX.fonts
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=235853 Bug ID: 235853 Summary: Add danish translation to INDEX.keymaps/INDEX.fonts Product: Base System Version: CURRENT Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: conf Assignee: b...@freebsd.org Reporter: scootergri...@gmail.com Created attachment 202152 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=202152&action=edit Danish translation for INDEX.keymaps/INDEX.fonts Me trying to add danish translation to these files: share/syscons/fonts/INDEX.fonts share/syscons/keymaps/INDEX.keymaps share/vt/fonts/INDEX.fonts share/vt/keymaps/INDEX.keymaps I also removed some trailing spaces and moved a few lines so its more in order. -- 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"