custom syspatch
Suppose I want to add a custom patch to a release system (backport patch from
current and compile on release),
but keep the system able to load more official syspatches:
is it enough to put the relevant new object file (say pf.o) in
/usr/share/relink/kernel/GENERIC.MP/
and just do reorder_kernel?
The new object will come from manually compiling release sources kernel with
specific patch backported from current (on another machine).
I took for example syspatch74-009_pf.tgz
Apart from the pf.o I also see vers.o and gap.o
Should I also provide a new gap.o? I don't understand what this does.
In Makefile I see
newbsd:
${MAKE_GAP}
${SYSTEM_LD_HEAD}
${SYSTEM_LD} swapgeneric.o
${SYSTEM_LD_TAIL}
rm -f bsd.gdb
mv -f newbsd bsd
so makegap.sh is run from ${MAKE_GAP} which seems to provide a new gap.o
Thanks,
G
Re: 7.5 install crashes on "entry point at 0x1001000" HP Elitebook 840 G10
Hi, I had a silimar issue on a Lenovo V130. For this machine I needed to remove the amdgpu driver in the kernel. See also: https://marc.info/?l=openbsd-misc&m=160232897421774&w=2 https://marc.info/?l=openbsd-tech&m=160383074317608&w=2 Do you get the error "entry point at 0x1001000" also with the bsd.rd kernel or only after you installed the system with the bsd.mp/bsd.sp kernel? Best regards, Sven On 5/23/24 22:40, Comète wrote: Hello, I tried to install OpenBSD 7.5 on a new HP Elitebook 840 G10 (UEFI capable only) without success. It is stuck at boot on "entry point at 0x1001000". Even retried after a BIOS upgrade but no luck either. I tried with a snapshot install too with the same result. I post here what lspci returns from a debian bookworm: 00:00.0 Host bridge: Intel Corporation Device a706 00:02.0 VGA compatible controller: Intel Corporation Raptor Lake-P [Iris Xe Graphics] (rev 04) 00:04.0 Signal processing controller: Intel Corporation Raptor Lake Dynamic Platform and Thermal Framework Processor Participant 00:06.0 PCI bridge: Intel Corporation Raptor Lake PCIe 4.0 Graphics Port 00:06.2 PCI bridge: Intel Corporation Device a73d 00:07.0 PCI bridge: Intel Corporation Raptor Lake-P Thunderbolt 4 PCI Express Root Port 00:07.2 PCI bridge: Intel Corporation Raptor Lake-P Thunderbolt 4 PCI Express Root Port 00:08.0 System peripheral: Intel Corporation GNA Scoring Accelerator module 00:0a.0 Signal processing controller: Intel Corporation Raptor Lake Crashlog and Telemetry (rev 01) 00:0d.0 USB controller: Intel Corporation Raptor Lake-P Thunderbolt 4 USB Controller 00:0d.2 USB controller: Intel Corporation Raptor Lake-P Thunderbolt 4 NHI 00:0d.3 USB controller: Intel Corporation Raptor Lake-P Thunderbolt 4 NHI 00:14.0 USB controller: Intel Corporation Alder Lake PCH USB 3.2 xHCI Host Controller (rev 01) 00:14.2 RAM memory: Intel Corporation Alder Lake PCH Shared SRAM (rev 01) 00:14.3 Network controller: Intel Corporation Raptor Lake PCH CNVi WiFi (rev 01) 00:15.0 Serial bus controller: Intel Corporation Alder Lake PCH Serial IO I2C Controller #0 (rev 01) 00:16.0 Communication controller: Intel Corporation Alder Lake PCH HECI Controller (rev 01) 00:16.3 Serial controller: Intel Corporation Alder Lake AMT SOL Redirection (rev 01) 00:1c.0 PCI bridge: Intel Corporation Alder Lake PCH-P PCI Express Root Port #9 (rev 01) 00:1e.0 Communication controller: Intel Corporation Alder Lake PCH UART #0 (rev 01) 00:1e.2 Serial bus controller: Intel Corporation Alder Lake SPI Controller (rev 01) 00:1f.0 ISA bridge: Intel Corporation Raptor Lake LPC/eSPI Controller (rev 01) 00:1f.3 Multimedia audio controller: Intel Corporation Raptor Lake-P/U/H cAVS (rev 01) 00:1f.4 SMBus: Intel Corporation Alder Lake PCH-P SMBus Host Controller (rev 01) 00:1f.5 Serial bus controller: Intel Corporation Alder Lake-P PCH SPI Controller (rev 01) 02:00.0 Non-Volatile memory controller: SK hynix BC901 NVMe Solid State Drive (DRAM-less) (rev 03) 57:00.0 Wireless controller [0d40]: Intel Corporation XMM7560 LTE Advanced Pro Modem (rev 01) Thanks for your help. Comete
Re: advice debugging lockups with swap-thrashing symptoms?
You are probably haunted by a bad issue with DMA memory and running out of it. Your top is missing -SH since then you would probably see the pagedameon go bananas. The problem is you have not enough memory below 4G but the pagedaemon is not able to properly free memory there since it has no proper tracking for that condition. It only knows memory is short and tries to drop as much as possible over and over again. As a result your system becomes unresponsive. The boot loader can print the memory map. Which should show you how much memory is below 4G (I think the command is machine mem). This is a known issue and there is some work going on to fix the problem. -- :wq Claudio Thanks, Claudio. Let me know if I can help by testing anything. In case it's useful, here is the output of "machine memory" at the boot prompt. Transcribed by hand so there are probably errors. boot> machine memory Region 0: type 1 at 0x0 for 609KB Region 1: type 2 at 0xf for 64KB Region 2: type 2 at 0xfec0 for 20480KB Region 3: type 2 at 0xe000 for 262144KB Region 4: type 2 at 0x98400 for 31KB Region 5: type 2 at 0xcfdf for 64KB Region 6: type 1 at 0x10 for 3404292KB Region 7: type 3 at 0xcfde3000 for 52KB Region 8: type 4 at 0xcfde for 12KB REgion 9: type 1 at 0x1 for 13369344KB Low ram: 609KB High ram: 3404292KB Total free memory: 16774245KB -- James
7.5 install crashes on "entry point at 0x1001000" HP Elitebook 840 G10
Hello, I tried to install OpenBSD 7.5 on a new HP Elitebook 840 G10 (UEFI capable only) without success. It is stuck at boot on "entry point at 0x1001000". Even retried after a BIOS upgrade but no luck either. I tried with a snapshot install too with the same result. I post here what lspci returns from a debian bookworm: 00:00.0 Host bridge: Intel Corporation Device a706 00:02.0 VGA compatible controller: Intel Corporation Raptor Lake-P [Iris Xe Graphics] (rev 04) 00:04.0 Signal processing controller: Intel Corporation Raptor Lake Dynamic Platform and Thermal Framework Processor Participant 00:06.0 PCI bridge: Intel Corporation Raptor Lake PCIe 4.0 Graphics Port 00:06.2 PCI bridge: Intel Corporation Device a73d 00:07.0 PCI bridge: Intel Corporation Raptor Lake-P Thunderbolt 4 PCI Express Root Port 00:07.2 PCI bridge: Intel Corporation Raptor Lake-P Thunderbolt 4 PCI Express Root Port 00:08.0 System peripheral: Intel Corporation GNA Scoring Accelerator module 00:0a.0 Signal processing controller: Intel Corporation Raptor Lake Crashlog and Telemetry (rev 01) 00:0d.0 USB controller: Intel Corporation Raptor Lake-P Thunderbolt 4 USB Controller 00:0d.2 USB controller: Intel Corporation Raptor Lake-P Thunderbolt 4 NHI 00:0d.3 USB controller: Intel Corporation Raptor Lake-P Thunderbolt 4 NHI 00:14.0 USB controller: Intel Corporation Alder Lake PCH USB 3.2 xHCI Host Controller (rev 01) 00:14.2 RAM memory: Intel Corporation Alder Lake PCH Shared SRAM (rev 01) 00:14.3 Network controller: Intel Corporation Raptor Lake PCH CNVi WiFi (rev 01) 00:15.0 Serial bus controller: Intel Corporation Alder Lake PCH Serial IO I2C Controller #0 (rev 01) 00:16.0 Communication controller: Intel Corporation Alder Lake PCH HECI Controller (rev 01) 00:16.3 Serial controller: Intel Corporation Alder Lake AMT SOL Redirection (rev 01) 00:1c.0 PCI bridge: Intel Corporation Alder Lake PCH-P PCI Express Root Port #9 (rev 01) 00:1e.0 Communication controller: Intel Corporation Alder Lake PCH UART #0 (rev 01) 00:1e.2 Serial bus controller: Intel Corporation Alder Lake SPI Controller (rev 01) 00:1f.0 ISA bridge: Intel Corporation Raptor Lake LPC/eSPI Controller (rev 01) 00:1f.3 Multimedia audio controller: Intel Corporation Raptor Lake-P/U/H cAVS (rev 01) 00:1f.4 SMBus: Intel Corporation Alder Lake PCH-P SMBus Host Controller (rev 01) 00:1f.5 Serial bus controller: Intel Corporation Alder Lake-P PCH SPI Controller (rev 01) 02:00.0 Non-Volatile memory controller: SK hynix BC901 NVMe Solid State Drive (DRAM-less) (rev 03) 57:00.0 Wireless controller [0d40]: Intel Corporation XMM7560 LTE Advanced Pro Modem (rev 01) Thanks for your help. Comete
Re: Q: Problems forwarding traffic using pf ...
On Thu, May 23, 2024 at 08:24:03PM +0300, Kapetanakis Giannis wrote: > On 23/05/2024 20:18, Peter N. M. Hansteen wrote: > > On Thu, May 23, 2024 at 11:14:20AM +0200, Why 42? The lists account. wrote: > > > I need to quickly create a solution for forwarding multicast traffic > > > between two systems, so I though perhaps I could use pf to do just that > > > by writing some rules along the lines of: > > > > > > 1. pass in on iface A proto UDP ... tag mcast > > > 2. pass out on iface B tagged mcast > > > > > > And another pair of rules for the reverse direction B -> A. > > > > > > (Obviously I'd add more options to filter specific addresses, etc.) > > Possibly stupid question, but did you set the sysctl(s) to enable > > forwarding? > > > > $ sysctl net.inet.ip.forwarding > > > > and > > > > $ sysctl net.inet6.ip6.forwarding > > > > will provide the answer (as in, if those values are not 1, forwarding > > between interfaces is not enabled) > > > > > And there is also mforwarding > > net.inet.ip.forwarding > net.inet.ip.mforwarding > net.inet6.ip6.forwarding > net.inet6.ip6.mforwarding > > G > And multicast=YES rc.conf.local --
Re: Q: Problems forwarding traffic using pf ...
On 23/05/2024 20:18, Peter N. M. Hansteen wrote: On Thu, May 23, 2024 at 11:14:20AM +0200, Why 42? The lists account. wrote: I need to quickly create a solution for forwarding multicast traffic between two systems, so I though perhaps I could use pf to do just that by writing some rules along the lines of: 1. pass in on iface A proto UDP ... tag mcast 2. pass out on iface B tagged mcast And another pair of rules for the reverse direction B -> A. (Obviously I'd add more options to filter specific addresses, etc.) Possibly stupid question, but did you set the sysctl(s) to enable forwarding? $ sysctl net.inet.ip.forwarding and $ sysctl net.inet6.ip6.forwarding will provide the answer (as in, if those values are not 1, forwarding between interfaces is not enabled) And there is also mforwarding net.inet.ip.forwarding net.inet.ip.mforwarding net.inet6.ip6.forwarding net.inet6.ip6.mforwarding G
Re: Q: Problems forwarding traffic using pf ...
On Thu, May 23, 2024 at 11:14:20AM +0200, Why 42? The lists account. wrote: > I need to quickly create a solution for forwarding multicast traffic > between two systems, so I though perhaps I could use pf to do just that > by writing some rules along the lines of: > > 1. pass in on iface A proto UDP ... tag mcast > 2. pass out on iface B tagged mcast > > And another pair of rules for the reverse direction B -> A. > > (Obviously I'd add more options to filter specific addresses, etc.) Possibly stupid question, but did you set the sysctl(s) to enable forwarding? $ sysctl net.inet.ip.forwarding and $ sysctl net.inet6.ip6.forwarding will provide the answer (as in, if those values are not 1, forwarding between interfaces is not enabled) -- Peter N. M. Hansteen, member of the first RFC 1149 implementation team https://bsdly.blogspot.com/ https://www.bsdly.net/ https://www.nuug.no/ "Remember to set the evil bit on all malicious network traffic" delilah spamd[29949]: 85.152.224.147: disconnected after 42673 seconds.
Re: advice debugging lockups with swap-thrashing symptoms?
On Thu, May 23, 2024 at 03:37:24PM +, James Cook wrote: > On Thu, May 23, 2024 at 08:00:37AM GMT, Nick Holland wrote: > > On 5/23/24 03:18, Stuart Henderson wrote: > > > On 2024-05-22, James Cook wrote: > > > > One of my OpenBSD boxes sometimes gets in a weird locked-up or > > > > almost-locked-up state. I'm wondering what I can do to debug it > > > > further next time it happens. > > > ... > > > > I would also expect the cache number to be much higher. E.g. on > > > > this occasion, I was running "git annex fsck", which reads plenty > > > > of data from disk. > > > > > > Heavy filesystem access can result in this sort of thing, I used to > > > have unpacked ports source on one of my machines for grepping over, > > > the machine was pretty much unusable for anything else while that was > > > running. > > > > > > Might be worth trying some noatime mount flags if you don't already have > > > them, at least then you can avoid turning some reads into writes. > > > > > > > Definitely a possibility. Long time ago, I think I asked about the > > possibility of a "disknice" to throttle disk access on individual > > tasks. TedU@ came through for me with something that definitely solved > > my problem, and I use it from time to time since -- basically, it just > > suspends a particular program occasionally, which lets other programs > > have a chance to get disk access. I saved it (and made a tiny update > > that is needed now) and put it here: > > > > https://holland-consulting.net/scripts/disknice.html > > > > > > Also... > > I've seen disks "fail" where they get super-slow. The failure modes > > seems to be difficulty reading data...but after enough retries, it > > succeeds, resetting the retry counter back to zero, and then the next > > read encounters the same problem. You may be able to hear lots of > > activity on the drive with little obvious progress. I'm not convinced > > this is your problem, but ... something to consider. > > > > Nick. > > Thanks for the pointers. disknice sounds useful. However I am skeptical that > this can be explained away as a normal consequence of intense filesystem > access, for a few reasons. > > 1. In the past, even the mouse pointer has frozen. (I'm 95% sure of this > from memory. Will note it more carefully next time this happens.) Surely > that shouldn't depend on disk access? See also tmux/xterm updating very > slowly; does that depend on the filesystem? > > 2. The low 165M cache number makes me suspicious. With 14G free and plenty > of data being read, shouldn't that grow? E.g. right now it's at 11G (and I'm > running git annex fsck like I was before; I have a lot of data to fsck). I > believe I've seen similar small cache numbers in the past. > > 3. The git annex fsck was running on a different hard disk. (Normally it > sits in a cubpoard; I've hooked it up temporarily.) Swap, /, /home etc are > all on a different SSD. I am running the same thing now (different disk) and > perceive no impact on performance. That's not to say there wasn't intense > access to the SSD, though; Firefox is a suspect here. > > Nonetheless, if I can't make any other progress, I'll look into noatime > and/or disknice. (I really wish I could reliably reproduce this, but > unfortunately it just happens every few days or weeks with no apparent > pattern other than the system being under some load when it happens.) > > (I'll note one other thing, just in case: I also experience random crashes > and restarts with this machine that seem to be hardware-related. Very > different from what I'm describing here; has even happened during BIOS POST, > and with no disks inside the machine. I just mention it because it opens the > possibility of unreliable hardware involved, in case that changes things.) > You are probably haunted by a bad issue with DMA memory and running out of it. Your top is missing -SH since then you would probably see the pagedameon go bananas. The problem is you have not enough memory below 4G but the pagedaemon is not able to properly free memory there since it has no proper tracking for that condition. It only knows memory is short and tries to drop as much as possible over and over again. As a result your system becomes unresponsive. The boot loader can print the memory map. Which should show you how much memory is below 4G (I think the command is machine mem). This is a known issue and there is some work going on to fix the problem. -- :wq Claudio
Re: advice debugging lockups with swap-thrashing symptoms?
On Thu, May 23, 2024 at 08:00:37AM GMT, Nick Holland wrote: On 5/23/24 03:18, Stuart Henderson wrote: On 2024-05-22, James Cook wrote: One of my OpenBSD boxes sometimes gets in a weird locked-up or almost-locked-up state. I'm wondering what I can do to debug it further next time it happens. ... I would also expect the cache number to be much higher. E.g. on this occasion, I was running "git annex fsck", which reads plenty of data from disk. Heavy filesystem access can result in this sort of thing, I used to have unpacked ports source on one of my machines for grepping over, the machine was pretty much unusable for anything else while that was running. Might be worth trying some noatime mount flags if you don't already have them, at least then you can avoid turning some reads into writes. Definitely a possibility. Long time ago, I think I asked about the possibility of a "disknice" to throttle disk access on individual tasks. TedU@ came through for me with something that definitely solved my problem, and I use it from time to time since -- basically, it just suspends a particular program occasionally, which lets other programs have a chance to get disk access. I saved it (and made a tiny update that is needed now) and put it here: https://holland-consulting.net/scripts/disknice.html Also... I've seen disks "fail" where they get super-slow. The failure modes seems to be difficulty reading data...but after enough retries, it succeeds, resetting the retry counter back to zero, and then the next read encounters the same problem. You may be able to hear lots of activity on the drive with little obvious progress. I'm not convinced this is your problem, but ... something to consider. Nick. Thanks for the pointers. disknice sounds useful. However I am skeptical that this can be explained away as a normal consequence of intense filesystem access, for a few reasons. 1. In the past, even the mouse pointer has frozen. (I'm 95% sure of this from memory. Will note it more carefully next time this happens.) Surely that shouldn't depend on disk access? See also tmux/xterm updating very slowly; does that depend on the filesystem? 2. The low 165M cache number makes me suspicious. With 14G free and plenty of data being read, shouldn't that grow? E.g. right now it's at 11G (and I'm running git annex fsck like I was before; I have a lot of data to fsck). I believe I've seen similar small cache numbers in the past. 3. The git annex fsck was running on a different hard disk. (Normally it sits in a cubpoard; I've hooked it up temporarily.) Swap, /, /home etc are all on a different SSD. I am running the same thing now (different disk) and perceive no impact on performance. That's not to say there wasn't intense access to the SSD, though; Firefox is a suspect here. Nonetheless, if I can't make any other progress, I'll look into noatime and/or disknice. (I really wish I could reliably reproduce this, but unfortunately it just happens every few days or weeks with no apparent pattern other than the system being under some load when it happens.) (I'll note one other thing, just in case: I also experience random crashes and restarts with this machine that seem to be hardware-related. Very different from what I'm describing here; has even happened during BIOS POST, and with no disks inside the machine. I just mention it because it opens the possibility of unreliable hardware involved, in case that changes things.) -- James
Re: How to assign apps to cwm groups?
On 2024-05-23 22:07:27, Sadeep Madurange wrote: > I'm trying to assign xterm to group 1 and firefox to group 2. Then, > I'd like to only see a specific group at any given time. > > After logging in, I start xterm. Then I start firefox. Problem is > firefox opens right on top of my terminal. I expected it to open in > group 2 such that either it's not visible till I press 4+2 or start > firefox in group 2 and move me to group 2 automatically. Is that not > how groups work? > > Also, with the config below and firefox and terminal open, when I > press 4+1 nothing happens (I still see firefox and xterm stacked). > When I press 4+2, both windows disappears. > > Can someone please let me know how I can configure groups to work a > little like workspaces in i3, if that's possible? Actually, it seems to be working. Not sure what I did, but works as expected with the following config. sticky no autogroup 1"xterm,XTerm" autogroup 2"Firefox" # Commands command mail "xterm -e 'cd ~/Downloads && mutt -F ~/.mutt/muttrc'" command firefoxfirefox bind-key 4-Returnterminal bind-key 4-d menu-cmd bind-key 4S-rrestart bind-key 4S-equit bind-key 4S-qwindow-close bind-key 4-1group-only-1 bind-key 4-2group-only-2 bind-key 4-3group-only-3 bind-key 4-4group-only-4 bind-key 4-5group-only-5 bind-key 4-6group-only-6 bind-key 4-7group-only-7 bind-key 4-8group-only-8 bind-key 4-9group-only-9 bind-key 4S-1 window-movetogroup-1 bind-key 4S-2 window-movetogroup-2 bind-key 4S-3 window-movetogroup-3 bind-key 4S-4 window-movetogroup-4 bind-key 4S-5 window-movetogroup-5 bind-key 4S-6 window-movetogroup-6 bind-key 4S-7 window-movetogroup-7 bind-key 4S-8 window-movetogroup-8 bind-key 4S-9 window-movetogroup-9 # Mouse bindings bind-mouse M-2 window-lower bind-mouse M-3 window-resize -- Sadeep Madurange PGP: 103BF9E3E750BF7E
How to assign apps to cwm groups?
Hello, I'm trying to assign xterm to group 1 and firefox to group 2. Then, I'd like to only see a specific group at any given time. After logging in, I start xterm. Then I start firefox. Problem is firefox opens right on top of my terminal. I expected it to open in group 2 such that either it's not visible till I press 4+2 or start firefox in group 2 and move me to group 2 automatically. Is that not how groups work? Also, with the config below and firefox and terminal open, when I press 4+1 nothing happens (I still see firefox and xterm stacked). When I press 4+2, both windows disappears. Can someone please let me know how I can configure groups to work a little like workspaces in i3, if that's possible? cwmrc content: sticky no bind-key 4-Return "terminal" bind-key 4-d "menu-exec" bind-key 4S-r "restart" bind-key 4S-e "quit" bind-key 4S-q "window-close" bind-key 4-1 "group-only-1" bind-key 4-2 "group-only-2" bind-key 4-3 "group-only-3" # Groups autogroup 1 "xterm,XTerm" autogroup 2 "Firefox" # Mouse bindings bind-mouse M-2 window-lower bind-mouse M-3 window-resize -- Sadeep Madurange PGP: 103BF9E3E750BF7E
Re: Sudden reboot every 5-10 minutes on latest snapshot
On 2024/05/23 12:12, Ali Farzanrad wrote: > Hi Stuart, > > Stuart Henderson wrote: > > On 2024-05-23, Ali Farzanrad wrote: > > > Hi misc@, > > > > > > My Minisforum UM790 keeps reboot every 5-10 minutes, without any Kernel > > > Panic or visible message how may I debug it? > > > I'm using latest OpenBSD snapshot with this amd64/BUILDINFO: > > > Build date: 1716424636 - Thu May 23 00:37:16 UTC 2024 > > > > Not a lot to go on really. > > > > Is the machine doing anything or just idle? > > It get reboot even in xenodm login screen without any interaction from me. > > > Is X running? > > It's funny. I disabled the xenodm and it lived for more than 10 minutes; > then I enabled and started xenodm and it suddenly rebooted after few > minutes! > > Next time I keep xenodm running, but switched to ttyC0 terminal using > Alt+Ctrl+F1 key and it lived for more than 10 minutes; then I just > switched to Xorg using Alt+Ctrl+F5 and it suddenly rebooted again after > few minutes! > > > Do you get the same with 7.5? if yes, try older releases - can you > > find one where it doesn't happen? > > I rarely got same issue in previous snapshots (I think my last snapshot > was for 6 days ago and I had no serious issue with that). > > I think I sould compile and test previous versions of xenocara, right? Try with just an older kernel first and leave userland alone. ftp.hostserver.de and openbsd.cs.toronto.edu both have some old snaps in /archive. (If no snap was built on a certain day then the files will be identical in the archive so no point testing when there was no change - you can use what(1) to show the version - I'd save a few under names like /bsd.mp. and type "boot bsd.mp." at the boot loader). > > > > > > # (dmesg; sysctl hw.sensors) > > > OpenBSD 7.5-current (GENERIC.MP) #78: Wed May 22 18:31:14 MDT 2024 > > > dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP > > > real mem = 31909883904 (30431MB) > > > avail mem = 30921310208 (29488MB) > > > random: good seed from bootblocks > > > mpath0 at root > > > scsibus0 at mpath0: 256 targets > > > mainbus0 at root > > > bios0 at mainbus0: SMBIOS rev. 3.5 @ 0x9ab7f000 (45 entries) > > > bios0: vendor American Megatrends International, LLC. version "1.01" date > > > 06/05/2023 > > > bios0: Micro Computer (HK) Tech Limited F7BSC > > > efi0 at bios0: UEFI 2.8 > > > efi0: American Megatrends rev 0x5001d > > > acpi0 at bios0: ACPI 6.4 > > > acpi0: sleep states S0 S4 S5 > > > acpi0: tables DSDT FACP SSDT SSDT FIDT MCFG FPDT VFCT BGRT TPM2 SSDT CRAT > > > CDIT SSDT SSDT SSDT SSDT SSDT SSDT SSDT SSDT SSDT WSMT APIC IVRS SSDT > > > SSDT SSDT SSDT SSDT SSDT SSDT SSDT SSDT SSDT > > > acpi0: wakeup devices GPP1(S4) GPP0(S4) GPP5(S4) GPP7(S4) GP11(S4) > > > SWUS(S4) GP12(S4) SWUS(S4) > > > acpitimer0 at acpi0: 3579545 Hz, 32 bits > > > acpimcfg0 at acpi0 > > > acpimcfg0: addr 0xe000, bus 0-255 > > > acpimadt0 at acpi0 addr 0xfee0: PC-AT compat > > > cpu0 at mainbus0: apid 0 (boot processor) > > > cpu0: AMD Ryzen 9 7940HS w/ Radeon 780M Graphics, 4000.00 MHz, 19-74-01, > > > patch 0a704101 > > > cpu0: cpuid 1 > > > edx=178bfbff > > > > > > ecx=76f8320b > > > cpu0: cpuid 6 eax=4 ecx=1 > > > cpu0: cpuid 7.0 > > > ebx=f1bf97a9 > > > ecx=405fce edx=1000 > > > cpu0: cpuid d.1 eax=f > > > cpu0: cpuid 8001 edx=2fd3fbff > > > ecx=75c237ff > > > cpu0: cpuid 8007 edx=e799 > > > cpu0: cpuid 8008 > > > ebx=791ef257 > > > cpu0: 32KB 64b/line 8-way D-cache, 32KB 64b/line 8-way I-cache, 1MB > > > 64b/line 8-way L2 cache, 16MB 64b/line 16-way L3 cache > > > cpu0: smt 0, core 0, package 0 > > > mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges > > > cpu0: apic clock running at 24MHz > > > cpu0: mwait min=64, max=64, C-substates=1.1, IBE > > > cpu1 at mainbus0: apid 2 (application processor) > > > cpu1: AMD Ryzen 9 7940HS w/ Radeon 780M Graphics, 4000.00 MHz, 19-74-01, > > > patch 0a704101 > > > cpu1: smt 0, core 1, package 0 > > > cpu2 at mainbus0: apid 4 (application processor) > > > cpu2: AMD Ryzen 9 7940HS w/ Radeon 780M Graphics, 4000.00 MHz, 19-74-01, > > > patch 0a704101 > > > cpu2: smt 0, core 2, package 0 > > > cpu3 at mainbus0: apid 6 (application processor) > > > cpu3: AMD Ryzen 9 7940HS w/ Radeon 780M Graphics, 4000.00 MHz, 19-74-01, > > > patch 0a704101 > > > cpu3: smt 0, core 3, package 0 > > > cpu4 at mainbus0: apid 8 (application processor) > > > cpu4: AMD Ryzen 9 7940HS w/ Radeon 780M Graphics, 4000.00 MHz, 19-74-01, > > > patch 0a704101 > > > cpu4: smt 0, core 4, package 0 > > > cpu5 at mainbus0: apid 10 (application processor) > > > cpu5: AMD Ryzen 9 7940HS w/ Radeon 780M Graphics, 4000.00 MHz, 19-74-01, > > > patch 0a704101 > > > cpu5: smt 0, core 5, package 0 > > > cpu6 at mainbus0: apid 12 (application processor) > > > cpu6: AMD Ryzen 9 7940HS w/ Radeon 780M Graphics, 4000.00 MHz, 19-74-01, > > > patch 0a704101 > > > cpu6: smt 0, core 6, package 0 > > > cpu7 at mainbus0: apid 14 (application proce
Re: Sudden reboot every 5-10 minutes on latest snapshot
Hi Stuart, Stuart Henderson wrote: > On 2024-05-23, Ali Farzanrad wrote: > > Hi misc@, > > > > My Minisforum UM790 keeps reboot every 5-10 minutes, without any Kernel > > Panic or visible message how may I debug it? > > I'm using latest OpenBSD snapshot with this amd64/BUILDINFO: > > Build date: 1716424636 - Thu May 23 00:37:16 UTC 2024 > > Not a lot to go on really. > > Is the machine doing anything or just idle? It get reboot even in xenodm login screen without any interaction from me. > Is X running? It's funny. I disabled the xenodm and it lived for more than 10 minutes; then I enabled and started xenodm and it suddenly rebooted after few minutes! Next time I keep xenodm running, but switched to ttyC0 terminal using Alt+Ctrl+F1 key and it lived for more than 10 minutes; then I just switched to Xorg using Alt+Ctrl+F5 and it suddenly rebooted again after few minutes! > Do you get the same with 7.5? if yes, try older releases - can you > find one where it doesn't happen? I rarely got same issue in previous snapshots (I think my last snapshot was for 6 days ago and I had no serious issue with that). I think I sould compile and test previous versions of xenocara, right? > > > > # (dmesg; sysctl hw.sensors) > > OpenBSD 7.5-current (GENERIC.MP) #78: Wed May 22 18:31:14 MDT 2024 > > dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP > > real mem = 31909883904 (30431MB) > > avail mem = 30921310208 (29488MB) > > random: good seed from bootblocks > > mpath0 at root > > scsibus0 at mpath0: 256 targets > > mainbus0 at root > > bios0 at mainbus0: SMBIOS rev. 3.5 @ 0x9ab7f000 (45 entries) > > bios0: vendor American Megatrends International, LLC. version "1.01" date > > 06/05/2023 > > bios0: Micro Computer (HK) Tech Limited F7BSC > > efi0 at bios0: UEFI 2.8 > > efi0: American Megatrends rev 0x5001d > > acpi0 at bios0: ACPI 6.4 > > acpi0: sleep states S0 S4 S5 > > acpi0: tables DSDT FACP SSDT SSDT FIDT MCFG FPDT VFCT BGRT TPM2 SSDT CRAT > > CDIT SSDT SSDT SSDT SSDT SSDT SSDT SSDT SSDT SSDT WSMT APIC IVRS SSDT SSDT > > SSDT SSDT SSDT SSDT SSDT SSDT SSDT SSDT > > acpi0: wakeup devices GPP1(S4) GPP0(S4) GPP5(S4) GPP7(S4) GP11(S4) SWUS(S4) > > GP12(S4) SWUS(S4) > > acpitimer0 at acpi0: 3579545 Hz, 32 bits > > acpimcfg0 at acpi0 > > acpimcfg0: addr 0xe000, bus 0-255 > > acpimadt0 at acpi0 addr 0xfee0: PC-AT compat > > cpu0 at mainbus0: apid 0 (boot processor) > > cpu0: AMD Ryzen 9 7940HS w/ Radeon 780M Graphics, 4000.00 MHz, 19-74-01, > > patch 0a704101 > > cpu0: cpuid 1 > > edx=178bfbff > > > > ecx=76f8320b > > cpu0: cpuid 6 eax=4 ecx=1 > > cpu0: cpuid 7.0 > > ebx=f1bf97a9 > > ecx=405fce edx=1000 > > cpu0: cpuid d.1 eax=f > > cpu0: cpuid 8001 edx=2fd3fbff > > ecx=75c237ff > > cpu0: cpuid 8007 edx=e799 > > cpu0: cpuid 8008 > > ebx=791ef257 > > cpu0: 32KB 64b/line 8-way D-cache, 32KB 64b/line 8-way I-cache, 1MB > > 64b/line 8-way L2 cache, 16MB 64b/line 16-way L3 cache > > cpu0: smt 0, core 0, package 0 > > mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges > > cpu0: apic clock running at 24MHz > > cpu0: mwait min=64, max=64, C-substates=1.1, IBE > > cpu1 at mainbus0: apid 2 (application processor) > > cpu1: AMD Ryzen 9 7940HS w/ Radeon 780M Graphics, 4000.00 MHz, 19-74-01, > > patch 0a704101 > > cpu1: smt 0, core 1, package 0 > > cpu2 at mainbus0: apid 4 (application processor) > > cpu2: AMD Ryzen 9 7940HS w/ Radeon 780M Graphics, 4000.00 MHz, 19-74-01, > > patch 0a704101 > > cpu2: smt 0, core 2, package 0 > > cpu3 at mainbus0: apid 6 (application processor) > > cpu3: AMD Ryzen 9 7940HS w/ Radeon 780M Graphics, 4000.00 MHz, 19-74-01, > > patch 0a704101 > > cpu3: smt 0, core 3, package 0 > > cpu4 at mainbus0: apid 8 (application processor) > > cpu4: AMD Ryzen 9 7940HS w/ Radeon 780M Graphics, 4000.00 MHz, 19-74-01, > > patch 0a704101 > > cpu4: smt 0, core 4, package 0 > > cpu5 at mainbus0: apid 10 (application processor) > > cpu5: AMD Ryzen 9 7940HS w/ Radeon 780M Graphics, 4000.00 MHz, 19-74-01, > > patch 0a704101 > > cpu5: smt 0, core 5, package 0 > > cpu6 at mainbus0: apid 12 (application processor) > > cpu6: AMD Ryzen 9 7940HS w/ Radeon 780M Graphics, 4000.00 MHz, 19-74-01, > > patch 0a704101 > > cpu6: smt 0, core 6, package 0 > > cpu7 at mainbus0: apid 14 (application processor) > > cpu7: AMD Ryzen 9 7940HS w/ Radeon 780M Graphics, 4000.00 MHz, 19-74-01, > > patch 0a704101 > > cpu7: smt 0, core 7, package 0 > > cpu8 at mainbus0: apid 1 (application processor) > > cpu8: AMD Ryzen 9 7940HS w/ Radeon 780M Graphics, 4000.01 MHz, 19-74-01, > > patch 0a704101 > > cpu8: smt 1, core 0, package 0 > > cpu9 at mainbus0: apid 3 (application processor) > > cpu9: AMD Ryzen 9 7940HS w/ Radeon 780M Graphics, 4000.01 MHz, 19-74-01, > > patch 0a704101 > > cpu9: smt 1, core 1, package 0 > > cpu10 at mainbus0: apid 5 (application processor) > > cpu10: AMD Ryzen 9 7940HS w/ Radeon 780M Graphics, 4000.01 MHz, 19-74-01, > > patch 0a704101 > > cpu10:
Re: advice debugging lockups with swap-thrashing symptoms?
On 5/23/24 03:18, Stuart Henderson wrote: On 2024-05-22, James Cook wrote: One of my OpenBSD boxes sometimes gets in a weird locked-up or almost-locked-up state. I'm wondering what I can do to debug it further next time it happens. ... I would also expect the cache number to be much higher. E.g. on this occasion, I was running "git annex fsck", which reads plenty of data from disk. Heavy filesystem access can result in this sort of thing, I used to have unpacked ports source on one of my machines for grepping over, the machine was pretty much unusable for anything else while that was running. Might be worth trying some noatime mount flags if you don't already have them, at least then you can avoid turning some reads into writes. Definitely a possibility. Long time ago, I think I asked about the possibility of a "disknice" to throttle disk access on individual tasks. TedU@ came through for me with something that definitely solved my problem, and I use it from time to time since -- basically, it just suspends a particular program occasionally, which lets other programs have a chance to get disk access. I saved it (and made a tiny update that is needed now) and put it here: https://holland-consulting.net/scripts/disknice.html Also... I've seen disks "fail" where they get super-slow. The failure modes seems to be difficulty reading data...but after enough retries, it succeeds, resetting the retry counter back to zero, and then the next read encounters the same problem. You may be able to hear lots of activity on the drive with little obvious progress. I'm not convinced this is your problem, but ... something to consider. Nick.
Re: how to fsck automatically at boot
On 5/22/24 08:08, Kirill A. Korinsky wrote: On Wed, 22 May 2024 12:53:11 +0100, Nick Holland wrote: For reasons of multi-hour fsck's on a few systems, I'm looking at remounting the problem file systems as "rw" when writing is actually needed and "ro" after the writing is complete (IN THIS APPLICATION, this is known) to reduce my "at risk of power outage" window a lot, but I suspect this will fall deeply within the category of "when I break things, I get to keep all the pieces". :) Do you need atime on that FS? Disable it dramatically reduces chances of manual interraction with fsck. If you move forward and add sync which slow down write but allows to get almost zero porbability of fsck interraction. Already done. :) This is a backup system I have -- lots of symlinks, lots of files. Cool thing is, the fsck is painful, but almost never have to help the fsck along, at least once softdep was removed and they quit crashing in the middle of backups. (softdep removal really hurt these systems -- some tasks went from an hour or so to many hours...but it doesn't impact my life one bit. On the other hand, obviously I was tickling some of those softdep bugs I had heard hit some people). And in other news: couple days ago, I said I rarely need manual intervention on the systems I just yank the cords from. Well, this morning, a system I manage remotely apparently had a couple power events, and one system needed help with the fsck. That's what happens when one boasts. :D Nick.
Re: Sudden reboot every 5-10 minutes on latest snapshot
On 2024-05-23, Ali Farzanrad wrote: > Hi misc@, > > My Minisforum UM790 keeps reboot every 5-10 minutes, without any Kernel > Panic or visible message how may I debug it? > I'm using latest OpenBSD snapshot with this amd64/BUILDINFO: > Build date: 1716424636 - Thu May 23 00:37:16 UTC 2024 Not a lot to go on really. Is the machine doing anything or just idle? Is X running? Do you get the same with 7.5? if yes, try older releases - can you find one where it doesn't happen? > > # (dmesg; sysctl hw.sensors) > OpenBSD 7.5-current (GENERIC.MP) #78: Wed May 22 18:31:14 MDT 2024 > dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP > real mem = 31909883904 (30431MB) > avail mem = 30921310208 (29488MB) > random: good seed from bootblocks > mpath0 at root > scsibus0 at mpath0: 256 targets > mainbus0 at root > bios0 at mainbus0: SMBIOS rev. 3.5 @ 0x9ab7f000 (45 entries) > bios0: vendor American Megatrends International, LLC. version "1.01" date > 06/05/2023 > bios0: Micro Computer (HK) Tech Limited F7BSC > efi0 at bios0: UEFI 2.8 > efi0: American Megatrends rev 0x5001d > acpi0 at bios0: ACPI 6.4 > acpi0: sleep states S0 S4 S5 > acpi0: tables DSDT FACP SSDT SSDT FIDT MCFG FPDT VFCT BGRT TPM2 SSDT CRAT > CDIT SSDT SSDT SSDT SSDT SSDT SSDT SSDT SSDT SSDT WSMT APIC IVRS SSDT SSDT > SSDT SSDT SSDT SSDT SSDT SSDT SSDT SSDT > acpi0: wakeup devices GPP1(S4) GPP0(S4) GPP5(S4) GPP7(S4) GP11(S4) SWUS(S4) > GP12(S4) SWUS(S4) > acpitimer0 at acpi0: 3579545 Hz, 32 bits > acpimcfg0 at acpi0 > acpimcfg0: addr 0xe000, bus 0-255 > acpimadt0 at acpi0 addr 0xfee0: PC-AT compat > cpu0 at mainbus0: apid 0 (boot processor) > cpu0: AMD Ryzen 9 7940HS w/ Radeon 780M Graphics, 4000.00 MHz, 19-74-01, > patch 0a704101 > cpu0: cpuid 1 > edx=178bfbff > > ecx=76f8320b > cpu0: cpuid 6 eax=4 ecx=1 > cpu0: cpuid 7.0 > ebx=f1bf97a9 > ecx=405fce edx=1000 > cpu0: cpuid d.1 eax=f > cpu0: cpuid 8001 edx=2fd3fbff > ecx=75c237ff > cpu0: cpuid 8007 edx=e799 > cpu0: cpuid 8008 > ebx=791ef257 > cpu0: 32KB 64b/line 8-way D-cache, 32KB 64b/line 8-way I-cache, 1MB 64b/line > 8-way L2 cache, 16MB 64b/line 16-way L3 cache > cpu0: smt 0, core 0, package 0 > mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges > cpu0: apic clock running at 24MHz > cpu0: mwait min=64, max=64, C-substates=1.1, IBE > cpu1 at mainbus0: apid 2 (application processor) > cpu1: AMD Ryzen 9 7940HS w/ Radeon 780M Graphics, 4000.00 MHz, 19-74-01, > patch 0a704101 > cpu1: smt 0, core 1, package 0 > cpu2 at mainbus0: apid 4 (application processor) > cpu2: AMD Ryzen 9 7940HS w/ Radeon 780M Graphics, 4000.00 MHz, 19-74-01, > patch 0a704101 > cpu2: smt 0, core 2, package 0 > cpu3 at mainbus0: apid 6 (application processor) > cpu3: AMD Ryzen 9 7940HS w/ Radeon 780M Graphics, 4000.00 MHz, 19-74-01, > patch 0a704101 > cpu3: smt 0, core 3, package 0 > cpu4 at mainbus0: apid 8 (application processor) > cpu4: AMD Ryzen 9 7940HS w/ Radeon 780M Graphics, 4000.00 MHz, 19-74-01, > patch 0a704101 > cpu4: smt 0, core 4, package 0 > cpu5 at mainbus0: apid 10 (application processor) > cpu5: AMD Ryzen 9 7940HS w/ Radeon 780M Graphics, 4000.00 MHz, 19-74-01, > patch 0a704101 > cpu5: smt 0, core 5, package 0 > cpu6 at mainbus0: apid 12 (application processor) > cpu6: AMD Ryzen 9 7940HS w/ Radeon 780M Graphics, 4000.00 MHz, 19-74-01, > patch 0a704101 > cpu6: smt 0, core 6, package 0 > cpu7 at mainbus0: apid 14 (application processor) > cpu7: AMD Ryzen 9 7940HS w/ Radeon 780M Graphics, 4000.00 MHz, 19-74-01, > patch 0a704101 > cpu7: smt 0, core 7, package 0 > cpu8 at mainbus0: apid 1 (application processor) > cpu8: AMD Ryzen 9 7940HS w/ Radeon 780M Graphics, 4000.01 MHz, 19-74-01, > patch 0a704101 > cpu8: smt 1, core 0, package 0 > cpu9 at mainbus0: apid 3 (application processor) > cpu9: AMD Ryzen 9 7940HS w/ Radeon 780M Graphics, 4000.01 MHz, 19-74-01, > patch 0a704101 > cpu9: smt 1, core 1, package 0 > cpu10 at mainbus0: apid 5 (application processor) > cpu10: AMD Ryzen 9 7940HS w/ Radeon 780M Graphics, 4000.01 MHz, 19-74-01, > patch 0a704101 > cpu10: smt 1, core 2, package 0 > cpu11 at mainbus0: apid 7 (application processor) > cpu11: AMD Ryzen 9 7940HS w/ Radeon 780M Graphics, 4000.01 MHz, 19-74-01, > patch 0a704101 > cpu11: smt 1, core 3, package 0 > cpu12 at mainbus0: apid 9 (application processor) > cpu12: AMD Ryzen 9 7940HS w/ Radeon 780M Graphics, 4000.01 MHz, 19-74-01, > patch 0a704101 > cpu12: smt 1, core 4, package 0 > cpu13 at mainbus0: apid 11 (application processor) > cpu13: AMD Ryzen 9 7940HS w/ Radeon 780M Graphics, 4000.01 MHz, 19-74-01, > patch 0a704101 > cpu13: smt 1, core 5, package 0 > cpu14 at mainbus0: apid 13 (application processor) > cpu14: AMD Ryzen 9 7940HS w/ Radeon 780M Graphics, 4000.01 MHz, 19-74-01, > patch 0a704101 > cpu14: smt 1, core 6, package 0 > cpu15 at mainbus0: apid 15 (application processor) > cpu15: AMD Ryzen 9 7940HS w/ Radeon 780M Graphics, 4000.01 MHz, 19-74-01, > patch 0a704101 > cpu15:
Sudden reboot every 5-10 minutes on latest snapshot
Hi misc@, My Minisforum UM790 keeps reboot every 5-10 minutes, without any Kernel Panic or visible message how may I debug it? I'm using latest OpenBSD snapshot with this amd64/BUILDINFO: Build date: 1716424636 - Thu May 23 00:37:16 UTC 2024 # (dmesg; sysctl hw.sensors) OpenBSD 7.5-current (GENERIC.MP) #78: Wed May 22 18:31:14 MDT 2024 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 31909883904 (30431MB) avail mem = 30921310208 (29488MB) random: good seed from bootblocks mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: SMBIOS rev. 3.5 @ 0x9ab7f000 (45 entries) bios0: vendor American Megatrends International, LLC. version "1.01" date 06/05/2023 bios0: Micro Computer (HK) Tech Limited F7BSC efi0 at bios0: UEFI 2.8 efi0: American Megatrends rev 0x5001d acpi0 at bios0: ACPI 6.4 acpi0: sleep states S0 S4 S5 acpi0: tables DSDT FACP SSDT SSDT FIDT MCFG FPDT VFCT BGRT TPM2 SSDT CRAT CDIT SSDT SSDT SSDT SSDT SSDT SSDT SSDT SSDT SSDT WSMT APIC IVRS SSDT SSDT SSDT SSDT SSDT SSDT SSDT SSDT SSDT SSDT acpi0: wakeup devices GPP1(S4) GPP0(S4) GPP5(S4) GPP7(S4) GP11(S4) SWUS(S4) GP12(S4) SWUS(S4) acpitimer0 at acpi0: 3579545 Hz, 32 bits acpimcfg0 at acpi0 acpimcfg0: addr 0xe000, bus 0-255 acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: AMD Ryzen 9 7940HS w/ Radeon 780M Graphics, 4000.00 MHz, 19-74-01, patch 0a704101 cpu0: cpuid 1 edx=178bfbff ecx=76f8320b cpu0: cpuid 6 eax=4 ecx=1 cpu0: cpuid 7.0 ebx=f1bf97a9 ecx=405fce edx=1000 cpu0: cpuid d.1 eax=f cpu0: cpuid 8001 edx=2fd3fbff ecx=75c237ff cpu0: cpuid 8007 edx=e799 cpu0: cpuid 8008 ebx=791ef257 cpu0: 32KB 64b/line 8-way D-cache, 32KB 64b/line 8-way I-cache, 1MB 64b/line 8-way L2 cache, 16MB 64b/line 16-way L3 cache cpu0: smt 0, core 0, package 0 mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges cpu0: apic clock running at 24MHz cpu0: mwait min=64, max=64, C-substates=1.1, IBE cpu1 at mainbus0: apid 2 (application processor) cpu1: AMD Ryzen 9 7940HS w/ Radeon 780M Graphics, 4000.00 MHz, 19-74-01, patch 0a704101 cpu1: smt 0, core 1, package 0 cpu2 at mainbus0: apid 4 (application processor) cpu2: AMD Ryzen 9 7940HS w/ Radeon 780M Graphics, 4000.00 MHz, 19-74-01, patch 0a704101 cpu2: smt 0, core 2, package 0 cpu3 at mainbus0: apid 6 (application processor) cpu3: AMD Ryzen 9 7940HS w/ Radeon 780M Graphics, 4000.00 MHz, 19-74-01, patch 0a704101 cpu3: smt 0, core 3, package 0 cpu4 at mainbus0: apid 8 (application processor) cpu4: AMD Ryzen 9 7940HS w/ Radeon 780M Graphics, 4000.00 MHz, 19-74-01, patch 0a704101 cpu4: smt 0, core 4, package 0 cpu5 at mainbus0: apid 10 (application processor) cpu5: AMD Ryzen 9 7940HS w/ Radeon 780M Graphics, 4000.00 MHz, 19-74-01, patch 0a704101 cpu5: smt 0, core 5, package 0 cpu6 at mainbus0: apid 12 (application processor) cpu6: AMD Ryzen 9 7940HS w/ Radeon 780M Graphics, 4000.00 MHz, 19-74-01, patch 0a704101 cpu6: smt 0, core 6, package 0 cpu7 at mainbus0: apid 14 (application processor) cpu7: AMD Ryzen 9 7940HS w/ Radeon 780M Graphics, 4000.00 MHz, 19-74-01, patch 0a704101 cpu7: smt 0, core 7, package 0 cpu8 at mainbus0: apid 1 (application processor) cpu8: AMD Ryzen 9 7940HS w/ Radeon 780M Graphics, 4000.01 MHz, 19-74-01, patch 0a704101 cpu8: smt 1, core 0, package 0 cpu9 at mainbus0: apid 3 (application processor) cpu9: AMD Ryzen 9 7940HS w/ Radeon 780M Graphics, 4000.01 MHz, 19-74-01, patch 0a704101 cpu9: smt 1, core 1, package 0 cpu10 at mainbus0: apid 5 (application processor) cpu10: AMD Ryzen 9 7940HS w/ Radeon 780M Graphics, 4000.01 MHz, 19-74-01, patch 0a704101 cpu10: smt 1, core 2, package 0 cpu11 at mainbus0: apid 7 (application processor) cpu11: AMD Ryzen 9 7940HS w/ Radeon 780M Graphics, 4000.01 MHz, 19-74-01, patch 0a704101 cpu11: smt 1, core 3, package 0 cpu12 at mainbus0: apid 9 (application processor) cpu12: AMD Ryzen 9 7940HS w/ Radeon 780M Graphics, 4000.01 MHz, 19-74-01, patch 0a704101 cpu12: smt 1, core 4, package 0 cpu13 at mainbus0: apid 11 (application processor) cpu13: AMD Ryzen 9 7940HS w/ Radeon 780M Graphics, 4000.01 MHz, 19-74-01, patch 0a704101 cpu13: smt 1, core 5, package 0 cpu14 at mainbus0: apid 13 (application processor) cpu14: AMD Ryzen 9 7940HS w/ Radeon 780M Graphics, 4000.01 MHz, 19-74-01, patch 0a704101 cpu14: smt 1, core 6, package 0 cpu15 at mainbus0: apid 15 (application processor) cpu15: AMD Ryzen 9 7940HS w/ Radeon 780M Graphics, 4000.01 MHz, 19-74-01, patch 0a704101 cpu15: smt 1, core 7, package 0 ioapic0 at mainbus0: apid 33 pa 0xfec0, version 21, 24 pins, can't remap ioapic1 at mainbus0: apid 34 pa 0xfec01000, version 21, 32 pins, can't remap acpiprt0 at acpi0: bus 0 (PCI0) acpiprt1 at acpi0: bus 1 (GPP1) acpiprt2 at acpi0: bus -1 (GPP2) acpiprt3 at acpi0: bus -1 (GPP0) acpiprt4 at acpi0: bus -1 (GPP3) acpiprt5 at acpi0: bus -1 (GPP4) acpiprt6 at acpi0: bus 2 (GPP5) acpiprt7 at acpi0: bus -1 (GPP6) acpiprt8 at acp
Q: Problems forwarding traffic using pf ...
Hi All, I need to quickly create a solution for forwarding multicast traffic between two systems, so I though perhaps I could use pf to do just that by writing some rules along the lines of: 1. pass in on iface A proto UDP ... tag mcast 2. pass out on iface B tagged mcast And another pair of rules for the reverse direction B -> A. (Obviously I'd add more options to filter specific addresses, etc.) So I tried to do a quick test / proof of concept. Here is the pf.conf: # cat pf.conf set skip on lo0 set block-policy return set debug warning # Begin by blocking everything block log all # Begin by blocking everything pass in log on em0proto udp from 192.168.178.166 tag UDP pass out log on ure0 tagged UDP ###match route dup-to ure0 tagged TAG_UP # Allow all outbound #pass out log modulate state The two "pass" lines are the basis of the idea. This seems to be pretty much identical to the tagging example "INTNET" in the pf.conf man page. pfctl reports: # pfctl -vvs rules | grep @ @0 block return log all @1 pass in log on em0 inet proto udp from 192.168.178.166 to any tag UDP @2 pass out log on ure0 all flags S/SA tagged UDP I see that rule 1 is matched, but never rule 2. E.g. ... May 23 10:32:06.602759 rule 0/(match) block in on em0: 192.168.178.179.5353 > 224.0.0.251.5353: 46[|domain] (DF) May 23 10:32:06.603963 rule 0/(match) block in on em0: fe80::4434:8bff:fecd:b116.5353 > ff02::fb.5353: 46[|domain] [flowlabel 0xbaff9] May 23 10:32:09.700212 rule 0/(match) block in on em0: 192.168.178.254 > 224.0.0.1: igmp query [len 12] (DF) [tos 0xc0] [ttl 1] May 23 10:32:13.267374 rule 1/(match) pass in on em0: 192.168.178.166.56334 > 192.168.178.11.54321: udp 7 May 23 10:32:20.592971 rule 0/(match) block in on em0: 192.168.178.179.5353 > 224.0.0.251.5353: 16 [3q][|domain] (DF) May 23 10:32:21.136275 rule 0/(match) block in on em0: 192.168.178.252.5353 > 224.0.0.251.5353: 48084+[|domain] May 23 10:32:21.137074 rule 0/(match) block in on em0: 192.168.178.252.5353 > 224.0.0.251.5353: 0* [0q] 3/0/3[|domain] ... May 23 10:32:48.588466 rule 1/(match) pass in on em0: 192.168.178.166.56335 > 192.168.178.11.54321: udp 42 May 23 10:32:49.705282 rule 0/(match) block in on em0: 192.168.178.179.5353 > 224.0.0.251.5353: 0[|domain] (DF) May 23 10:32:49.705839 rule 0/(match) block in on em0: fe80::4434:8bff:fecd:b116.5353 > ff02::fb.5353: 0[|domain] [flowlabel 0xbaff9] ... I must be missing something, but what? Both interfaces are up and configured with IP addresses. I'm running the current snapshot i.e. 7.5 GENERIC.MP#77 amd64. Thanks in advance! Cheers, Robb.
Re: wifi
>From a quick glance it is a bog-standard m.2 / NGFF card, so it should be >fairly trivial to replace the card with a supported one, see the removal >steps at 01:30 : https://www.youtube.com/watch?app=desktop&v=dqJ9LjY0Jco Stuart Henderson írta 2024. máj.. 23, Cs-n 09:23 órakor: > On 2024-05-23, Gustavo Rios wrote: >> --1fa3f9061917b744 >> Content-Type: text/plain; charset="UTF-8" >> >> Hi folks! >> >> I would like to setup my openbsd wifi but up to now, no success. >> Here is my lspci output. May some one help me ? >> >> Thanks a lot. >> >> 02:00.0 Network controller: Realtek Semiconductor Co., Ltd. RTL8821CE >> 802.11ac PCIe Wireless Network Adapter > > OpenBSD doesn't support Realtek 11ac wifi. > > > -- > Please keep replies on the mailing list. -- --Z--
Re: wifi
On 2024-05-23, Gustavo Rios wrote: > --1fa3f9061917b744 > Content-Type: text/plain; charset="UTF-8" > > Hi folks! > > I would like to setup my openbsd wifi but up to now, no success. > Here is my lspci output. May some one help me ? > > Thanks a lot. > > 02:00.0 Network controller: Realtek Semiconductor Co., Ltd. RTL8821CE > 802.11ac PCIe Wireless Network Adapter OpenBSD doesn't support Realtek 11ac wifi. -- Please keep replies on the mailing list.
Re: advice debugging lockups with swap-thrashing symptoms?
On 2024-05-22, James Cook wrote: > One of my OpenBSD boxes sometimes gets in a weird locked-up or > almost-locked-up state. I'm wondering what I can do to debug it > further next time it happens. ... > I would also expect the cache number to be much higher. E.g. on > this occasion, I was running "git annex fsck", which reads plenty > of data from disk. Heavy filesystem access can result in this sort of thing, I used to have unpacked ports source on one of my machines for grepping over, the machine was pretty much unusable for anything else while that was running. Might be worth trying some noatime mount flags if you don't already have them, at least then you can avoid turning some reads into writes.
Re: wifi
On Thu, May 23, 2024 at 03:56:01AM -0300, Gustavo Rios wrote: > Here you have them: ... "Realtek 8821CE" rev 0x00 at pci2 dev 0 function 0 not configured That means there is no driver available in OpenBSD for that card. -Otto
