Re: Cannot configure wi-fi card
there are three engineers on a road trip: one is mechanical the other electronic and the last a systems engineer . The car suddenly breaks down. The mechanical one jumps out of the car, exclaiming " it's going to be an engine problem! " ...but the engine works properly. Then comes the electronic one with " definitely a short circuit! " ...but the electrical system is fine . the systems engineer : "I found the problem ! everybody out of the car and back inside." :-) ...Really without logs and debugs the problem can be far away from a mere hardware detach... Translated with www.DeepL.com/Translator (free version) On 5/29/2022 10:13 AM, Matsuda Kenji wrote: Hello. I finally solved the problem. I just detach and re-attach the wifi card physically and it worked. First, I updated BIOS and nothing changed. Then I made several changes to BIOS configuration. I found that I've installed for legacy BIOS and MBR. So I reinstalled OpenBSD for UEFI and GPT. But the problem was not solved. And at this morning, I recalled that I could use this wifi from Linux. So I tried to boot from Linux live USB(Debian), and encountered a similar problem of iwlwifi with error code -110. I googled for this problem and found an article: https://bugzilla.kernel.org/show_bug.cgi?id=205299 It implies that the problem has something to do with Windows. Actually I installed Windows on this machine and my sister used it until I installed OpenBSD last week. I wondered if I could reset some configuration on the wifi card made by Windows by disconnecting it from the motherboard. And this worked for me. Anyway, thanks a lot everyone. Matsuda Kenji
Re: Cannot configure wi-fi card
Hello. I finally solved the problem. I just detach and re-attach the wifi card physically and it worked. First, I updated BIOS and nothing changed. Then I made several changes to BIOS configuration. I found that I've installed for legacy BIOS and MBR. So I reinstalled OpenBSD for UEFI and GPT. But the problem was not solved. And at this morning, I recalled that I could use this wifi from Linux. So I tried to boot from Linux live USB(Debian), and encountered a similar problem of iwlwifi with error code -110. I googled for this problem and found an article: https://bugzilla.kernel.org/show_bug.cgi?id=205299 It implies that the problem has something to do with Windows. Actually I installed Windows on this machine and my sister used it until I installed OpenBSD last week. I wondered if I could reset some configuration on the wifi card made by Windows by disconnecting it from the motherboard. And this worked for me. Anyway, thanks a lot everyone. Matsuda Kenji
Re: Cannot configure wi-fi card
On 5/27/22 10:25 PM, Matsuda Kenji wrote: Hello. I just installed OpenBSD 7.1 and am having trouble setting up a wi-fi card. There is no wi-fi interface in ifconfig output. Dmesg says that there is some error configuring NIC: iwm0 at pci1 dev 0 function 0 "Intel Dual Band Wireless-AC 9260"\ rev 0x29, msix iwm0: Failed to wake up the nic. do you have any options in the system setup that might help? Maybe even switching between UEFI and "legacy" boot modes, I have a machine that refuses to see its storage devices if it is booted in Legacy mode, but works pretty well in UEFI mode, and I could imagine it going the other way, too. Oh...a BIOS upgrade might be in order. No promises. Nick.
Re: Cron running at 99% CPU for seemingly no reason
>From l...@md5collisions.eu Thu May 26 19:51:47 2022 Date: Thu, 26 May 2022 19:51:47 +0200 From: Stephan Mending To: misc@openbsd.org Subject: Re: Cron running at 99% CPU for seemingly no reason Message-ID: Mail-Followup-To: Stephan Mending , misc@openbsd.org References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Operating-System: not-disclosed Status: RO Content-Length: 10166 Lines: 244 On Sun, May 15, 2022 at 12:25:24PM +0200, Claudio Jeker wrote: > On Sun, May 15, 2022 at 12:06:33PM +0200, Stephan Mending wrote: > > Hi *, > > I've got a system running -current that keeps crashing on me every couple > > of days. > > Output of ddb: > > > > Connected to /dev/cuaU0 (speed 115200) > > > > ddb{0}> show panic > > the kernel did not panic > > ddb{0}> show uvm > > Current UVM status: > > pagesize=4096 (0x1000), pagemask=0xfff, pageshift=12 > > 482451 VM pages: 43158 active, 132795 inactive, 35 wired, 192336 free > > (24054 z > > ero) > > min 10% (25) anon, 10% (25) vnode, 5% (12) vtext > > freemin=16081, free-target=21441, inactive-target=0, wired-max=160817 > > faults=2487210, traps=2404140, intrs=211883, ctxswitch=1960560 fpuswitch=0 > > softint=3499069, syscalls=2015497, kmapent=9 > > fault counts: > > noram=0, noanon=0, noamap=0, pgwait=0, pgrele=0 > > ok relocks(total)=192470(193514), anget(retries)=603205(0), > > amapcopy=177151 > > > > neighbor anon/obj pg=82033/639788, gets(lock/unlock)=415897/193548 > > cases: anon=570367, anoncow=32838, obj=347149, prcopy=67670, > > przero=1469152 > > > > daemon and swap counts: > > woke=0, revs=0, scans=0, obscans=0, anscans=0 > > busy=0, freed=0, reactivate=0, deactivate=0 > > pageouts=0, pending=0, nswget=0 > > nswapdev=1 > > swpages=526020, swpginuse=0, swpgonly=0 paging=0 > > kernel pointers: > > objs(kern)=0x8238a038 > > ddb{0}> show trace > > No such command > > ddb{0}> trace > > icmp_mtudisc_timeout(fd807a50b070,0) at icmp_mtudisc_timeout+0x77 > > rt_timer_timer(8235d668) at rt_timer_timer+0x1cc > > softclock_thread(8000f260) at softclock_thread+0x13b > > end trace frame: 0x0, count: -3 > > ddb{0}> > > > > This looks like some bad memory access. This is a fault and not really a > panic this is why 'show panic' returns 'the kernel did not panic'. > > The crash in icmp_mtudisc_timeout() points to some error in the rttimer > code refactor I made. Please try a newer snapshot and include the dmesg. > > If it happens again a call to db_show_rtentry in ddb may help better > understand what is going on: > > call db_show_rtentry(fd807a50b070, 0, 0) > Where the first argument is derived from the first argument of > icmp_mtudisc_timeout from the trace. > > -- > :wq Claudio @Claudio The error seems to persist as attached occurred a couple of days back. (This time I've got the full dmesg for you) I tried your "call db_show_rtentry<...>". That somehow returned an error. Just reporting right here. I'll try and run a kernel with symbols and wait for the next crash. 'Til then. Best regards, Stephan dmesg: OpenBSD 7.1-current (GENERIC.MP) #525: Sat May 14 23:04:32 MDT 2022 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 2046992384 (1952MB) avail mem = 1967644672 (1876MB) random: good seed from bootblocks mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.8 @ 0x7bef9000 (81 entries) bios0: vendor American Megatrends Inc. version "5.011" date 10/10/2016 bios0: INTEL Corporation CRESCENTBAY acpi0 at bios0: ACPI 5.0 acpi0: sleep states S0 S3 S4 S5 acpi0: tables DSDT FACP APIC FPDT FIDT MCFG HPET SSDT UEFI SSDT ASF! SSDT SSDT acpi0: wakeup devices PEG0(S4) PEGP(S4) PEG1(S4) PEGP(S4) PEG2(S4) PEGP(S4) RP0 1(S4) PXSX(S4) RP02(S4) PXSX(S4) RP03(S4) PXSX(S4) RP04(S4) PXSX(S4) RP05(S4) P XSX(S4) [...] acpitimer0 at acpi0: 3579545 Hz, 24 bits acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: Intel(R) Pentium(R) 3558U @ 1.70GHz, 1696.36 MHz, 06-45-01 cpu0: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,C FLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,V MX,EST,TM2,SSSE3,SDBG,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,MOVBE,POPCNT,DEADLINE,X SAVE,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,PERF,ITSC,FSGSBASE,TSC_ADJUST,ERMS ,INVPCID,SRBDS_CTRL,MD_CLEAR,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,MEL TDOWN cpu0: 256KB 64b/line 8-way L2 cache cpu0: smt 0, core 0, package 0 mtrr: Pentium Pro MTRR support, 10 var ranges, 88 fixed ranges cpu0: apic clock running at 99MHz cpu0: mwait min=64, max=64, C-substates=0.2.1.2.4.1.1.1, IBE cpu1 at mainbus0: apid 2 (application processor) cpu1: Intel(R) Pentium(R) 3558U @ 1.70GHz, 1696.08 MHz, 06-45-01 cpu1: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,C
Re: C states lost on amd64
On May 27 19:39:18, guent...@gmail.com wrote: > On Fri, 27 May 2022, Jan Stary wrote: > > ... and with the latest snapshot, they are back. > ... > > acpicpu0 at acpi0: C3(350@96 mwait.1@0x20), C2(500@64 mwait.1@0x10), > > C1(1000@1 mwait.1), PSS > > acpicpu1 at acpi0: C3(350@96 mwait.1@0x20), C2(500@64 mwait.1@0x10), > > C1(1000@1 mwait.1), PSS > > acpicpu2 at acpi0: C3(350@96 mwait.1@0x20), C2(500@64 mwait.1@0x10), > > C1(1000@1 mwait.1), PSS > > acpicpu3 at acpi0: C3(350@96 mwait.1@0x20), C2(500@64 mwait.1@0x10), > > C1(1000@1 mwait.1), PSS > > > > On May 26 14:34:43, h...@stare.cz wrote: > > > This is current/adm64, dmesgs below. > > > With the current snapshot, the C states are gone: > > > > > > -acpicpu0 at acpi0: C3(350@96 mwait.1@0x20), C2(500@64 mwait.1@0x10), > > > C1(1000@1 mwait.1), PSS > > > -acpicpu1 at acpi0: C3(350@96 mwait.1@0x20), C2(500@64 mwait.1@0x10), > > > C1(1000@1 mwait.1), PSS > > > -acpicpu2 at acpi0: C3(350@96 mwait.1@0x20), C2(500@64 mwait.1@0x10), > > > C1(1000@1 mwait.1), PSS > > > -acpicpu3 at acpi0: C3(350@96 mwait.1@0x20), C2(500@64 mwait.1@0x10), > > > C1(1000@1 mwait.1), PSS > > > +acpicpu0 at acpi0: C1(@1 halt!), PSS > > > +acpicpu1 at acpi0: C1(@1 halt!), PSS > > > +acpicpu2 at acpi0: C1(@1 halt!), PSS > > > +acpicpu3 at acpi0: C1(@1 halt!), PSS > > > > > > Is this expected? > > > Is it related to the recent apmd -A change? > > Not really. Well, unless your box is one where the states change > depending on, say, whether the box is plugged in. This is a PC workstation that is always plugged in. > You could give this diff a shot. It enables processing of CST change > notifications. No committers have a (working) box that does that, so I > couldn't get any interest and I have no idea when--or even if--it might go > in. Thanks. The current snapshots seem to work fine (like they have been), this was the only snapshot that didn't show the C-states. Is anyone please aware of a change that could have temporarily coused that around May 25th? Jan > > > Index: sys/dev/acpi/acpicpu.c > === > RCS file: /data/src/openbsd/src/sys/dev/acpi/acpicpu.c,v > retrieving revision 1.92 > diff -u -p -r1.92 acpicpu.c > --- sys/dev/acpi/acpicpu.c6 Apr 2022 18:59:27 - 1.92 > +++ sys/dev/acpi/acpicpu.c12 Apr 2022 06:13:55 - > @@ -25,6 +25,7 @@ > #include > #include > #include > +#include > > #include > #include > @@ -80,6 +81,7 @@ voidacpicpu_setperf_ppc_change(struct a > #define CST_FLAG_FALLBACK0x4000 /* fallback for broken _CST */ > #define CST_FLAG_SKIP0x8000 /* state is worse > choice */ > > +#define FLAGS_NOCST 0x01 > #define FLAGS_MWAIT_ONLY 0x02 > #define FLAGS_BMCHECK0x04 > #define FLAGS_NOTHROTTLE 0x08 > @@ -113,8 +115,10 @@ struct acpi_cstate > uint64_taddress;/* or mwait hint */ > }; > > -unsigned long cst_stats[4] = { 0 }; > - > +/* > + * Locking: > + * m sc_mtx > + */ > struct acpicpu_softc { > struct device sc_dev; > int sc_cpu; > @@ -130,6 +134,10 @@ struct acpicpu_softc { > struct cpu_info *sc_ci; > SLIST_HEAD(,acpi_cstate) sc_cstates; > > + struct mutexsc_mtx; > + struct acpi_cstate *sc_cstates_active; /* [m] */ > + int sc_mwait_only; /* [m] */ > + > bus_space_tag_t sc_iot; > bus_space_handle_t sc_ioh; > > @@ -161,10 +169,13 @@ struct acpicpu_softc { > > void acpicpu_add_cstatepkg(struct aml_value *, void *); > void acpicpu_add_cdeppkg(struct aml_value *, void *); > +void acpicpu_cst_activate(struct acpicpu_softc *); > int acpicpu_getppc(struct acpicpu_softc *); > int acpicpu_getpct(struct acpicpu_softc *); > int acpicpu_getpss(struct acpicpu_softc *); > int acpicpu_getcst(struct acpicpu_softc *); > +int acpicpu_cst_changed(struct acpicpu_softc *); > +void acpicpu_free_states(struct acpi_cstate *); > void acpicpu_getcst_from_fadt(struct acpicpu_softc *); > void acpicpu_print_one_cst(struct acpi_cstate *_cx); > void acpicpu_print_cst(struct acpicpu_softc *_sc); > @@ -510,11 +521,11 @@ acpicpu_getcst(struct acpicpu_softc *sc) > struct acpi_cstate *cx, *next_cx; > int use_nonmwait; > > - /* delete the existing list */ > - while ((cx = SLIST_FIRST(>sc_cstates)) != NULL) { > - SLIST_REMOVE_HEAD(>sc_cstates, link); > - free(cx, M_DEVBUF, sizeof(*cx)); > - } > + /* set aside the existing list and free it if not active */ > + cx = SLIST_FIRST(>sc_cstates); > + SLIST_INIT(>sc_cstates); > + if (cx != sc->sc_cstates_active) > + acpicpu_free_states(cx); > > /* provide a fallback C1-via-halt in case _CST's C1 is bogus */ > acpicpu_add_cstate(sc, ACPI_STATE_C1,
Re: mv expected behavior?
Ignore the post. It was software I had installed in my home directory.
mv expected behavior?
I know the mv command is being asked to do the wrong thing. It tells me that in 7.0. Is it expected behavior for 7.1 versus 7.0 release? Using 7.1 with all patches and all packages up to date. mkdir A cd A mkdir B mv ~/A B mv: Abort trap (core dumped)
Re: Cannot configure wi-fi card
On 2022-05-28, Peter Nicolai Mathias Hansteen wrote: > --Apple-Mail=_2B4B5EC6-B0C2-4A8D-9201-FCBDE33C5566 > Content-Transfer-Encoding: 8bit > Content-Type: text/plain; > charset=utf-8 > > > >> 28. mai 2022 kl. 04:25 skrev Matsuda Kenji : >> >> Hello. >> >> I just installed OpenBSD 7.1 and am having trouble >> setting up a wi-fi card. >> There is no wi-fi interface in ifconfig output. >> Dmesg says that there is some error configuring NIC: >> iwm0 at pci1 dev 0 function 0 "Intel Dual Band Wireless-AC 9260"\ >> rev 0x29, msix >> iwm0: Failed to wake up the nic. > > Some laptops have a physical switch, sometimes implemented as a Fn-function > key combo to enable or disable the wifi (think airplane mode). Could that be > what you are seeing here? This isn't a laptop: bios0: ASRock Z390 Pro4 It may be worth looking in the BIOS for options to do with PCIE ASPM. Somebody who knows more than me might find something useful in one of the files included in the template generated by "sendbug" when run as root..
Re: Cannot configure wi-fi card
I installed on a dedicated desktop computer at home. And it is not dual boot. I have only OpenBSD installed on my ssd drive. On Sat, May 28, 2022 at 03:11:12PM +0900, Fabrizio Francione wrote: > Are You installing on a VM like Proxmox or is that a dedicated HW? > > Do you have a dual boot or related?
Re: Cannot configure wi-fi card
Are You installing on a VM like Proxmox or is that a dedicated HW? Do you have a dual boot or related? On 5/28/2022 1:21 PM, Matsuda Kenji wrote: Thank you for your reply. Did you install the iwm firmware? https://www.openbsd.org/faq/faq4.html#WifiOnly I can connect to the Internet via Ethernet, and iwm firmware was installed by fw_update at the first boot. There is firmware files in /etc/firmware: $ls /etc/firmware/iwm* /etc/firmware/iwm-3160-17 /etc/firmware/iwm-3168-29 /etc/firmware/iwm-7260-17 /etc/firmware/iwm-7265-17 /etc/firmware/iwm-7265D-29 /etc/firmware/iwm-8000C-34 /etc/firmware/iwm-8000C-36 /etc/firmware/iwm-8265-34 /etc/firmware/iwm-8265-36 /etc/firmware/iwm-9000-34 /etc/firmware/iwm-9000-46 /etc/firmware/iwm-9260-34 /etc/firmware/iwm-9260-46 /etc/firmware/iwm-license Matsuda Kenji