Re: INTRNG
On 02/23/18 07:25, Jon Brawn wrote: > Wotcha Gang! > > In my travels through the arm64 GENERIC config file I came across the option > ‘INTRNG’, and wondered what it was: > > INTeRrupt Next Generation? > INTeger Random Number Generator? > IN TRaiNinG? > INTerrupt Random Number Generator? > INdependent TRaiNinG? > > So, please put me out of my misery, what does INTRNG stand for, and what are > its implications when selected vs not selected? > A quick grep in src/sys gave me this: MALLOC_DEFINE(M_INTRNG, "intr", "intr interrupt handling"); Also: arm/arm/machdep.c:#if __ARM_ARCH >= 6 && !defined(INTRNG) arm/arm/machdep.c:#error armv6 requires INTRNG So it's about interrupts and mandatory for arm processors, I suspect it's and arm (and mips too, since I found grep hits there too) specific interrupts handling method. this looks like the original RFC for this code: https://lists.freebsd.org/pipermail/freebsd-arm/2014-April/007915.html -- Guido Falsi ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Intel SST Audio Device(WDM)
Hi, all I'm searching Intel SST Audio Device(WDM) for FreeBSD which seems not yet implemented. In Linux/Debien, the non-free firmware firmware-intel-sound[1] may be supported. How does it work in FreeBSD ? Best regards [1] https://unix.stackexchange.com/questions/307623/system-mute-of-fresh-install-debian-cant-find-the-audio-devices --- KIRIYAMA Kazuhiko ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: kernel: failed: cg 5, cgp: 0xd11ecd0d != bp: 0x63d3ff1d
> From: "Chris H" > Reply-To: bsd-li...@bsdforge.com > To: "FreeBSD Current" > Subject: kernel: failed: cg 5, cgp: 0xd11ecd0d != bp: 0x63d3ff1d > Date: Mon, 19 Feb 2018 14:18:15 -0800 > > I'm seeing a number of messages like the following: > kernel: failed: cg 5, cgp: 0xd11ecd0d != bp: 0x63d3ff1d > > and was wondering if it's anything to be concerned with, or whether > fsck(8) is fixing them. > This began to happen when the power went out on a new install: > FreeBSD dns0 12.0-CURRENT FreeBSD 12.0-CURRENT #0: Wed Dec 13 06:07:59 PST > 2017 > root@dns0:/usr/obj/usr/src/amd64.amd64/sys/DNS0 amd64 > which hadn't yet been hooked up to the UPS. > I performed an fsck in single user mode upon power-up. Which ended with the > mount points being masked CLEAN. I was asked if I wanted to use the JOURNAL. > I answered Y. > FWIW the systems are UFS2 (ffs) have gpart labels, and were newfs'd thusly: > newfs -U -j > > Thank you for all your time, and consideration. > > --Chris This problem should have been fixed with this commit: r328914 | mckusick | 2018-02-05 16:19:46 -0800 (Mon, 05 Feb 2018) You need to update your kernel to get the fix. Kirk McKusick ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: kernel: failed: cg 5, cgp: 0xd11ecd0d != bp: 0x63d3ff1d
On Thu, 22 Feb 2018 22:57:38 -0800 "Kirk McKusick" said > From: "Chris H" > Reply-To: bsd-li...@bsdforge.com > To: "FreeBSD Current" > Subject: kernel: failed: cg 5, cgp: 0xd11ecd0d != bp: 0x63d3ff1d > Date: Mon, 19 Feb 2018 14:18:15 -0800 > > I'm seeing a number of messages like the following: > kernel: failed: cg 5, cgp: 0xd11ecd0d != bp: 0x63d3ff1d > > and was wondering if it's anything to be concerned with, or whether > fsck(8) is fixing them. > This began to happen when the power went out on a new install: > FreeBSD dns0 12.0-CURRENT FreeBSD 12.0-CURRENT #0: Wed Dec 13 06:07:59 PST > 2017 > root@dns0:/usr/obj/usr/src/amd64.amd64/sys/DNS0 amd64 > which hadn't yet been hooked up to the UPS. > I performed an fsck in single user mode upon power-up. Which ended with the > mount points being masked CLEAN. I was asked if I wanted to use the JOURNAL. > I answered Y. > FWIW the systems are UFS2 (ffs) have gpart labels, and were newfs'd thusly: > newfs -U -j > > Thank you for all your time, and consideration. > > --Chris This problem should have been fixed with this commit: r328914 | mckusick | 2018-02-05 16:19:46 -0800 (Mon, 05 Feb 2018) Good news. Thank you very much, Kirk! --Chris You need to update your kernel to get the fix. Kirk McKusick ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org" ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: INTRNG
Jon Brawn (j...@brawn.org) wrote: > Wotcha Gang! > > In my travels through the arm64 GENERIC config file I came across the option > ‘INTRNG’, and wondered what it was: > > INTeRrupt Next Generation? > INTeger Random Number Generator? > IN TRaiNinG? > INTerrupt Random Number Generator? > INdependent TRaiNinG? > > So, please put me out of my misery, what does INTRNG stand for, and what are > its implications when selected vs not selected? "INTeRrupt Next Generation". It's a framework to manage complex interrupt routing cases. I think it's required for all recent ARM platforms, you can't disable it for ARM64. It can be disabled for older ARM/MIPS platforms that use old-style interrupt cascading. -- gonzo ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
