Re: linking to git revisions in bugzilla
Kubilay Kocak (ko...@freebsd.org) wrote: > On 12/04/2021 9:02 am, Yuri Pankov wrote: > > While filing a bug, I noticed that the help only mentions svn revision > > numbers, and "Preview" tab had no output when I tried putting "base > > ", so I'm wondering how do you link to git revisions? > > We'll (bugmeister) be adding parsing support for it (along with a few > other related auto-linking things) > > I'd encourage people to use " " (repo = src|doc|ports) > where short hash is at least 8 chars in the meantime. Once parsing is > added all previous references will be linked. Links to git hashes should work now, please test and let us know if feature works as expected. As Michael mentioned - preview is a different matter, I'll try to look into it later. -- 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"
Re: WSLg update on 1-5-2021 - BSD / WSL
On Sat, 1 May 2021 21:42:38 +0200 Chargen wrote: > With FreeBSD subsystem and interops , windows should feel less > monolithic > Waste our resourses to increase MS money profit. ___ 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: Problems with realtek NIC
On Saturday, 1 May 2021 16:45:03 CDT Stefan Esser wrote: > Am 01.05.21 um 21:48 schrieb Greg Rivers via freebsd-current: > > On Saturday, 1 May 2021 14:09:46 CDT Nilton Jose Rizzo wrote: > >> I using a FreeBSD 14-Current and get random error with my NIC. The > >> watchdog timer send a timeout message and I loose connection temporaly. In > >> logs show only this message: > >> > > Switch to the official Realtek driver in ports: net/realtek-re-kmod > > The "official" RealTek driver is based on a very old version of "our" > driver that was written by Bill Paul. > > It lacks many features that have been introduced in FreeBSD in the > last decade (or even earlier) like NETMAP-Support. > > The RealTek-driver has special cases for some 50 variants of RealTek > Ethernet chips and contains individual firmware patches for nearly all > of them. > > I had started to merge chip specific changes from the official driver > to the FreeBSD driver in the hope to get it to support the RTL8125A/B > chips. But I have stopped that project for lack of RTL8125 documentation, > especially regarding the PHY, which has its own driver module in our > version but not the RealTek code. (And somebody claimed to know that > another FreeBSD developer was working on RTL8125 support but did not > tell who that might be and whether he had documentation.) > > Anyway, there are changes regarding the initialization and error recovery > of different RealTek chips in the official driver that could be merged > into our version. But I do not know whether these changes require the > firmware changes provided by the RealTek driver to correctly work. > Thanks for the information Stefan, and for your work on FreeBSD. My use of the term "official" was apparently inaccurate. I was not aware of the deficiencies in the RealTek driver. I would prefer to use the FreeBSD driver, but I don't for purely pragmatic reasons: the FreeBSD driver continually locks up and resets under load (as described by the OP), while the RealTek driver does not. FWIW, here are the particulars on the RealTek chip-set that I've got: re0: port 0xe000-0xe0ff mem 0xb0804000-0xb0804fff,0xb080-0xb0803fff irq 16 at device 0.0 on pci1 re0: Using 1 MSI-X message re0: Chip rev. 0x2c80 re0: MAC rev. 0x0010 re0@pci0:1:0:0: class=0x02 rev=0x06 hdr=0x00 vendor=0x10ec device=0x8168 subvendor=0x1458 subdevice=0xe000 vendor = 'Realtek Semiconductor Co., Ltd.' device = 'RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller' class = network subclass = ethernet Would the FreeBSD Foundation be able to help with getting documentation from RealTek? -- Greg ___ 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: Problems with realtek NIC
Am 01.05.21 um 21:48 schrieb Greg Rivers via freebsd-current: > On Saturday, 1 May 2021 14:09:46 CDT Nilton Jose Rizzo wrote: >> I using a FreeBSD 14-Current and get random error with my NIC. The watchdog >> timer send a timeout message and I loose connection temporaly. In logs show >> only this message: >> > Switch to the official Realtek driver in ports: net/realtek-re-kmod The "official" RealTek driver is based on a very old version of "our" driver that was written by Bill Paul. It lacks many features that have been introduced in FreeBSD in the last decade (or even earlier) like NETMAP-Support. The RealTek-driver has special cases for some 50 variants of RealTek Ethernet chips and contains individual firmware patches for nearly all of them. I had started to merge chip specific changes from the official driver to the FreeBSD driver in the hope to get it to support the RTL8125A/B chips. But I have stopped that project for lack of RTL8125 documentation, especially regarding the PHY, which has its own driver module in our version but not the RealTek code. (And somebody claimed to know that another FreeBSD developer was working on RTL8125 support but did not tell who that might be and whether he had documentation.) Anyway, there are changes regarding the initialization and error recovery of different RealTek chips in the official driver that could be merged into our version. But I do not know whether these changes require the firmware changes provided by the RealTek driver to correctly work. Regards, STefan OpenPGP_signature Description: OpenPGP digital signature
Re: Problems with realtek NIC
On Saturday, 1 May 2021 14:09:46 CDT Nilton Jose Rizzo wrote: > I using a FreeBSD 14-Current and get random error with my NIC. The watchdog > timer send a timeout message and I loose connection temporaly. In logs show > only this message: > Switch to the official Realtek driver in ports: net/realtek-re-kmod -- Greg ___ 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"
WSLg update on 1-5-2021 - BSD / WSL
Dear all please note that I hope this message will be discussed to get this on the roadmap for FreeBSD. Perhaps there is already talk about && work done on that. I would like to suggest having a BSD side for Microsoft FOSS ambitions and get to know the BSD license. I hope the tech people here, know which nuts and bolts would be ready to boot a *BSD subsystem kernel and make that available on Windows 10 installations. Dru Do "we" want that for FreeBSD? I think so I hope so... Today I saw Window 10 doing a WSLg update, and with that, automatic reinstalled Debian applications that can now use Wayland *compositor hooks to serve graphics (xaos, rxvt, stellarium)it works, even pong.scr I'm also on the Windows Insider team, "MacBethwin" for over 6 years. I have seen so many GSOD Green Screens of Death that provoked by me, I have that record of breaking stuff. So I also know a bit about what went wrong, what is good, what was needed .. to state that the guy Jamie (fame) from Xscreensavershould get paid for losing business in the days I dare mention all the Bad juju of Microsoft from the past. that I know of, I'm also honest when for ack the excellent development at Redwood, developers have done a hell of a job With FreeBSD subsystem and interops , windows should feel less monolithic Best Regards Edwin (chargen at gmail dot com) -- Deze e-mail en de inhoud is vertrouwelijk en uitsluitend bestemd voor de geadresseerde(n). Indien u niet de geadresseerde bent van deze e-mail verzoeken wij u dit direct door te geven aan de verzender door middel van een reply e-mail en de ontvangen e-mail uit uw systemen te verwijderen. Als u geen geadresseerde bent, is het niet toegestaan om kennis te nemen van de inhoud, deze te kopieren, te verspreiden, bekend te maken aan derden noch anderszins te gebruiken. The information contained in this e-mail is confidential and may be legally privileged. It is intended solely for the addressee. If you are not the intended recipient, any disclosure, copying, distribution or any action taken or omitted to be taken in reliance on it, is prohibited and may be unlawful. Please notify us immediately if you have received it in error by reply e-mail and then delete this message from your system. Thanks, _ _ (_)(_) (,,) =()= ((__)\ _|L\___/ Save The Lab Rats ___ 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: Problems with realtek NIC
On 01.05.2021 21.09, Nilton Jose Rizzo wrote: Hi all I using a FreeBSD 14-Current and get random error with my NIC. The watchdog timer send a timeout message and I loose connection temporaly. In logs show only this message: May 1 14:24:18 valfenda kernel: re0: watchdog timeout May 1 14:24:18 valfenda kernel: re0: link state changed to DOWN May 1 14:24:22 valfenda kernel: re0: link state changed to UP May 1 14:46:12 valfenda kernel: re0: watchdog timeout May 1 14:46:12 valfenda kernel: re0: link state changed to DOWN May 1 14:46:16 valfenda kernel: re0: link state changed to UP May 1 14:58:58 valfenda kernel: re0: watchdog timeout May 1 14:58:58 valfenda kernel: re0: link state changed to DOWN May 1 14:59:02 valfenda kernel: re0: link state changed to UP May 1 15:06:20 valfenda kernel: re0: watchdog timeout May 1 15:06:20 valfenda kernel: re0: link state changed to DOWN May 1 15:06:25 valfenda kernel: re0: link state changed to UP May 1 15:25:32 valfenda kernel: re0: watchdog timeout May 1 15:25:32 valfenda kernel: re0: link state changed to DOWN May 1 15:25:36 valfenda kernel: re0: link state changed to UP May 1 15:28:24 valfenda kernel: re0: watchdog timeout May 1 15:28:24 valfenda kernel: re0: link state changed to DOWN May 1 15:28:28 valfenda kernel: re0: link state changed to UP This occur frequently when i use a Mozilla Firefox in meet session, but not only in this case. My box: % uname -a FreeBSD valfenda 14.0-CURRENT FreeBSD 14.0-CURRENT #0 main-7ea3223c7: Thu Apr 22 13:24:05 -03 2021 rizzo@valfenda:/usr/obj/usr/src/amd64.amd64/sys/GENERIC amd64 % pkg info -a | grep firefox firefox-88.0,2 Web browser based on the browser portion of Mozilla % kldstat Id Refs AddressSize Name 1 85 0x8020 2131010 kernel 21 0x82333000 91d0 cryptodev.ko 31 0x8233d000 7cae50 zfs.ko 41 0x8301 d940 geom_eli.ko 51 0x8301e000 3530 fdescfs.ko 61 0x83022000 3378 acpi_wmi.ko 71 0x83026000 3218 intpm.ko 81 0x8302a000 2180 smbus.ko 91 0x8302d000 10b310 nvidia-modeset.ko 101 0x8320 1e834a8 nvidia.ko 112 0x83139000378f8 linux.ko 123 0x83171000 db70 linux_common.ko 131 0x8317f000 3238 filemon.ko 141 0x83183000 5730 cuse.ko 151 0x83189000 3160 amdtemp.ko 161 0x8318d000 2138 amdsmn.ko 171 0x8319 e538 snd_uaudio.ko 181 0x8319f000 2340 uhid.ko 191 0x831a2000 2380 usbhid.ko 201 0x831a5000 31f8 hidbus.ko 211 0x831a9000 3320 wmt.ko 221 0x831ad000 4350 ums.ko 231 0x831b200027040 ipfw.ko 241 0x831da0001ae88 ext2fs.ko 251 0x8508400011f10 fusefs.ko 261 0x831f5000 5354 geom_linux_lvm.ko 271 0x8509600056ec0 vboxdrv.ko % TIA, Rizzo ___ 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" Back on 12 net/realtek-re-kmod solved it for me. With the following in /boot/loader.conf if_re_load="YES" if_re_name="/boot/modules/if_re.ko" ___ 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"
Problems with realtek NIC
Hi all I using a FreeBSD 14-Current and get random error with my NIC. The watchdog timer send a timeout message and I loose connection temporaly. In logs show only this message: May 1 14:24:18 valfenda kernel: re0: watchdog timeout May 1 14:24:18 valfenda kernel: re0: link state changed to DOWN May 1 14:24:22 valfenda kernel: re0: link state changed to UP May 1 14:46:12 valfenda kernel: re0: watchdog timeout May 1 14:46:12 valfenda kernel: re0: link state changed to DOWN May 1 14:46:16 valfenda kernel: re0: link state changed to UP May 1 14:58:58 valfenda kernel: re0: watchdog timeout May 1 14:58:58 valfenda kernel: re0: link state changed to DOWN May 1 14:59:02 valfenda kernel: re0: link state changed to UP May 1 15:06:20 valfenda kernel: re0: watchdog timeout May 1 15:06:20 valfenda kernel: re0: link state changed to DOWN May 1 15:06:25 valfenda kernel: re0: link state changed to UP May 1 15:25:32 valfenda kernel: re0: watchdog timeout May 1 15:25:32 valfenda kernel: re0: link state changed to DOWN May 1 15:25:36 valfenda kernel: re0: link state changed to UP May 1 15:28:24 valfenda kernel: re0: watchdog timeout May 1 15:28:24 valfenda kernel: re0: link state changed to DOWN May 1 15:28:28 valfenda kernel: re0: link state changed to UP This occur frequently when i use a Mozilla Firefox in meet session, but not only in this case. My box: % uname -a FreeBSD valfenda 14.0-CURRENT FreeBSD 14.0-CURRENT #0 main-7ea3223c7: Thu Apr 22 13:24:05 -03 2021 rizzo@valfenda:/usr/obj/usr/src/amd64.amd64/sys/GENERIC amd64 % pkg info -a | grep firefox firefox-88.0,2 Web browser based on the browser portion of Mozilla % kldstat Id Refs AddressSize Name 1 85 0x8020 2131010 kernel 21 0x82333000 91d0 cryptodev.ko 31 0x8233d000 7cae50 zfs.ko 41 0x8301 d940 geom_eli.ko 51 0x8301e000 3530 fdescfs.ko 61 0x83022000 3378 acpi_wmi.ko 71 0x83026000 3218 intpm.ko 81 0x8302a000 2180 smbus.ko 91 0x8302d000 10b310 nvidia-modeset.ko 101 0x8320 1e834a8 nvidia.ko 112 0x83139000378f8 linux.ko 123 0x83171000 db70 linux_common.ko 131 0x8317f000 3238 filemon.ko 141 0x83183000 5730 cuse.ko 151 0x83189000 3160 amdtemp.ko 161 0x8318d000 2138 amdsmn.ko 171 0x8319 e538 snd_uaudio.ko 181 0x8319f000 2340 uhid.ko 191 0x831a2000 2380 usbhid.ko 201 0x831a5000 31f8 hidbus.ko 211 0x831a9000 3320 wmt.ko 221 0x831ad000 4350 ums.ko 231 0x831b200027040 ipfw.ko 241 0x831da0001ae88 ext2fs.ko 251 0x8508400011f10 fusefs.ko 261 0x831f5000 5354 geom_linux_lvm.ko 271 0x8509600056ec0 vboxdrv.ko % TIA, Rizzo ___ 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: Build fail updating from n246398-388c0cde1029 -> n246413-c78ad207baed
https://lists.freebsd.org/pipermail/dev-commits-src-main/2021-May/003953.html
reports for main's commit just after c78ad207baed :
The branch main has been updated by andrew:
URL:
https://cgit.FreeBSD.org/src/commit/?id=f1957db43d28dbae1f82905304bab5be51942342
commit f1957db43d28dbae1f82905304bab5be51942342
Author: Andrew Turner
AuthorDate: 2021-05-01 11:10:03 +
Commit: Andrew Turner
CommitDate: 2021-05-01 11:10:03 +
Fix building sysctl(8) after c78ad20
In sysctl we parse an efi header on amd64. Fix this after changing the
virtual memory type from a void * to a uint64_t in c78ad20.
---
sbin/sysctl/sysctl.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/sbin/sysctl/sysctl.c b/sbin/sysctl/sysctl.c
index 30d6d94723fa..8d658dc2debe 100644
--- a/sbin/sysctl/sysctl.c
+++ b/sbin/sysctl/sysctl.c
@@ -794,8 +794,8 @@ S_efi_map(size_t l2, void *p)
type = types[map->md_type];
if (type == NULL)
type = "";
- printf("\n%23s %012jx %12p %08jx ", type,
- (uintmax_t)map->md_phys, map->md_virt,
+ printf("\n%23s %012jx %012jx %08jx ", type,
+ (uintmax_t)map->md_phys, (uintmax_t)map->md_virt,
(uintmax_t)map->md_pages);
if (map->md_attr & EFI_MD_ATTR_UC)
printf("UC ");
===
Mark Millard
marklmi at yahoo.com
( dsl-only.net went
away in early 2018-Mar)
___
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: ZFS going forward, on stable/13 vs. main: question
Question . . . Are there any potential future upgrade issues with main [so: 14] vs. stable/13 and releng/13.0 , say by main updates involving ZFS updates in a way stable/13 or the recent releng/13.* might not handle? There's no issue if you don't upgrade the pool on main with new features that aren't present in 13. It won't happen automatically, you'd have to manually run zpool upgrade. -Ryan ___ 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"
Build fail updating from n246398-388c0cde1029 -> n246413-c78ad207baed
Per the ERROR_META_FILE: # Meta data file /common/S4/obj/usr/src/amd64.amd64/sbin/sysctl/sysctl.o.meta CMD cc -target x86_64-unknown-freebsd14.0 --sysroot=/common/S4/obj/usr/src/amd64.amd64/tmp -B/common/S4/obj/usr/src/amd64.amd64/tmp/usr/bin -O2 -pipe -fno-common -fPIE -std=gnu99 -Wno-format-zero-length -fstack-protector-strong -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wno-uninitialized -Wno-pointer-sign -Wno-empty-body -Wno-string-plus-int -Wno-unused-const-variable -Wno-tautological-compare -Wno-unused-value -Wno-parentheses-equality -Wno-unused-function -Wno-enum-conversion -Wno-unused-local-typedef -Wno-address-of-packed-member -Qunused-arguments-c /usr/src/sbin/sysctl/sysctl.c -o sysctl.o CMD CWD /common/S4/obj/usr/src/amd64.amd64/sbin/sysctl TARGET sysctl.o -- command output -- /usr/src/sbin/sysctl/sysctl.c:798:32: error: format specifies type 'void *' but the argument has type 'uint64_t' (aka 'unsigned long') [-Werror,-Wformat] (uintmax_t)map->md_phys, map->md_virt, ^~~~ 1 error generated. *** Error code 1 -- filemon acquired metadata -- # filemon version 5 # Target pid 94559 # Start 1619869639.590308 V 5 E 94581 /bin/sh R 94581 /etc/libmap.conf R 94581 /var/run/ld-elf.so.hints R 94581 /lib/libedit.so.8 R 94581 /lib/libc.so.7 R 94581 /lib/libncursesw.so.9 R 94581 /usr/share/locale/en_US.UTF-8/LC_COLLATE R 94581 /usr/share/locale/en_US.UTF-8/LC_CTYPE R 94581 /usr/share/locale/en_US.UTF-8/LC_MONETARY R 94581 /usr/share/locale/en_US.UTF-8/LC_NUMERIC R 94581 /usr/share/locale/en_US.UTF-8/LC_TIME R 94581 /usr/share/locale/en_US.UTF-8/LC_MESSAGES F 94581 94587 E 94587 /usr/bin/cc R 94587 /etc/libmap.conf R 94587 /var/run/ld-elf.so.hints R 94587 /lib/libz.so.6 R 94587 /usr/lib/libexecinfo.so.1 R 94587 /lib/libncursesw.so.9 R 94587 /lib/libthr.so.3 R 94587 /usr/lib/libc++.so.1 R 94587 /lib/libcxxrt.so.1 R 94587 /lib/libm.so.5 R 94587 /lib/libc.so.7 R 94587 /lib/libelf.so.2 R 94587 /lib/libgcc_s.so.1 R 94587 /usr/src/sbin/sysctl/sysctl.c R 94587 sysctl-a47e0ae5.o.tmp W 94587 sysctl-a47e0ae5.o.tmp R 94587 /common/S4/obj/usr/src/amd64.amd64/tmp/usr/include/sys/cdefs.h R 94587 /common/S4/obj/usr/src/amd64.amd64/tmp/usr/include/sys/param.h R 94587 /common/S4/obj/usr/src/amd64.amd64/tmp/usr/include/sys/_null.h R 94587 /common/S4/obj/usr/src/amd64.amd64/tmp/usr/include/sys/types.h R 94587 /common/S4/obj/usr/src/amd64.amd64/tmp/usr/include/machine/endian.h R 94587 /common/S4/obj/usr/src/amd64.amd64/tmp/usr/include/x86/endian.h R 94587 /common/S4/obj/usr/src/amd64.amd64/tmp/usr/include/sys/_types.h R 94587 /common/S4/obj/usr/src/amd64.amd64/tmp/usr/include/machine/_types.h R 94587 /common/S4/obj/usr/src/amd64.amd64/tmp/usr/include/x86/_types.h R 94587 /common/S4/obj/usr/src/amd64.amd64/tmp/usr/include/machine/_limits.h R 94587 /common/S4/obj/usr/src/amd64.amd64/tmp/usr/include/x86/_limits.h R 94587 /common/S4/obj/usr/src/amd64.amd64/tmp/usr/include/sys/_endian.h R 94587 /common/S4/obj/usr/src/amd64.amd64/tmp/usr/include/sys/_pthreadtypes.h R 94587 /common/S4/obj/usr/src/amd64.amd64/tmp/usr/include/sys/_stdint.h R 94587 /common/S4/obj/usr/src/amd64.amd64/tmp/usr/include/sys/select.h R 94587 /common/S4/obj/usr/src/amd64.amd64/tmp/usr/include/sys/_sigset.h R 94587 /common/S4/obj/usr/src/amd64.amd64/tmp/usr/include/sys/_timeval.h R 94587 /common/S4/obj/usr/src/amd64.amd64/tmp/usr/include/sys/timespec.h R 94587 /common/S4/obj/usr/src/amd64.amd64/tmp/usr/include/sys/_timespec.h R 94587 /common/S4/obj/usr/src/amd64.amd64/tmp/usr/include/sys/syslimits.h R 94587 /common/S4/obj/usr/src/amd64.amd64/tmp/usr/include/sys/signal.h R 94587 /common/S4/obj/usr/src/amd64.amd64/tmp/usr/include/machine/signal.h R 94587 /common/S4/obj/usr/src/amd64.amd64/tmp/usr/include/x86/signal.h R 94587 /common/S4/obj/usr/src/amd64.amd64/tmp/usr/include/machine/param.h R 94587 /common/S4/obj/usr/src/amd64.amd64/tmp/usr/include/machine/_align.h R 94587 /common/S4/obj/usr/src/amd64.amd64/tmp/usr/include/x86/_align.h R 94587 /common/S4/obj/usr/src/amd64.amd64/tmp/usr/include/sys/limits.h R 94587 /common/S4/obj/usr/src/amd64.amd64/tmp/usr/include/sys/time.h R 94587 /common/S4/obj/usr/src/amd64.amd64/tmp/usr/include/time.h R 94587 /common/S4/obj/usr/src/amd64.amd64/tmp/usr/include/xlocale/_time.h R 94587 /common/S4/obj/usr/src/amd64.amd64/tmp/usr/include/sys/resource.h R 94587 /common/S4/obj/usr/src/amd64.amd64/tmp/usr/include/sys/stat.h R 94587 /common/S4/obj/usr/src/amd64.amd64/tmp/usr/include/sys/sysctl.h R 94587 /common/S4/obj/usr/src/amd64.amd64/tmp/usr/include/sys/vmmeter.h R 94587 /common/S4/obj/usr/src/amd64.amd64/tmp/usr/include/dev/evdev/input.h R 94587 /common/S4/obj/usr/src/amd64.amd64/tmp/usr/include/sys/ioccom.h R 94587 /common/S4/obj/usr/src/amd64.amd64/tmp/usr/include/dev/evdev/input-event-codes.h R 94587
