[Bug 244852] Crash in sysctl(3) after call to "sysctl -a | grep ..."
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=244852 Juraj Lutter changed: What|Removed |Added Resolution|--- |Unable to Reproduce Status|New |Closed --- Comment #3 from Juraj Lutter --- Unable to reproduce, closing this ticket. Should this reoccur with 11.4, we can investigate further. -- 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 203349] [META] FreeBSD Foundation sponsored project dependencies for FreeBSD 11.x
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203349 Ed Maste changed: What|Removed |Added Depends on|191607, 194641, 201052, | |201763 | Referenced Bugs: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=191607 [Bug 191607] Inconsistent documentation on entering the debugger https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=194641 [Bug 194641] [EFI] boot/loader.efi: miscompilation on Intel Haswell with AVX2 and CPUTYPE=native https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=201052 [Bug 201052] capsicum: propagate rights on sctp_peeloff https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=201763 [Bug 201763] Tracking bug for AArch64 port build failures -- 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 194641] [EFI] boot/loader.efi: miscompilation on Intel Haswell with AVX2 and CPUTYPE=native
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=194641 Ed Maste changed: What|Removed |Added Blocks|203349 | Referenced Bugs: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203349 [Bug 203349] [META] FreeBSD Foundation sponsored project dependencies for FreeBSD 11.x -- 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 201052] capsicum: propagate rights on sctp_peeloff
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=201052 Ed Maste changed: What|Removed |Added Blocks|203349 | Referenced Bugs: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203349 [Bug 203349] [META] FreeBSD Foundation sponsored project dependencies for FreeBSD 11.x -- 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 231027] [META] FreeBSD-Foundation sponsored issues for FreeBSD 13-CURRENT
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=231027 Ed Maste changed: What|Removed |Added Depends on||194641 Referenced Bugs: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=194641 [Bug 194641] [EFI] boot/loader.efi: miscompilation on Intel Haswell with AVX2 and CPUTYPE=native -- 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 194641] [EFI] boot/loader.efi: miscompilation on Intel Haswell with AVX2 and CPUTYPE=native
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=194641 Ed Maste changed: What|Removed |Added Blocks||231027 Referenced Bugs: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=231027 [Bug 231027] [META] FreeBSD-Foundation sponsored issues for FreeBSD 13-CURRENT -- 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 246630] stable/11 regression: base.txz reproducibility depends on number of cpu cores
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=246630 --- Comment #35 from commit-h...@freebsd.org --- A commit references this bug: Author: dim Date: Thu Jun 18 20:41:44 UTC 2020 New revision: 362341 URL: https://svnweb.freebsd.org/changeset/base/362341 Log: Merge commit 0cecafd647cc from llvm git (by Alina Sbirlea): [BasicAA] Make BasicAA a cfg pass. Summary: Part of the changes in D44564 made BasicAA not CFG only due to it using PhiAnalysisValues which may have values invalidated. Subsequent patches (rL340613) appear to have addressed this limitation. BasicAA should not be invalidated by non-CFG-altering passes. A concrete example is MemCpyOpt which preserves CFG, but we are testing it invalidates BasicAA. llvm-dev RFC: https://groups.google.com/forum/#!topic/llvm-dev/eSPXuWnNfzM Reviewers: john.brawn, sebpop, hfinkel, brzycki Subscribers: hiraditya, llvm-commits Tags: #llvm Differential Revision: https://reviews.llvm.org/D74353 This fixes an issue with clang's -fintegrated-cc1 feature, which could make it output slightly different assembly code, depending on the way it was invoked. In r361755 we attempted to work around it by disabling the integrated cc1 stage, but it did not solve the root cause for all situations. Extensive testing and bisecting showed that the above change finally makes the output deterministic, even if -fintegrated-cc1 is on. Reported by: Fabian Keil PR: 246630 MFC after:3 days Changes: head/contrib/llvm-project/llvm/lib/Analysis/BasicAliasAnalysis.cpp -- 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 204521] [new driver] [request] Port rtsx from OpenBSD to FreeBSD
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=204521 --- Comment #239 from Dave Cottlehuber --- GTM here with 15a1c44 against 12.1Rp5 [179] rtsx0: mem 0xdc10-0xdc100fff at device 0.0 on pci3 [179] rtsx0: Card absent mount/unmount, ro & rw to EFI partition. more logs with debug.bootverbose=1 if needed https://gist.github.com/1b86f0c63575485423f90a8968e6baa2 I did get 1 panic already after successful unmount & device removal, I'll need to compile a debug kernel for next time. Reading symbols from /boot/kernel/kernel... (No debugging symbols found in /boot/kernel/kernel) 0x80c01eea in sched_switch () (kgdb) #0 0x80c01eea in sched_switch () #1 0x80bdbfb2 in mi_switch () #2 0x80c2bb85 in sleepq_catch_signals () #3 0x80c2b6bf in sleepq_wait_sig () #4 0x80b6a664 in _cv_wait_sig () #5 0x80c3c53f in seltdwait () #6 0x80c3c0cf in kern_select () #7 0x80c3c466 in sys_select () #8 0x810a8984 in amd64_syscall () #9 #10 0x0008007b1dda in ?? () Backtrace stopped: Cannot access memory at address 0x7fffcde8 (kgdb) -- 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 247386] Description of the last argument of procctl is confusing
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=247386 Mateusz Piotrowski <0...@freebsd.org> changed: What|Removed |Added Keywords||needs-patch CC||0...@freebsd.org Status|New |Open --- Comment #1 from Mateusz Piotrowski <0...@freebsd.org> --- Thanks a lot for the report! -- 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 247385] Typo in cpuset_getdomain
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=247385 Mateusz Piotrowski <0...@freebsd.org> changed: What|Removed |Added CC||0...@freebsd.org Assignee|b...@freebsd.org|0...@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 247389] 800.loginfail and 900.tcpwrap (/etc/periodic/security) don't produce output
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=247389
Bug ID: 247389
Summary: 800.loginfail and 900.tcpwrap (/etc/periodic/security)
don't produce output
Product: Base System
Version: 12.1-STABLE
Hardware: Any
OS: Any
Status: New
Severity: Affects Only Me
Priority: ---
Component: conf
Assignee: b...@freebsd.org
Reporter: xap...@sdf.org
/etc/periodic/security/800.loginfail
/etc/periodic/security/900.tcpwrap
Perhaps it's just me missing the bleeding obvious, but these two scripts appear
to be wired backwards, and therefore don't produce output. Also, the egrep
regex in 800.loginfail doesn't work for me either. A quick edit & test... and
all appears to work as intended.
--- 800.loginfail-old 2019-10-19 19:05:16.208356000 +
+++ 800.loginfail 2020-06-18 18:24:45.77296 +
@@ -46,7 +46,7 @@
yesterday=`date -v-1d "+%b %e "`
catmsgs() {
- find ${LOG} -name 'auth.log.*' -mtime -2 |
+ find ${LOG} -name 'messages.*' -mtime -2 |
sort -t. -r -n -k 2,2 |
while read f
do
@@ -55,7 +55,7 @@
*.bz2) bzcat -f $f;;
esac
done
- [ -f ${LOG}/auth.log ] && cat $LOG/auth.log
+ [ -f ${LOG}/messages ] && cat $LOG/messages
}
rc=0
@@ -64,7 +64,7 @@
then
echo ""
echo "${host} login failures:"
- n=$(catmsgs | egrep -ia "^$yesterday.*:
.*\b(fail(ures?|ed)?|invalid|bad|illegal|auth.*error)\b" |
+ n=$(catmsgs | egrep -ia "^$yesterday.*:
.*\<(fail(ures?|ed)?|invalid|bad|illegal|auth.*error)\>" |
tee /dev/stderr | wc -l)
[ $n -gt 0 ] && rc=1 || rc=0
fi
--- 900.tcpwrap-old 2019-10-19 19:05:16.22447 +
+++ 900.tcpwrap 2020-06-18 18:24:07.948855000 +
@@ -46,7 +46,7 @@
yesterday=`date -v-1d "+%b %e "`
catmsgs() {
- find ${LOG} -name 'messages.*' -mtime -2 |
+ find ${LOG} -name 'auth.log.*' -mtime -2 |
sort -t. -r -n -k 2,2 |
while read f
do
@@ -55,7 +55,7 @@
*.bz2) bzcat -f $f;;
esac
done
- [ -f ${LOG}/messages ] && cat $LOG/messages
+ [ -f ${LOG}/auth.log ] && cat $LOG/auth.log
}
rc=0
--
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 204521] [new driver] [request] Port rtsx from OpenBSD to FreeBSD
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=204521 --- Comment #238 from Henri Hennebert --- (In reply to Zeus Panchenko from comment #237) something really interesting to dig into. It may take some time but it itch me so ... -- 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 247386] Description of the last argument of procctl is confusing
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=247386 Bug ID: 247386 Summary: Description of the last argument of procctl is confusing Product: Documentation Version: Latest Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: Manual Pages Assignee: b...@freebsd.org Reporter: pa...@free.fr CC: d...@freebsd.org The man page gives the following signature int procctl(idtype_t idtype, id_t id, int cmd, void *arg); (note the name of the last argument, 'arg'). In the following descriptions 'arg' is used for PROC_ASLR_CTL, PROC_ASLR_STATUS, PROC_SPROTECT. PROC_REAP_ACQUIRE seems not to use the 4th argument. Then the 7 following descriptions starting with PROC_REAP_STATUS use 'data' PROC_PDEATHSIG_STATUS switches back to 'arg'. And the last two are 'data' again. I see that syscalls.master calls the last argument 'data', so there seems to be a mix of the signature given in the man page and the one in syscalls.master. I think that it would be clearer to use 'arg' consistently. -- 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 247385] Typo in cpuset_getdomain
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=247385 Bug ID: 247385 Summary: Typo in cpuset_getdomain Product: Documentation Version: Latest Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: Manual Pages Assignee: b...@freebsd.org Reporter: pa...@free.fr CC: d...@freebsd.org The signature given is int cpuset_getdomain(cpulevel_t level, cpuwhich_t which, id_t id, size_t setsize, domainet_t *mask, int *policy); where domainet_t should be domainset_t (missing 's'). Seen with 12.1 and online manpage. -- 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 204521] [new driver] [request] Port rtsx from OpenBSD to FreeBSD
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=204521 --- Comment #237 from Zeus Panchenko --- (In reply to Henri Hennebert from comment #236) yes, as I mentioned in #232, with inversion, insert/remove are detected correctly on master -- 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 204521] [new driver] [request] Port rtsx from OpenBSD to FreeBSD
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=204521 --- Comment #236 from Henri Hennebert --- (In reply to Zeus Panchenko from comment #235) So between 15a1c448 and now, the card detection is inverted? -- 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 204521] [new driver] [request] Port rtsx from OpenBSD to FreeBSD
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=204521 --- Comment #235 from Zeus Panchenko --- (In reply to Henri Hennebert from comment #234) I have only HP PB 430 g2 master is broken, 15a1c448 works well (I'm checking out to it each time master fails to work) -- 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 247143] FEATURE IDEA: implement module_disable=YES in /boot/loader.conf file
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=247143 Allan Jude changed: What|Removed |Added CC||allanj...@freebsd.org --- Comment #1 from Allan Jude --- The loader.conf variables are not read by the kernel, but by the loader scripting language, and used to load modules. You can disable some hardware using the device.hints file, but that won't disable the code in the kernel, just keep it from attaching to the hardware. There is a version of the kernel, called MINIMAL, that moves as much as possible out of GENERIC, and uses the 'devmatch' tool to load the drivers for all of the hardware that is detected on your system. With some more polish, this could replace GENERIC and achieve your goal. -- 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 204521] [new driver] [request] Port rtsx from OpenBSD to FreeBSD
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=204521 --- Comment #234 from Henri Hennebert --- (In reply to Zeus Panchenko from comment #232) Did you test on your HP Probook 430 g2 which was working before? Did you test on a Lenovo P50 or Lenovo T470p? -- 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 204521] [new driver] [request] Port rtsx from OpenBSD to FreeBSD
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=204521 --- Comment #233 from Gary Jennejohn --- (In reply to Zeus Panchenko from comment #232) If the lock (read-only) tab was not set then that means two INVERSION defines are needed - one for card present and a different one for read-only. Right now RTSX_INVERSION inverts both together. So, was lock enabled? Also, if you see that read-only is set then you must mount the filesystem as read-only. Looks like there may be a bug in the VFS layer. -- 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 204521] [new driver] [request] Port rtsx from OpenBSD to FreeBSD
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=204521 --- Comment #232 from Zeus Panchenko --- (In reply to Henri Hennebert from comment #230) it helped, now insert/remove is detected correctly but on card insert I'm getting this: Jun 18 13:54:55 iz kernel: mmcsd0: 2GB (read-only) at mmc0 50.0MHz/1bit/256-block on mount attempt, I'm getting fs read-only and no mounted fs and after a couple of minutes panic and reboot in logs this: Jun 18 13:53:22 iz kernel: g_vfs_done():mmcsd0s1[WRITE(offset=16384, length=4096)]error = 30 Jun 18 13:53:22 iz syslogd: last message repeated 2 times Jun 18 13:53:22 iz kernel: fsync: giving up on dirty (error = 30) 0xf802d79325a0: tag devfs, type VCHR Jun 18 13:53:22 iz kernel: usecount 1, writecount 0, refcount 472 rdev 0xf80132db9c00 Jun 18 13:53:22 iz kernel: flags (VI_ACTIVE) Jun 18 13:53:22 iz kernel: v_object 0xf8028dd8d000 ref 0 pages 470 cleanbuf 469 dirtybuf 1 Jun 18 13:53:22 iz kernel: lock type devfs: UNLOCKED Jun 18 13:53:22 iz kernel: dev mmcsd0s1 -- 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 204521] [new driver] [request] Port rtsx from OpenBSD to FreeBSD
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=204521 --- Comment #231 from Gary Jennejohn --- (In reply to unitrunker from comment #228) This is pretty weird. Looking at my kernel. which has the same address for mmc_go_discovery() as your kernel, the panic is happening in a call to memset() in the first call to mmc_send_app_op_cond(). Apparently the compiler has optimized mmc_go_discovery() by inlining mmc_send_app_op_cond(), since that function is only used in mc_go_discovery(). This conclusion is supported by the fact that there is no entry for mmc_send_app_op_cond in the ELF header. The really strange thing is that memset() is being called to zero out a struct mmc_command cmd which is on the kernel stack. That should bever raise an error. It should also never result in a calltrap, because this is an in-kernel call. I must admit that I can see no way that this error could happen. -- 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 204521] [new driver] [request] Port rtsx from OpenBSD to FreeBSD
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=204521 --- Comment #230 from Henri Hennebert --- (In reply to Zeus Panchenko from comment #229) It is strange. Can you compile the module with: make -D RTSX_INVERSION Thanks and X-fingers -- 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"
