Re: swapping is completely broken in -CURRENT r334649?
On Tue, Jun 05, 2018 at 05:48:08PM -0400, Mark Johnston wrote: > > On Wed, Jun 06, 2018 at 12:22:08AM +0300, Lev Serebryakov wrote: > > On 05.06.2018 19:17, Gary Jennejohn wrote: > > > > > > > I complained about this also and alc@ gave me this hint: > > > sysctl vm.pageout_update_period=0 > > > > Really, situation is worse than stated in subject, because processes > > are being killed AFTER memory pressure, when here are a lot of free > > memory already! > > > > It looks like very serious bug. > > The issue was identified earlier this week and is being worked on. It's > a regression from r329882 which appears only on certain hardware. You > can probably work around it by setting vm.pageout_oom_seq to a large > value (try 1000 for instance), though this will make the "true" OOM > killer take longer to kick in. The problem is unrelated to the > pageout_update_period. I have a large swap space and I've encountered this issue as well pid 90707 (getty), uid 0, was killed: out of swap space pid 90709 (getty), uid 0, was killed: out of swap space pid 90709 (getty), uid 0, was killed: out of swap space ... Setting vm.pageout_oom_seq to 1000 doesn't help. If you have a patch I'll be happy to test it, thanks. Kevin ___ 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: utilities in /usr/bin or /usr/sbin?
Rodney W. Grimes wrote: ?> On Thu, Jun 14, 2018 at 2:15 PM, Rick Macklem wrote: >> >> > Hi, >> > >> > I have three new utilities that are mainly useful for managing the pNFS >> > server >> > committed as r335130. >> > >> > In the projects tree, I have them in /usr/bin and man section 1. However, >> > since they are mostly useful to a sysadmin managing the pNFS service, >> > I'm thinking that maybe they should be in /usr/sbin with man pages in >> > section 8. >> > >> > Which of these sounds correct? >> > >> >> /usr/sbin is the more proper location if they are truly admin-only commands. > >Dont these commands require root priv to work? >If so they are certainly /usr/sbin material. Yea, this is a little amusing. The first of these three utilities would just get an extended attribute and display the info (it's binary) and I didn't see any reason for this being restricted to root, so I didn't do that in the utility. However, I just realized I had never tried it as non-root and it doesn't work as non-root (apparently get extended attribute of "system" namespace is restricted to root). So, I think it's settled. They should all go in /usr/sbin. Thanks everyone for your comments, rick ___ 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: utilities in /usr/bin or /usr/sbin?
> On Thu, Jun 14, 2018 at 2:15 PM, Rick Macklem wrote: > > > Hi, > > > > I have three new utilities that are mainly useful for managing the pNFS > > server > > committed as r335130. > > > > In the projects tree, I have them in /usr/bin and man section 1. However, > > since they are mostly useful to a sysadmin managing the pNFS service, > > I'm thinking that maybe they should be in /usr/sbin with man pages in > > section 8. > > > > Which of these sounds correct? > > > > /usr/sbin is the more proper location if they are truly admin-only commands. Dont these commands require root priv to work? If so they are certainly /usr/sbin material. -- Rod Grimes rgri...@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: utilities in /usr/bin or /usr/sbin?
On Thu, Jun 14, 2018 at 2:15 PM, Rick Macklem wrote: > Hi, > > I have three new utilities that are mainly useful for managing the pNFS > server > committed as r335130. > > In the projects tree, I have them in /usr/bin and man section 1. However, > since they are mostly useful to a sysadmin managing the pNFS service, > I'm thinking that maybe they should be in /usr/sbin with man pages in > section 8. > > Which of these sounds correct? > /usr/sbin is the more proper location if they are truly admin-only commands. Warner ___ 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: freebsd bhyve instance does not show kernel messages after boot screen
Try in /boot/loader.conf of the VM : console=userboot or after beastie drop to loader OK promot and try : set console=userboot I think 11.x should fall back to userboot in bhyve if vidconsole of comconsole were set. (This is assuming non-EFI booting - using bhyveloader ). -- David P. Discher https://davidpdischer.com/ 408.368.3725 • d...@dpdtech.com > On Jun 14, 2018, at 2:49 PM, tech-lists wrote: > > Hello list, > > context is freebsd-12 r317212 host and freebsd-11-stable r333924 guest > > I run this freebsd instance in screen. I start it like this: > > vmrun.sh -c 4 -m 8192M -t tap3 -d fbsd-guest.img fbsd-guest > > It starts, I get the daemon screen, then this: > > /boot/kernel/kernel text=0x70572d data=0xa5648+0x340ac0 > syms=[0x8+0xc0c78+0x8+0xde421] > /boot/entropy size=0x1000 > Booting... > Unhandled ps2 mouse command 0xe1 > > and that's it. The guest loads, is functional, I can ssh into it, etc. > > Other freebsd-11 VMs started in the exact same way on the same server give > the expected messages scrolling up when the VM starts. Why is this VM > different and how can I fix? There was a time when the messages were > displayed, then one day they didn't. > > I've built/installed a new world/kernel on this VM to no effect. > > thanks, > -- > J. > ___ > 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" signature.asc Description: Message signed with OpenPGP
freebsd bhyve instance does not show kernel messages after boot screen
Hello list, context is freebsd-12 r317212 host and freebsd-11-stable r333924 guest I run this freebsd instance in screen. I start it like this: vmrun.sh -c 4 -m 8192M -t tap3 -d fbsd-guest.img fbsd-guest It starts, I get the daemon screen, then this: /boot/kernel/kernel text=0x70572d data=0xa5648+0x340ac0 syms=[0x8+0xc0c78+0x8+0xde421] /boot/entropy size=0x1000 Booting... Unhandled ps2 mouse command 0xe1 and that's it. The guest loads, is functional, I can ssh into it, etc. Other freebsd-11 VMs started in the exact same way on the same server give the expected messages scrolling up when the VM starts. Why is this VM different and how can I fix? There was a time when the messages were displayed, then one day they didn't. I've built/installed a new world/kernel on this VM to no effect. thanks, -- J. ___ 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: Can't seem to use 5GHz APs with Intel wireless
On Wed, Jun 13, 2018 at 08:29:06AM -0700, Adrian Chadd wrote: > hm. Which country are you in? india? > > It seems to think you're in the FCC4 regdomain and DE country, which > if I read it right won't give you 5G. So somehow it determined you're > in the "wrong" country? No it was entirely my fault. I had "country DE regdomain FCC4" set in my rc.conf. I don't remmeber why I set regulatory domain or why I explicitly chose FCC4. :-( I was travelling around a bit when this thread was active, thats why my replies had different country code in them. - dbalan ___ 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: Ryzen public erratas (and Epyc ?)
On Thursday, June 14, 2018, Mike Tancsa wrote: > On 6/14/2018 11:03 AM, Konstantin Belousov wrote: > > I am not sure about only microcode update. Depending on the BIOS > > vendor and current BIOS, you may need all three: BIOS update, microcode > > update using cpucontrol/devcpu-data, and running the script I posted. > > In the best case, some of this is just redundand. > > OK, before and after shows the same microcode rev > > CPU: AMD EPYC 7281 16-Core Processor (2100.06-MHz > K8-class CPU) > Origin="AuthenticAMD" Id=0x800f12 Family=0x17 Model=0x1 Stepping=2 > > Features=0x178bfbff APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,MMX,FXSR,SSE,SSE2,HTT> > > Features2=0x7ed8320b SSE4.1,SSE4.2,MOVBE,POPCNT,AESNI,XSAVE,OSXSAVE,AVX,F16C,RDRAND> > AMD Features=0x2e500800 > AMD > Features2=0x35c233ff Prefetch,OSVW,SKINIT,WDT,TCE,Topology,PCXC,PNXC,DBE,PL2I,MWAITX> > Structured Extended > Features=0x209c01a9 ADX,SMAP,CLFLUSHOPT,SHA> > XSAVE Features=0xf > AMD Extended Feature Extensions ID EBX=0x1007 > SVM: NP,NRIP,VClean,AFlush,DAssist,NAsids=32768 > TSC: P-state invariant, performance statistics > > # x86info -a | grep -i micro > Microcode patch level: 0x8001227 > # > > I then ran the fix script. I will let the box grind away over the > weekend to see if it survives. Previously, a couple of hours would lock > it up. I am running it now. One thing I did notice is a bunch of these > showing up > > Jun 14 17:11:18 r11epyc kernel: fpudna: fpcurthread == curthread This is a side effect of enabled eager FPU switch, it's orthogonal and already fixed - the printf has been removed - in current. > > > ---Mike > > -- > --- > Mike Tancsa, tel +1 519 651 3400 x203 > Sentex Communications, m...@sentex.net > Providing Internet services since 1994 www.sentex.net > Cambridge, Ontario Canada > ___ > 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: Ryzen public erratas (and Epyc ?)
On 6/14/2018 11:03 AM, Konstantin Belousov wrote: > I am not sure about only microcode update. Depending on the BIOS > vendor and current BIOS, you may need all three: BIOS update, microcode > update using cpucontrol/devcpu-data, and running the script I posted. > In the best case, some of this is just redundand. OK, before and after shows the same microcode rev CPU: AMD EPYC 7281 16-Core Processor (2100.06-MHz K8-class CPU) Origin="AuthenticAMD" Id=0x800f12 Family=0x17 Model=0x1 Stepping=2 Features=0x178bfbff Features2=0x7ed8320b AMD Features=0x2e500800 AMD Features2=0x35c233ff Structured Extended Features=0x209c01a9 XSAVE Features=0xf AMD Extended Feature Extensions ID EBX=0x1007 SVM: NP,NRIP,VClean,AFlush,DAssist,NAsids=32768 TSC: P-state invariant, performance statistics # x86info -a | grep -i micro Microcode patch level: 0x8001227 # I then ran the fix script. I will let the box grind away over the weekend to see if it survives. Previously, a couple of hours would lock it up. I am running it now. One thing I did notice is a bunch of these showing up Jun 14 17:11:18 r11epyc kernel: fpudna: fpcurthread == curthread ---Mike -- --- Mike Tancsa, tel +1 519 651 3400 x203 Sentex Communications, m...@sentex.net Providing Internet services since 1994 www.sentex.net Cambridge, Ontario Canada ___ 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: RealTek RTL8192E/RTL8192SE Wireless Support
Hans, /boot/modules is indeed empty. I tried both with generic and custom kernels, it makes no difference. kldstat: Id Refs AddressSize Name 11 0x80 1af33b8 kernel /etc/rc.conf kld_list="rtwn.ko" kld_list="rtwnfw.ko" kld_list="rtwn_pci.ko" kld_list="rtwn_usb.ko" Here is dmesg output: MP Table Default Configuration 137 is unsupported Copyright (c) 1992-2018 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 12.0-CURRENT #0: Thu Jun 14 02:55:01 EDT 2018 root@loki:/usr/obj/usr/src/i386.i386/sys/GENERIC i386 FreeBSD clang version 6.0.0 (tags/RELEASE_600/final 326565) (based on LLVM 6.0.0) WARNING: WITNESS option enabled, expect reduced performance. VT(vga): resolution 640x480 CPU: Intel(R) Atom(TM) CPU N280 @ 1.66GHz (1662.54-MHz 686-class CPU) Origin="GenuineIntel" Id=0x106c2 Family=0x6 Model=0x1c Stepping=2 Features=0xbfe9fbff Features2=0x40c39d AMD Features2=0x1 TSC: P-state invariant, performance statistics real memory = 2147483648 (2048 MB) avail memory = 2065616896 (1969 MB) Event timer "LAPIC" quality 100 ACPI APIC Table: FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs FreeBSD/SMP: 1 package(s) x 1 core(s) x 2 hardware threads random: unblocking device. ioapic0: Changing APIC ID to 1 ioapic0 irqs 0-23 on motherboard Launching APs: 1 Timecounter "TSC" frequency 1662535610 Hz quality 1000 random: entropy device external interface [ath_hal] loaded module_register_init: MOD_LOAD (vesa, 0x1602d80, 0) error 19 kbd1 at kbdmux0 nexus0 vtvga0: on motherboard cryptosoft0: on motherboard acpi0: on motherboard acpi0: Power Button (fixed) hpet0: iomem 0xfed0-0xfed003ff on acpi0 Timecounter "HPET" frequency 14318180 Hz quality 950 Event timer "HPET" frequency 14318180 Hz quality 450 Event timer "HPET1" frequency 14318180 Hz quality 440 Event timer "HPET2" frequency 14318180 Hz quality 440 cpu0: on acpi0 atrtc0: port 0x70-0x77 irq 8 on acpi0 atrtc0: Warning: Couldn't map I/O. atrtc0: registered as a time-of-day clock, resolution 1.00s Event timer "RTC" frequency 32768 Hz quality 0 attimer0: port 0x40-0x43,0x50-0x53 irq 0 on acpi0 Timecounter "i8254" frequency 1193182 Hz quality 0 Event timer "i8254" frequency 1193182 Hz quality 100 Timecounter "ACPI-fast" frequency 3579545 Hz quality 900 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x1008-0x100b on acpi0 acpi_ec0: port 0x62,0x66 on acpi0 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 vgapci0: port 0x1800-0x1807 mem 0xf000-0xf007,0xd000-0xdfff,0xf020-0xf023 irq 16 at device 2.0 on pci0 agp0: on vgapci0 agp0: aperture size is 256M, detected 7932k stolen memory vgapci0: Boot video device vgapci1: mem 0xf008-0xf00f at device 2.1 on pci0 hdac0: mem 0xf044-0xf0443fff irq 22 at device 27.0 on pci0 pcib1: irq 17 at device 28.0 on pci0 pcib1: [GIANT-LOCKED] pci1: on pcib1 pci1: at device 0.0 (no driver attached) pcib2: irq 18 at device 28.2 on pci0 pcib2: [GIANT-LOCKED] pci2: on pcib2 re0: port 0x3000-0x30ff mem 0xf051-0xf0510fff,0xf050-0xf050 irq 18 at device 0.0 on pci2 re0: Using 1 MSI-X message re0: ASPM disabled re0: Chip rev. 0x2480 re0: MAC rev. 0x0040 miibus0: on re0 rlphy0: PHY 1 on miibus0 rlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto, auto-flow re0: Using defaults for TSO: 65518/35/2048 re0: Ethernet address: 00:24:54:14:39:5d uhci0: port 0x1820-0x183f irq 23 at device 29.0 on pci0 usbus0 on uhci0 usbus0: 12Mbps Full Speed USB v1.0 uhci1: port 0x1840-0x185f irq 19 at device 29.1 on pci0 usbus1 on uhci1 usbus1: 12Mbps Full Speed USB v1.0 uhci2: port 0x1860-0x187f irq 20 at device 29.2 on pci0 usbus2 on uhci2 usbus2: 12Mbps Full Speed USB v1.0 uhci3: port 0x1880-0x189f irq 16 at device 29.3 on pci0 usbus3 on uhci3 usbus3: 12Mbps Full Speed USB v1.0 ehci0: mem 0xf0444000-0xf04443ff irq 23 at device 29.7 on pci0 usbus4: EHCI version 1.0 usbus4 on ehci0 usbus4: 480Mbps High Speed USB v2.0 pcib3: at device 30.0 on pci0 pci3: on pcib3 isab0: at device 31.0 on pci0 isa0: on isab0 atapci0: port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0x1810-0x181f at device 31.2 on pci0 ata0: at channel 0 on atapci0 ata1: at channel 1 on atapci0 acpi_acad0: on acpi0 acpi_lid0: on acpi0 acpi_button0: on acpi0 acpi_button1: on acpi0 acpi_tz0: on acpi0 atkbdc0: port 0x60,0x64 irq 1 on acpi0 atkbd0: irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] psm0: irq 12 on atkbdc0 psm0: [GIANT-LOCKED] psm0: model Generic PS/2 mouse, device ID 0 battery0: on acpi0 orm0: at iomem 0xdf000-0xd,0xe-0xe17ff pnpid ORM on isa0 ppc0: parallel port not found. est0: on cpu0 Timecounters tick every 1.000 msec hdacc0: at cad 0 on hdac0 hdaa0: at nid 1 on hdacc0 pcm0: at nid 20,21 and 24,25 on hdaa0 ugen1.1: at usbus1 ugen4.1: at usbus4 uhub0:
Re: utilities in /usr/bin or /usr/sbin?
I wrote: >I have three new utilities that are mainly useful for managing the pNFS server >committed as r335130. Oops, I meant r334930, although it doesn't really affect the question. >In the projects tree, I have them in /usr/bin and man section 1. However, >since they are mostly useful to a sysadmin managing the pNFS service, >I'm thinking that maybe they should be in /usr/sbin with man pages in section >8. > >Which of these sounds correct? rick ___ 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"
utilities in /usr/bin or /usr/sbin?
Hi, I have three new utilities that are mainly useful for managing the pNFS server committed as r335130. In the projects tree, I have them in /usr/bin and man section 1. However, since they are mostly useful to a sysadmin managing the pNFS service, I'm thinking that maybe they should be in /usr/sbin with man pages in section 8. Which of these sounds correct? Thanks, rick ___ 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: Ryzen public erratas
On 6/14/2018 11:03 AM, Konstantin Belousov wrote: > I am not sure about only microcode update. Depending on the BIOS > vendor and current BIOS, you may need all three: BIOS update, microcode > update using cpucontrol/devcpu-data, and running the script I posted. > In the best case, some of this is just redundand. Thanks, I will run the tests on the Epyc system over the next few days. It took a little longer to crash the Epyc than the Ryzen. The Ryzen is still going now for 20hrs. Previously 5-10 min were enough to trigger the hard lockup. ---Mike -- --- Mike Tancsa, tel +1 519 651 3400 x203 Sentex Communications, m...@sentex.net Providing Internet services since 1994 www.sentex.net Cambridge, Ontario Canada ___ 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: Ryzen public erratas
On Thu, Jun 14, 2018 at 10:24:17AM -0400, Mike Tancsa wrote: > On 6/14/2018 9:36 AM, Eric van Gyzen wrote: > > On 06/13/2018 05:35, Konstantin Belousov wrote: > >> Today I noted that AMD published the public errata document for Ryzens, > >> https://developer.amd.com/wp-content/resources/55449_1.12.pdf > >> > >> Some of the issues listed there looks quite relevant to the potential > >> hangs that some people still experience with the machines. I wrote > >> a script which should apply the recommended workarounds to the erratas > >> that I find interesting. > >> > >> To run it, kldload cpuctl, then apply the latest firmware update to your > >> CPU, then run the following shell script. Comments indicate the errata > >> number for the workarounds. > >> > >> Please report the results. If the script helps, I will code the kernel > >> change to apply the workarounds. > > Kostik: This thread on the -stable list has a lot of positive feedback: > > > > https://lists.freebsd.org/pipermail/freebsd-stable/2018-June/089110.html > > I have a couple of Epyc boxes that showed the same lockup behaviour. I > will re-install FreeBSD on them and see if their microcode updates fix > this issue as well... I am not sure about only microcode update. Depending on the BIOS vendor and current BIOS, you may need all three: BIOS update, microcode update using cpucontrol/devcpu-data, and running the script I posted. In the best case, some of this is just redundand. > > Should I run the same cpuctl commands on those CPUs ? BTW, I am happy > to loan one out to you in the FreeBSD netperf cluster for a few weeks > > ---Mike > > > > -- > --- > Mike Tancsa, tel +1 519 651 3400 x203 > Sentex Communications, m...@sentex.net > Providing Internet services since 1994 www.sentex.net > Cambridge, Ontario Canada ___ 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: Ryzen public erratas
On 6/14/2018 9:36 AM, Eric van Gyzen wrote: > On 06/13/2018 05:35, Konstantin Belousov wrote: >> Today I noted that AMD published the public errata document for Ryzens, >> https://developer.amd.com/wp-content/resources/55449_1.12.pdf >> >> Some of the issues listed there looks quite relevant to the potential >> hangs that some people still experience with the machines. I wrote >> a script which should apply the recommended workarounds to the erratas >> that I find interesting. >> >> To run it, kldload cpuctl, then apply the latest firmware update to your >> CPU, then run the following shell script. Comments indicate the errata >> number for the workarounds. >> >> Please report the results. If the script helps, I will code the kernel >> change to apply the workarounds. > Kostik: This thread on the -stable list has a lot of positive feedback: > > https://lists.freebsd.org/pipermail/freebsd-stable/2018-June/089110.html I have a couple of Epyc boxes that showed the same lockup behaviour. I will re-install FreeBSD on them and see if their microcode updates fix this issue as well... Should I run the same cpuctl commands on those CPUs ? BTW, I am happy to loan one out to you in the FreeBSD netperf cluster for a few weeks ---Mike -- --- Mike Tancsa, tel +1 519 651 3400 x203 Sentex Communications, m...@sentex.net Providing Internet services since 1994 www.sentex.net Cambridge, Ontario Canada ___ 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: RealTek RTL8192E/RTL8192SE Wireless Support
On 06/14/18 12:15, Stephen Albright wrote: Pete, That did not work either. interestingly enough, they did not load after reboot. 'kldstat' reports 'kernel' as the only thing loaded. Is /boot/modules empty? Are there any errors in dmesg? --HPS ___ 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: Ryzen public erratas
On 06/13/2018 05:35, Konstantin Belousov wrote: > Today I noted that AMD published the public errata document for Ryzens, > https://developer.amd.com/wp-content/resources/55449_1.12.pdf > > Some of the issues listed there looks quite relevant to the potential > hangs that some people still experience with the machines. I wrote > a script which should apply the recommended workarounds to the erratas > that I find interesting. > > To run it, kldload cpuctl, then apply the latest firmware update to your > CPU, then run the following shell script. Comments indicate the errata > number for the workarounds. > > Please report the results. If the script helps, I will code the kernel > change to apply the workarounds. Kostik: This thread on the -stable list has a lot of positive feedback: https://lists.freebsd.org/pipermail/freebsd-stable/2018-June/089110.html Eric ___ 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: RealTek RTL8192E/RTL8192SE Wireless Support
Pete, That did not work either. interestingly enough, they did not load after reboot. 'kldstat' reports 'kernel' as the only thing loaded. Stephen On Wed, Jun 13, 2018 at 9:20 PM, Stephen Albright wrote: > Hi Pete, > > I did not try in /etc/rc.conf. I did however try with GENERIC and use > kldload and kldstat listed them as loaded. I will try the rc.conf method > momentarily. > > Stephen > > On Wed, Jun 13, 2018 at 9:12 PM, Pete Wright wrote: > >> >> >> On 06/13/2018 17:31, Stephen Albright wrote: >> >>> Hello All: >>> >>> I have a Samsung NP-N140 with a RTL8192E card and I am having difficulty >>> with it. I am running -current because if I read the man pages >>> correctly, >>> only 12-Current has the driver in rtwn (from the rtwn(4) man page). So, >>> I >>> built a custom kernel per the man pages: >>> >> >> >> out of curiosity have you attempted to boot 12-CURRENT with the stock >> GENERIC kernel and attempt to load the kernel module by hand or via >> /etc/rc.conf? >> >> for example you could create this line in /etc/rc.conf: >> kld_list="rtwn.ko" >> >> then verify it is loaded after reboot by running "kldstat". >> >> cheers, >> -pete >> >> -- >> Pete Wright >> p...@nomadlogic.org >> @nomadlogicLA >> >> > ___ 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"
