Re: "kbd -l" -> wskbd_displayioctl_sc uvm_fault
On Tue, Feb 13, 2024 at 08:44:32AM +, Miod Vallat wrote: >> Does this help? >> >> diff --git sys/dev/wscons/wskbd.c sys/dev/wscons/wskbd.c >> index 7631cd5f701..dd65f61ce63 100644 >> --- sys/dev/wscons/wskbd.c >> +++ sys/dev/wscons/wskbd.c >> @@ -1229,7 +1229,10 @@ getkeyrepeat: >> >> case WSKBDIO_GETENCODINGS: >> uedp = (struct wskbd_encoding_data *)data; >> -for (count = 0; sc->id->t_keymap.keydesc[count].name; count++) >> +for (count = 0; >> + sc->id->t_keymap.keydesc != NULL && >> + sc->id->t_keymap.keydesc[count].name; >> + count++) >> ; >> if (uedp->nencodings > count) >> uedp->nencodings = count; >> > This ought to fix the panic Stuart is getting. > > However I don't understand how t_keymap.keydesc can be a NULL pointer > (yet it obviousl was); it is initialized at wskbd attachment time with > valid data. > > Stuart, did you issue specific wsconsctl or wsconscfg operations in this > VM prior to running 'kbd -l'? What are the contents of > /etc/wsconsctl.conf, if it exists? In case it helps, this looks like the same bug I saw 18 months ago: https://marc.info/?l=openbsd-bugs=165946663019894=2 https://marc.info/?l=openbsd-bugs=166032382028448=2 Laurie
Re: Different lm attaching?
On Wed, Feb 14, 2024 at 12:34:17PM +0100, Mark Kettenis wrote:
Hello Mark,
>> It seems that I have two (at least) lm devices on my motherboard and
>> that it's random which attaches. Here are the two I've seen:
>>
>> lm0 at isa0 port 0x290/8: W83627DHG
>> lm0 at isa0 port 0x290/8: NCT6792D
>>
>> The W83627DHG gives one fan reading, with an obviously incorrect value:
>>
>> $ sysctl hw|grep fan
>> hw.sensors.lm0.fan0=56250 RPM
>>
>> The NCT6792D gave more than one, and seemingly correct, fan readings in
>> `sysctl hw`. From memory there were at least fan readings for the CPU
>> and rear fan, both were showing in the range 350-600 RPM when idling,
>> and as soon as I made the CPU do some work the readings went up, and
>> when the CPU stopped doing some work the readings went down.
>>
>> The reason I'm being vague about that is that I have only noticed the
>> NCT6792D attaching once, so I can't give those fan readings now. AFAICT
>> the W83627DHG nearly always attaches: out of 19 dmesgs I've
>> (accidentally) stored over many months, only one contains
>> "lm0...NCT6792D".
>>
>> I'm attaching a dmesg from a kernel built from -current yesterday in
>> case this is useful, though it's from an W83627DHG attach.
> It is probably a misdetection. There are some heuristics involved in
> detecting the chip. And there may even be a 2nd agent here (IPMI, SMM)
> that may interfere with the code that tries to detect the chip.
I put a `printf` to see what value `sc->sioid` is set to. In fact it seems
it can be set to more than one value! So far I've seen: 0x9, 0x89, 0xe9.
If I match on those values with the (obviously not commitable!) diff at
the end of this email then I get sensible fan values:
$ dmesg | grep lm0
lm0 at isa0 port 0x290/8 (0xe9) : unknown 6779D-ish
$ sysctl hw.sensors|grep fan
hw.sensors.lm0.fan0=610 RPM (System Fan)
hw.sensors.lm0.fan1=363 RPM (CPU Fan)
hw.sensors.lm0.fan2=0 RPM (Aux Fan0)
hw.sensors.lm0.fan3=0 RPM (Aux Fan1)
hw.sensors.lm0.fan4=0 RPM (Aux Fan2)
These go up and down as I'd expect as the system load varies.
I had a quick look at the equivalent Linux driver, but it looks to me like
it does detection in a very way that doesn't involve making choices based
on sioid?
Laurie
diff --git sys/dev/ic/lm78.c sys/dev/ic/lm78.c
index e60f38577a6..561fe603689 100644
--- sys/dev/ic/lm78.c
+++ sys/dev/ic/lm78.c
@@ -563,6 +563,7 @@ wb_match(struct lm_softc *sc)
lm_setup_sensors(sc, w83627ehf_sensors);
break;
case WB_CHIPID_W83627DHG:
+ printf(" (%d) ", sc->sioid);
switch (sc->sioid) {
case WBSIO_ID_NCT6775F:
printf(": NCT6775F\n");
@@ -596,6 +597,12 @@ wb_match(struct lm_softc *sc)
printf(": NCT6795D\n");
lm_setup_sensors(sc, nct6779d_sensors);
break;
+ case 0x89:
+ case 0x9:
+ case 0xe9:
+ printf(": unknown 6779D-ish\n");
+ lm_setup_sensors(sc, nct6779d_sensors);
+ break;
default:
printf(": W83627DHG\n");
lm_setup_s
Different lm attaching?
It seems that I have two (at least) lm devices on my motherboard and that it's random which attaches. Here are the two I've seen: lm0 at isa0 port 0x290/8: W83627DHG lm0 at isa0 port 0x290/8: NCT6792D The W83627DHG gives one fan reading, with an obviously incorrect value: $ sysctl hw|grep fan hw.sensors.lm0.fan0=56250 RPM The NCT6792D gave more than one, and seemingly correct, fan readings in `sysctl hw`. From memory there were at least fan readings for the CPU and rear fan, both were showing in the range 350-600 RPM when idling, and as soon as I made the CPU do some work the readings went up, and when the CPU stopped doing some work the readings went down. The reason I'm being vague about that is that I have only noticed the NCT6792D attaching once, so I can't give those fan readings now. AFAICT the W83627DHG nearly always attaches: out of 19 dmesgs I've (accidentally) stored over many months, only one contains "lm0...NCT6792D". I'm attaching a dmesg from a kernel built from -current yesterday in case this is useful, though it's from an W83627DHG attach. Laurie OpenBSD 7.4-current (GENERIC.MP) #18: Tue Feb 13 16:07:15 GMT 2024 ltr...@overdrive.tratt.net:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 68431765504 (65261MB) avail mem = 66336387072 (63263MB) random: good seed from bootblocks mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: SMBIOS rev. 3.5 @ 0x75a58000 (104 entries) bios0: vendor American Megatrends Inc. version "1801" date 12/08/2023 bios0: ASUS ROG STRIX Z790-H GAMING WIFI efi0 at bios0: UEFI 2.8 efi0: American Megatrends rev 0x5001b acpi0 at bios0: ACPI 6.4 acpi0: sleep states S0 S3 S4 S5 acpi0: tables DSDT FACP SSDT FIDT SSDT SSDT SSDT SSDT HPET APIC MCFG SSDT NHLT LPIT SSDT SSDT DBGP DBG2 SSDT DMAR FPDT SSDT SSDT SSDT UEFI UEFI BGRT WPBT TPM2 PHAT WSMT acpi0: wakeup devices PEG1(S4) PEGP(S4) PEGP(S4) PEG0(S4) PEGP(S4) RP09(S4) PXSX(S4) RP10(S4) PXSX(S4) RP11(S4) PXSX(S4) RP12(S4) PXSX(S4) RP13(S4) PXSX(S4) RP14(S4) [...] acpitimer0 at acpi0: 3579545 Hz, 24 bits acpihpet0 at acpi0: 1920 Hz acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: 13th Gen Intel(R) Core(TM) i9-13900K, 5902.40 MHz, 06-b7-01, patch 011f cpu0: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,TSC_ADJUST,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,RDSEED,ADX,SMAP,CLFLUSHOPT,CLWB,PT,SHA,UMIP,PKU,WAITPKG,PKS,MD_CLEAR,IBT,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,IBRS_ALL,SKIP_L1DFL,MDS_NO,IF_PSCHANGE,TAA_NO,MISC_PKG_CT,ENERGY_FILT,DOITM,SBDR_SSDP_N,FBSDP_NO,PSDP_NO,RRSBA,OVERCLOCK,GDS_NO,XSAVEOPT,XSAVEC,XGETBV1,XSAVES cpu0: 48KB 64b/line 12-way D-cache, 32KB 64b/line 8-way I-cache, 2MB 64b/line 16-way L2 cache, 36MB 64b/line 12-way L3 cache cpu0: smt 0, core 0, package 0 mtrr: Pentium Pro MTRR support, 10 var ranges, 88 fixed ranges cpu0: apic clock running at 38MHz cpu0: mwait min=64, max=64, C-substates=0.2.0.1.0.1.0.1, IBE cpu1 at mainbus0: apid 8 (application processor) cpu1: 13th Gen Intel(R) Core(TM) i9-13900K, 5902.54 MHz, 06-b7-01, patch 011f cpu1: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,TSC_ADJUST,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,RDSEED,ADX,SMAP,CLFLUSHOPT,CLWB,PT,SHA,UMIP,PKU,WAITPKG,PKS,MD_CLEAR,IBT,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,IBRS_ALL,SKIP_L1DFL,MDS_NO,IF_PSCHANGE,TAA_NO,MISC_PKG_CT,ENERGY_FILT,DOITM,SBDR_SSDP_N,FBSDP_NO,PSDP_NO,RRSBA,OVERCLOCK,GDS_NO,XSAVEOPT,XSAVEC,XGETBV1,XSAVES cpu1: 48KB 64b/line 12-way D-cache, 32KB 64b/line 8-way I-cache, 2MB 64b/line 16-way L2 cache, 36MB 64b/line 12-way L3 cache cpu1: smt 0, core 4, package 0 cpu2 at mainbus0: apid 16 (application processor) cpu2: 13th Gen Intel(R) Core(TM) i9-13900K, 5802.40 MHz, 06-b7-01, patch 011f cpu2: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,TSC_ADJUST,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,RDSEED,ADX,SMAP,CLFLUSHOPT,CLWB,PT,SHA,UMIP,PKU,WAITPKG,PKS,MD_CLEAR,IBT,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,IBRS_ALL,SKIP_L1DFL,MDS_NO,IF_PSCHANGE,TAA_NO,MISC_PKG_CT,ENERGY_FILT,DOITM,SBDR_SSDP_N,FBSDP_NO,PSDP_NO,RRSBA,OVERCLOCK,GDS_NO,XSAVEOPT,XSAVEC,XGETBV1,XSAVES cpu2: 48KB
zzz failing and uvn_flush errors
Yesterday my amd64 machine failed to `zzz` for the first time (with a kernel built from yesterday with the now-commited "support Alder Lake-N and Alder Lake-S" from jsg@). This might just be one of those random things that we so love about computers but after reboot I had `uvn_flush` errors and warnings in my dmesg, which I don't remember having seen before. Those errors seemed to start at the same point that a long-lived process had managed to stop /tmp from freeing space up. That might just be coincidence, but one side effect of /tmp filling up these days is that Chrome-based browser and Firefox both tend to exit without any indication of why. Here's the probably-relevant part of the dmesg: uid 1000 on /tmp: file system full uid 1000 on /tmp: file system full uvn_flush: obj=0xfd8ace67dee8, offset=0x3. error during pageout. uvn_flush: WARNING: changes to page may be lost! uid 1000 on /tmp: file system full uvn_flush: obj=0xfd8ace67dad8, offset=0x2. error during pageout. uvn_flush: WARNING: changes to page may be lost! uid 1000 on /tmp: file system full uid 1000 on /tmp: file system full drm:pid56681:intel_pipe_update_start *ERROR* [drm] *ERROR* Potential atomic update failure on pipe A uid 1000 on /tmp: file system full drm:pid56681:intel_pipe_update_start *ERROR* [drm] *ERROR* Potential atomic update failure on pipe A drm:pid56681:intel_pipe_update_start *ERROR* [drm] *ERROR* Potential atomic update failure on pipe A drm:pid56681:intel_pipe_update_start *ERROR* [drm] *ERROR* Potential atomic update failure on pipe A drm:pid56681:intel_pipe_update_start *ERROR* [drm] *ERROR* Potential atomic update failure on pipe A drm:pid56681:intel_pipe_update_end *ERROR* [drm] *ERROR* Atomic update failure on pipe A (start=32449 end=32450) time 2 us, min 2544, max 2559, scanline start 2554, end 2559 drm:pid56681:intel_pipe_update_start *ERROR* [drm] *ERROR* Potential atomic update failure on pipe A uhid0 detached uhidev0 detached ugen0 detached xhci0: command ring abort timeout xhci0: command ring abort timeout xhci0: command ring abort timeout uaudio0: can't reset interface xhci0: command ring abort timeout uaudio0: can't reset interface audio1 detached uaudio0 detached midi0 detached xhci0: command ring abort timeout xhci0: command ring abort timeout umidi0 detached ugen1 detached xhci0: command ring abort timeout xhci0: command ring abort timeout video0 detached uvideo0 detached audio2 detached uaudio1 detached uhid1 detached uhidev1 detached xhci0: command ring abort timeout xhci0: command ring abort timeout xhci0: command ring abort timeout wskbd1: disconnecting from wsdisplay0 wskbd1 detached ukbd0 detached uhidev2 detached xhci0: command ring abort timeout uhid2 detached wskbd2: disconnecting from wsdisplay0 wskbd2 detached ucc0 detached uhidev3 detached xhci0: command ring abort timeout xhci0: command ring abort timeout xhci0: command ring abort timeout uhub1 detached xhci0: command ring abort timeout xhci0: command ring abort timeout xhci0: command ring abort timeout wskbd3: disconnecting from wsdisplay0 wskbd3 detached ukbd1 detached uhidev4 detached xhci0: command ring abort timeout wsmouse0 detached ums0 detached wskbd4: disconnecting from wsdisplay0 wskbd4 detached ucc1 detached uhid3 detached uhid4 detached uhidev5 detached xhci0: command ring abort timeout uhidpp0 detached uhid5 detached uhid6 detached uhidev6 detached xhci0: command ring abort timeout xhci0: command ring abort timeout sd1 detached scsibus3 detached xhci0: command ring abort timeout xhci0: command ring abort timeout umass0 detached xhci0: command ring abort timeout xhci0: command ring abort timeout xhci0: command ring abort timeout uhub2 detached xhci0: command ring abort timeout xhci0: command ring abort timeout ugen2 detached xhci0: command ring abort timeout xhci0: command ring abort timeout xhci0: command ring abort timeout uhub3 detached xhci0: command ring abort timeout xhci0: command ring abort timeout uhub0 detached Note that the kernel never got to "syncing disks" (and I left it for at least an hour). The full dmesg is as follows: OpenBSD 7.4-current (GENERIC.MP) #1: Sun Nov 26 14:20:54 GMT 2023 ltr...@overdrive.tratt.net:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 68431814656 (65261MB) avail mem = 66338222080 (63265MB) random: good seed from bootblocks mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: SMBIOS rev. 3.5 @ 0x75a58000 (104 entries) bios0: vendor American Megatrends Inc. version "1501" date 10/05/2023 bios0: ASUS ROG STRIX Z790-H GAMING WIFI efi0 at bios0: UEFI 2.8 efi0: American Megatrends rev 0x5001b acpi0 at bios0: ACPI 6.4 acpi0: sleep states S0 S3 S4 S5 acpi0: tables DSDT FACP FIDT SSDT SSDT SSDT SSDT HPET
Xorg crashing after waking monitor from standby
Perhaps 5-8 times in the past few weeks I've experienced X crashing. Interestingly, each time it's happened has been while the monitor has been in standby. Things seem to be fine until I wake the screen up by pressing a key. Almost immediately Xorg crashes, and drops me back to the console; perhaps 10 seconds later Xorg restarts and automatically puts me back into xenodm. Here's the salient part of the most recent Xorg.0.log.old output: [123208.185] (EE) Segmentation fault at address 0xe9d67855000 [123208.185] (EE) Fatal server error: [123208.185] (EE) Caught signal 11 (Segmentation fault). Server aborting [123208.185] (EE) [123208.185] (EE) Please consult the The X.Org Foundation support at http://wiki.x.org for help. [123208.185] (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information. [123208.185] (EE) [123208.186] (EE) ws: /dev/wsmouse: unknown command 4 [123208.186] (II) AIGLX: Suspending AIGLX clients for VT switch [123208.200] (EE) Server terminated with error (1). Closing log file. This is on a 3 day old amd64 snapshot with inteldrm. Full Xorg.0.log (and dmesg afterwards): [22.229] (WW) checkDevMem: failed to open /dev/xf86 and /dev/mem (Operation not permitted) Check that you have set 'machdep.allowaperture=1' in /etc/sysctl.conf and reboot your machine refer to xf86(4) for details [22.229] linear framebuffer access unavailable [22.234] (--) Using wscons driver on /dev/ttyC4 [22.262] X.Org X Server 1.21.1.9 X Protocol Version 11, Revision 0 [22.262] Current Operating System: OpenBSD overdrive.tratt.net 7.4 GENERIC.MP#1461 amd64 [22.262] [22.262] Current version of pixman: 0.42.2 [22.262] Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. [22.262] Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. [22.262] (==) Log file: "/var/log/Xorg.0.log", Time: Wed Nov 22 12:27:22 2023 [22.263] (==) Using system config directory "/usr/X11R6/share/X11/xorg.conf.d" [22.264] (==) No Layout section. Using the first Screen section. [22.264] (==) No screen section available. Using defaults. [22.264] (**) |-->Screen "Default Screen Section" (0) [22.264] (**) | |-->Monitor "" [22.264] (==) No monitor specified for screen "Default Screen Section". Using a default monitor configuration. [22.264] (==) Automatically adding devices [22.264] (==) Automatically enabling devices [22.264] (==) Not automatically adding GPU devices [22.264] (==) Automatically binding GPU devices [22.264] (==) Max clients allowed: 256, resource mask: 0x1f [22.265] (==) FontPath set to: /usr/X11R6/lib/X11/fonts/misc/, /usr/X11R6/lib/X11/fonts/TTF/, /usr/X11R6/lib/X11/fonts/OTF/, /usr/X11R6/lib/X11/fonts/Type1/, /usr/X11R6/lib/X11/fonts/100dpi/, /usr/X11R6/lib/X11/fonts/75dpi/ [22.265] (==) ModulePath set to "/usr/X11R6/lib/modules" [22.265] (II) The server relies on wscons to provide the list of input devices. If no devices become available, reconfigure wscons or disable AutoAddDevices. [22.265] (II) Loader magic: 0xe990705e530 [22.265] (II) Module ABI versions: [22.265] X.Org ANSI C Emulation: 0.4 [22.265] X.Org Video Driver: 25.2 [22.265] X.Org XInput driver : 24.4 [22.265] X.Org Server Extension : 10.0 [22.265] (--) PCI:*(0@0:2:0) 8086:a780:1043:8882 rev 4, Mem @ 0x600400/16777216, 0x40/268435456, I/O @ 0x6000/64 [22.265] (II) LoadModule: "glx" [22.265] (II) Loading /usr/X11R6/lib/modules/extensions/libglx.so [22.272] (II) Module glx: vendor="X.Org Foundation" [22.272] compiled for 1.21.1.9, module version = 1.0.0 [22.272] ABI class: X.Org Server Extension, version 10.0 [22.272] (==) Matched modesetting as autoconfigured driver 0 [22.272] (==) Assigned the driver to the xf86ConfigLayout [22.272] (II) LoadModule: "modesetting" [22.272] (II) Loading /usr/X11R6/lib/modules/drivers/modesetting_drv.so [22.273] (II) Module modesetting: vendor="X.Org Foundation" [22.273] compiled for 1.21.1.9, module version = 1.21.1 [22.273] Module class: X.Org Video Driver [22.273] ABI class: X.Org Video Driver, version 25.2 [22.273] (II) modesetting: Driver for Modesetting Kernel Drivers: kms [22.277] (**) modeset(0): claimed PCI slot 0@0:2:0 [22.277] (II) modeset(0): using default device [22.277] (II) modeset(0): Creating default Display subsection in Screen section "Default Screen Section" for depth/fbbpp 24/32 [22.277] (==) modeset(0): Depth
Re: inteldrm atomic update failure and PCI conflict
On Tue, Nov 07, 2023 at 09:03:59AM +, Laurence Tratt wrote:
> Across a few Intel machines I've had, I've often seen warnings about
> "potential atomic update failures". On my current desktop with an
> i5-13600K I've now seen actual failures:
>
> drm:pid51847:intel_pipe_update_start *ERROR* [drm] *ERROR* Potential atomic
> update failure on pipe A
> drm:pid51847:intel_pipe_update_end *ERROR* [drm] *ERROR* Atomic update
> failure on pipe A (start=84142 end=84143) time 3 us, min 2544, max 2559,
> scanline start 2555, end 2560
>
> I think these correlate with occasional roughly-second-long locks in X.
In the last couple of days (with a Nov 17th snapshot) I've twice
experienced an interesting variation on this: the machine became almost
unusable for about 10s, with the mouse lurching slowly around the screen
like someone at the end of a long Friday night out. After today's version I
ended up with this in my dmesg:
Asynchronous wait on fence :Xorg[79196]:498526 timed out
(hint:0x81b8c2c0s)
i915_vma_coredump_create: stub
i915_vma_coredump_create: stub
i915_vma_coredump_create: stub
i915_vma_coredump_create: stub
i915_vma_coredump_create: stub
i915_vma_coredump_create: stub
i915_vma_coredump_create: stub
i915_vma_coredump_create: stub
i915_vma_coredump_create: stub
i915_vma_coredump_create: stub
i915_vma_coredump_create: stub
i915_vma_coredump_create: stub
i915_vma_coredump_create: stub
i915_vma_coredump_create: stub
i915_vma_coredump_create: stub
i915_vma_coredump_create: stub
i915_vma_coredump_create: stub
i915_vma_coredump_create: stub
i915_vma_coredump_create: stub
i915_vma_coredump_create: stub
i915_vma_coredump_create: stub
i915_vma_coredump_create: stub
i915_vma_coredump_create: stub
i915_vma_coredump_create: stub
i915_vma_coredump_create: stub
i915_vma_coredump_create: stub
pool_fini: stub
drm:pid13130:__intel_engine_reset_bh *NOTICE* [drm] Resetting rcs0 for
stopped heartbeat on rcs0
drm:pid13130:gen8_engine_reset_prepare *ERROR* [drm] *ERROR* rcs0 reset
request timed out: {request: 0001, RESET_CTL: 0001}
drm:pid13130:intel_gt_reset *NOTICE* [drm] Resetting chip for stopped
heartbeat on rcs0
drm:pid13130:gen8_engine_reset_prepare *ERROR* [drm] *ERROR* rcs0 reset
request timed out: {request: 0001, RESET_CTL: 0001}
drm:pid13130:gen8_engine_reset_prepare *ERROR* [drm] *ERROR* rcs0 reset
request timed out: {request: 0001, RESET_CTL: 0001}
drm:pid13130:mark_guilty *NOTICE* [drm] firefox[92248] context reset due to
GPU hang
As that last line suggests, I was using Firefox at the time.
Laurie
inteldrm atomic update failure and PCI conflict
Across a few Intel machines I've had, I've often seen warnings about "potential atomic update failures". On my current desktop with an i5-13600K I've now seen actual failures: drm:pid51847:intel_pipe_update_start *ERROR* [drm] *ERROR* Potential atomic update failure on pipe A drm:pid51847:intel_pipe_update_end *ERROR* [drm] *ERROR* Atomic update failure on pipe A (start=84142 end=84143) time 3 us, min 2544, max 2559, scanline start 2555, end 2560 I think these correlate with occasional roughly-second-long locks in X. A poke around the internet suggests that Linux users sometimes see this, and it seems to be due to (faulty?) Intel IOMMU support: https://gitlab.freedesktop.org/drm/intel/-/issues/2215 I won't pretend I understand all the stuff in there. Apart from that, this machine mostly works well, with the notable exception of USB support. In particular, USB audio frequently stutters and sometimes stops (you can see many "rec xfer, err = 6" in the dmesg below) and video capture frequently glitches -- far more than happens on slower machines. The obvious new-to-me oddity I see in my dmesg that might be related to this is: pci0 at mainbus0 bus 0 0:31:5: mem address conflict 0xfe01/0x1000 but I have no idea what the effects of such a conflict might be, or whether it's in anyway correlated to inteldrm issues or not. Laurie OpenBSD 7.4-current (GENERIC.MP) #1441: Fri Nov 3 17:45:32 MDT 2023 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 68431814656 (65261MB) avail mem = 66338111488 (63264MB) random: good seed from bootblocks mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: SMBIOS rev. 3.5 @ 0x75a58000 (108 entries) bios0: vendor American Megatrends Inc. version "1501" date 10/05/2023 bios0: ASUS ROG STRIX Z790-H GAMING WIFI efi0 at bios0: UEFI 2.8 efi0: American Megatrends rev 0x5001b acpi0 at bios0: ACPI 6.4 acpi0: sleep states S0 S3 S4 S5 acpi0: tables DSDT FACP FIDT SSDT SSDT SSDT SSDT HPET APIC MCFG SSDT NHLT LPIT SSDT SSDT DBGP DBG2 SSDT DMAR FPDT SSDT SSDT SSDT BGRT WPBT TPM2 BERT PHAT WSMT acpi0: wakeup devices PEG1(S4) PEGP(S4) PEGP(S4) PEG0(S4) PEGP(S4) RP09(S4) PXSX(S4) RP10(S4) PXSX(S4) RP11(S4) PXSX(S4) RP12(S4) PXSX(S4) RP13(S4) PXSX(S4) RP14(S4) [...] acpitimer0 at acpi0: 3579545 Hz, 24 bits acpihpet0 at acpi0: 1920 Hz acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: 13th Gen Intel(R) Core(TM) i5-13600K, 5102.07 MHz, 06-b7-01, patch 011d cpu0: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,TSC_ADJUST,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,RDSEED,ADX,SMAP,CLFLUSHOPT,CLWB,PT,SHA,UMIP,PKU,WAITPKG,PKS,MD_CLEAR,IBT,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,IBRS_ALL,SKIP_L1DFL,MDS_NO,IF_PSCHANGE,TAA_NO,MISC_PKG_CT,ENERGY_FILT,DOITM,SBDR_SSDP_N,FBSDP_NO,PSDP_NO,RRSBA,OVERCLOCK,GDS_NO,XSAVEOPT,XSAVEC,XGETBV1,XSAVES cpu0: 48KB 64b/line 12-way D-cache, 32KB 64b/line 8-way I-cache, 2MB 64b/line 16-way L2 cache, 24MB 64b/line 12-way L3 cache cpu0: smt 0, core 0, package 0 mtrr: Pentium Pro MTRR support, 10 var ranges, 88 fixed ranges cpu0: apic clock running at 38MHz cpu0: mwait min=64, max=64, C-substates=0.2.0.2.0.1.0.1, IBE cpu1 at mainbus0: apid 8 (application processor) cpu1: 13th Gen Intel(R) Core(TM) i5-13600K, 5101.99 MHz, 06-b7-01, patch 011d cpu1: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,TSC_ADJUST,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,RDSEED,ADX,SMAP,CLFLUSHOPT,CLWB,PT,SHA,UMIP,PKU,WAITPKG,PKS,MD_CLEAR,IBT,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,IBRS_ALL,SKIP_L1DFL,MDS_NO,IF_PSCHANGE,TAA_NO,MISC_PKG_CT,ENERGY_FILT,DOITM,SBDR_SSDP_N,FBSDP_NO,PSDP_NO,RRSBA,OVERCLOCK,GDS_NO,XSAVEOPT,XSAVEC,XGETBV1,XSAVES cpu1: 48KB 64b/line 12-way D-cache, 32KB 64b/line 8-way I-cache, 2MB 64b/line 16-way L2 cache, 24MB 64b/line 12-way L3 cache cpu1: smt 0, core 4, package 0 cpu2 at mainbus0: apid 16 (application processor) cpu2: 13th Gen Intel(R) Core(TM) i5-13600K, 5102.12 MHz, 06-b7-01, patch 011d cpu2:
amdgpu: async flip with non-fast update
I built a new kernel this morning which includes a number of amdgpu patches. I saw a bizarre situation where: the machine almost-but-not-quite ground to a halt for quite a while, with the display not updating properly. Then the display updated normally, the mouse continued working OK, but the keyboard mostly didn't work. Oddly, I could sort-of Ctrl+Alt+F1 to the console in the sense that X stopped updating -- but the display didn't show the consle. I could then Ctrl+Alt+F5 back and X would (slowly) update. I've noticed I now have this in my dmesg: Jul 28 13:20:24 overdrive /bsd: drm:pid97220:amdgpu_dm_commit_planes *WARNING* [drm] [PLANE:55:plane-3] async flip with non-fast update which may perhaps be correlated with this? Output from /var/log/messages below of the session below. Edd (CCd) has also seen the "mouse works but keyboard doesn't" bug today, but I'm not sure if he has amdgpu or not. Laurie Jul 28 13:07:02 overdrive /bsd: OpenBSD 7.3-current (GENERIC.MP) #153: Fri Jul 28 13:04:54 BST 2023 Jul 28 13:07:02 overdrive /bsd: ltr...@overdrive.tratt.net:/usr/src/sys/arch/amd64/compile/GENERIC.MP Jul 28 13:07:02 overdrive /bsd: real mem = 33382141952 (31835MB) Jul 28 13:07:02 overdrive /bsd: avail mem = 32350748672 (30852MB) Jul 28 13:07:02 overdrive /bsd: random: good seed from bootblocks Jul 28 13:07:02 overdrive /bsd: mpath0 at root Jul 28 13:07:02 overdrive /bsd: scsibus0 at mpath0: 256 targets Jul 28 13:07:02 overdrive /bsd: mainbus0 at root Jul 28 13:07:02 overdrive /bsd: bios0 at mainbus0: SMBIOS rev. 3.5 @ 0xb94dc000 (42 entries) Jul 28 13:07:02 overdrive /bsd: bios0: vendor American Megatrends International, LLC. version "1.A1" date 06/21/2023 Jul 28 13:07:02 overdrive /bsd: bios0: Micro-Star International Co., Ltd. MS-7D67 Jul 28 13:07:02 overdrive /bsd: efi0 at bios0: UEFI 2.8 Jul 28 13:07:02 overdrive /bsd: efi0: American Megatrends rev 0x5001a Jul 28 13:07:02 overdrive /bsd: acpi0 at bios0: ACPI 6.4 Jul 28 13:07:02 overdrive /bsd: acpi0: sleep states S0 S3 S4 S5 Jul 28 13:07:02 overdrive /bsd: acpi0: tables DSDT FACP SSDT SSDT FIDT MCFG HPET WDRT UEFI FPDT VFCT BGRT TPM2 SSDT CRAT CDIT BGRT SSDT SSDT SSDT SSDT WSMT APIC SSDT SSDT SSDT IVRS SSDT SSDT SSDT SSDT SSDT SSDT Jul 28 13:07:02 overdrive /bsd: acpi0: wakeup devices GPP3(S4) GPP4(S4) GPP5(S4) GPP6(S4) GP17(S4) XHC0(S4) XHC1(S4) XHC2(S4) GPP0(S4) GPP1(S4) GPP2(S4) GPP7(S4) UP00(S4) DP00(S4) NV00(S4) DP20(S4) [...] Jul 28 13:07:02 overdrive /bsd: acpitimer0 at acpi0: 3579545 Hz, 32 bits Jul 28 13:07:02 overdrive /bsd: acpimcfg0 at acpi0 Jul 28 13:07:02 overdrive /bsd: acpimcfg0: addr 0xf000, bus 0-127 Jul 28 13:07:02 overdrive /bsd: acpihpet0 at acpi0: 14318180 Hz Jul 28 13:07:02 overdrive /bsd: acpimadt0 at acpi0 addr 0xfee0: PC-AT compat Jul 28 13:07:02 overdrive /bsd: cpu0 at mainbus0: apid 0 (boot processor) Jul 28 13:07:02 overdrive /bsd: cpu0: AMD Ryzen 9 7900X 12-Core Processor, 4700.00 MHz, 19-61-02 Jul 28 13:07:02 overdrive /bsd: cpu0: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,PCLMUL,MWAIT,SSSE3,FMA3,CX16,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,AES,XSAVE,AVX,F16C,RDRAND,NXE,MMXX,FFXSR,PAGE1GB,RDTSCP,LONG,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,ABM,SSE4A,MASSE,3DNOWP,OSVW,IBS,SKINIT,TCE,TOPEXT,CPCTR,DBKP,PCTRL3,MWAITX,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,PQM,AVX512F,AVX512DQ,RDSEED,ADX,SMAP,AVX512IFMA,CLFLUSHOPT,CLWB,AVX512CD,SHA,AVX512BW,AVX512VL,AVX512VBMI,UMIP,PKU,L1DF,IBPB,IBRS,STIBP,STIBP_ALL,IBRS_PREF,IBRS_SM,SSBD,XSAVEOPT,XSAVEC,XGETBV1,XSAVES Jul 28 13:07:02 overdrive /bsd: cpu0: 32KB 64b/line 8-way D-cache, 32KB 64b/line 8-way I-cache, 1MB 64b/line 8-way L2 cache, 32MB 64b/line 16-way L3 cache Jul 28 13:07:02 overdrive /bsd: cpu0: smt 0, core 0, package 0 Jul 28 13:07:02 overdrive /bsd: mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges Jul 28 13:07:02 overdrive /bsd: cpu0: apic clock running at 25MHz Jul 28 13:07:02 overdrive /bsd: cpu0: mwait min=64, max=64, C-substates=1.1, IBE Jul 28 13:07:02 overdrive /bsd: cpu1 at mainbus0: apid 2 (application processor) Jul 28 13:07:02 overdrive /bsd: cpu1: AMD Ryzen 9 7900X 12-Core Processor, 4700.00 MHz, 19-61-02 Jul 28 13:07:02 overdrive /bsd: cpu1: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,PCLMUL,MWAIT,SSSE3,FMA3,CX16,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,AES,XSAVE,AVX,F16C,RDRAND,NXE,MMXX,FFXSR,PAGE1GB,RDTSCP,LONG,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,ABM,SSE4A,MASSE,3DNOWP,OSVW,IBS,SKINIT,TCE,TOPEXT,CPCTR,DBKP,PCTRL3,MWAITX,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,PQM,AVX512F,AVX512DQ,RDSEED,ADX,SMAP,AVX512IFMA,CLFLUSHOPT,CLWB,AVX512CD,SHA,AVX512BW,AVX512VL,AVX512VBMI,UMIP,PKU,L1DF,IBPB,IBRS,STIBP,STIBP_ALL,IBRS_PREF,IBRS_SM,SSBD,XSAVEOPT,XSAVEC,XGETBV1,XSAVES Jul 28 13:07:02 overdrive /bsd: cpu1: 32KB 64b/line 8-way D-cache, 32KB 64b/line 8-way I-cache, 1MB 64b/line 8-way L2 cache, 32MB 64b/line 16-way L3
Re: amdgpu: Error waiting for DMUB idle / Error queuing DMUB command
On Thu, Jun 29, 2023 at 07:17:03PM +1000, Jonathan Gray wrote: Hello Jonathan, > Paul de Weerd also reported problems with the firmware update. > We tracked it down to > > amdgpu: DMCUB updates for DCN 3.1.4 and 3.1.5 > https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=ade163aaaeae0c1ad20cb3dd8ce878bf61c91b3a > > (Ryzen 7000 includes DCN 3.1.5) > > A diff to switch the port to a snapshot before that commit: I can confirm that this fixes the problem -- thanks for the quick reply! Laurie
amdgpu: Error waiting for DMUB idle / Error queuing DMUB command
Upgrading to last night's snapshot I think updated amdgpu's firmware (to amdgpu-firmware-20230625). I'm now getting lots of stutter (X freezes for ~0.5-1s, key presses dropped etc) and lots of these in dmesg: [drm] *ERROR* Error waiting for DMUB idle: status=3 [drm] *ERROR* Error queuing DMUB command: status=2 I've rebuilt a new kernel (git# 2b5ea97f) but am seeing the same behaviour. dmesg below. Laurie OpenBSD 7.3-current (GENERIC.MP) #133: Thu Jun 29 09:47:49 BST 2023 ltr...@overdrive.tratt.net:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 33381998592 (31835MB) avail mem = 32350625792 (30851MB) random: good seed from bootblocks mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: SMBIOS rev. 3.5 @ 0xb94dc000 (42 entries) bios0: vendor American Megatrends International, LLC. version "1.94" date 05/12/2023 bios0: Micro-Star International Co., Ltd. MS-7D67 efi0 at bios0: UEFI 2.8 efi0: American Megatrends rev 0x5001a acpi0 at bios0: ACPI 6.4 acpi0: sleep states S0 S3 S4 S5 acpi0: tables DSDT FACP SSDT SSDT FIDT MCFG HPET WDRT UEFI FPDT VFCT BGRT TPM2 SSDT CRAT CDIT BGRT SSDT SSDT SSDT SSDT WSMT APIC SSDT SSDT SSDT IVRS SSDT SSDT SSDT SSDT SSDT SSDT acpi0: wakeup devices GPP3(S4) GPP4(S4) GPP5(S4) GPP6(S4) GP17(S4) XHC0(S4) XHC1(S4) XHC2(S4) GPP0(S4) GPP1(S4) GPP2(S4) GPP7(S4) UP00(S4) DP00(S4) NV00(S4) DP20(S4) [...] acpitimer0 at acpi0: 3579545 Hz, 32 bits acpimcfg0 at acpi0 acpimcfg0: addr 0xf000, bus 0-127 acpihpet0 at acpi0: 14318180 Hz acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: AMD Ryzen 9 7900X 12-Core Processor, 4700.00 MHz, 19-61-02 cpu0: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,PCLMUL,MWAIT,SSSE3,FMA3,CX16,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,AES,XSAVE,AVX,F16C,RDRAND,NXE,MMXX,FFXSR,PAGE1GB,RDTSCP,LONG,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,ABM,SSE4A,MASSE,3DNOWP,OSVW,IBS,SKINIT,TCE,TOPEXT,CPCTR,DBKP,PCTRL3,MWAITX,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,PQM,AVX512F,AVX512DQ,RDSEED,ADX,SMAP,AVX512IFMA,CLFLUSHOPT,CLWB,AVX512CD,SHA,AVX512BW,AVX512VL,AVX512VBMI,UMIP,PKU,WAITPKG,L1DF,IBPB,IBRS,STIBP,SSBD,XSAVEOPT,XSAVEC,XGETBV1,XSAVES cpu0: 32KB 64b/line 8-way D-cache, 32KB 64b/line 8-way I-cache, 1MB 64b/line 8-way L2 cache, 32MB 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 25MHz cpu0: mwait min=64, max=64, C-substates=1.1, IBE cpu1 at mainbus0: apid 2 (application processor) cpu1: AMD Ryzen 9 7900X 12-Core Processor, 4700.00 MHz, 19-61-02 cpu1: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,PCLMUL,MWAIT,SSSE3,FMA3,CX16,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,AES,XSAVE,AVX,F16C,RDRAND,NXE,MMXX,FFXSR,PAGE1GB,RDTSCP,LONG,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,ABM,SSE4A,MASSE,3DNOWP,OSVW,IBS,SKINIT,TCE,TOPEXT,CPCTR,DBKP,PCTRL3,MWAITX,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,PQM,AVX512F,AVX512DQ,RDSEED,ADX,SMAP,AVX512IFMA,CLFLUSHOPT,CLWB,AVX512CD,SHA,AVX512BW,AVX512VL,AVX512VBMI,UMIP,PKU,L1DF,IBPB,IBRS,STIBP,SSBD,XSAVEOPT,XSAVEC,XGETBV1,XSAVES cpu1: 32KB 64b/line 8-way D-cache, 32KB 64b/line 8-way I-cache, 1MB 64b/line 8-way L2 cache, 32MB 64b/line 16-way L3 cache cpu1: smt 0, core 1, package 0 cpu2 at mainbus0: apid 4 (application processor) cpu2: AMD Ryzen 9 7900X 12-Core Processor, 4700.00 MHz, 19-61-02 cpu2: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,PCLMUL,MWAIT,SSSE3,FMA3,CX16,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,AES,XSAVE,AVX,F16C,RDRAND,NXE,MMXX,FFXSR,PAGE1GB,RDTSCP,LONG,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,ABM,SSE4A,MASSE,3DNOWP,OSVW,IBS,SKINIT,TCE,TOPEXT,CPCTR,DBKP,PCTRL3,MWAITX,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,PQM,AVX512F,AVX512DQ,RDSEED,ADX,SMAP,AVX512IFMA,CLFLUSHOPT,CLWB,AVX512CD,SHA,AVX512BW,AVX512VL,AVX512VBMI,UMIP,PKU,L1DF,IBPB,IBRS,STIBP,SSBD,XSAVEOPT,XSAVEC,XGETBV1,XSAVES cpu2: 32KB 64b/line 8-way D-cache, 32KB 64b/line 8-way I-cache, 1MB 64b/line 8-way L2 cache, 32MB 64b/line 16-way L3 cache cpu2: smt 0, core 2, package 0 cpu3 at mainbus0: apid 6 (application processor) cpu3: AMD Ryzen 9 7900X 12-Core Processor, 4700.00 MHz, 19-61-02 cpu3: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,PCLMUL,MWAIT,SSSE3,FMA3,CX16,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,AES,XSAVE,AVX,F16C,RDRAND,NXE,MMXX,FFXSR,PAGE1GB,RDTSCP,LONG,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,ABM,SSE4A,MASSE,3DNOWP,OSVW,IBS,SKINIT,TCE,TOPEXT,CPCTR,DBKP,PCTRL3,MWAITX,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,PQM,AVX512F,AVX512DQ,RDSEED,ADX,SMAP,AVX512IFMA,CLFLUSHOPT,CLWB,AVX512CD,SHA,AVX512BW,AVX512VL,AVX512VBMI,UMIP,PKU,L1DF,IBPB,IBRS,STIBP,SSBD,XSAVEOPT,XSAVEC,XGETBV1,XSAVES cpu3: 32KB 64b/line 8-way D-cache, 32KB 64b/line 8-way I-cache, 1MB 64b/line 8-way L2 cache, 32MB 64b/line
DPMS wakeup and kernel lock?
In my `.xsession` I have: xidle -no -program "/usr/X11R6/bin/xlock -mode fadeplot -dpmsstandby 180 -dpmssuspend 0 -dpmsoff 0" -timeout 500 -delay 100 & So, after 8 minutes, `xidle` runs `xlock` and after another 3 minutes the monitor is put into standby mode. When the monitor is in standby mode and I later press keys to force it to wakeup, I think the kernel grabs a lock (the main kernel lock?) that causes everything to freeze for a bit over a second. I notice this most often if music is playing -- audio stops completely during this time. I don't think this behaviour is particularly worrisome as such, but it made me wonder if a) such a lock should be held during DPMS wakeup b) whether it suggests that this part of whatever part of the graphics system is a bit lock-grab-happy? Laurie OpenBSD 7.3-current (GENERIC.MP) #1175: Wed May 3 08:19:33 MDT 2023 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 33381998592 (31835MB) avail mem = 32350654464 (30851MB) random: good seed from bootblocks mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: SMBIOS rev. 3.5 @ 0xb94dc000 (43 entries) bios0: vendor American Megatrends International, LLC. version "1.92" date 04/28/2023 bios0: Micro-Star International Co., Ltd. MS-7D67 efi0 at bios0: UEFI 2.8 efi0: American Megatrends rev 0x5001a acpi0 at bios0: ACPI 6.4 acpi0: sleep states S0 S3 S4 S5 acpi0: tables DSDT FACP SSDT SSDT FIDT MCFG HPET WDRT UEFI FPDT VFCT BGRT TPM2 SSDT CRAT CDIT BGRT SSDT SSDT SSDT SSDT WSMT APIC SSDT SSDT SSDT IVRS SSDT SSDT SSDT SSDT SSDT SSDT acpi0: wakeup devices GPP3(S4) GPP4(S4) GPP5(S4) GPP6(S4) GP17(S4) XHC0(S4) XHC1(S4) XHC2(S4) GPP0(S4) GPP1(S4) GPP2(S4) GPP7(S4) UP00(S4) DP00(S4) NV00(S4) DP20(S4) [...] acpitimer0 at acpi0: 3579545 Hz, 32 bits acpimcfg0 at acpi0 acpimcfg0: addr 0xf000, bus 0-127 acpihpet0 at acpi0: 14318180 Hz acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: AMD Ryzen 9 7900X 12-Core Processor, 4700.01 MHz, 19-61-02 cpu0: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,PCLMUL,MWAIT,SSSE3,FMA3,CX16,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,AES,XSAVE,AVX,F16C,RDRAND,NXE,MMXX,FFXSR,PAGE1GB,RDTSCP,LONG,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,ABM,SSE4A,MASSE,3DNOWP,OSVW,IBS,SKINIT,TCE,TOPEXT,CPCTR,DBKP,PCTRL3,MWAITX,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,PQM,AVX512F,AVX512DQ,RDSEED,ADX,SMAP,AVX512IFMA,CLFLUSHOPT,CLWB,AVX512CD,SHA,AVX512BW,AVX512VL,AVX512VBMI,UMIP,PKU,WAITPKG,L1DF,IBPB,IBRS,STIBP,SSBD,XSAVEOPT,XSAVEC,XGETBV1,XSAVES cpu0: 32KB 64b/line 8-way D-cache, 32KB 64b/line 8-way I-cache, 1MB 64b/line 8-way L2 cache, 32MB 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 25MHz cpu0: mwait min=64, max=64, C-substates=1.1, IBE cpu1 at mainbus0: apid 2 (application processor) cpu1: AMD Ryzen 9 7900X 12-Core Processor, 4700.00 MHz, 19-61-02 cpu1: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,PCLMUL,MWAIT,SSSE3,FMA3,CX16,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,AES,XSAVE,AVX,F16C,RDRAND,NXE,MMXX,FFXSR,PAGE1GB,RDTSCP,LONG,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,ABM,SSE4A,MASSE,3DNOWP,OSVW,IBS,SKINIT,TCE,TOPEXT,CPCTR,DBKP,PCTRL3,MWAITX,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,PQM,AVX512F,AVX512DQ,RDSEED,ADX,SMAP,AVX512IFMA,CLFLUSHOPT,CLWB,AVX512CD,SHA,AVX512BW,AVX512VL,AVX512VBMI,UMIP,PKU,L1DF,IBPB,IBRS,STIBP,SSBD,XSAVEOPT,XSAVEC,XGETBV1,XSAVES cpu1: 32KB 64b/line 8-way D-cache, 32KB 64b/line 8-way I-cache, 1MB 64b/line 8-way L2 cache, 32MB 64b/line 16-way L3 cache cpu1: smt 0, core 1, package 0 cpu2 at mainbus0: apid 4 (application processor) cpu2: AMD Ryzen 9 7900X 12-Core Processor, 4700.00 MHz, 19-61-02 cpu2: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,PCLMUL,MWAIT,SSSE3,FMA3,CX16,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,AES,XSAVE,AVX,F16C,RDRAND,NXE,MMXX,FFXSR,PAGE1GB,RDTSCP,LONG,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,ABM,SSE4A,MASSE,3DNOWP,OSVW,IBS,SKINIT,TCE,TOPEXT,CPCTR,DBKP,PCTRL3,MWAITX,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,PQM,AVX512F,AVX512DQ,RDSEED,ADX,SMAP,AVX512IFMA,CLFLUSHOPT,CLWB,AVX512CD,SHA,AVX512BW,AVX512VL,AVX512VBMI,UMIP,PKU,L1DF,IBPB,IBRS,STIBP,SSBD,XSAVEOPT,XSAVEC,XGETBV1,XSAVES cpu2: 32KB 64b/line 8-way D-cache, 32KB 64b/line 8-way I-cache, 1MB 64b/line 8-way L2 cache, 32MB 64b/line 16-way L3 cache cpu2: smt 0, core 2, package 0 cpu3 at mainbus0: apid 6 (application processor) cpu3: AMD Ryzen 9 7900X 12-Core Processor, 4700.00 MHz, 19-61-02 cpu3:
Re: iwx0 fatal firmware error - Status: 0x239, OpenBSD 7.3 #1122 2023-March-19
On Mon, Apr 03, 2023 at 09:56:20PM +0200, Stefan Sperling wrote: Hello Stefan, > This particular sysassert code (0x20002806) is a known issue since > the -77 firmware update. I don't know what is triggering this error > and so far I have failed to reproduce it. Apparently something is > wrong with the scan command but I don't know what is wrong exactly. > > As a workaround, does it help to disable background scanning by > temporarily hard-coding the MAC address of the working 2GHz AP? > > ifconfig iwx0 bssid 04:20:84:31:dd:ab As you might remember, I've also encountered the same issue with iwx, on two machines -- I could rack up a few hundred timeouts in an hour if I was unlucky. Since, as you suggested above, forcing the bssid to a specific address, I've had no timeouts on either machine in a bit over 24 hours, even when I've been deliberately hammering the network on both machines! So that's a good short-term fix for me, though whether or not it helps you work out the underlying cause, I don't know! Laurie
uvideo0: can't allocate mmap buffer
On a new-ish Ryzen 7900X machine my USB webcam randomly fails to start (normally after 1 or 2 times of working, though it can sometimes fail to start even on the first attempt), leaving this in dmesg: uvideo0: can't allocate mmap buffer! Taking the device out and reinserting it doesn't fix the problem -- only a reboot allows it to work again. This card worked without any such issue on a Ryzen 9 machine and I must admit that I can't really guess what might have changed to cause mmap to fail in allocating a buffer. I'm attaching a dmesg with jsg's drm patches from this morning included (I've had exactly the same outcome with snapshots, including Friday(ish)'s for the last 2 or 3 weeks). Laurie OpenBSD 7.2-current (GENERIC.MP) #83: Mon Jan 9 07:58:57 GMT 2023 ltr...@overdrive.tratt.net:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 33390415872 (31843MB) avail mem = 32359079936 (30860MB) random: good seed from bootblocks mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: SMBIOS rev. 3.5 @ 0xa9b2b000 (43 entries) bios0: vendor American Megatrends International, LLC. version "1.40" date 11/23/2022 bios0: Micro-Star International Co., Ltd. MS-7D67 efi0 at bios0: UEFI 2.8 efi0: American Megatrends rev 0x5001a acpi0 at bios0: ACPI 6.4 acpi0: sleep states S0 S3 S4 S5 acpi0: tables DSDT FACP IVRS SSDT SSDT FIDT MCFG HPET WDRT UEFI FPDT VFCT TPM2 SSDT CRAT CDIT BGRT SSDT SSDT SSDT SSDT WSMT APIC SSDT SSDT SSDT SSDT SSDT SSDT SSDT SSDT acpi0: wakeup devices GPP3(S4) GPP4(S4) GPP5(S4) GPP6(S4) GP17(S4) XHC0(S4) XHC1(S4) XHC2(S4) GPP0(S4) GPP1(S4) GPP2(S4) GPP7(S4) UP00(S4) DP00(S4) NV00(S4) DP20(S4) [...] acpitimer0 at acpi0: 3579545 Hz, 32 bits acpimcfg0 at acpi0 acpimcfg0: addr 0xf000, bus 0-127 acpihpet0 at acpi0: 14318180 Hz acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: AMD Ryzen 9 7900X 12-Core Processor, 4700.00 MHz, 19-61-02 cpu0: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,PCLMUL,MWAIT,SSSE3,FMA3,CX16,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,AES,XSAVE,AVX,F16C,RDRAND,NXE,MMXX,FFXSR,PAGE1GB,RDTSCP,LONG,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,ABM,SSE4A,MASSE,3DNOWP,OSVW,IBS,SKINIT,TCE,TOPEXT,CPCTR,DBKP,PCTRL3,MWAITX,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,PQM,AVX512F,AVX512DQ,RDSEED,ADX,SMAP,AVX512IFMA,CLFLUSHOPT,CLWB,AVX512CD,SHA,AVX512BW,AVX512VL,AVX512VBMI,UMIP,PKU,L1DF,IBPB,IBRS,STIBP,SSBD,XSAVEOPT,XSAVEC,XGETBV1,XSAVES cpu0: 32KB 64b/line 8-way D-cache, 32KB 64b/line 8-way I-cache, 1MB 64b/line 8-way L2 cache, 32MB 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 25MHz cpu0: mwait min=64, max=64, C-substates=1.1, IBE cpu1 at mainbus0: apid 2 (application processor) cpu1: AMD Ryzen 9 7900X 12-Core Processor, 4700.00 MHz, 19-61-02 cpu1: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,PCLMUL,MWAIT,SSSE3,FMA3,CX16,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,AES,XSAVE,AVX,F16C,RDRAND,NXE,MMXX,FFXSR,PAGE1GB,RDTSCP,LONG,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,ABM,SSE4A,MASSE,3DNOWP,OSVW,IBS,SKINIT,TCE,TOPEXT,CPCTR,DBKP,PCTRL3,MWAITX,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,PQM,AVX512F,AVX512DQ,RDSEED,ADX,SMAP,AVX512IFMA,CLFLUSHOPT,CLWB,AVX512CD,SHA,AVX512BW,AVX512VL,AVX512VBMI,UMIP,PKU,L1DF,IBPB,IBRS,STIBP,SSBD,XSAVEOPT,XSAVEC,XGETBV1,XSAVES cpu1: 32KB 64b/line 8-way D-cache, 32KB 64b/line 8-way I-cache, 1MB 64b/line 8-way L2 cache, 32MB 64b/line 16-way L3 cache cpu1: smt 0, core 1, package 0 cpu2 at mainbus0: apid 4 (application processor) cpu2: AMD Ryzen 9 7900X 12-Core Processor, 4700.00 MHz, 19-61-02 cpu2: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,PCLMUL,MWAIT,SSSE3,FMA3,CX16,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,AES,XSAVE,AVX,F16C,RDRAND,NXE,MMXX,FFXSR,PAGE1GB,RDTSCP,LONG,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,ABM,SSE4A,MASSE,3DNOWP,OSVW,IBS,SKINIT,TCE,TOPEXT,CPCTR,DBKP,PCTRL3,MWAITX,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,PQM,AVX512F,AVX512DQ,RDSEED,ADX,SMAP,AVX512IFMA,CLFLUSHOPT,CLWB,AVX512CD,SHA,AVX512BW,AVX512VL,AVX512VBMI,UMIP,PKU,L1DF,IBPB,IBRS,STIBP,SSBD,XSAVEOPT,XSAVEC,XGETBV1,XSAVES cpu2: 32KB 64b/line 8-way D-cache, 32KB 64b/line 8-way I-cache, 1MB 64b/line 8-way L2 cache, 32MB 64b/line 16-way L3 cache cpu2: smt 0, core 2, package 0 cpu3 at mainbus0: apid 6 (application processor) cpu3: AMD Ryzen 9 7900X 12-Core Processor, 4700.00 MHz, 19-61-02 cpu3:
Re: ACPI "Undefined scope"
On Tue, Nov 29, 2022 at 10:34:58AM +0100, Mark Kettenis wrote: Hello Mark, >> "AMDIF031" at acpi0 not configured > That is some sort of new GPIO controller that we don't support yet. > Not used on your machine though. A quick look at the Linux driver suggests that they treat AMDIF031 as the other amdgpio devices, but with 24 pins, not 8 [1, 2]. That doesn't quite map onto our amdgpio driver though (where `npins` is 184 pins)? But I suppose if my machine doesn't use it, there's no way I can test it! A bit more time with the machine has shown that it has more problems than I first realised. In particular, things randomly stop working (notably iwx and input into X, where it won't respond to keyboard/mouse, but I can Ctrl+Alt+F1 switch to the console and work fine there), and only a hard reboot fixes them. I'm not quite sure what to make of that: there's no obvious trigger, and the machine can last anywhere from about 14-45 minutes before hitting such an issue. Laurie [1] https://github.com/torvalds/linux/blob/cdeffe87f790dfd1baa193020411ce9a538446d7/drivers/gpio/gpio-amdpt.c#L137 [2] https://github.com/torvalds/linux/blob/cdeffe87f790dfd1baa193020411ce9a538446d7/drivers/gpio/gpio-amdpt.c#L137
Panic on Framework Gen 2
On my Framework (gen 2) laptop I experience intermittent panics, most without an obvious cause, with -current (this is a snapshot from last week, with a stock kernel + Ulf's trackpad patch from [1], which seems unlikely to be related to this panic). Here's my transcript (photo of the panic at [2]) of the most recent: panic: pool_do_get: namei free list modified: page 0x80002799b000: item addr 0x80002799b8aea6f2 154d Stopped at db_enter+0x10: popq %rbp COMMAND * xenodm reaper drmwq db_enter() at db_enter+0x10 panic(81fccef5) + panic+0xbf pool_do_get(822f0e10,1,800026a01f04) at pool_do_get+0x321 pool_get(822fe0e10,1) at pool_get+0x96 namei(800026a01ff0) at namei+0x6e dofstatat(80002619e2a0,ff9c,9784ac72740, syscall(800026a02250) at syscall+0x3f Xsyscall() at Xsyscall+0x128 end of kernel end trace frame: 0x7f7da5f0, count: 7 One thing that another user and I have been discussing is that making applications full screen (at least with XFCE's compositor) fairly reliably causes a panic. Laurie [1] https://marc.info/?l=openbsd-tech=166310982023026=2 [2] https://postimg.cc/d7qpzcK8 OpenBSD 7.2 (GENERIC.MP) #8: Tue Sep 20 08:57:19 BST 2022 ltr...@phase.tratt.net:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 34006142976 (32430MB) avail mem = 32958099456 (31431MB) random: good seed from bootblocks mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: SMBIOS rev. 3.3 @ 0x3f085000 (54 entries) bios0: vendor INSYDE Corp. version "03.04" date 07/15/2022 bios0: Framework Laptop (12th Gen Intel Core) acpi0 at bios0: ACPI 6.3 acpi0: sleep states S0 S3 S4 S5 acpi0: tables DSDT FACP UEFI SSDT SSDT SSDT SSDT SSDT SSDT SSDT LPIT WSMT SSDT SSDT DBGP DBG2 NHLT ECDT HPET APIC MCFG SSDT DMAR SSDT SSDT SSDT SSDT FPDT ASF! PHAT BGRT acpi0: wakeup devices PEG0(S4) PEGP(S4) PEGP(S4) PEGP(S4) XHCI(S4) XDCI(S4) HDAS(S4) CNVW(S4) RP01(S4) PXSX(S4) RP02(S4) PXSX(S4) RP03(S4) PXSX(S4) RP04(S4) PXSX(S4) [...] acpitimer0 at acpi0: 3579545 Hz, 24 bits acpiec0 at acpi0 acpihpet0 at acpi0: 1920 Hz acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: 12th Gen Intel(R) Core(TM) i7-1260P, 1996.02 MHz, 06-9a-03 cpu0: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,TSC_ADJUST,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,RDSEED,ADX,SMAP,CLFLUSHOPT,CLWB,PT,SHA,UMIP,PKU,MD_CLEAR,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,XSAVEC,XGETBV1,XSAVES cpu0: 48KB 64b/line 12-way D-cache, 32KB 64b/line 8-way I-cache, 1MB 64b/line 10-way L2 cache, 18MB 64b/line 12-way L3 cache cpu0: smt 0, core 0, package 0 mtrr: Pentium Pro MTRR support, 10 var ranges, 88 fixed ranges cpu0: apic clock running at 38MHz cpu0: mwait min=64, max=64, C-substates=0.2.0.2.0.1.0.1, IBE cpu1 at mainbus0: apid 1 (application processor) cpu1: 12th Gen Intel(R) Core(TM) i7-1260P, 1995.57 MHz, 06-9a-03 cpu1: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,TSC_ADJUST,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,RDSEED,ADX,SMAP,CLFLUSHOPT,CLWB,PT,SHA,UMIP,PKU,MD_CLEAR,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,XSAVEC,XGETBV1,XSAVES cpu1: 48KB 64b/line 12-way D-cache, 32KB 64b/line 8-way I-cache, 1MB 64b/line 10-way L2 cache, 18MB 64b/line 12-way L3 cache cpu1: smt 1, core 0, package 0 cpu2 at mainbus0: apid 8 (application processor) cpu2: 12th Gen Intel(R) Core(TM) i7-1260P, 1995.57 MHz, 06-9a-03 cpu2: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,TSC_ADJUST,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,RDSEED,ADX,SMAP,CLFLUSHOPT,CLWB,PT,SHA,UMIP,PKU,MD_CLEAR,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,XSAVEC,XGETBV1,XSAVES cpu2: 48KB 64b/line 12-way D-cache, 32KB 64b/line 8-way I-cache, 1MB 64b/line 10-way L2 cache, 18MB 64b/line 12-way L3 cache cpu2: smt 0, core 4, package 0 cpu3 at mainbus0: apid 9 (application processor) cpu3: 12th Gen Intel(R) Core(TM) i7-1260P, 1995.57 MHz, 06-9a-03 cpu3:
Re: uvm_fault on Framework 12th Gen Intel
On Wed, Aug 03, 2022 at 09:10:01AM +0100, Laurence Tratt wrote: [Framework laptop keyboard encoding crashing] > I did a bit more digging and I've confused myself considerably, possibly > because I don't know how wscons works. If I boot the machine without the > external keyboard attached, stay in the console (i.e. outside X), and then > plug in the external keyboard causes the laptop keyboard behaves bizarrely: > for example "1" and "a" are inverted (i.e. I press "1" and "a" is > displayed). After I unplug the external keyboard, I seem to get a new (more > bizarre) map in the console where "a" is some sort of control code. I've been poking around a bit more trying to understand what's going on, and I have some more information -- but nothing that I'd say is exactly definitive. Although I didn't realise it (since it was the first thing I did in the installer) /etc/kbdtype is set: $ cat /etc/kbdtype uk And indeed, the first thing after the kernel boots and userland starts doing its thing says: kbd: keyboard mapping set to uk Provided I don't have an external keyboard plugged in, then on the console the laptop keyboard really does reflect the UK layout (including things like the £ key), but X does not reflect that. However if I later try to set uk encoding with kbd (as /etc/rc does with /etc/kbdtype) it doesn't work: $ doas kbd uk kbd: WSKBDIO_SETENCODING /dev/wskbd0: Bad address I'm unsure how the call to kbd from /etc/rc can work but not subsequently if I issue it manually. The final piece of information I've dug out is that (even with Miod's patch), kbd -l causes a uvm_fault panic in wskbd_displayioctl_sc. I think this is just the same underlying bug manifesting in a different way Laurie
Re: uvm_fault on Framework 12th Gen Intel
On Wed, Aug 03, 2022 at 07:17:27AM +0200, Anton Lindqvist wrote: Hello Anton, >> `disable ucc` has no effect (it doesn't attach normally, so I guess that's >> not surprising?) -- I still get a kernel panic. > ucc does attach according to your dmesg. However, while ucc attaches it > sets it's own layout to `KB_US | KB_NOENCODING', meaning that > wskbd_load_keymap() requests are ignored since only one map is provided. OK, this one baffled me for a while! You're quite right, in the very first dmesg I got (which is the one I sent in my first email): ucc0 at uhidev1 reportid 1: 4 usages, 3 keys, enum wskbd1 at ucc0 mux 1 but I have a record of several subsequent dmesg's and not one of them contains ucc -- even if I boot with the same snapshot kernel (#658). It turns out that's because my first dmesg was recorded while attached to an external keyboard (via a hub) and all the subsequent ones without an external keyboard. Here's wsconsctl if I boot without the external keyboard attached: $ doas wsconsctl | grep "^keyboard" wsconsctl: Use explicit arg to view keyboard.map. keyboard.type=pc-xt keyboard.bell.pitch=400 keyboard.bell.period=100 keyboard.bell.volume=50 keyboard.bell.pitch.default=400 keyboard.bell.period.default=100 keyboard.bell.volume.default=50 keyboard.repeat.del1=400 keyboard.repeat.deln=100 keyboard.repeat.del1.default=400 keyboard.repeat.deln.default=100 keyboard.ledstate=0 keyboard.encoding=unknown_0 And when I attach the external keyboard this becomes: $ doas wsconsctl | grep "^keyboard" keyboard.type=pc-xt keyboard.bell.pitch=400 keyboard.bell.period=100 keyboard.bell.volume=50 keyboard.bell.pitch.default=400 keyboard.bell.period.default=100 keyboard.bell.volume.default=50 keyboard.repeat.del1=400 keyboard.repeat.deln=100 keyboard.repeat.del1.default=400 keyboard.repeat.deln.default=100 keyboard.ledstate=0 keyboard.encoding=uk keyboard1.type=usb keyboard1.bell.pitch=400 keyboard1.bell.period=100 keyboard1.bell.volume=50 keyboard1.bell.pitch.default=400 keyboard1.bell.period.default=100 keyboard1.bell.volume.default=50 keyboard1.repeat.del1=400 keyboard1.repeat.deln=100 keyboard1.repeat.del1.default=400 keyboard1.repeat.deln.default=100 keyboard1.ledstate=0 keyboard1.encoding=uk keyboard2.type=usb keyboard2.bell.pitch=400 keyboard2.bell.period=100 keyboard2.bell.volume=50 keyboard2.bell.pitch.default=400 keyboard2.bell.period.default=100 keyboard2.bell.volume.default=50 keyboard2.repeat.del1=400 keyboard2.repeat.deln=100 keyboard2.repeat.del1.default=400 keyboard2.repeat.deln.default=100 keyboard2.ledstate=0 keyboard2.encoding=us.noencoding keyboard3.type=usb keyboard3.bell.pitch=400 keyboard3.bell.period=100 keyboard3.bell.volume=50 keyboard3.bell.pitch.default=400 keyboard3.bell.period.default=100 keyboard3.bell.volume.default=50 keyboard3.repeat.del1=400 keyboard3.repeat.deln=100 keyboard3.repeat.del1.default=400 keyboard3.repeat.deln.default=100 keyboard3.ledstate=0 keyboard3.encoding=uk Note that after the external keyboard attaches keyboard.encoding has changed from unknown_0 to uk; if I unplug the external keyboard the encoding goes back to unknown_0. I did a bit more digging and I've confused myself considerably, possibly because I don't know how wscons works. If I boot the machine without the external keyboard attached, stay in the console (i.e. outside X), and then plug in the external keyboard causes the laptop keyboard behaves bizarrely: for example "1" and "a" are inverted (i.e. I press "1" and "a" is displayed). After I unplug the external keyboard, I seem to get a new (more bizarre) map in the console where "a" is some sort of control code. I eventually managed to trigger a panic in wskbd_translate by doing this: https://postimg.cc/JtrN1GWy Note this happened with the stock #658 kernel (i.e. without Miod's patch). I suppose this isn't a very interesting panic in the sense that something has gone wrong quite before this panic occurred, but still, it might be useful info for someone! Laurie
Re: uvm_fault on Framework 12th Gen Intel
On Tue, Aug 02, 2022 at 07:00:52PM +, Miod Vallat wrote: Hello Miod, > Do the uvm_fault errors disappear if you `boot -c' and `disable ucc'? `disable ucc` has no effect (it doesn't attach normally, so I guess that's not surprising?) -- I still get a kernel panic. > Or if you `disable pckbd'? `disable pckbd` causes lines in dmesg like: pms1: disable error ... pckbc: command timeout pms1: disable error and so on. The keyboard is non-operational at that point and, since I (temporarily at least) don't have another machine, I don't have any way of executing wsconsctl to see if it panics. I can try tomorrow if it would be helpful? The patch you provided works (thanks!): $ doas wsconsctl keyboard.encoding keyboard.encoding=unknown_0 $ doas wsconsctl keyboard.encoding=uk wsconsctl: WSKBDIO_SETENCODING: Bad address $ doas wsconsctl keyboard.encoding=gb wsconsctl: gb: not a valid encoding I realise as I type the above that I've never had a need to configure a keyboard encoding before. I guess the "unknown_0" is unexpected? It may also be significant that "uk" (which I *guess* is the keyboard's encoding) borks in a different way than "gb"? Laurie
Re: uvm_fault on Framework 12th Gen Intel
On Tue, Aug 02, 2022 at 08:56:09PM +1000, Jonathan Gray wrote: Hello Jonathan, >> I'm also starting to understand a bit more about some of the random panics: >> they seem to happen very soon after X starts. Sometimes the mouse appears as >> a two inch square of weird colours (!) -- things only last for a few seconds >> after that. Only once have I got a visible panic out of this which said >> solely: >> >> uvm_fault(0x822f0400, 0xfff80001660014, 0, 1) -> e >> drm: Global state not read locked >> drm: Global state not read locked >> >> That particular panic was on my custom compiled kernel, not the most recent >> snapshot. > I don't see panics on a thinkpad with the same i7-1260P cpu > > Does this change help? > > drm/i915/adlp: Fix register corruption after DDI clock enabling > > From Imre Deak > 59207e63801fbcd39ca68df6e2ba5ae90f76c0c3 in mainline linux > > https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=59207e63801fbcd39ca68df6e2ba5ae90f76c0c3 A kernel with this patch has now survived 10 reboots (previously I was getting a panic perhaps 1 time in 3), so I think it's quite likely that the effect is real. Thanks! Laurie
Re: uvm_fault on Framework 12th Gen Intel
On Tue, Aug 02, 2022 at 11:54:48AM +1000, Jonathan Gray wrote:
Hello Jonathan,
>> I've just got my sticky mits on a Framework 12th Gen Intel laptop. It
>> somewhat works, but regularly hits kernel panics and other oddities on
>> -current. I haven't worked out why yet, but uvm_faults seem to be frequent.
>> For example setting the keyboard encoding causes a uvm_fault.
>>
>> $ doas wsconsctl keyboard.encoding=uk
>> uvm_fault(0xfd87b4e6a780, 0x8, 0, 1) -> e
>>
>> Screenshot of this particular panic at https://postimg.cc/nM5rLGY6
> wskbd_load_keymap+0x33: movl 0x8(%rax),%ecx
> wskbd_displayioctl_sc+0x76c
> wskbd_do_ioctl_sc+0xbb
> wskbd_ioctl+0x4a
> VOP_IOCTL+0x5c
> vn_ioctl+0x75
> sys_ioctl+0x2c4
>
>0x81017abe <+46>:je 0x81017b3e
>
>0x81017ac0 <+48>:mov(%rdi),%rax
>0x81017ac3 <+51>:mov0x8(%rax),%ecx
>0x81017ac6 <+54>:xor%r13d,%r13d
>0x81017ac9 <+57>:mov$0x16,%r15d
>0x81017acf <+63>:test %ecx,%ecx
>0x81017ad1 <+65>:jle0x81017bba
>
>
> info line *0x81017ac3
> Line 405 of "/sys/dev/wscons/wskbdutil.c"
>starts at address 0x81017abe
>and ends at 0x81017ad1 .
>
>395 int
>396 wskbd_load_keymap(const struct wskbd_mapdata *mapdata, kbd_t layout,
>397 struct wscons_keymap **map, int *maplen)
>398 {
>399 int i, s, kc, stack_ptr;
>400 const keysym_t *kp;
>401 const struct wscons_keydesc *mp, *stack[10];
>402 kbd_t cur;
>403 keysym_t ksg;
>404
>405 for (cur = layout & ~KB_HANDLEDBYWSKBD, stack_ptr = 0;
>406 cur != 0; stack_ptr++) {
>407 mp = mapdata->keydesc;
>408 while (mp->map_size > 0) {
>409 if (cur == 0 || mp->name == cur) {
>410 break;
>411 }
>412 mp++;
>413 }
>414
>415 if (stack_ptr == nitems(stack))
>416 panic("wskbd_load_keymap: %d: recursion too
> deep",
>417mapdata->layout);
>418 if (mp->map_size <= 0)
>419 return(EINVAL);
>420
>421 stack[stack_ptr] = mp;
>422 cur = mp->base;
>423 }
Thanks for expanding this (and duly noted!).
I also noted your commit to add some devices. The salient part of the dmesg
diff (ignoring all the CPU frequencies changing) is:
--- dmesg1Tue Aug 2 10:26:22 2022
+++ dmesg2Tue Aug 2 10:34:02 2022
@@ -1,7 +1,7 @@
-OpenBSD 7.2-beta (GENERIC.MP) #658: Mon Aug 1 10:06:39 MDT 2022
-dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
+OpenBSD 7.2-beta (GENERIC.MP) #0: Tue Aug 2 10:16:12 BST 2022
+ltr...@phase.tratt.net:/usr/src/sys/arch/amd64/compile/GENERIC.MP
real mem = 34006142976 (32430MB)
-avail mem = 32958144512 (31431MB)
+avail mem = 32958132224 (31431MB)
random: good seed from bootblocks
mpath0 at root
scsibus0 at mpath0: 256 targets
@@ -251,18 +251,18 @@
"Intel Core 12G DTT" rev 0x02 at pci0 dev 4 function 0 not configured
ppb0 at pci0 dev 6 function 0 "Intel Core 12G PCIE" rev 0x02: msi
pci1 at ppb0 bus 1
-nvme0 at pci1 dev 0 function 0 vendor "SanDisk", unknown product 0x5011 rev
0x01: msix, NVMe 1.4
+nvme0 at pci1 dev 0 function 0 "SanDisk SN850" rev 0x01: msix, NVMe 1.4
nvme0: WDS100T1X0E-00AFY0, firmware 614900WD, serial XYZ
scsibus1 at nvme0: 2 targets, initiator 0
sd0 at scsibus1 targ 1 lun 0:
sd0: 953869MB, 512 bytes/sector, 1953525168 sectors
ppb1 at pci0 dev 7 function 0 "Intel Core 12G PCIE" rev 0x02: msi
pci2 at ppb1 bus 2
-ppb2 at pci0 dev 7 function 1 vendor "Intel", unknown product 0x463f rev
0x02: msi
+ppb2 at pci0 dev 7 function 1 "Intel Core 12G PCIE" rev 0x02: msi
pci3 at ppb2 bus 43
ppb3 at pci0 dev 7 function 2 "Intel Core 12G PCIE" rev 0x02: msi
pci4 at ppb3 bus 84
-ppb4 at pci0 dev 7 function 3 vendor "Intel", unknown product 0x461f rev
0x02: msi
+ppb4 at pci0 dev 7 function 3 "Intel Core 12G PCIE" rev 0x02: msi
pci5 at ppb4 bus 125
"Intel Core 12G GNA" rev 0x02 at pci0 dev 8 function 0 not configured
"Intel Core 12G CL" rev 0x01 at pci0 dev 10 function 0 not configured
@@ -288,7 +288,7 @@
iic2 at dwiic2
ihidev1 at iic2 addr 0x2c gpio 3, vendor 0x93a product 0x274, PIXA3854
ihidev1: 67 report ids
-imt0 at ihidev1: clickpad, 5 contacts
+imt0 at ihidev1: touchpad, 5 contacts
wsmouse0 at imt0 mux 0
ims0 at ihidev1 reportid 2: 2 buttons
wsmouse1 at ims0 mux 0
@@ -300,8 +300,9 @@
hid at ihidev1 reportid 66 not configured
hid at ihidev1 reportid 67 not configured
"Intel 600 Series HECI" rev
uvm_fault on Framework 12th Gen Intel
I've just got my sticky mits on a Framework 12th Gen Intel laptop. It somewhat works, but regularly hits kernel panics and other oddities on -current. I haven't worked out why yet, but uvm_faults seem to be frequent. For example setting the keyboard encoding causes a uvm_fault. $ doas wsconsctl keyboard.encoding=uk uvm_fault(0xfd87b4e6a780, 0x8, 0, 1) -> e Screenshot of this particular panic at https://postimg.cc/nM5rLGY6 I suspect that it's simply that some hardware isn't yet fully supported. There are a few more "not configured"s than normal in the dmesg and it even contains this, which is a new one on me (presumably PCI related?): 0:31:5: mem address conflict 0xfe01/0x1000 Laurie OpenBSD 7.2-beta (GENERIC.MP) #658: Mon Aug 1 10:06:39 MDT 2022 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 34006142976 (32430MB) avail mem = 32958140416 (31431MB) random: good seed from bootblocks mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: SMBIOS rev. 3.3 @ 0x3f085000 (54 entries) bios0: vendor INSYDE Corp. version "03.04" date 07/15/2022 bios0: Framework Laptop (12th Gen Intel Core) acpi0 at bios0: ACPI 6.3 acpi0: sleep states S0 S3 S4 S5 acpi0: tables DSDT FACP UEFI SSDT SSDT SSDT SSDT SSDT SSDT SSDT LPIT WSMT SSDT SSDT DBGP DBG2 NHLT ECDT HPET APIC MCFG SSDT DMAR SSDT SSDT SSDT SSDT FPDT ASF! PHAT BGRT acpi0: wakeup devices PEG0(S4) PEGP(S4) PEGP(S4) PEGP(S4) XHCI(S4) XDCI(S4) HDAS(S4) CNVW(S4) RP01(S4) PXSX(S4) RP02(S4) PXSX(S4) RP03(S4) PXSX(S4) RP04(S4) PXSX(S4) [...] acpitimer0 at acpi0: 3579545 Hz, 24 bits acpiec0 at acpi0 acpihpet0 at acpi0: 1920 Hz acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: 12th Gen Intel(R) Core(TM) i7-1260P, 4689.83 MHz, 06-9a-03 cpu0: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,TSC_ADJUST,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,RDSEED,ADX,SMAP,CLFLUSHOPT,CLWB,PT,SHA,UMIP,PKU,MD_CLEAR,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,XSAVEC,XGETBV1,XSAVES cpu0: 48KB 64b/line 12-way D-cache, 32KB 64b/line 8-way I-cache, 1MB 64b/line 10-way L2 cache, 18MB 64b/line 12-way L3 cache cpu0: smt 0, core 0, package 0 mtrr: Pentium Pro MTRR support, 10 var ranges, 88 fixed ranges cpu0: apic clock running at 38MHz cpu0: mwait min=64, max=64, C-substates=0.2.0.2.0.1.0.1, IBE cpu1 at mainbus0: apid 1 (application processor) cpu1: 12th Gen Intel(R) Core(TM) i7-1260P, 4689.82 MHz, 06-9a-03 cpu1: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,TSC_ADJUST,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,RDSEED,ADX,SMAP,CLFLUSHOPT,CLWB,PT,SHA,UMIP,PKU,MD_CLEAR,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,XSAVEC,XGETBV1,XSAVES cpu1: 48KB 64b/line 12-way D-cache, 32KB 64b/line 8-way I-cache, 1MB 64b/line 10-way L2 cache, 18MB 64b/line 12-way L3 cache cpu1: smt 1, core 0, package 0 cpu2 at mainbus0: apid 8 (application processor) cpu2: 12th Gen Intel(R) Core(TM) i7-1260P, 4689.87 MHz, 06-9a-03 cpu2: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,TSC_ADJUST,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,RDSEED,ADX,SMAP,CLFLUSHOPT,CLWB,PT,SHA,UMIP,PKU,MD_CLEAR,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,XSAVEC,XGETBV1,XSAVES cpu2: 48KB 64b/line 12-way D-cache, 32KB 64b/line 8-way I-cache, 1MB 64b/line 10-way L2 cache, 18MB 64b/line 12-way L3 cache cpu2: smt 0, core 4, package 0 cpu3 at mainbus0: apid 9 (application processor) cpu3: 12th Gen Intel(R) Core(TM) i7-1260P, 4689.88 MHz, 06-9a-03 cpu3: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,TSC_ADJUST,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,RDSEED,ADX,SMAP,CLFLUSHOPT,CLWB,PT,SHA,UMIP,PKU,MD_CLEAR,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,XSAVEC,XGETBV1,XSAVES cpu3: 48KB 64b/line 12-way D-cache, 32KB 64b/line 8-way I-cache, 1MB 64b/line 10-way L2 cache, 18MB 64b/line 12-way L3 cache cpu3: smt 1, core 4, package 0 cpu4 at
suspend: xhci0: command ring abort timeout
One of my amd64-current boxes only suspends correctly about 50% of the time, but gets completely stuck the rest of the time (i.e. I have to hard reboot and fsck). I've now noticed a correlation between successful and unsuccessful suspends and an xhci error. From /var/log/messages, here's a successful suspend: Jul 7 23:16:28 overdrive apmd: system suspending Jul 7 23:16:28 overdrive apmd: battery status: absent. external power status: not known. estimated battery life 0% Jul 7 23:16:29 overdrive /bsd: ugen0 detached Jul 7 23:16:30 overdrive /bsd: uhid0 detached Jul 7 23:16:30 overdrive /bsd: uhidev0 detached Jul 7 23:16:30 overdrive /bsd: ugen1 detached Jul 7 23:16:32 overdrive /bsd: uhub2 detached Jul 7 23:16:33 overdrive /bsd: audio0 detached Jul 7 23:16:33 overdrive /bsd: uaudio0 detached Jul 7 23:16:33 overdrive /bsd: midi0 detached Jul 7 23:16:34 overdrive /bsd: umidi0 detached Jul 7 23:16:34 overdrive /bsd: ugen2 detached Here's an unsuccessful suspend: Jul 8 10:06:11 overdrive apmd: system suspending Jul 8 10:06:11 overdrive apmd: battery status: absent. external power status: not known. estimated battery life 0% Jul 8 10:06:12 overdrive /bsd: ugen0 detached Jul 8 10:06:13 overdrive /bsd: xhci0: command ring abort timeout Jul 8 10:06:13 overdrive /bsd: uhid0 detached Jul 8 10:06:13 overdrive /bsd: uhidev0 detached Jul 8 10:06:13 overdrive /bsd: ugen1 detached Jul 8 10:06:14 overdrive /bsd: xhci0: command ring abort timeout Jul 8 10:06:15 overdrive last message repeated 2 times Jul 8 10:06:15 overdrive /bsd: uhub2 detached Jul 8 10:06:16 overdrive /bsd: xhci0: command ring abort timeout Jul 8 10:06:18 overdrive last message repeated 3 times Jul 8 10:06:18 overdrive /bsd: uaudio0: can't reset interface Jul 8 10:06:19 overdrive /bsd: xhci0: command ring abort timeout Jul 8 10:06:19 overdrive /bsd: uaudio0: can't reset interface Jul 8 10:06:19 overdrive /bsd: audio0 detached Jul 8 10:06:19 overdrive /bsd: uaudio0 detached Jul 8 10:06:19 overdrive /bsd: midi0 detached Jul 8 10:06:20 overdrive /bsd: xhci0: command ring abort timeout Jul 8 10:06:20 overdrive /bsd: xhci0: command ring abort timeout Jul 8 10:06:20 overdrive /bsd: umidi0 detached Jul 8 10:06:20 overdrive /bsd: ugen2 detached Jul 8 10:06:21 overdrive /bsd: xhci0: command ring abort timeout In other words lots of "xhci0: command ring abort timeout" messages appear. I have tried fiddling with every USB option in the BIOS to no avail. "disable xhci" means that I don't have keyboard, mouse, or network, so I can't really say if that solves anything or not ;) The "xhci0: command ring abort timeout" messages only appear after I try suspending (i.e. they don't ever seem to happen in normal operation). Laurie OpenBSD 7.1-current (GENERIC.MP) #607: Wed Jul 6 09:06:31 MDT 2022 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 34212954112 (32628MB) avail mem = 33158705152 (31622MB) random: good seed from bootblocks mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: SMBIOS rev. 3.3 @ 0xcb7e6000 (72 entries) bios0: vendor American Megatrends Inc. version "2803" date 04/28/2022 bios0: ASUS ROG STRIX B550-E GAMING acpi0 at bios0: ACPI 6.0 acpi0: sleep states S0 S3 S4 S5 acpi0: tables DSDT FACP SSDT SSDT SSDT FIDT FPDT MCFG HPET IVRS VFCT BGRT WPBT PCCT SSDT CRAT CDIT SSDT SSDT SSDT SSDT WSMT APIC SSDT SSDT acpi0: wakeup devices GP12(S4) GP13(S4) XHC0(S4) GP30(S4) GP31(S4) X161(S4) X162(S4) PTXH(S4) X1_1(S4) X1_2(S4) WIFI(S4) I225(S4) X163(S4) M2_2(S4) acpitimer0 at acpi0: 3579545 Hz, 32 bits acpimcfg0 at acpi0 acpimcfg0: addr 0xf000, bus 0-127 acpihpet0 at acpi0: 14318180 Hz acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: AMD Ryzen 9 5900X 12-Core Processor, 3700.49 MHz, 19-21-00 cpu0: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,PCLMUL,MWAIT,SSSE3,FMA3,CX16,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,AES,XSAVE,AVX,F16C,RDRAND,NXE,MMXX,FFXSR,PAGE1GB,RDTSCP,LONG,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,ABM,SSE4A,MASSE,3DNOWP,OSVW,IBS,SKINIT,TCE,TOPEXT,CPCTR,DBKP,PCTRL3,MWAITX,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,PQM,RDSEED,ADX,SMAP,CLFLUSHOPT,CLWB,SHA,UMIP,PKU,IBPB,IBRS,STIBP,SSBD,XSAVEOPT,XSAVEC,XGETBV1,XSAVES cpu0: 32KB 64b/line 8-way D-cache, 32KB 64b/line 8-way I-cache, 512KB 64b/line 8-way L2 cache, 32MB 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 99MHz cpu0: mwait min=64, max=64, C-substates=1.1, IBE cpu1 at mainbus0: apid 2 (application processor) cpu1: AMD Ryzen 9 5900X 12-Core Processor, 3699.99 MHz, 19-21-00 cpu1:
Re: amdgpu not reliably resuming?
On Tue, May 10, 2022 at 09:26:48PM +0100, Laurence Tratt wrote: > Maybe! Would that device have some sort of interaction with X one way or > another? Because it seems that I can reliably suspend/resume if xenodm is > on the login page, but after I've logged in via xenodm, suspend rarely > works and, if it does, resume almost certainly doesn't. Partly based on a prompt from Mike Larkin, I went through all my running applications to see if anything caused suspend problems and I believe I've now found the culprit: web browsers, both Firefox and Chrome. To cut a long story short, and for the benefit of the mailing list archive, if I used Firefox or Chrome (with long-standing config/cache), suspend didn't work. Blowing away their config & cache makes suspend (and resume!) work. [Firefox was auto-started by XFCE hence why I'd conflated "login via xenodm" with "can't suspend". But Chrome also caused the same problem if I ran it even if Firefox hadn't been started.] I don't know what in the old config/cache could have caused this, other than the config/cache for both browsers was pretty old. Building the config back up to what I believe I had before has not made the problem come back so far. Should that change, I'll post a follow-up. Thanks Jonathan and Mike for your help and suggestions! Laurie
Re: amdgpu not reliably resuming?
On Tue, May 10, 2022 at 09:08:04PM +1000, Jonathan Gray wrote: Hello Jonathan, >>> I've had a Ryzen machine with a (basic!) Polaris GPU for about a year. >>> Over that time nearly all of the GPU related bugs have disappeared >>> (thanks Jonathan et al.!), except for the fact that I don't seem to be >>> able to reliably suspend/resume from X. >> I thought it might be worth noting that, unfortunately, despite amdgpu and >> mesa updates this machine still can't reliably suspend or resume once X is >> doing something. [From the non-X terminal, suspend/resume works fine.] >> >> Since I guess this machine is now fairly standard hardware, I wonder if >> there's some obvious X or BIOS setting that I should be tweaking, but >> nothing I've tried seems to help so far! > I can't think of anything besides the tpm bios settings on some intel based > laptops a while ago. > > "AMDIF030" at acpi0 not configured is a gpio device without a driver. > Perhaps that state needs to be restored? > Though that appears on a x470 board I can resume and unhibernate on with a > vega10 card. Maybe! Would that device have some sort of interaction with X one way or another? Because it seems that I can reliably suspend/resume if xenodm is on the login page, but after I've logged in via xenodm, suspend rarely works and, if it does, resume almost certainly doesn't. As that suggest, I haven't got a clue where to start with this! Laurie
Re: amdgpu not reliably resuming?
On Sun, Jan 23, 2022 at 09:20:20AM +, Laurence Tratt wrote: > I've had a Ryzen machine with a (basic!) Polaris GPU for about a year. Over > that time nearly all of the GPU related bugs have disappeared (thanks > Jonathan et al.!), except for the fact that I don't seem to be able to > reliably suspend/resume from X. I thought it might be worth noting that, unfortunately, despite amdgpu and mesa updates this machine still can't reliably suspend or resume once X is doing something. [From the non-X terminal, suspend/resume works fine.] Since I guess this machine is now fairly standard hardware, I wonder if there's some obvious X or BIOS setting that I should be tweaking, but nothing I've tried seems to help so far! In case it's useful here's today's dmesg, where when I tried to suspect the display did (as expected) stop displaying anything, but the machine did not stop running (e.g. the fans & lights didn't turn off): OpenBSD 7.1-current (GENERIC.MP) #509: Mon May 9 22:13:31 MDT 2022 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 34211557376 (32626MB) avail mem = 33157357568 (31621MB) random: good seed from bootblocks mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: SMBIOS rev. 3.3 @ 0xcb9f7000 (72 entries) bios0: vendor American Megatrends Inc. version "2423" date 08/09/2021 bios0: ASUS ROG STRIX B550-E GAMING acpi0 at bios0: ACPI 6.0 acpi0: sleep states S0 S3 S4 S5 acpi0: tables DSDT FACP SSDT SSDT SSDT FIDT FPDT MCFG HPET IVRS VFCT BGRT WPBT PCCT SSDT CRAT CDIT SSDT SSDT SSDT SSDT WSMT APIC SSDT SSDT acpi0: wakeup devices GP12(S4) GP13(S4) XHC0(S4) GP30(S4) GP31(S4) X161(S4) X162(S4) PTXH(S4) X1_1(S4) X1_2(S4) WIFI(S4) I225(S4) X163(S4) M2_2(S4) acpitimer0 at acpi0: 3579545 Hz, 32 bits acpimcfg0 at acpi0 acpimcfg0: addr 0xf000, bus 0-127 acpihpet0 at acpi0: 14318180 Hz acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: AMD Ryzen 9 5900X 12-Core Processor, 3700.48 MHz, 19-21-00 cpu0: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,PCLMUL,MWAIT,SSSE3,FMA3,CX16,SSE4.1,SSE4.2,MOVBE,POPCNT,AES,XSAVE,AVX,F16C,RDRAND,NXE,MMXX,FFXSR,PAGE1GB,RDTSCP,LONG,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,ABM,SSE4A,MASSE,3DNOWP,OSVW,IBS,SKINIT,TCE,TOPEXT,CPCTR,DBKP,PCTRL3,MWAITX,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,PQM,RDSEED,ADX,SMAP,CLFLUSHOPT,CLWB,SHA,UMIP,PKU,IBPB,IBRS,STIBP,SSBD,XSAVEOPT,XSAVEC,XGETBV1,XSAVES cpu0: 32KB 64b/line 8-way I-cache, 32KB 64b/line 8-way D-cache, 512KB 64b/line 8-way L2 cache cpu0: ITLB 64 4KB entries fully associative, 64 4MB entries fully associative cpu0: DTLB 64 4KB entries fully associative, 64 4MB entries fully associative cpu0: smt 0, core 0, package 0 mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges cpu0: apic clock running at 100MHz cpu0: mwait min=64, max=64, C-substates=1.1, IBE cpu1 at mainbus0: apid 2 (application processor) cpu1: AMD Ryzen 9 5900X 12-Core Processor, 3700.01 MHz, 19-21-00 cpu1: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,PCLMUL,MWAIT,SSSE3,FMA3,CX16,SSE4.1,SSE4.2,MOVBE,POPCNT,AES,XSAVE,AVX,F16C,RDRAND,NXE,MMXX,FFXSR,PAGE1GB,RDTSCP,LONG,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,ABM,SSE4A,MASSE,3DNOWP,OSVW,IBS,SKINIT,TCE,TOPEXT,CPCTR,DBKP,PCTRL3,MWAITX,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,PQM,RDSEED,ADX,SMAP,CLFLUSHOPT,CLWB,SHA,UMIP,PKU,IBPB,IBRS,STIBP,SSBD,XSAVEOPT,XSAVEC,XGETBV1,XSAVES cpu1: 32KB 64b/line 8-way I-cache, 32KB 64b/line 8-way D-cache, 512KB 64b/line 8-way L2 cache cpu1: ITLB 64 4KB entries fully associative, 64 4MB entries fully associative cpu1: DTLB 64 4KB entries fully associative, 64 4MB entries fully associative cpu1: smt 0, core 1, package 0 cpu2 at mainbus0: apid 4 (application processor) cpu2: AMD Ryzen 9 5900X 12-Core Processor, 3700.00 MHz, 19-21-00 cpu2: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,PCLMUL,MWAIT,SSSE3,FMA3,CX16,SSE4.1,SSE4.2,MOVBE,POPCNT,AES,XSAVE,AVX,F16C,RDRAND,NXE,MMXX,FFXSR,PAGE1GB,RDTSCP,LONG,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,ABM,SSE4A,MASSE,3DNOWP,OSVW,IBS,SKINIT,TCE,TOPEXT,CPCTR,DBKP,PCTRL3,MWAITX,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,PQM,RDSEED,ADX,SMAP,CLFLUSHOPT,CLWB,SHA,UMIP,PKU,IBPB,IBRS,STIBP,SSBD,XSAVEOPT,XSAVEC,XGETBV1,XSAVES cpu2: 32KB 64b/line 8-way I-cache, 32KB 64b/line 8-way D-cache, 512KB 64b/line 8-way L2 cache cpu2: ITLB 64 4KB entries fully associative, 64 4MB entries fully associative cpu2: DTLB 64 4KB entries fully associative, 64 4MB entries fully associative cpu2: smt 0, core 2, package 0 cpu3 at mainbus0: apid 6 (application processor) cpu3: AMD Ryzen 9 5900X 12-Core Processor, 3700.01 MHz, 19-21-00 cpu3: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,M
Re: amdgpu not reliably resuming?
On Sun, Jan 23, 2022 at 09:50:58PM +1100, Jonathan Gray wrote: Hello Jonathan, Thanks for your fast reply! >> As of the last couple of weeks or so (at least), things are a little >> better. I now seem to be able to semi-reliably suspend/resume from the >> console. When I resume an odd white-ish bit-pattern is displayed on >> screen, but switching to/from another console restores things. I seem to >> be able to do this multiple times without issue. > Does hibernate behaviour differ? It seems to be the same, though I haven't tested it quite as extensively. > gpu faults tend to be problems in Mesa like this > https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/14409 polaris is > gfx8 but I'm not sure how relevant that particular fix is (see the table in > https://www.x.org/wiki/RadeonFeature/ ) I did quickly try it and it doesn't seem to have helped this particular case. However: > I have a Mesa update to 21.3 planned but am waiting till a bit after the > recent kernel changes. I would be very willing to try the update when you have it to see if it helps! Laurie
amdgpu not reliably resuming?
I've had a Ryzen machine with a (basic!) Polaris GPU for about a year. Over that time nearly all of the GPU related bugs have disappeared (thanks Jonathan et al.!), except for the fact that I don't seem to be able to reliably suspend/resume from X. Resuming used to crash the machine 9 times out of 10, generally causing a single block of colour to be displayed, before automatically rebooting itself. As of the last couple of weeks or so (at least), things are a little better. I now seem to be able to semi-reliably suspend/resume from the console. When I resume an odd white-ish bit-pattern is displayed on screen, but switching to/from another console restores things. I seem to be able to do this multiple times without issue. However, if I suspend/resume from X, the X server soon gets visually corrupted -- the white-ish bit pattern is mingled with whatever was last visible in my X session. The machine still responds to ssh (etc.) but the screen is no longer usable, even if I try switching to/from virtual consoles. [Perhaps unsurprisingly, even if I don't login to X, merely suspending/resuming from the console seems to corrupt xenodm after a while.] I now seem to have triggered some sort of output from dmesg after a recent suspend/resume sequence: drm:pid33800:gmc_v8_0_process_interrupt *ERROR* GPU fault detected: 146 0x0448480c for process pid 0 thread Xorg pid 21509 drm:pid33800:gmc_v8_0_process_interrupt *ERROR* VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x00102E89 drm:pid33800:gmc_v8_0_process_interrupt *ERROR* VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x0E04800C drm:pid33800:gmc_v8_0_vm_decode_fault *ERROR* VM fault (0x0c, vmid 7, pasid 32769) at page 1060489, read from 'TC0' (0x54433000) (72) Does that mean anything? I have no idea, but I thought it might be worth noting it here in case it helps any amdgpu hackers! This is on amd64 -current as of a couple of days ago with amdgpu-firmware-20211027. I have fiddled with just about every BIOS setting I can think of (e.g. TPM, secure boot), but they have no apparent effect on this issue. Full dmesg below. Laurie OpenBSD 7.0-current (GENERIC.MP) #278: Fri Jan 21 19:12:31 MST 2022 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 34211557376 (32626MB) avail mem = 33157517312 (31621MB) random: good seed from bootblocks mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: SMBIOS rev. 3.3 @ 0xcb9f7000 (72 entries) bios0: vendor American Megatrends Inc. version "2423" date 08/09/2021 bios0: ASUS ROG STRIX B550-E GAMING acpi0 at bios0: ACPI 6.0 acpi0: sleep states S0 S3 S4 S5 acpi0: tables DSDT FACP SSDT SSDT SSDT FIDT FPDT MCFG HPET IVRS VFCT BGRT WPBT PCCT SSDT CRAT CDIT SSDT SSDT SSDT SSDT WSMT APIC SSDT SSDT acpi0: wakeup devices GP12(S4) GP13(S4) XHC0(S4) GP30(S4) GP31(S4) X161(S4) X162(S4) PTXH(S4) X1_1(S4) X1_2(S4) WIFI(S4) I225(S4) X163(S4) M2_2(S4) acpitimer0 at acpi0: 3579545 Hz, 32 bits acpimcfg0 at acpi0 acpimcfg0: addr 0xf000, bus 0-127 acpihpet0 at acpi0: 14318180 Hz acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: AMD Ryzen 9 5900X 12-Core Processor, 3700.53 MHz, 19-21-00 cpu0: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,PCLMUL,MWAIT,SSSE3,FMA3,CX16,SSE4.1,SSE4.2,MOVBE,POPCNT,AES,XSAVE,AVX,F16C,RDRAND,NXE,MMXX,FFXSR,PAGE1GB,RDTSCP,LONG,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,ABM,SSE4A,MASSE,3DNOWP,OSVW,IBS,SKINIT,TCE,TOPEXT,CPCTR,DBKP,PCTRL3,MWAITX,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,PQM,RDSEED,ADX,SMAP,CLFLUSHOPT,CLWB,SHA,UMIP,PKU,IBPB,IBRS,STIBP,SSBD,XSAVEOPT,XSAVEC,XGETBV1,XSAVES cpu0: 32KB 64b/line 8-way I-cache, 32KB 64b/line 8-way D-cache, 512KB 64b/line 8-way L2 cache cpu0: ITLB 64 4KB entries fully associative, 64 4MB entries fully associative cpu0: DTLB 64 4KB entries fully associative, 64 4MB entries fully associative cpu0: smt 0, core 0, package 0 mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges cpu0: apic clock running at 99MHz cpu0: mwait min=64, max=64, C-substates=1.1, IBE cpu1 at mainbus0: apid 2 (application processor) cpu1: AMD Ryzen 9 5900X 12-Core Processor, 3699.99 MHz, 19-21-00 cpu1: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,PCLMUL,MWAIT,SSSE3,FMA3,CX16,SSE4.1,SSE4.2,MOVBE,POPCNT,AES,XSAVE,AVX,F16C,RDRAND,NXE,MMXX,FFXSR,PAGE1GB,RDTSCP,LONG,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,ABM,SSE4A,MASSE,3DNOWP,OSVW,IBS,SKINIT,TCE,TOPEXT,CPCTR,DBKP,PCTRL3,MWAITX,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,PQM,RDSEED,ADX,SMAP,CLFLUSHOPT,CLWB,SHA,UMIP,PKU,IBPB,IBRS,STIBP,SSBD,XSAVEOPT,XSAVEC,XGETBV1,XSAVES cpu1: 32KB 64b/line 8-way I-cache, 32KB 64b/line 8-way D-cache, 512KB 64b/line 8-way L2 cache cpu1: ITLB 64 4KB entries fully associative, 64 4MB entries fully associative cpu1: DTLB 64 4KB entries fully associative, 64 4MB entries fully associative cpu1: smt 0, core 1,
Re: iwx now stops more often?
On Sun, Nov 21, 2021 at 06:06:33PM +0100, Stefan Sperling wrote: Hello Stefan, >> As of a kernel from a couple of days ago, iwx semi-regularly stops >> associating with my wireless AP. An easy way to trigger this is "pkg_add >> -u": at some point, downloading stops mid-package, and I need to "sh >> /etc/netstart" to bring the interface back up. > Please try this patch. I cannot promise that it will help, but it might. I don't understand why, but I have since been unable to replicate the problem, which I feel I need to do in order to meaningfully test your patch. I'm clutching at straws to think of possible reasons. The best I can think of is that `pkg_add -u`'s tendency to cut downloads off mid-stream might have caused the odd behaviour. That could be a very long way off the mark. If/when I can work out how to more reliably trigger the problem, I will post back, but until then I can only apologise for the noise. Laurie
iwx now stops more often?
As of a kernel from a couple of days ago, iwx semi-regularly stops associating with my wireless AP. An easy way to trigger this is "pkg_add -u": at some point, downloading stops mid-package, and I need to "sh /etc/netstart" to bring the interface back up. My previous kernel was about a week old. I had noticed with that kernel that sometimes iwx stopped soon after boot, but one kick of /etc/netstart seemed to make it good for the whole day, whereas now it seems to stop multiple times (but I hadn't done pkg_add very often in that week!). The AP is a Ruckus R510 and none of the other clients connected to it seems to have this issue. I'm attaching my dmesg + IWX_DEBUG set to 1 in case it helps anyone. Laurie OpenBSD 7.0-current (GENERIC.MP) #22: Sun Nov 21 08:51:31 GMT 2021 ltr...@overdrive.tratt.net:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 34252939264 (32666MB) avail mem = 33198870528 (31660MB) random: good seed from bootblocks mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: SMBIOS rev. 3.3 @ 0xcb7f7000 (73 entries) bios0: vendor American Megatrends Inc. version "2423" date 08/09/2021 bios0: ASUS ROG STRIX B550-E GAMING acpi0 at bios0: ACPI 6.0 acpi0: sleep states S0 S3 S4 S5 acpi0: tables DSDT FACP SSDT SSDT SSDT FIDT FPDT MCFG HPET IVRS VFCT BGRT WPBT TPM2 PCCT SSDT CRAT CDIT SSDT SSDT SSDT SSDT WSMT APIC SSDT SSDT acpi0: wakeup devices GP12(S4) GP13(S4) XHC0(S4) GP30(S4) GP31(S4) X161(S4) X162(S4) PTXH(S4) X1_1(S4) X1_2(S4) WIFI(S4) I225(S4) X163(S4) M2_2(S4) acpitimer0 at acpi0: 3579545 Hz, 32 bits acpimcfg0 at acpi0 acpimcfg0: addr 0xf000, bus 0-127 acpihpet0 at acpi0: 14318180 Hz acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: AMD Ryzen 9 5900X 12-Core Processor, 3693.63 MHz, 19-21-00 cpu0: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,PCLMUL,MWAIT,SSSE3,FMA3,CX16,SSE4.1,SSE4.2,MOVBE,POPCNT,AES,XSAVE,AVX,F16C,RDRAND,NXE,MMXX,FFXSR,PAGE1GB,RDTSCP,LONG,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,ABM,SSE4A,MASSE,3DNOWP,OSVW,IBS,SKINIT,TCE,TOPEXT,CPCTR,DBKP,PCTRL3,MWAITX,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,PQM,RDSEED,ADX,SMAP,CLFLUSHOPT,CLWB,SHA,UMIP,PKU,IBPB,IBRS,STIBP,SSBD,XSAVEOPT,XSAVEC,XGETBV1,XSAVES cpu0: 32KB 64b/line 8-way I-cache, 32KB 64b/line 8-way D-cache, 512KB 64b/line 8-way L2 cache cpu0: ITLB 64 4KB entries fully associative, 64 4MB entries fully associative cpu0: DTLB 64 4KB entries fully associative, 64 4MB entries fully associative cpu0: smt 0, core 0, package 0 mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges cpu0: apic clock running at 99MHz cpu0: mwait min=64, max=64, C-substates=1.1, IBE cpu1 at mainbus0: apid 2 (application processor) cpu1: AMD Ryzen 9 5900X 12-Core Processor, 3693.05 MHz, 19-21-00 cpu1: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,PCLMUL,MWAIT,SSSE3,FMA3,CX16,SSE4.1,SSE4.2,MOVBE,POPCNT,AES,XSAVE,AVX,F16C,RDRAND,NXE,MMXX,FFXSR,PAGE1GB,RDTSCP,LONG,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,ABM,SSE4A,MASSE,3DNOWP,OSVW,IBS,SKINIT,TCE,TOPEXT,CPCTR,DBKP,PCTRL3,MWAITX,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,PQM,RDSEED,ADX,SMAP,CLFLUSHOPT,CLWB,SHA,UMIP,PKU,IBPB,IBRS,STIBP,SSBD,XSAVEOPT,XSAVEC,XGETBV1,XSAVES cpu1: 32KB 64b/line 8-way I-cache, 32KB 64b/line 8-way D-cache, 512KB 64b/line 8-way L2 cache cpu1: ITLB 64 4KB entries fully associative, 64 4MB entries fully associative cpu1: DTLB 64 4KB entries fully associative, 64 4MB entries fully associative cpu1: smt 0, core 1, package 0 cpu2 at mainbus0: apid 4 (application processor) cpu2: AMD Ryzen 9 5900X 12-Core Processor, 3693.05 MHz, 19-21-00 cpu2: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,PCLMUL,MWAIT,SSSE3,FMA3,CX16,SSE4.1,SSE4.2,MOVBE,POPCNT,AES,XSAVE,AVX,F16C,RDRAND,NXE,MMXX,FFXSR,PAGE1GB,RDTSCP,LONG,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,ABM,SSE4A,MASSE,3DNOWP,OSVW,IBS,SKINIT,TCE,TOPEXT,CPCTR,DBKP,PCTRL3,MWAITX,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,PQM,RDSEED,ADX,SMAP,CLFLUSHOPT,CLWB,SHA,UMIP,PKU,IBPB,IBRS,STIBP,SSBD,XSAVEOPT,XSAVEC,XGETBV1,XSAVES cpu2: 32KB 64b/line 8-way I-cache, 32KB 64b/line 8-way D-cache, 512KB 64b/line 8-way L2 cache cpu2: ITLB 64 4KB entries fully associative, 64 4MB entries fully associative cpu2: DTLB 64 4KB entries fully associative, 64 4MB entries fully associative cpu2: smt 0, core 2, package 0 cpu3 at mainbus0: apid 6 (application processor) cpu3: AMD Ryzen 9 5900X 12-Core Processor, 3693.05 MHz, 19-21-00 cpu3:
Re: xorg crashing and returning to xenodm (amd64/amdgpu)
On Tue, Nov 16, 2021 at 04:30:23PM +, Nicola Dell'Uomo wrote: Hello Nicola, > Maybe you should follow this thread: > > X.org segmentation fault - snapshot amd64 > > I think it could be the same problem you're experiencing. Yes, it does look like it's probably the same -- thanks! One extra (small) bit of information I think I'm adding is that it happens on amdgpu too. FWIW, I am also using XFCE4. Laurie
xorg crashing and returning to xenodm (amd64/amdgpu)
As of the last couple of days' snapshots, xorg is regularly crashing (probably once every 1-2 hours on average) and dumping me back to xenodm. This seems to happen only when I use Firefox though I guess this is related to the xorg update? This is on amdgpu / amd64. I can't see anything in the dmesg or Xorg.log that gives a hint as to what might be going on, but I'm attaching both -- just in case! Laurie OpenBSD 7.0-current (GENERIC.MP) #98: Mon Nov 15 12:16:19 MST 2021 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 34252939264 (32666MB) avail mem = 33198878720 (31660MB) random: good seed from bootblocks mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: SMBIOS rev. 3.3 @ 0xcb7f7000 (73 entries) bios0: vendor American Megatrends Inc. version "2423" date 08/09/2021 bios0: ASUS ROG STRIX B550-E GAMING acpi0 at bios0: ACPI 6.0 acpi0: sleep states S0 S3 S4 S5 acpi0: tables DSDT FACP SSDT SSDT SSDT FIDT FPDT MCFG HPET IVRS VFCT BGRT WPBT TPM2 PCCT SSDT CRAT CDIT SSDT SSDT SSDT SSDT WSMT APIC SSDT SSDT acpi0: wakeup devices GP12(S4) GP13(S4) XHC0(S4) GP30(S4) GP31(S4) X161(S4) X162(S4) PTXH(S4) X1_1(S4) X1_2(S4) WIFI(S4) I225(S4) X163(S4) M2_2(S4) acpitimer0 at acpi0: 3579545 Hz, 32 bits acpimcfg0 at acpi0 acpimcfg0: addr 0xf000, bus 0-127 acpihpet0 at acpi0: 14318180 Hz acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: AMD Ryzen 9 5900X 12-Core Processor, 3693.61 MHz, 19-21-00 cpu0: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,PCLMUL,MWAIT,SSSE3,FMA3,CX16,SSE4.1,SSE4.2,MOVBE,POPCNT,AES,XSAVE,AVX,F16C,RDRAND,NXE,MMXX,FFXSR,PAGE1GB,RDTSCP,LONG,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,ABM,SSE4A,MASSE,3DNOWP,OSVW,IBS,SKINIT,TCE,TOPEXT,CPCTR,DBKP,PCTRL3,MWAITX,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,PQM,RDSEED,ADX,SMAP,CLFLUSHOPT,CLWB,SHA,UMIP,PKU,IBPB,IBRS,STIBP,SSBD,XSAVEOPT,XSAVEC,XGETBV1,XSAVES cpu0: 32KB 64b/line 8-way I-cache, 32KB 64b/line 8-way D-cache, 512KB 64b/line 8-way L2 cache cpu0: ITLB 64 4KB entries fully associative, 64 4MB entries fully associative cpu0: DTLB 64 4KB entries fully associative, 64 4MB entries fully associative cpu0: smt 0, core 0, package 0 mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges cpu0: apic clock running at 99MHz cpu0: mwait min=64, max=64, C-substates=1.1, IBE cpu1 at mainbus0: apid 2 (application processor) cpu1: AMD Ryzen 9 5900X 12-Core Processor, 3693.06 MHz, 19-21-00 cpu1: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,PCLMUL,MWAIT,SSSE3,FMA3,CX16,SSE4.1,SSE4.2,MOVBE,POPCNT,AES,XSAVE,AVX,F16C,RDRAND,NXE,MMXX,FFXSR,PAGE1GB,RDTSCP,LONG,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,ABM,SSE4A,MASSE,3DNOWP,OSVW,IBS,SKINIT,TCE,TOPEXT,CPCTR,DBKP,PCTRL3,MWAITX,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,PQM,RDSEED,ADX,SMAP,CLFLUSHOPT,CLWB,SHA,UMIP,PKU,IBPB,IBRS,STIBP,SSBD,XSAVEOPT,XSAVEC,XGETBV1,XSAVES cpu1: 32KB 64b/line 8-way I-cache, 32KB 64b/line 8-way D-cache, 512KB 64b/line 8-way L2 cache cpu1: ITLB 64 4KB entries fully associative, 64 4MB entries fully associative cpu1: DTLB 64 4KB entries fully associative, 64 4MB entries fully associative cpu1: smt 0, core 1, package 0 cpu2 at mainbus0: apid 4 (application processor) cpu2: AMD Ryzen 9 5900X 12-Core Processor, 3693.06 MHz, 19-21-00 cpu2: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,PCLMUL,MWAIT,SSSE3,FMA3,CX16,SSE4.1,SSE4.2,MOVBE,POPCNT,AES,XSAVE,AVX,F16C,RDRAND,NXE,MMXX,FFXSR,PAGE1GB,RDTSCP,LONG,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,ABM,SSE4A,MASSE,3DNOWP,OSVW,IBS,SKINIT,TCE,TOPEXT,CPCTR,DBKP,PCTRL3,MWAITX,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,PQM,RDSEED,ADX,SMAP,CLFLUSHOPT,CLWB,SHA,UMIP,PKU,IBPB,IBRS,STIBP,SSBD,XSAVEOPT,XSAVEC,XGETBV1,XSAVES cpu2: 32KB 64b/line 8-way I-cache, 32KB 64b/line 8-way D-cache, 512KB 64b/line 8-way L2 cache cpu2: ITLB 64 4KB entries fully associative, 64 4MB entries fully associative cpu2: DTLB 64 4KB entries fully associative, 64 4MB entries fully associative cpu2: smt 0, core 2, package 0 cpu3 at mainbus0: apid 6 (application processor) cpu3: AMD Ryzen 9 5900X 12-Core Processor, 3693.06 MHz, 19-21-00 cpu3: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,PCLMUL,MWAIT,SSSE3,FMA3,CX16,SSE4.1,SSE4.2,MOVBE,POPCNT,AES,XSAVE,AVX,F16C,RDRAND,NXE,MMXX,FFXSR,PAGE1GB,RDTSCP,LONG,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,ABM,SSE4A,MASSE,3DNOWP,OSVW,IBS,SKINIT,TCE,TOPEXT,CPCTR,DBKP,PCTRL3,MWAITX,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,PQM,RDSEED,ADX,SMAP,CLFLUSHOPT,CLWB,SHA,UMIP,PKU,IBPB,IBRS,STIBP,SSBD,XSAVEOPT,XSAVEC,XGETBV1,XSAVES cpu3: 32KB 64b/line 8-way I-cache, 32KB 64b/line 8-way D-cache, 512KB 64b/line 8-way L2 cache cpu3: ITLB 64 4KB entries fully associative, 64 4MB entries fully associative cpu3: DTLB 64 4KB entries fully
Re: amd64-current hard lock
On Thu, Nov 04, 2021 at 10:24:07PM +1100, Jonathan Gray wrote: Hello Jonathan, >> I updated my amd64 machine from a snapshot from about 2 weeks ago to the >> Nov 2nd and then Nov 3rd snapshots. In both cases, as soon as I log into >> X, start Firefox, and try and load a page the machine hard locks and has >> to be power cycled. > Are you able to ssh into the machine when this occurs? I didn't try ssh'ing since it didn't respond to the normal "press the power button and wait for it to shut down cleanly", which normally indicates a kernel panic. > Does this diff which reverts the recent ttm change help? It does seem to! I've only been running for a few minutes, including using Firefox, but that's a few minutes more than I managed before this! [I also reupgraded from 7.0 to a snapshot, then used your proposed diff, so that I can be fairly sure that it's the culprit.] Laurie
amd64-current hard lock
I updated my amd64 machine from a snapshot from about 2 weeks ago to the Nov 2nd and then Nov 3rd snapshots. In both cases, as soon as I log into X, start Firefox, and try and load a page the machine hard locks and has to be power cycled. I thought that the new amdgpu firmware might be the culprit, so I reverted to amdgpu-firmware-20210818 with no success. In slight desperation, I've reverted back to 7.0 release, which has fixed the problem. dmesg from one of the problematic snapshots below Laurie OpenBSD 7.0-current (GENERIC.MP) #68: Wed Nov 3 17:05:01 MDT 2021 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 34253148160 (32666MB) avail mem = 33199013888 (31661MB) random: good seed from bootblocks mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: SMBIOS rev. 3.3 @ 0xcb9f7000 (72 entries) bios0: vendor American Megatrends Inc. version "2420" date 07/27/2021 bios0: ASUS ROG STRIX B550-E GAMING acpi0 at bios0: ACPI 6.0 acpi0: sleep states S0 S3 S4 S5 acpi0: tables DSDT FACP SSDT SSDT SSDT FIDT FPDT MCFG HPET IVRS VFCT BGRT WPBT PCCT SSDT CRAT CDIT SSDT SSDT SSDT SSDT WSMT APIC SSDT SSDT acpi0: wakeup devices GP12(S4) GP13(S4) XHC0(S4) GP30(S4) GP31(S4) X161(S4) X162(S4) PTXH(S4) X1_1(S4) X1_2(S4) WIFI(S4) I225(S4) X163(S4) M2_2(S4) acpitimer0 at acpi0: 3579545 Hz, 32 bits acpimcfg0 at acpi0 acpimcfg0: addr 0xf000, bus 0-127 acpihpet0 at acpi0: 14318180 Hz acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: AMD Ryzen 9 5900X 12-Core Processor, 3700.54 MHz, 19-21-00 cpu0: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,PCLMUL,MWAIT,SSSE3,FMA3,CX16,SSE4.1,SSE4.2,MOVBE,POPCNT,AES,XSAVE,AVX,F16C,RDRAND,NXE,MMXX,FFXSR,PAGE1GB,RDTSCP,LONG,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,ABM,SSE4A,MASSE,3DNOWP,OSVW,IBS,SKINIT,TCE,TOPEXT,CPCTR,DBKP,PCTRL3,MWAITX,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,PQM,RDSEED,ADX,SMAP,CLFLUSHOPT,CLWB,SHA,UMIP,PKU,IBPB,IBRS,STIBP,SSBD,XSAVEOPT,XSAVEC,XGETBV1,XSAVES cpu0: 32KB 64b/line 8-way I-cache, 32KB 64b/line 8-way D-cache, 512KB 64b/line 8-way L2 cache cpu0: ITLB 64 4KB entries fully associative, 64 4MB entries fully associative cpu0: DTLB 64 4KB entries fully associative, 64 4MB entries fully associative cpu0: smt 0, core 0, package 0 mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges cpu0: apic clock running at 99MHz cpu0: mwait min=64, max=64, C-substates=1.1, IBE cpu1 at mainbus0: apid 2 (application processor) cpu1: AMD Ryzen 9 5900X 12-Core Processor, 3699.99 MHz, 19-21-00 cpu1: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,PCLMUL,MWAIT,SSSE3,FMA3,CX16,SSE4.1,SSE4.2,MOVBE,POPCNT,AES,XSAVE,AVX,F16C,RDRAND,NXE,MMXX,FFXSR,PAGE1GB,RDTSCP,LONG,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,ABM,SSE4A,MASSE,3DNOWP,OSVW,IBS,SKINIT,TCE,TOPEXT,CPCTR,DBKP,PCTRL3,MWAITX,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,PQM,RDSEED,ADX,SMAP,CLFLUSHOPT,CLWB,SHA,UMIP,PKU,IBPB,IBRS,STIBP,SSBD,XSAVEOPT,XSAVEC,XGETBV1,XSAVES cpu1: 32KB 64b/line 8-way I-cache, 32KB 64b/line 8-way D-cache, 512KB 64b/line 8-way L2 cache cpu1: ITLB 64 4KB entries fully associative, 64 4MB entries fully associative cpu1: DTLB 64 4KB entries fully associative, 64 4MB entries fully associative cpu1: smt 0, core 1, package 0 cpu2 at mainbus0: apid 4 (application processor) cpu2: AMD Ryzen 9 5900X 12-Core Processor, 3699.99 MHz, 19-21-00 cpu2: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,PCLMUL,MWAIT,SSSE3,FMA3,CX16,SSE4.1,SSE4.2,MOVBE,POPCNT,AES,XSAVE,AVX,F16C,RDRAND,NXE,MMXX,FFXSR,PAGE1GB,RDTSCP,LONG,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,ABM,SSE4A,MASSE,3DNOWP,OSVW,IBS,SKINIT,TCE,TOPEXT,CPCTR,DBKP,PCTRL3,MWAITX,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,PQM,RDSEED,ADX,SMAP,CLFLUSHOPT,CLWB,SHA,UMIP,PKU,IBPB,IBRS,STIBP,SSBD,XSAVEOPT,XSAVEC,XGETBV1,XSAVES cpu2: 32KB 64b/line 8-way I-cache, 32KB 64b/line 8-way D-cache, 512KB 64b/line 8-way L2 cache cpu2: ITLB 64 4KB entries fully associative, 64 4MB entries fully associative cpu2: DTLB 64 4KB entries fully associative, 64 4MB entries fully associative cpu2: smt 0, core 2, package 0 cpu3 at mainbus0: apid 6 (application processor) cpu3: AMD Ryzen 9 5900X 12-Core Processor, 3699.99 MHz, 19-21-00 cpu3: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,PCLMUL,MWAIT,SSSE3,FMA3,CX16,SSE4.1,SSE4.2,MOVBE,POPCNT,AES,XSAVE,AVX,F16C,RDRAND,NXE,MMXX,FFXSR,PAGE1GB,RDTSCP,LONG,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,ABM,SSE4A,MASSE,3DNOWP,OSVW,IBS,SKINIT,TCE,TOPEXT,CPCTR,DBKP,PCTRL3,MWAITX,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,PQM,RDSEED,ADX,SMAP,CLFLUSHOPT,CLWB,SHA,UMIP,PKU,IBPB,IBRS,STIBP,SSBD,XSAVEOPT,XSAVEC,XGETBV1,XSAVES cpu3: 32KB 64b/line 8-way I-cache, 32KB 64b/line 8-way D-cache, 512KB 64b/line 8-way L2 cache cpu3: ITLB 64 4KB entries
`toe` reference in man 7 term
`man 7 term` contains the following: Terminal type descriptions are stored as files of capability data underneath /usr/share/terminfo. To browse a list of all terminal names recognized by the system, do toe | more However, I cannot see a `toe` command on any of my OpenBSD boxes, nor does it seem to be a shell builtin, nor can I see any meaningful references in src/ other than in the man page source file. It's quite probable that I'm being an idiot, and that I should know how to run `toe`, but perhaps this reference in the man page is out of date? Laurie
drm 'perform_link_training_with_retries:'
I've got a Ryzen 5900X machine with a Radeon Polaris 12 GPU. It's a basic GPU, and has mostly worked for 5 months, but not fully: 1. Suspend/resume nearly always fails, with resume leading to a (generally green) solid colour before automatically rebooting. Occasionally the machine will resume but then fall over within a minute, generally only lasting a handful of seconds. 2. The longer it's running, the more visual corruption I get, mostly on my XFCE background. Mostly it's been the odd pixel here or there, but since upgrading to a higher-DPI monitor, this is happening much more often, with tens (maybe more) of pixels becoming corrupted over the course of a working day. Today, on the Sep 7th snapshot, I noticed this in my dmesg: [drm] perform_link_training_with_retries: Link training attempt 1 of 4 failed which I don't think I've ever seen before. Perhaps it means nothing, but perhaps it's a hint that might mean something to someone? Laurie OpenBSD 7.0-beta (GENERIC.MP) #203: Tue Sep 7 10:09:21 MDT 2021 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 34253148160 (32666MB) avail mem = 33199038464 (31661MB) random: good seed from bootblocks mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: SMBIOS rev. 3.3 @ 0xcb9f7000 (72 entries) bios0: vendor American Megatrends Inc. version "2420" date 07/27/2021 bios0: ASUS ROG STRIX B550-E GAMING acpi0 at bios0: ACPI 6.0 acpi0: sleep states S0 S3 S4 S5 acpi0: tables DSDT FACP SSDT SSDT SSDT FIDT FPDT MCFG HPET IVRS VFCT BGRT WPBT PCCT SSDT CRAT CDIT SSDT SSDT SSDT SSDT WSMT APIC SSDT SSDT acpi0: wakeup devices GP12(S4) GP13(S4) XHC0(S4) GP30(S4) GP31(S4) X161(S4) X162(S4) PTXH(S4) X1_1(S4) X1_2(S4) WIFI(S4) I225(S4) X163(S4) M2_2(S4) acpitimer0 at acpi0: 3579545 Hz, 32 bits acpimcfg0 at acpi0 acpimcfg0: addr 0xf000, bus 0-127 acpihpet0 at acpi0: 14318180 Hz acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: AMD Ryzen 9 5900X 12-Core Processor, 3700.45 MHz, 19-21-00 cpu0: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,PCLMUL,MWAIT,SSSE3,FMA3,CX16,SSE4.1,SSE4.2,MOVBE,POPCNT,AES,XSAVE,AVX,F16C,RDRAND,NXE,MMXX,FFXSR,PAGE1GB,RDTSCP,LONG,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,ABM,SSE4A,MASSE,3DNOWP,OSVW,IBS,SKINIT,TCE,TOPEXT,CPCTR,DBKP,PCTRL3,MWAITX,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,PQM,RDSEED,ADX,SMAP,CLFLUSHOPT,CLWB,SHA,UMIP,PKU,IBPB,IBRS,STIBP,SSBD,XSAVEOPT,XSAVEC,XGETBV1,XSAVES cpu0: 32KB 64b/line 8-way I-cache, 32KB 64b/line 8-way D-cache, 512KB 64b/line 8-way L2 cache cpu0: ITLB 64 4KB entries fully associative, 64 4MB entries fully associative cpu0: DTLB 64 4KB entries fully associative, 64 4MB entries fully associative cpu0: smt 0, core 0, package 0 mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges cpu0: apic clock running at 99MHz cpu0: mwait min=64, max=64, C-substates=1.1, IBE cpu1 at mainbus0: apid 2 (application processor) cpu1: AMD Ryzen 9 5900X 12-Core Processor, 3699.99 MHz, 19-21-00 cpu1: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,PCLMUL,MWAIT,SSSE3,FMA3,CX16,SSE4.1,SSE4.2,MOVBE,POPCNT,AES,XSAVE,AVX,F16C,RDRAND,NXE,MMXX,FFXSR,PAGE1GB,RDTSCP,LONG,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,ABM,SSE4A,MASSE,3DNOWP,OSVW,IBS,SKINIT,TCE,TOPEXT,CPCTR,DBKP,PCTRL3,MWAITX,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,PQM,RDSEED,ADX,SMAP,CLFLUSHOPT,CLWB,SHA,UMIP,PKU,IBPB,IBRS,STIBP,SSBD,XSAVEOPT,XSAVEC,XGETBV1,XSAVES cpu1: 32KB 64b/line 8-way I-cache, 32KB 64b/line 8-way D-cache, 512KB 64b/line 8-way L2 cache cpu1: ITLB 64 4KB entries fully associative, 64 4MB entries fully associative cpu1: DTLB 64 4KB entries fully associative, 64 4MB entries fully associative cpu1: smt 0, core 1, package 0 cpu2 at mainbus0: apid 4 (application processor) cpu2: AMD Ryzen 9 5900X 12-Core Processor, 3699.99 MHz, 19-21-00 cpu2: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,PCLMUL,MWAIT,SSSE3,FMA3,CX16,SSE4.1,SSE4.2,MOVBE,POPCNT,AES,XSAVE,AVX,F16C,RDRAND,NXE,MMXX,FFXSR,PAGE1GB,RDTSCP,LONG,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,ABM,SSE4A,MASSE,3DNOWP,OSVW,IBS,SKINIT,TCE,TOPEXT,CPCTR,DBKP,PCTRL3,MWAITX,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,PQM,RDSEED,ADX,SMAP,CLFLUSHOPT,CLWB,SHA,UMIP,PKU,IBPB,IBRS,STIBP,SSBD,XSAVEOPT,XSAVEC,XGETBV1,XSAVES cpu2: 32KB 64b/line 8-way I-cache, 32KB 64b/line 8-way D-cache, 512KB 64b/line 8-way L2 cache cpu2: ITLB 64 4KB entries fully associative, 64 4MB entries fully associative cpu2: DTLB 64 4KB entries fully associative, 64 4MB entries fully associative cpu2: smt 0, core 2, package 0 cpu3 at mainbus0: apid 6 (application processor) cpu3: AMD Ryzen 9 5900X 12-Core Processor, 3699.99 MHz, 19-21-00 cpu3:
xenodm man page's Xsession script doesn't reflect /etc/X11/xenodm/Xsession
For some years I've had a seemingly odd problem where logging in via xenodm did not respect my login class. I've tried repeatedly to work out why, and until now always failed -- it turns out that my ~/.xsession file was not marked as executable and this caused our Xsession to run it via /bin/sh. This is ultimately an act of gross stupidity on my part, but I thought it might be worth documenting how I'd managed not to fix this for so long. Here's the relevant chunk of xenodm's default Xsession: # The startup script is not intended to have arguments. startup=$HOME/.xsession resources=$HOME/.Xresources if [ -s "$startup" ]; then if [ -x "$startup" ]; then "$startup" else /bin/sh "$startup" fi else ... fi Notice that it runs ~/.xsession differently based on its executable permission bits. This isn't documented anywhere and xenodm's man page unintentionally threw me off the scent, partly because it's not very OpenBSD-like. The first mention of Xsession in xenodm's man page is vague (this should have been a clue to me to read Xsession more carefully I now realise!): Then xenodm runs the Xsession script as the user. This system session file may do some additional startup and typically runs the .xsession script in the user's home directory. When the Xsession script exits, the session is over. It's quite easy at that point not to realise that there is a section of the man page later called "SESSION PROGRAM" which clears up some of that vagueness. A forward link might be a good idea? The "SESSION PROGRAM" section itself implicitly describes all possible Xsession scripts rather than the one xenodm actually ships with. For example: At most installations, Xsession should look in $HOME for a file .xsession, which contains commands that each user would like to use as a session. An example Xsession script is then described: This example recognizes the special failsafe mode, specified in the translations in the Xresources file, to provide an escape from the ordinary session. It also requires that the .xsession file be executable so we don't have to guess what shell it wants to use. Of course, if I'd read that carefully I should have checked that my ~/.xsession file is executable. However, the example Xsession script in the man page then contains this code: if [ -f "$startup" ]; then exec "$startup" else ... fi i.e. it doesn't contain the "if ~/.xsession isn't executable, run it via /bin/sh" part that xenodm's default Xsession does. It thus never occurred to me to check whether my ~/.xsession is executable, because under the example Xsession, it couldn't possibly run if it wasn't executable. The reason I'm filing a bug report and not a patch is that I'm not really sure if/what a fix for this might be. I am not sure if xenodm's man page is structured as it is to keep it in sync with upstream, and I'm also not sure if it's expected that people will actually change Xsession or not. Some possible ideas are: tell people to read the source of /etc/X11/xenodm/Xsession to; change the example Xsession to reflect what xenodm's default Xsession does. Laurie
Sensors not being picked up
I seem to have an odd situation with sensor enumeration in sensorsd, but I'm not sure if the real cause is in sensorsd, the relevant drivers (xhci and friends, uhidpp), or the kernel. This is on amd64 -current. My Logitech mouse attaches as uhidpp0 and exposes a battery sensor: $ sysctl|grep uhidpp0 hw.sensors.uhidpp0.raw0=4 (battery levels) hw.sensors.uhidpp0.percent0=20.00% (battery level), WARNING I have the following sensorsd.conf: hw.sensors.uhidpp0.percent0:low=30%:command=... However, if I start sensorsd in rc.conf.local, it does not pick up the uhidpp0 sensor. Indeed, /var/log/daemon contains these two lines from sensorsd: Jul 26 08:44:05 overdrive sensorsd[65091]: startup, system has 2 sensors ... Jul 26 08:45:05 overdrive sensorsd[10230]: softraid0.drive0: online, OK Notice that only 1 sensor is printed out: I assume, but am not certain, that the unnamed sensor is my CPU's temperature sensor. Even though my mouse battery is currently below the threshold, the limit does not trigger. Equally oddly, during boot, everything associated with the mouse seems to attach, detach, then reattach, though all of this is printed on the console before the local daemons are started. I get this in /var/log/dmesg: Jul 26 08:44:04 overdrive /bsd: uhidev2 at uhub3 port 2 configuration 1 interface 1 "Logitech USB Receiver" rev 2.00/12.03 addr 5 Jul 26 08:44:04 overdrive /bsd: uhidev2: iclass 3/1, 8 report ids Jul 26 08:44:04 overdrive /bsd: ums0 at uhidev2 reportid 2: 16 buttons, Z and W dir Jul 26 08:44:04 overdrive /bsd: wsmouse0 at ums0 mux 0 Jul 26 08:44:04 overdrive /bsd: uhid1 at uhidev2 reportid 3: input=4, output=0, feature=0 Jul 26 08:44:04 overdrive /bsd: uhid2 at uhidev2 reportid 4: input=1, output=0, feature=0 Jul 26 08:44:04 overdrive /bsd: uhid3 at uhidev2 reportid 8: input=1, output=0, feature=0 Jul 26 08:44:04 overdrive /bsd: uhidev3 at uhub3 port 2 configuration 1 interface 2 "Logitech USB Receiver" rev 2.00/12.03 addr 5 Jul 26 08:44:04 overdrive /bsd: uhidev3: iclass 3/0, 33 report ids Jul 26 08:44:04 overdrive /bsd: uhidpp0 at uhidev3 reportid 16 device 1 trackball "MX Ergo" serial XYZ Jul 26 08:44:04 overdrive /bsd: uhid4 at uhidev3 reportid 32: input=14, output=14, feature=0 Jul 26 08:44:04 overdrive /bsd: uhid5 at uhidev3 reportid 33: input=31, output=31, feature=0 ... Jul 26 08:44:04 overdrive /bsd: wsdisplay0 at amdgpu0 mux 1: console (std, vt100 emulation), using wskbd0 Jul 26 08:44:04 overdrive /bsd: wskbd1: connecting to wsdisplay0 Jul 26 08:44:04 overdrive /bsd: wskbd2: connecting to wsdisplay0 Jul 26 08:44:04 overdrive /bsd: wsdisplay0: screen 1-5 added (std, vt100 emulation) Jul 26 08:44:04 overdrive /bsd: wskbd1: disconnecting from wsdisplay0 Jul 26 08:44:04 overdrive /bsd: wskbd1 detached Jul 26 08:44:04 overdrive /bsd: ukbd0 detached Jul 26 08:44:04 overdrive /bsd: uhidev1 detached Jul 26 08:44:04 overdrive /bsd: wsmouse0 detached Jul 26 08:44:04 overdrive /bsd: ums0 detached Jul 26 08:44:04 overdrive /bsd: uhid1 detached Jul 26 08:44:04 overdrive /bsd: uhid2 detached Jul 26 08:44:04 overdrive /bsd: uhid3 detached Jul 26 08:44:04 overdrive /bsd: uhidev2 detached Jul 26 08:44:04 overdrive /bsd: uhidpp0 detached Jul 26 08:44:04 overdrive /bsd: uhid4 detached Jul 26 08:44:04 overdrive /bsd: uhid5 detached Jul 26 08:44:04 overdrive /bsd: uhidev3 detached Jul 26 08:44:04 overdrive /bsd: uhidev1 at uhub3 port 2 configuration 1 interface 0 "Logitech USB Receiver" rev 2.00/12.03 addr 5 Jul 26 08:44:04 overdrive /bsd: uhidev1: iclass 3/1 Jul 26 08:44:04 overdrive /bsd: ukbd0 at uhidev1: 8 variable keys, 6 key codes Jul 26 08:44:04 overdrive /bsd: wskbd1 at ukbd0: console keyboard, using wsdisplay0 Jul 26 08:44:04 overdrive /bsd: uhidev2 at uhub3 port 2 configuration 1 interface 1 "Logitech USB Receiver" rev 2.00/12.03 addr 5 Jul 26 08:44:04 overdrive /bsd: uhidev2: iclass 3/1, 8 report ids Jul 26 08:44:04 overdrive /bsd: ums0 at uhidev2 reportid 2: 16 buttons, Z and W dir Jul 26 08:44:04 overdrive /bsd: wsmouse0 at ums0 mux 0 Jul 26 08:44:04 overdrive /bsd: uhid1 at uhidev2 reportid 3: input=4, output=0, feature=0 Jul 26 08:44:04 overdrive /bsd: uhid2 at uhidev2 reportid 4: input=1, output=0, feature=0 Jul 26 08:44:04 overdrive /bsd: uhid3 at uhidev2 reportid 8: input=1, output=0, feature=0 Jul 26 08:44:04 overdrive /bsd: uhidev3 at uhub3 port 2 configuration 1 interface 2 "Logitech USB Receiver" rev 2.00/12.03 addr 5 Jul 26 08:44:04 overdrive /bsd: uhidev3: iclass 3/0, 33 report ids Jul 26 08:44:04 overdrive /bsd: uhidpp0 at uhidev3 reportid 16 device 1 trackball "MX Ergo" serial XYZ Jul 26 08:44:04 overdrive /bsd: uhid4 at uhidev3 reportid 32: input=14, output=14, feature=0 Jul 26 08:44:04 overdrive /bsd: uhid5 at uhidev3 reportid 33: input=31, output=31, feature=0 Jul 26 08:44:05 overdrive savecore: no core dump Notice that the attach, detach, and
Re: X11 blanking problem related to page flipping?
On Sat, Nov 21, 2020 at 10:16:23AM +0100, Antoine Jacoutot wrote: >> I've been having an intermittent problem for some months with my X11 >> screen blanking (i.e. going totally black -- however, the mouse still >> displays and changes shape depending on what it's hovering over!). >> Switching to Ctrl+Alt+F1 and back fixes it, though once in a while causes >> X11 to crash. Sometimes this doesn't happen for a few days, at which point >> I think I've fixed it. Sometimes it happens several times in 10 minutes. >> There is no obvious trigger for it: I might have a web browser loaded or >> not, or ffmpeg running or not etc etc. > I have been seeing the same. I can usually reproduce it by having lots of > chromium tabs with heavy web sites opened (like clicking on 5 or 6 links > from google news). A follow-up to this, since the problem still occurs. I've been playing around with not running Chrome or Iridium, and I think Antoine has put his finger on the nub of the problem: if I don't use Chrome or Iridium, the problem never manifests. At some point after using them, I then have intermittent blanking, which sometimes needs a console switch to fix, and perhaps 1/3 of the time a console fix kills X. I don't know what Chrome or Iridium are doing that triggers this problem, but nothing else I run seems to trigger it. Laurie
Re: X11 blanking problem related to page flipping?
On Sat, Nov 21, 2020 at 10:16:23AM +0100, Antoine Jacoutot wrote: Hello Antoine, >> I've been having an intermittent problem for some months with my X11 >> screen blanking (i.e. going totally black -- however, the mouse still >> displays and changes shape depending on what it's hovering over!). >> Switching to Ctrl+Alt+F1 and back fixes it, though once in a while causes >> X11 to crash. >> Sometimes this doesn't happen for a few days, at which point I think I've >> fixed it. Sometimes it happens several times in 10 minutes. There is no >> obvious trigger for it: I might have a web browser loaded or not, or >> ffmpeg running or not etc etc. > I have been seeing the same. > I can usually reproduce it by having lots of chromium tabs with heavy web > sites opened (like clicking on 5 or 6 links from google news). > I blamed GNOME but that might not be the case... I'm running XFCE, so we can probably rule GNOME out. I wonder if you have the same hardware as me for example? [Maybe you can do a dmesg diff?] Laurie
X11 blanking problem related to page flipping?
I've been having an intermittent problem for some months with my X11 screen blanking (i.e. going totally black -- however, the mouse still displays and changes shape depending on what it's hovering over!). Switching to Ctrl+Alt+F1 and back fixes it, though once in a while causes X11 to crash. Sometimes this doesn't happen for a few days, at which point I think I've fixed it. Sometimes it happens several times in 10 minutes. There is no obvious trigger for it: I might have a web browser loaded or not, or ffmpeg running or not etc etc. I now think I might have a clue from Xorg.0.log. The full Xorg.0.log is attached but I suspect this might be the crucial part: [ 86235.372] (II) modeset(0): Modeline "1280x1024"x0.0 108.00 1280 1328 1440 1688 1024 1025 1028 1066 +hsync +vsync (64.0 kHz e) [ 86235.372] (II) modeset(0): Modeline "1600x1200"x0.0 162.00 1600 1664 1856 2160 1200 1201 1204 1250 +hsync +vsync (75.0 kHz e) [ 88657.765] (WW) modeset(0): Page flip failed: No such file or directory [ 88657.765] (EE) modeset(0): present flip failed [ 88657.766] (WW) modeset(0): Page flip failed: No such file or directory [ 88657.799] failed to add fb -2 [ 88657.799] (EE) modeset(0): failed to set mode: No such file or directory [ 88657.835] (WW) modeset(0): Page flip failed: No such file or directory [ 88657.835] (EE) modeset(0): present flip failed [ 88657.894] (WW) modeset(0): Page flip failed: No such file or directory [ 88657.894] (EE) modeset(0): present flip failed [ 88657.915] (WW) modeset(0): Page flip failed: No such file or directory [ 88657.915] (EE) modeset(0): present flip failed [ 88657.932] (WW) modeset(0): Page flip failed: No such file or directory [ 88657.932] (EE) modeset(0): present flip failed [ 88657.965] (WW) modeset(0): Page flip failed: No such file or directory [ 88657.965] (EE) modeset(0): present flip failed [ 88657.994] (WW) modeset(0): Page flip failed: No such file or directory [ 88657.994] (EE) modeset(0): present flip failed [ 88658.032] (WW) modeset(0): Page flip failed: No such file or directory [ 88658.032] (EE) modeset(0): present flip failed [ 88658.049] (WW) modeset(0): Page flip failed: No such file or directory [ 88658.049] (EE) modeset(0): present flip failed [ 88658.083] (WW) modeset(0): Page flip failed: No such file or directory [ 88658.083] (EE) modeset(0): present flip failed [ 88658.131] (WW) modeset(0): Page flip failed: No such file or directory [ 88658.131] (EE) modeset(0): present flip failed [ 88658.149] (WW) modeset(0): Page flip failed: No such file or directory [ 88658.149] (EE) modeset(0): present flip failed [ 88658.189] (WW) modeset(0): flip queue failed: Device busy [ 88658.189] (WW) modeset(0): Page flip failed: Device busy These last 3 lines repeat until, I think, I've done a terminal switch at which point we get: [ 88662.674] (WW) modeset(0): flip queue failed: Device busy [ 88662.674] (WW) modeset(0): Page flip failed: Device busy [ 88662.674] (EE) modeset(0): present flip failed [ 88662.696] (II) AIGLX: Suspending AIGLX clients for VT switch [ 88664.420] (II) AIGLX: Resuming AIGLX clients after VT switch [ 88664.526] (II) modeset(0): EDID vendor "DEL", prod id 41148 [ 88664.526] (II) modeset(0): Using hsync ranges from config file [ 88664.526] (II) modeset(0): Using vrefresh ranges from config file [ 88664.526] (II) modeset(0): Printing DDC gathered Modelines: [ 88664.526] (II) modeset(0): Modeline "1920x1200"x0.0 154.00 1920 1968 2000 2080 1200 1203 1209 1235 +hsync +vsync (74.0 kHz eP) [ 88664.526] (II) modeset(0): Modeline "1920x1080"x0.0 148.50 1920 2008 2052 2200 1080 1084 1089 1125 +hsync +vsync (67.5 kHz e) [ 88664.526] (II) modeset(0): Modeline "1920x1080i"x0.0 74.25 1920 2008 2052 2200 1080 1084 1094 1125 interlace +hsync +vsync (33.8 kHz e) [ 88664.526] (II) modeset(0): Modeline "1280x720"x0.0 74.25 1280 1390 1430 1650 720 725 730 750 +hsync +vsync (45.0 kHz e) [ 88664.526] (II) modeset(0): Modeline "720x480"x0.0 27.00 720 736 798 858 480 489 495 525 -hsync -vsync (31.5 kHz e) [ 88664.526] (II) modeset(0): Modeline "1440x480i"x0.0 27.00 1440 1478 1602 1716 480 488 494 525 interlace -hsync -vsync (15.7 kHz e) [ 88664.526] (II) modeset(0): Modeline "1440x576i"x0.0 27.00 1440 1464 1590 1728 576 580 586 625 interlace -hsync -vsync (15.6 kHz e) [ 88664.526] (II) modeset(0): Modeline "640x480"x0.0 25.18 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz e) [ 88664.526] (II) modeset(0): Modeline "1920x1080i"x0.0 74.25 1920 2448 2492 2640 1080 1084 1094 1125 interlace +hsync +vsync (28.1 kHz e) [ 88664.526] (II) modeset(0): Modeline "1920x1080"x0.0 148.50 1920 2448 2492 2640 1080 1084 1089 1125 +hsync +vsync (56.2 kHz e) [ 88664.526] (II) modeset(0): Modeline "720x576"x0.0 27.00 720 732 796 864 576 581 586 625 -hsync -vsync (31.2 kHz e) [ 88664.526] (II) modeset(0): Modeline
Re: X11 intermittently blanking
On Fri, Oct 02, 2020 at 03:20:36PM +0100, Laurence Tratt wrote: >> For the past couple of weeks I've been encountering a weird problem on >> -current amd64 -- my screen intermittently blanks for around 2-4 seconds >> when running xorg. At first I thought this was a hardware problem (the >> machine isn't a spring chicken), but then ffmpeg caught the blanking while >> I was doing a screencast (i.e. the recording of the xorg part of things >> goes entirely blank for a couple of seconds), so it seems to be a software >> problem. >> >> Unfortunately I can't seem to find any obvious trigger. It seems to happen >> more often when the machine is under heavy load, but sometimes it happens >> under light load. Frankly, I don't have any real idea *what* could be >> causing it, and I'm hoping that someone else might have seen this, and >> perhaps have been equally baffled as to the cause! > I have now found a semi-reliable way of triggering this with the following > ffmpeg command on a decent length video file: > > ffmpeg -i -c:a flac out.flac > > The blanking effect is not consistent or continuous: sometimes the display > will blank every few seconds, sometimes it might go 30 seconds without > doing so. > > I'm running on a 4 core machine, and this task maxes out all 4 cores. > Interestingly, however, other tasks which use all 4 cores do not cause the > display blanking problem as often. I don't know what ffmpeg is doing > differently, other than 'top' shows that it's often 'fsleep'ing (which may > well be completely irrelevant to the problem I'm seeing). For the record, I've not had this problem in the last week or so -- hopefully it's disappeared for good! Laurie
Re: X11 intermittently blanking
On Wed, Sep 30, 2020 at 10:30:57PM +0100, Laurence Tratt wrote: > For the past couple of weeks I've been encountering a weird problem on > -current amd64 -- my screen intermittently blanks for around 2-4 seconds > when running xorg. At first I thought this was a hardware problem (the > machine isn't a spring chicken), but then ffmpeg caught the blanking while > I was doing a screencast (i.e. the recording of the xorg part of things > goes entirely blank for a couple of seconds), so it seems to be a software > problem. > > Unfortunately I can't seem to find any obvious trigger. It seems to happen > more often when the machine is under heavy load, but sometimes it happens > under light load. Frankly, I don't have any real idea *what* could be > causing it, and I'm hoping that someone else might have seen this, and > perhaps have been equally baffled as to the cause! I have now found a semi-reliable way of triggering this with the following ffmpeg command on a decent length video file: ffmpeg -i -c:a flac out.flac The blanking effect is not consistent or continuous: sometimes the display will blank every few seconds, sometimes it might go 30 seconds without doing so. I'm running on a 4 core machine, and this task maxes out all 4 cores. Interestingly, however, other tasks which use all 4 cores do not cause the display blanking problem as often. I don't know what ffmpeg is doing differently, other than 'top' shows that it's often 'fsleep'ing (which may well be completely irrelevant to the problem I'm seeing). Laurie
X11 intermittently blanking
For the past couple of weeks I've been encountering a weird problem on -current amd64 -- my screen intermittently blanks for around 2-4 seconds when running xorg. At first I thought this was a hardware problem (the machine isn't a spring chicken), but then ffmpeg caught the blanking while I was doing a screencast (i.e. the recording of the xorg part of things goes entirely blank for a couple of seconds), so it seems to be a software problem. Unfortunately I can't seem to find any obvious trigger. It seems to happen more often when the machine is under heavy load, but sometimes it happens under light load. Frankly, I don't have any real idea *what* could be causing it, and I'm hoping that someone else might have seen this, and perhaps have been equally baffled as to the cause! Laurie OpenBSD 6.8 (GENERIC.MP) #94: Tue Sep 29 00:13:21 MDT 2020 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 17028239360 (16239MB) avail mem = 16497115136 (15732MB) random: good seed from bootblocks mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: SMBIOS rev. 3.0 @ 0xc320 (89 entries) bios0: vendor American Megatrends Inc. version "3805" date 05/16/2018 bios0: ASUSTeK COMPUTER INC. Z170M-PLUS acpi0 at bios0: ACPI 6.1 acpi0: sleep states S0 S3 S4 S5 acpi0: tables DSDT FACP APIC FPDT BGRT MCFG SSDT FIDT SSDT SSDT HPET SSDT SSDT UEFI SSDT LPIT WSMT SSDT SSDT DBGP DBG2 acpi0: wakeup devices PEG0(S4) PEGP(S4) PEG1(S4) PEGP(S4) PEG2(S4) PEGP(S4) SIO1(S3) UAR1(S4) RP09(S4) PXSX(S4) RP10(S4) PXSX(S4) RP11(S4) PXSX(S4) RP12(S4) PXSX(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) Core(TM) i7-6700K CPU @ 4.00GHz, 4121.53 MHz, 06-5e-03 cpu0: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,TSC_ADJUST,SGX,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,MPX,RDSEED,ADX,SMAP,CLFLUSHOPT,PT,MD_CLEAR,TSXFA,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,XSAVEC,XGETBV1,XSAVES,MELTDOWN 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 24MHz cpu0: mwait min=64, max=64, C-substates=0.2.1.2.4.1, IBE cpu1 at mainbus0: apid 2 (application processor) cpu1: Intel(R) Core(TM) i7-6700K CPU @ 4.00GHz, 4120.01 MHz, 06-5e-03 cpu1: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,TSC_ADJUST,SGX,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,MPX,RDSEED,ADX,SMAP,CLFLUSHOPT,PT,MD_CLEAR,TSXFA,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,XSAVEC,XGETBV1,XSAVES,MELTDOWN cpu1: 256KB 64b/line 8-way L2 cache cpu1: smt 0, core 1, package 0 cpu2 at mainbus0: apid 4 (application processor) cpu2: Intel(R) Core(TM) i7-6700K CPU @ 4.00GHz, 4120.01 MHz, 06-5e-03 cpu2: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,TSC_ADJUST,SGX,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,MPX,RDSEED,ADX,SMAP,CLFLUSHOPT,PT,MD_CLEAR,TSXFA,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,XSAVEC,XGETBV1,XSAVES,MELTDOWN cpu2: 256KB 64b/line 8-way L2 cache cpu2: smt 0, core 2, package 0 cpu3 at mainbus0: apid 6 (application processor) cpu3: Intel(R) Core(TM) i7-6700K CPU @ 4.00GHz, 4120.01 MHz, 06-5e-03 cpu3: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,TSC_ADJUST,SGX,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,MPX,RDSEED,ADX,SMAP,CLFLUSHOPT,PT,MD_CLEAR,TSXFA,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,XSAVEC,XGETBV1,XSAVES,MELTDOWN cpu3: 256KB 64b/line 8-way L2 cache cpu3: smt 0, core 3, package 0 ioapic0 at mainbus0: apid 2 pa 0xfec0, version 20, 120 pins acpimcfg0 at acpi0 acpimcfg0: addr 0xf800, bus 0-63 acpihpet0 at acpi0: 2399 Hz acpiprt0 at acpi0: bus 0 (PCI0) acpiprt1 at acpi0: bus -1 (PEG0) acpiprt2 at acpi0: bus -1 (PEG1) acpiprt3 at acpi0: bus -1 (PEG2) acpiprt4 at acpi0: bus 4 (RP09) acpiprt5 at
Re: uvideo problems with mjpeg on external cameras
On Thu, Jul 02, 2020 at 01:54:52PM +0200, Marcus Glocker wrote: Hello Marcus, > Can you send me your cams USB device id again please? Here's the relevant excerpt from usbdevs: addr 04: 046d:0892 Logitech, HD Pro Webcam C920 high speed, power 500 mA, config 1, rev 0.19, iSerial AECF521F driver: uvideo0 driver: uaudio0 That corresponds to the "modern" USB ID from [1]. > I just can re-test my Logitech C920 Pro next week again since I'm > currently not at home. Thanks! > Since the last time I have tested it there were some more changes in > xhci(4) - Not sure if there is any relation to that. But you said you face > the same issues on USB3 and USB2, right? My Asus 170M-PLUS manual claims to have a mix of USB2 and USB3 ports on the back (I'm not sure how I can actually tell other than hoping the manual is correct!), but plugging it into either type seemed to make no difference. One other odd thing to add to the mix. `video -q` now (sometimes? always? I'm not sure) shows extra modes: video device /dev/video: encodings: yuy2 frame sizes (width x height, in pixels) and rates (in frames per second): 160x90: 30, 24, 20, 15, 10, 7, 5 160x120: 30, 24, 20, 15, 10, 7, 5 176x144: 30, 24, 20, 15, 10, 7, 5 320x180: 30, 24, 20, 15, 10, 7, 5 320x240: 30, 24, 20, 15, 10, 7, 5 352x288: 30, 24, 20, 15, 10, 7, 5 432x240: 30, 24, 20, 15, 10, 7, 5 640x360: 30, 24, 20, 15, 10, 7, 5 640x480: 30, 24, 20, 15, 10, 7, 5 800x448: 30, 24, 20, 15, 10, 7, 5 800x600: 24, 20, 15, 10, 7, 5 864x480: 24, 20, 15, 10, 7, 5 960x720: 15, 10, 7, 5 1024x576: 15, 10, 7, 5 1280x720: 10, 7, 5 1600x896: 7, 5 1920x1080: 5 2304x1296: 2 2304x1536: 2 controls: brightness, contrast, saturation, gain, sharpness In my original bug report [2], only modes up to 1920x1080 (inclusive) were shown. Those new modes do work -- sort of. For the first few seconds, `video -s 2304x1536` does show about two frames a second for roughly 10 seconds. Then it pauses with a certain frame for several seconds before printing "video: ioctl VIDIOC_DQBUF: Invalid argument". Sometimes it then resumes, but with 1 frame every 2-4 seconds; sometimes it crashes outright. [The same thing happens with ffplay at that resolution -- a few seconds of 2fps, a big pause, then "video: ioctl VIDIOC_DQBUF: Invalid argument".] Sometimes I get "usbd_start_next: error=13" in my dmesg at about the same time, though I'm not entirely sure if that's related or not. One possibility has occurred to me: when communicating with Alexandre Ratchov about sound on my machine sometimes dying, he said (from memory) that the USB stack could only buffer about 50ms of audio before failing, and that the USB stack ran at a relatively low priority in the kernel. [Apologies to Alexandre if I've misrepresented him!] I'm wondering if maybe the amount of data the camera is trying to transfer exceeds the USB stack's ability to transfer it? This is a wild stab in the dark: I don't have the first idea as to how I might test this theory out! Laurie [1] https://trac.ffmpeg.org/ticket/8413 [2] https://marc.info/?l=openbsd-bugs=159298546428570=2
Re: uvideo problems with mjpeg on external cameras
On Sat, Jun 27, 2020 at 02:41:25AM +0200, Ingo Feinerer wrote: Hello Ingo, > Same behavior with an old MS LifeCam NX-6000 (which only supports > MJPEG). It works up to 160x120 without problems on USB3 ports and up to > the maximum resolution supported by the camera on USB2 ports (i.e., USB3 > disabled in the BIOS). Interesting. I've just tried the webcam on what my desktop motherboard manual claims is a USB 2.0/2.1 port, but it doesn't make any difference to MJPEG mode on the C920 for me unfortunately. Indeed, MJPEG mode functions worse on my desktop than it did on my Thinkpad (more modes break up). I'm CCing Marcus, because he's had recent success with Logitech webcams [1, 2, 3] and perhaps can tell us if that was in H264 or MJPEG mode? I've also noticed that I can now make video(1) work properly more often. Basically if I invoke it twice: $ video -s 800x480 $ video -s 800x480 on the second invocation it will always show a black screen. However, if I change the resolution it works again: $ video -s 800x600 Flipping resolution seems to always work, perhaps because it's resetting some internal state in the camera? [video(1)'s settings such as saturation are otherwise "sticky".] Laurie [1] https://marc.info/?l=openbsd-cvs=157863712513236=2 [2] https://marc.info/?l=openbsd-cvs=157610240222816=2 [3] https://marc.info/?l=openbsd-cvs=157301922818383=2
Re: uvideo problems with mjpeg on external cameras
On Thu, Jun 25, 2020 at 11:21:51PM +0100, Laurence Tratt wrote: > It seems this is because the Logitech C920 has been revised (mine has the > USB ID 046d:0892) and no longer supports a separate H264 mode. This turns out to be a total red herring -- modern FFmpeg deals with the MJPEG fine and you *can* get it to work for pointlessly small resolutions on OpenBSD. Using this command: ffplay -f v4l2 -input_format mjpeg -video_size 160x90 -i /dev/video0 one can quickly map which resolutions work and which don't. There is some variation from reboot to reboot, but the approximate summary for MJPEG resolutions is roughly as follows: 160x90 Works 160x120 Works 176x144 Works 320x180 Mostly works 320x240 Sometimes works 352x288 Sometimes works 432x240 Breaks up 640x360 Breaks up 640x480 Breaks up 800x448 Breaks up 800x600 Breaks up 864x480 Breaks up 960x720 Breaks up 1024x576 Breaks up 1280x720 Breaks up 1600x896 Breaks up 1920x1080Breaks up I can only guess as to why this might be: perhaps OpenBSD's USB stack isn't able to transfer data from the USB device? Or maybe there's a problem in uvideo.c (but I've spent several hours fiddling with it and comparing it to the Linux UVC support: I couldn't find anything obvious)? Or ...? I'm now stuck. If anyone has suggestions, I'm all ears! At a basic level, it would be interesting simply to know if anyone else uses MJPEG mode on a webcam and whether they've experienced video break-up too. Laurie
Re: uvideo problems with mjpeg on external cameras
On Wed, Jun 24, 2020 at 08:51:37AM +0100, Laurence Tratt wrote: > External webcams don't seem to work fully correctly with the uvideo driver > and mjpeg? If I use this command as an example (since it's cross platform): > > $ ffmpeg -f v4l2 -input_format mjpeg -video_size 1280x720 -framerate 30 \ > -i /dev/video0 webcam.mkv > > on my X1 Carbon (6th gen), the internal camera produces correct output, but > an external Logitech C920s produces endless warnings along the lines of: > > [mjpeg @ 0xe666c20b800] mjpeg_decode_dc: bad vlc: 0:0 (0xe66ec71f248) > [mjpeg @ 0xe666c20b800] error dc > [mjpeg @ 0xe666c20b800] error y=57 x=9 > [mjpeg @ 0xe666c20b800] Found EOI before any SOF, ignoring > [mjpeg @ 0xe666c20b800] No JPEG data found in image > Error while decoding stream #0:0: Invalid data found when processing input > [mjpeg @ 0xe666c20b800] Found EOI before any SOF, ignoring > [mjpeg @ 0xe666c20b800] No JPEG data found in image > Error while decoding stream #0:0: Invalid data found when processing input It seems this is because the Logitech C920 has been revised (mine has the USB ID 046d:0892) and no longer supports a separate H264 mode. Instead it (somehow) embeds H264 data into the mjpeg stream. From what I can gather, most/all new Logitech webcams use this new Logitech format. This post [1] is informative. FFmpeg have an issue for this [2] which goes into more detail. Since my C920 works fine with FFmpeg on Linux, my working guess is that FFmpeg has implemented an appropriate demuxer for the Logitech format, but that uvideo chokes on it. If anyone has any suggestions, I'm all ears! Laurie [1] https://stackoverflow.com/posts/56403628/revisions [2] https://trac.ffmpeg.org/ticket/8413
drm panic
The recent DRM update has fixed one long-ish-standing bug for me where Xorg sometimes would get stuck while executing Xsession (I could never work out why) which is really good! However I've now had the following kernel panic several times: kernel: page fault trap, code=0 Stopped at intel_partial_pages+0xf4:moq 0x58,%rsi Unfortunately that also seems to take out my keyboard at ddb so I have no further information beyond my dmesg :/ Laurie OpenBSD 6.7-current (GENERIC.MP) #258: Wed Jun 10 20:46:20 MDT 2020 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 17028239360 (16239MB) avail mem = 16497246208 (15733MB) random: good seed from bootblocks mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: SMBIOS rev. 3.0 @ 0xc320 (89 entries) bios0: vendor American Megatrends Inc. version "3805" date 05/16/2018 bios0: ASUSTeK COMPUTER INC. Z170M-PLUS acpi0 at bios0: ACPI 6.1 acpi0: sleep states S0 S3 S4 S5 acpi0: tables DSDT FACP APIC FPDT BGRT MCFG SSDT FIDT SSDT SSDT HPET SSDT SSDT UEFI SSDT LPIT WSMT SSDT SSDT DBGP DBG2 acpi0: wakeup devices PEG0(S4) PEGP(S4) PEG1(S4) PEGP(S4) PEG2(S4) PEGP(S4) SIO1(S3) UAR1(S4) RP09(S4) PXSX(S4) RP10(S4) PXSX(S4) RP11(S4) PXSX(S4) RP12(S4) PXSX(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) Core(TM) i7-6700K CPU @ 4.00GHz, 4011.41 MHz, 06-5e-03 cpu0: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,TSC_ADJUST,SGX,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,MPX,RDSEED,ADX,SMAP,CLFLUSHOPT,PT,MD_CLEAR,TSXFA,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,XSAVEC,XGETBV1,XSAVES,MELTDOWN 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 24MHz cpu0: mwait min=64, max=64, C-substates=0.2.1.2.4.1, IBE cpu1 at mainbus0: apid 2 (application processor) cpu1: Intel(R) Core(TM) i7-6700K CPU @ 4.00GHz, 4009.91 MHz, 06-5e-03 cpu1: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,TSC_ADJUST,SGX,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,MPX,RDSEED,ADX,SMAP,CLFLUSHOPT,PT,MD_CLEAR,TSXFA,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,XSAVEC,XGETBV1,XSAVES,MELTDOWN cpu1: 256KB 64b/line 8-way L2 cache cpu1: smt 0, core 1, package 0 cpu2 at mainbus0: apid 4 (application processor) cpu2: Intel(R) Core(TM) i7-6700K CPU @ 4.00GHz, 4009.91 MHz, 06-5e-03 cpu2: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,TSC_ADJUST,SGX,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,MPX,RDSEED,ADX,SMAP,CLFLUSHOPT,PT,MD_CLEAR,TSXFA,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,XSAVEC,XGETBV1,XSAVES,MELTDOWN cpu2: 256KB 64b/line 8-way L2 cache cpu2: smt 0, core 2, package 0 cpu3 at mainbus0: apid 6 (application processor) cpu3: Intel(R) Core(TM) i7-6700K CPU @ 4.00GHz, 4009.91 MHz, 06-5e-03 cpu3: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,TSC_ADJUST,SGX,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,MPX,RDSEED,ADX,SMAP,CLFLUSHOPT,PT,MD_CLEAR,TSXFA,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,XSAVEC,XGETBV1,XSAVES,MELTDOWN cpu3: 256KB 64b/line 8-way L2 cache cpu3: smt 0, core 3, package 0 ioapic0 at mainbus0: apid 2 pa 0xfec0, version 20, 120 pins acpimcfg0 at acpi0 acpimcfg0: addr 0xf800, bus 0-63 acpihpet0 at acpi0: 2399 Hz acpiprt0 at acpi0: bus 0 (PCI0) acpiprt1 at acpi0: bus -1 (PEG0) acpiprt2 at acpi0: bus -1 (PEG1) acpiprt3 at acpi0: bus -1 (PEG2) acpiprt4 at acpi0: bus 4 (RP09) acpiprt5 at acpi0: bus -1 (RP10) acpiprt6 at acpi0: bus -1 (RP11) acpiprt7 at acpi0: bus -1 (RP12) acpiprt8 at acpi0: bus -1 (RP13) acpiprt9 at acpi0: bus 3 (RP01) acpiprt10 at acpi0: bus -1 (RP02) acpiprt11 at acpi0: bus -1 (RP03) acpiprt12 at acpi0: bus -1 (RP04) acpiprt13 at acpi0: bus -1 (RP05) acpiprt14 at acpi0: bus -1 (RP06) acpiprt15 at
Panic in ffs_mapsearch
>Synopsis: kernel crash in ffs_mapsearch >Environment: System : OpenBSD 6.4 Details : OpenBSD 6.4-beta (GENERIC.MP) #300: Tue Sep 18 02:27:17 MDT 2018 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP Architecture: OpenBSD.amd64 Machine : amd64 >Description: The machine paniced, apparently because something went wrong in FFS (specifically ffs_mapsearch): https://postimg.cc/ZBrtP1BP gzip was the active process: https://postimg.cc/nXzx8RgZ I don't have softdep turned on for any of the file systems in this machine. >How-To-Repeat: Unclear. This is the first time I've seen this particular panic. dmesg: OpenBSD 6.4-beta (GENERIC.MP) #300: Tue Sep 18 02:27:17 MDT 2018 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 16917921792 (16134MB) avail mem = 16395931648 (15636MB) mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: SMBIOS rev. 3.0 @ 0x4f0bb000 (62 entries) bios0: vendor LENOVO version "N1MET48W (1.33 )" date 05/16/2018 bios0: LENOVO 20HQS49Q00 acpi0 at bios0: rev 2 acpi0: sleep states S0 S3 S4 S5 acpi0: tables DSDT FACP SSDT TPM2 UEFI SSDT SSDT HPET APIC MCFG ECDT SSDT BOOT BATB SSDT SSDT SSDT WSMT SSDT SSDT DBGP DBG2 MSDM DMAR ASF! FPDT UEFI acpi0: wakeup devices GLAN(S4) XHC_(S3) XDCI(S4) HDAS(S4) RP01(S4) RP02(S4) RP04(S4) RP05(S4) RP06(S4) RP07(S4) RP08(S4) RP09(S4) RP10(S4) RP11(S4) RP12(S4) RP13(S4) [...] acpitimer0 at acpi0: 3579545 Hz, 24 bits acpihpet0 at acpi0: 2399 Hz acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: Intel(R) Core(TM) i7-7500U CPU @ 2.70GHz, 1392.77 MHz, 06-8e-09 cpu0: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,SGX,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,MPX,RDSEED,ADX,SMAP,CLFLUSHOPT,PT,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,XSAVEC,XGETBV1,XSAVES,MELTDOWN 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 23MHz 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) Core(TM) i7-7500U CPU @ 2.70GHz, 1133.04 MHz, 06-8e-09 cpu1: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,SGX,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,MPX,RDSEED,ADX,SMAP,CLFLUSHOPT,PT,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,XSAVEC,XGETBV1,XSAVES,MELTDOWN cpu1: 256KB 64b/line 8-way L2 cache cpu1: smt 0, core 1, package 0 cpu2 at mainbus0: apid 1 (application processor) cpu2: Intel(R) Core(TM) i7-7500U CPU @ 2.70GHz, 997.67 MHz, 06-8e-09 cpu2: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,SGX,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,MPX,RDSEED,ADX,SMAP,CLFLUSHOPT,PT,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,XSAVEC,XGETBV1,XSAVES,MELTDOWN cpu2: 256KB 64b/line 8-way L2 cache cpu2: smt 1, core 0, package 0 cpu3 at mainbus0: apid 3 (application processor) cpu3: Intel(R) Core(TM) i7-7500U CPU @ 2.70GHz, 997.67 MHz, 06-8e-09 cpu3: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,SGX,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,MPX,RDSEED,ADX,SMAP,CLFLUSHOPT,PT,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,XSAVEC,XGETBV1,XSAVES,MELTDOWN cpu3: 256KB 64b/line 8-way L2 cache cpu3: smt 1, core 1, package 0 ioapic0 at mainbus0: apid 2 pa 0xfec0, version 20, 120 pins acpimcfg0 at acpi0 acpimcfg0: addr 0xf000, bus 0-127 acpiec0 at acpi0 acpiprt0 at acpi0: bus 0 (PCI0) acpiprt1 at acpi0: bus 2 (RP01) acpiprt2 at acpi0: bus -1 (RP02) acpiprt3 at acpi0: bus 4 (RP03) acpiprt4 at acpi0: bus -1 (RP04) acpiprt5 at acpi0: bus 5 (RP05) acpiprt6 at acpi0: bus -1 (RP06) acpiprt7 at acpi0: bus -1 (RP07) acpiprt8 at acpi0: bus -1 (RP08) acpiprt9 at acpi0: bus 6 (RP09) acpiprt10 at acpi0: bus -1 (RP10) acpiprt11 at
Re: panic on resume in acpitz_setfan
On Mon, Aug 14, 2017 at 12:05:59AM +0100, Laurence Tratt wrote: > The following panic happened immediately after a resume (the second since > the machine was switched on) on the Aug 11th snapshot: > > uvm_fault(0x81b3ff8, 0x20003, 0, 1) -> e > kernel: page fault trap, code=0 > Stopped at acpitz_setfan+0x8c: movq 0(%rax), %rsi > > https://imagebin.ca/v/3Wmq884ayBSf > > This happened before the keyboard was reattached, so I couldn't get any > further information from the panic. It turns out that this happens repeatedly on this machine. The precise offset in the message changes but it's always of the form: kernel: page fault trap, code=0 Stopped at acpitz_setfan+0x94: movq 0(%rbx),%rsi AFAICT it never happens after the first resume, but only on a subsequent resume (sometimes the second, sometimes the third etc.). One thing that does occur to me is that this machine is fanless: the fans are turned off in the BIOS. Maybe a null pointer is leaking in somewhere because of that? Laurie
kernel_lock not locked
>Synopsis: kernel_lock not locked
>Category: kernel
>Environment:
System : OpenBSD 6.3
Details : OpenBSD 6.3-current (GENERIC.MP) #55: Mon Jun 25 23:01:52
MDT 2018
dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
Architecture: OpenBSD.amd64
Machine : amd64
>Description:
I just hit the following kernel panic (a locking error in sched_bsd.c):
https://imagebin.ca/v/46kV6Tfqe1sc
I can hit this repeatedly by gdb'ing the new quodlibet 4.1.0 update that
Stuart just pushed to ports. It crashes at load; exactly at the point I
quit gdb the kernel panics. Here's the userland trace I get just before
the kernel panic occurs:
$ gdb /usr/local/bin/python3.6
GNU gdb 6.3
Copyright 2004 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and
you are
welcome to change it and/or distribute copies of it under certain
conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB. Type "show warranty" for
details.
This GDB was configured as "amd64-unknown-openbsd6.3"...
(no debugging symbols found)
(gdb) run /usr/local/bin/quodlibet
Starting program: /usr/local/bin/python3.6 /usr/local/bin/quodlibet
[New process 34894]
Program received signal SIGTRAP, Trace/breakpoint trap.
0x027d5fc0ba27 in _dl_debug_state ()
at /usr/src/libexec/ld.so/resolve.c:764
764 {
Current language: auto; currently minimal
(gdb) bt
#0 0x027d5fc0ba27 in _dl_debug_state ()
at /usr/src/libexec/ld.so/resolve.c:764
#1 0x027d5fc00e60 in dlopen (
libname=0x27d19bf9040 "libgdk_pixbuf-2.0.so.3200.1",
flags=257)
at /usr/src/libexec/ld.so/dlfcn.c:76
#2 0x027cf73a79c9 in g_module_open (
file_name=0x27d19bf9480 "libgdk_pixbuf-2.0.so.3200.1",
flags=Variable "flags" is not available.
)
at gmodule-dl.c:98
#3 0x027d30429ead in g_typelib_symbol ()
from /usr/local/lib/libgirepository-1.0.so.3.0
#4 0x027d30424dda in g_registered_type_info_get_g_type ()
from /usr/local/lib/libgirepository-1.0.so.3.0
#5 0x027d9d0e88d8 in pygi_arg_interface_new_from_info ()
from /usr/local/lib/python3.6/site-packages/gi/_gi.so
#6 0x027d9d0ee241 in pygi_arg_gobject_new_from_info ()
from /usr/local/lib/python3.6/site-packages/gi/_gi.so
#7 0x027d9d0e8b71 in pygi_arg_cache_new ()
from /usr/local/lib/python3.6/site-packages/gi/_gi.so
#8 0x027d9d0e9ae2 in _callable_cache_generate_args_cache_real ()
from /usr/local/lib/python3.6/site-packages/gi/_gi.so
#9 0x027d9d0e9858 in _callable_cache_init ()
from /usr/local/lib/python3.6/site-packages/gi/_gi.so
#10 0x027d9d0e8e9b in _function_cache_init ()
from /usr/local/lib/python3.6/site-packages/gi/_gi.so
---Type to continue, or q to quit---
#11 0x027d9d0e9359 in pygi_method_cache_new ()
from /usr/local/lib/python3.6/site-packages/gi/_gi.so
#12 0x027d9d0e858c in _wrap_g_callable_info_invoke ()
from /usr/local/lib/python3.6/site-packages/gi/_gi.so
#13 0x027d9d0dd4ae in _callable_info_call ()
from /usr/local/lib/python3.6/site-packages/gi/_gi.so
#14 0x027db5e99a02 in _PyObject_FastCallDict ()
from /usr/local/lib/libpython3.6m.so.0.0
#15 0x027db5f66be1 in call_function ()
from /usr/local/lib/libpython3.6m.so.0.0
#16 0x027db5f63ce9 in _PyEval_EvalFrameDefault ()
from /usr/local/lib/libpython3.6m.so.0.0
#17 0x027db5f67dd0 in fast_function ()
from /usr/local/lib/libpython3.6m.so.0.0
#18 0x027db5f66be8 in call_function ()
from /usr/local/lib/libpython3.6m.so.0.0
#19 0x027db5f63ce9 in _PyEval_EvalFrameDefault ()
from /usr/local/lib/libpython3.6m.so.0.0
#20 0x027db5f67529 in _PyEval_EvalCodeWithName ()
from /usr/local/lib/libpython3.6m.so.0.0
#21 0x027db5f67d5c in fast_function ()
from /usr/local/lib/libpython3.6m.so.0.0
#22 0x027db5f66be8 in call_function ()
from /usr/local/lib/libpython3.6m.so.0.0
---Type to continue, or q to quit---
#23 0x027db5f63ce9 in _PyEval_EvalFrameDefault ()
from
Re: Digital audio out no longer working?
On Sat, Jun 23, 2018 at 06:43:04PM +0200, Alexandre Ratchov wrote: Hello Alexandre, >> As of the last two snapshots, digital audio out via S/PDIF on my machine >> no longer works: >> >> $ doas mixerctl outputs.mode=digital >> mixerctl: field outputs.mode does not exist >> >> There also seems to be something odd with mixerctl's output which may or >> may >> be related? Note the "invalid format" near the end and the incomplete >> formatting of "volume.record". > Could you confirm that this diff fixes the problem? I am happy to confirm that this completely solves the problem. Thanks so much for doing this! Laurie -- Personal http://tratt.net/laurie/ Software Development Teamhttp://soft-dev.org/ https://github.com/ltratt http://twitter.com/laurencetratt
Digital audio out no longer working?
>Synopsis: digital audio out no longer working? >Environment: System : OpenBSD 6.3 Details : OpenBSD 6.3-current (GENERIC.MP) #14: Thu Jun 14 23:55:47 MDT 2018 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP Architecture: OpenBSD.amd64 Machine : amd64 >Description: As of the last two snapshots, digital audio out via S/PDIF on my machine no longer works: $ doas mixerctl outputs.mode=digital mixerctl: field outputs.mode does not exist There also seems to be something odd with mixerctl's output which may or may be related? Note the "invalid format" near the end and the incomplete formatting of "volume.record". $ mixerctl inputs.dac-0:1=126,126 inputs.dac-2:3=126,126 inputs.dac-4:5=126,126 inputs.dac-6:7=126,126 record.adc-0:1_mute=off record.adc-0:1=125,125 record.adc-2:3_mute=off record.adc-2:3=125,125 inputs.mix_source=mic,mic2,line-in,hp,line inputs.mix_mic=120,120 inputs.mix_mic2=120,120 inputs.mix_line-in=120,120 inputs.mix_hp=120,120 inputs.mix_line=120,120 inputs.mix2_source=dac-0:1,mix inputs.mix3_source=dac-2:3,mix inputs.mix4_source=dac-4:5,mix inputs.mix5_source=dac-6:7,mix outputs.SPDIF_source=dig-dac-0:1 outputs.line_source=mix2 outputs.line_mute=off outputs.line_dir=output outputs.line_boost=off outputs.line_eapd=on outputs.mic_source=mix3 outputs.mic_mute=off inputs.mic=85,85 outputs.mic_dir=input-vr80 outputs.mic2_source=mix8 outputs.mic2_mute=off inputs.mic2=85,85 outputs.mic2_dir=input-vr80 outputs.mic2_boost=off outputs.line-in_source=mix4 outputs.line-in_mute=off inputs.line-in=85,85 outputs.line-in_dir=input outputs.hp_source=mix5 outputs.hp_mute=off inputs.hp=85,85 outputs.hp_dir=output outputs.hp_boost=off outputs.hp_eapd=on record.adc-2:3_source=mic,mic2,line-in,hp,line,mix record.adc-0:1_source=mic,mic2,line-in,hp,line,mix inputs.dac-8:9=126,126 inputs.mix8_source=dac-8:9,mix outputs.line_sense=unplugged outputs.mic_sense=plugged outputs.mic2_sense=unplugged outputs.line-in_sense=unplugged outputs.hp_sense=unplugged outputs.master=126,126 outputs.master.mute=off outputs.master.slaves=dac-0:1,dac-6:7,line,hp record.volume=125,125 mixerctl: Invalid format. volume.record=% $ dmesg: OpenBSD 6.3-current (GENERIC.MP) #14: Thu Jun 14 23:55:47 MDT 2018 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 17028538368 (16239MB) avail mem = 16372215808 (15613MB) mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: SMBIOS rev. 3.0 @ 0xc3202000 (89 entries) bios0: vendor American Megatrends Inc. version "3402" date 07/10/2017 bios0: ASUSTeK COMPUTER INC. Z170M-PLUS acpi0 at bios0: rev 2 acpi0: sleep states S0 S3 S4 S5 acpi0: tables DSDT FACP APIC FPDT BGRT MCFG SSDT FIDT SSDT SSDT HPET SSDT SSDT UEFI SSDT LPIT WSMT SSDT SSDT DBGP DBG2 acpi0: wakeup devices PEGP(S4) PEG0(S4) PEGP(S4) PEG1(S4) PEGP(S4) PEG2(S4) SIO1(S3) UAR1(S4) PXSX(S4) RP09(S4) PXSX(S4) RP10(S4) PXSX(S4) RP11(S4) PXSX(S4) RP12(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) Core(TM) i7-6700K CPU @ 4.00GHz, 4011.39 MHz cpu0: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,SGX,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,MPX,RDSEED,ADX,SMAP,CLFLUSHOPT,PT,SENSOR,ARAT,XSAVEOPT,XSAVEC,XGETBV1,XSAVES,MELTDOWN 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 23MHz cpu0: mwait min=64, max=64, C-substates=0.2.1.2.4.1, IBE cpu1 at mainbus0: apid 2 (application processor) cpu1: Intel(R) Core(TM) i7-6700K CPU @ 4.00GHz, 4009.90 MHz cpu1: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,SGX,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,MPX,RDSEED,ADX,SMAP,CLFLUSHOPT,PT,SENSOR,ARAT,XSAVEOPT,XSAVEC,XGETBV1,XSAVES,MELTDOWN cpu1: 256KB 64b/line 8-way L2 cache cpu1: smt 0, core 1, package 0 cpu2 at mainbus0: apid 4 (application processor) cpu2:
panic on resume in acpitz_setfan
>Synopsis: panic on resume in acpitz_setfan >Category: kernel >Environment: System : OpenBSD 6.1 Details : OpenBSD 6.1-current (GENERIC.MP) #1: Fri Aug 11 21:26:07 MDT 2017 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP Architecture: OpenBSD.amd64 Machine : amd64 >Description: The following panic happened immediately after a resume (the second since the machine was switched on) on the Aug 11th snapshot: uvm_fault(0x81b3ff8, 0x20003, 0, 1) -> e kernel: page fault trap, code=0 Stopped at acpitz_setfan+0x8c: movq 0(%rax), %rsi https://imagebin.ca/v/3Wmq884ayBSf This happened before the keyboard was reattached, so I couldn't get any further information from the panic. >How-To-Repeat: Unknown >Fix: Unknown dmesg: OpenBSD 6.1-current (GENERIC.MP) #1: Fri Aug 11 21:26:07 MDT 2017 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 17028448256 (16239MB) avail mem = 16506011648 (15741MB) mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: SMBIOS rev. 3.0 @ 0xc3202000 (89 entries) bios0: vendor American Megatrends Inc. version "3301" date 02/10/2017 bios0: ASUSTeK COMPUTER INC. Z170M-PLUS acpi0 at bios0: rev 2 acpi0: sleep states S0 S3 S4 S5 acpi0: tables DSDT FACP APIC FPDT BGRT MCFG SSDT FIDT SSDT SSDT HPET SSDT SSDT UEFI SSDT LPIT WSMT SSDT SSDT DBGP DBG2 acpi0: wakeup devices PEGP(S4) PEG0(S4) PEGP(S4) PEG1(S4) PEGP(S4) PEG2(S4) SIO1(S3) UAR1(S4) PS2K(S4) PS2M(S4) PXSX(S4) RP09(S4) PXSX(S4) RP10(S4) PXSX(S4) RP11(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) Core(TM) i7-6700K CPU @ 4.00GHz, 4008.00 MHz cpu0: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,SGX,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,MPX,RDSEED,ADX,SMAP,CLFLUSHOPT,PT,SENSOR,ARAT cpu0: 256KB 64b/line 8-way L2 cache cpu0: TSC frequency 400800 Hz cpu0: smt 0, core 0, package 0 mtrr: Pentium Pro MTRR support, 10 var ranges, 88 fixed ranges cpu0: apic clock running at 23MHz cpu0: mwait min=64, max=64, C-substates=0.2.1.2.4.1, IBE cpu1 at mainbus0: apid 2 (application processor) cpu1: Intel(R) Core(TM) i7-6700K CPU @ 4.00GHz, 4008.00 MHz cpu1: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,SGX,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,MPX,RDSEED,ADX,SMAP,CLFLUSHOPT,PT,SENSOR,ARAT cpu1: 256KB 64b/line 8-way L2 cache cpu1: smt 0, core 1, package 0 cpu2 at mainbus0: apid 4 (application processor) cpu2: Intel(R) Core(TM) i7-6700K CPU @ 4.00GHz, 4008.00 MHz cpu2: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,SGX,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,MPX,RDSEED,ADX,SMAP,CLFLUSHOPT,PT,SENSOR,ARAT cpu2: 256KB 64b/line 8-way L2 cache cpu2: smt 0, core 2, package 0 cpu3 at mainbus0: apid 6 (application processor) cpu3: Intel(R) Core(TM) i7-6700K CPU @ 4.00GHz, 4008.00 MHz cpu3: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,SGX,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,MPX,RDSEED,ADX,SMAP,CLFLUSHOPT,PT,SENSOR,ARAT cpu3: 256KB 64b/line 8-way L2 cache cpu3: smt 0, core 3, package 0 ioapic0 at mainbus0: apid 2 pa 0xfec0, version 20, 120 pins acpimcfg0 at acpi0 addr 0xf800, bus 0-63 acpihpet0 at acpi0: 2399 Hz acpiprt0 at acpi0: bus 0 (PCI0) acpiprt1 at acpi0: bus -1 (PEG0) acpiprt2 at acpi0: bus -1 (PEG1) acpiprt3 at acpi0: bus -1 (PEG2) acpiprt4 at acpi0: bus 4 (RP09) acpiprt5 at acpi0: bus -1 (RP10) acpiprt6 at acpi0: bus -1 (RP11) acpiprt7 at acpi0: bus -1 (RP12) acpiprt8 at acpi0: bus -1 (RP13) acpiprt9 at acpi0: bus 3 (RP01) acpiprt10 at acpi0: bus -1 (RP02) acpiprt11 at acpi0: bus -1 (RP03) acpiprt12 at acpi0: bus -1 (RP04) acpiprt13 at acpi0: bus -1 (RP05) acpiprt14 at acpi0: bus -1 (RP06)
iwm: could not add MAC context
>Synopsis: iwm: could not add MAC context >Category: kernel >Environment: System : OpenBSD 6.1 Details : OpenBSD 6.1-current (GENERIC.MP) #30: Mon Jul 31 22:48:24 MDT 2017 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP Architecture: OpenBSD.amd64 Machine : amd64 >Description: On the Jul 31st snapshot, iwm panics with heavy traffic on a WPA2 enterprise network. So far I haven't seen this on a non-WPA2 network. Screenshot of the panic: https://imagebin.ca/v/3VNEJhDM7fas In case it's useful (though I guess it isn't), here's the trace for the other CPUs: https://imagebin.ca/v/3VNEqn6y9s6N >How-To-Repeat: >Fix: dmesg: OpenBSD 6.1-current (GENERIC.MP) #30: Mon Jul 31 22:48:24 MDT 2017 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP RTC BIOS diagnostic error 80 real mem = 8238284800 (7856MB) avail mem = 7982264320 (7612MB) mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.7 @ 0xccbfd000 (66 entries) bios0: vendor LENOVO version "N14ET35W (1.13 )" date 04/07/2016 bios0: LENOVO 20BTS05Q00 acpi0 at bios0: rev 2 acpi0: sleep states S0 S3 S4 S5 acpi0: tables DSDT FACP ASF! HPET ECDT APIC MCFG SSDT SSDT SSDT SSDT SSDT SSDT SSDT SSDT SSDT PCCT SSDT UEFI MSDM BATB FPDT UEFI DMAR acpi0: wakeup devices LID_(S4) SLPB(S3) IGBE(S4) EXP2(S4) XHCI(S3) EHC1(S3) acpitimer0 at acpi0: 3579545 Hz, 24 bits acpihpet0 at acpi0: 14318179 Hz acpiec0 at acpi0 acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: Intel(R) Core(TM) i7-5600U CPU @ 2.60GHz, 2594.40 MHz cpu0: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,RDSEED,ADX,SMAP,PT,SENSOR,ARAT cpu0: 256KB 64b/line 8-way L2 cache cpu0: TSC frequency 2594401520 Hz 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 1 (application processor) cpu1: Intel(R) Core(TM) i7-5600U CPU @ 2.60GHz, 2593.99 MHz cpu1: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,RDSEED,ADX,SMAP,PT,SENSOR,ARAT cpu1: 256KB 64b/line 8-way L2 cache cpu1: smt 1, core 0, package 0 cpu2 at mainbus0: apid 2 (application processor) cpu2: Intel(R) Core(TM) i7-5600U CPU @ 2.60GHz, 2593.99 MHz cpu2: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,RDSEED,ADX,SMAP,PT,SENSOR,ARAT cpu2: 256KB 64b/line 8-way L2 cache cpu2: smt 0, core 1, package 0 cpu3 at mainbus0: apid 3 (application processor) cpu3: Intel(R) Core(TM) i7-5600U CPU @ 2.60GHz, 2593.99 MHz cpu3: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,RDSEED,ADX,SMAP,PT,SENSOR,ARAT cpu3: 256KB 64b/line 8-way L2 cache cpu3: smt 1, core 1, package 0 ioapic0 at mainbus0: apid 2 pa 0xfec0, version 20, 40 pins acpimcfg0 at acpi0 addr 0xf800, bus 0-63 acpiprt0 at acpi0: bus 0 (PCI0) acpiprt1 at acpi0: bus -1 (PEG_) acpiprt2 at acpi0: bus 3 (EXP1) acpiprt3 at acpi0: bus 4 (EXP2) acpiprt4 at acpi0: bus -1 (EXP3) acpiprt5 at acpi0: bus 10 (EXP6) acpicpu0 at acpi0: C3(200@233 mwait.1@0x40), C2(200@148 mwait.1@0x33), C1(1000@1 mwait.1), PSS acpicpu1 at acpi0: C3(200@233 mwait.1@0x40), C2(200@148 mwait.1@0x33), C1(1000@1 mwait.1), PSS acpicpu2 at acpi0: C3(200@233 mwait.1@0x40), C2(200@148 mwait.1@0x33), C1(1000@1 mwait.1), PSS acpicpu3 at acpi0: C3(200@233 mwait.1@0x40), C2(200@148 mwait.1@0x33), C1(1000@1 mwait.1), PSS acpipwrres0 at acpi0: PUBS, resource for XHCI, EHC1 acpipwrres1 at acpi0: NVP3, resource for PEG_ acpipwrres2 at acpi0: NVP2, resource for PEG_ acpitz0 at acpi0: critical
Re: Kernel panic (possibly inteldrm related)
On Thu, Jul 27, 2017 at 05:59:00PM +0200, Martin Pieuchot wrote: Hello Martin, > The only "leak" I'm seeing is the 'drmreq' pool. It grows until the > application is closed. Note that with my fix the allocated size for > 'drmreq' is divided by 4. So if that was the problem I might not be able > to reproduce it. I've been running with this commit (admittedly with slightly lighter than normal use) since yesterday evening and haven't experienced a crash yet, so I'm hopeful this has fixed it. Laurie -- Personal http://tratt.net/laurie/ Software Development Teamhttp://soft-dev.org/ https://github.com/ltratt http://twitter.com/laurencetratt
Re: Kernel panic (possibly inteldrm related)
On Sun, Jul 23, 2017 at 11:32:06PM +0100, Laurence Tratt wrote: > extsmaild (http://tratt.net/laurie/src/extsmail/) appears to be causing > the final panic, but given that it's just in a "wake every 60 seconds > and see if new files have appeared in a directory" loop, I'm not sure > why. I've now triggered another crash, this time without extsmaild (or Iridium) running. The trace is here: https://imagebin.ca/v/3UWOneXfuSWQ The "culprit" process is now mutt, but the panic is still "out of space in kmem_map" and the trace seems to be in ufs_readdir. Laurie -- Personal http://tratt.net/laurie/ Software Development Teamhttp://soft-dev.org/ https://github.com/ltratt http://twitter.com/laurencetratt
Kernel panic (possibly inteldrm related)
>Synopsis: Kernel panic (possibly inteldrm related) >Category: kernel >Environment: System : OpenBSD 6.1 Details : OpenBSD 6.1-current (GENERIC.MP) #0: Sun Jul 23 11:17:14 BST 2017 ltr...@phase.tratt.net:/usr/src/sys/arch/amd64/compile/GENERIC.MP Architecture: OpenBSD.amd64 Machine : amd64 >Description: Since the inteldrm update on both my desktop (a Skylake machine) and laptop (X1 Carbon 3rd gen) I have experienced random kernel panics. I've now had a ddb trace from both machines (both panic with "malloc: out of space in kmem_map"). The first ddb (from the desktop) is here (from a kernel a few days old; limited information as my keyboard didn't work at the ddb prompt): https://imagebin.ca/v/3UPGaXO2uK54 The second (from the laptop with snapshot from yesterday and a kernel built today) is here: https://imagebin.ca/v/3UPI4KUtloXi and then various output from ddb (tar file with several JPEGs inside): https://www.dropbox.com/s/xuhzpmftvz9vshj/ddb_output.tar?dl=0 extsmaild (http://tratt.net/laurie/src/extsmail/) appears to be causing the final panic, but given that it's just in a "wake every 60 seconds and see if new files have appeared in a directory" loop, I'm not sure why. I have also tried killing it, and still experienced at least 1 or 2 panics (albeit not ones that have ended up in ddb), so I suspect extsmaild is a symptom but not the cause. Interestingly, if I "boot -c" and "disable inteldrm" the panics go away on my desktop (I haven't yet tried this on my laptop). The dmesg below is from my laptop with a snapshot from yesterday and a kernel built today. >How-To-Repeat: Happens intermittently (generally within a hour of light-to-medium usage). >Fix: Unknown. dmesg: OpenBSD 6.1-current (GENERIC.MP) #0: Sun Jul 23 11:17:14 BST 2017 ltr...@phase.tratt.net:/usr/src/sys/arch/amd64/compile/GENERIC.MP RTC BIOS diagnostic error 80 real mem = 8238284800 (7856MB) avail mem = 7982817280 (7613MB) User Kernel Config UKC> quit Continuing... mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.7 @ 0xccbfd000 (66 entries) bios0: vendor LENOVO version "N14ET35W (1.13 )" date 04/07/2016 bios0: LENOVO 20BTS05Q00 acpi0 at bios0: rev 2 acpi0: sleep states S0 S3 S4 S5 acpi0: tables DSDT FACP ASF! HPET ECDT APIC MCFG SSDT SSDT SSDT SSDT SSDT SSDT SSDT SSDT SSDT PCCT SSDT UEFI MSDM BATB FPDT UEFI DMAR acpi0: wakeup devices LID_(S4) SLPB(S3) IGBE(S4) EXP2(S4) XHCI(S3) EHC1(S3) acpitimer0 at acpi0: 3579545 Hz, 24 bits acpihpet0 at acpi0: 14318179 Hz acpiec0 at acpi0 acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: Intel(R) Core(TM) i7-5600U CPU @ 2.60GHz, 2594.44 MHz cpu0: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,RDSEED,ADX,SMAP,PT,SENSOR,ARAT cpu0: 256KB 64b/line 8-way L2 cache cpu0: TSC frequency 2594442560 Hz 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 1 (application processor) cpu1: Intel(R) Core(TM) i7-5600U CPU @ 2.60GHz, 2594.00 MHz cpu1: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,RDSEED,ADX,SMAP,PT,SENSOR,ARAT cpu1: 256KB 64b/line 8-way L2 cache cpu1: smt 1, core 0, package 0 cpu2 at mainbus0: apid 2 (application processor) cpu2: Intel(R) Core(TM) i7-5600U CPU @ 2.60GHz, 2594.00 MHz cpu2: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,RDSEED,ADX,SMAP,PT,SENSOR,ARAT cpu2: 256KB 64b/line 8-way L2 cache cpu2: smt 0, core 1, package 0 cpu3 at mainbus0: apid 3 (application processor) cpu3: Intel(R) Core(TM) i7-5600U CPU @ 2.60GHz, 2594.00 MHz cpu3:
Re: Upgrading from already downloaded sets is broken?
On Tue, Oct 04, 2016 at 04:58:36PM -0600, Theo de Raadt wrote: Hello Theo, > anyways, rpe and I have discussed and figured out a solution that will > allow the old method to work. It is just unfortunate it takes so much > effort to maintain old strange methods for everyone. Thanks to Robert and yourself for taking the trouble on this one -- I for one really appreciate it. Laurie -- Personal http://tratt.net/laurie/ Software Development Teamhttp://soft-dev.org/ https://github.com/ltratt http://twitter.com/laurencetratt
Re: Upgrading from already downloaded sets is broken?
On Tue, Oct 04, 2016 at 01:13:42PM -0600, Theo de Raadt wrote: Hello Theo, >> However, if the new behaviour is preferred, it might be worth documenting >> it somewhere. > If this was mentioned in the INSTALL notes would you have seen it before > running into it? Go ahead, look at the document. Where in the document > should it be. Please make sure you point out a spot that you *WOULD HAVE > READ* before running into this. > > Then what, shall we document 50 things about the installer? Noone will > read it. We already know this file is rarely downloaded. Yes, like most others it seems, I can go years without checking INSTALL (after 17 years of using OpenBSD, it's easy to think that I know its content). I did however check the "following current" page on the website. I check that every so often (and whenever I hit a problem). [I often check the CVS list too, although in this case I looked for completely the wrong thing.] Laurie -- Personal http://tratt.net/laurie/ Software Development Teamhttp://soft-dev.org/ https://github.com/ltratt http://twitter.com/laurencetratt
Re: Upgrading from already downloaded sets is broken?
On Tue, Oct 04, 2016 at 06:23:24PM +, Robert Peichaer wrote: Hello Robert, Thanks for your quick reply! >> The last couple of snapshots seem to have changed the behaviour of >> upgrading. If when asked "Location of sets?" I select "disk", and type in >> an appropriate mounted location, the correct sets are presented to me. >> However, when I select "done" to install the sets, I get the following: > The installer script now uses the unpriv() wrapper to fetch the set files > as unprivileged user (see cvs log below). > Before, the root user was able to fetch the files no matter what the > ownership/permissions were. OK, so now I understand the message (/home/ltratt/tmp is drwx--). That said, the behaviour is maybe a little surprising, as I expect(ed) to be doing everything in the upgrader as root. It didn't even occur to me that an unprivileged user might be the culprit. My personal (biased :)) preference would be to maintain the original behaviour, as I suspect I won't be the only one caught out by this. However, if the new behaviour is preferred, it might be worth documenting it somewhere. I must admit that I don't know a sensible place to document it without becoming over-fussy though :/ Maybe a low-tech fix is to catch the "permission denied" message and substitute it for something like "User can't access ", at least for the next release while people are inducted into the new behaviour? That message might be a bit fiddly though... Laurie
Upgrading from already downloaded sets is broken?
>Synopsis: Upgrading from sets on a mounted disk no longer works >Environment: System : OpenBSD 6.0 Details : OpenBSD 6.0-current (GENERIC.MP) #2518: Sun Oct 2 21:41:07 MDT 2016 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP Architecture: OpenBSD.amd64 Machine : amd64 >Description: The last couple of snapshots seem to have changed the behaviour of upgrading. If when asked "Location of sets?" I select "disk", and type in an appropriate mounted location, the correct sets are presented to me. However, when I select "done" to install the sets, I get the following: ftp: Can't open file mnt/home/ltratt/tmp/bsd/SHA256.sig: Permission denied Cannot fetch SHA256.sig. Continue without verification? [no] The file(s) exist, and if I manually use ftp from the shell (with a file:/// URL), there is no permission problem at all. I assume, but don't know, that the install script is calling ftp incorrectly? >How-To-Repeat: Happens on two amd64 machines I have access to. >Fix: dmesg: OpenBSD 6.0-current (GENERIC.MP) #2518: Sun Oct 2 21:41:07 MDT 2016 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 17060859904 (16270MB) avail mem = 16539250688 (15773MB) mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: SMBIOS rev. 3.0 @ 0xc51d6000 (90 entries) bios0: vendor American Megatrends Inc. version "1805" date 06/20/2016 bios0: ASUSTeK COMPUTER INC. Z170M-PLUS acpi0 at bios0: rev 2 acpi0: sleep states S0 S3 S4 S5 acpi0: tables DSDT FACP APIC FPDT FIDT MCFG HPET SSDT LPIT SSDT SSDT SSDT SSDT DBGP DBG2 SSDT SSDT UEFI SSDT BGRT acpi0: wakeup devices PEGP(S4) PEG0(S4) PEGP(S4) PEG1(S4) PEGP(S4) PEG2(S4) UAR1(S4) PS2K(S3) PS2M(S3) PXSX(S4) RP09(S4) PXSX(S4) RP10(S4) PXSX(S4) RP11(S4) PXSX(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) Core(TM) i7-6700K CPU @ 4.00GHz, 4121.54 MHz cpu0: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,SGX,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,MPX,RDSEED,ADX,SMAP,CLFLUSHOPT,PT,SENSOR,ARAT 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 24MHz cpu0: mwait min=64, max=64, C-substates=0.2.1.2.4.1, IBE cpu1 at mainbus0: apid 2 (application processor) cpu1: Intel(R) Core(TM) i7-6700K CPU @ 4.00GHz, 4120.07 MHz cpu1: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,SGX,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,MPX,RDSEED,ADX,SMAP,CLFLUSHOPT,PT,SENSOR,ARAT cpu1: 256KB 64b/line 8-way L2 cache cpu1: smt 0, core 1, package 0 cpu2 at mainbus0: apid 4 (application processor) cpu2: Intel(R) Core(TM) i7-6700K CPU @ 4.00GHz, 4120.07 MHz cpu2: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,SGX,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,MPX,RDSEED,ADX,SMAP,CLFLUSHOPT,PT,SENSOR,ARAT cpu2: 256KB 64b/line 8-way L2 cache cpu2: smt 0, core 2, package 0 cpu3 at mainbus0: apid 6 (application processor) cpu3: Intel(R) Core(TM) i7-6700K CPU @ 4.00GHz, 4120.07 MHz cpu3: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,SGX,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,MPX,RDSEED,ADX,SMAP,CLFLUSHOPT,PT,SENSOR,ARAT cpu3: 256KB 64b/line 8-way L2 cache cpu3: smt 0, core 3, package 0 ioapic0 at mainbus0: apid 2 pa 0xfec0, version 20, 120 pins acpimcfg0 at acpi0 addr 0xf800, bus 0-63 acpihpet0 at acpi0: 2399 Hz acpiprt0 at acpi0: bus 0 (PCI0) acpiprt1 at acpi0: bus -1 (PEG0) acpiprt2 at acpi0: bus -1 (PEG1) acpiprt3 at acpi0: bus -1 (PEG2) acpiprt4 at acpi0: bus 4 (RP09) acpiprt5 at acpi0: bus -1 (RP10) acpiprt6 at acpi0: bus -1 (RP11) acpiprt7 at acpi0: bus -1 (RP12) acpiprt8 at acpi0: bus -1 (RP13) acpiprt9 at acpi0: bus 3 (RP01) acpiprt10 at acpi0: bus -1 (RP02)
drm panic
Hello, Yesterday, at the point that I did a mouse drag in gvim, my X session died, and I was dumped into the console with the following message appearing a split second later: error: [drm:pid29704:i915_reset] *ERROR* Failed to reset chip: -60 At that point, the machine was completely locked (keyboard didn't respond etc., so no ddb output) and I had to hard reboot. [Possibly relevant information: I had ZZZ'd this machine once before this happened, so the machine had come back after resuming from hibernation.] I'm not sure if the gvim connection is relevant or not. There is also an intermittent bug where gvim causes X to reset, but I've never seen it lock up the machine in this way before. Laurie dmesg: OpenBSD 5.9-beta (GENERIC.MP) #1864: Mon Jan 25 19:11:29 MST 2016 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 8476475392 (8083MB) avail mem = 8215384064 (7834MB) mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.7 @ 0xeb170 (52 entries) bios0: vendor Intel Corp. version "BLH6710H.86A.0160.2012.1204.1156" date 12/04/2012 bios0: TranquilPC IXL acpi0 at bios0: rev 2 acpi0: sleep states S0 S3 S4 S5 acpi0: tables DSDT FACP APIC SSDT MCFG HPET acpi0: wakeup devices PS2K(S3) PS2M(S3) UAR1(S3) P0P1(S4) P0P2(S4) P0P3(S4) P0P4(S4) GBE_(S4) BR20(S3) EUSB(S3) USBE(S3) PEX0(S4) BR21(S4) PEX1(S4) PEX2(S4) PEX3(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) Core(TM) i7-2600S CPU @ 2.80GHz, 2794.10 MHz cpu0: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,NXE,LONG,LAHF,PERF,ITSC,SENSOR,ARAT 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.1, IBE cpu1 at mainbus0: apid 2 (application processor) cpu1: Intel(R) Core(TM) i7-2600S CPU @ 2.80GHz, 2793.66 MHz cpu1: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,NXE,LONG,LAHF,PERF,ITSC,SENSOR,ARAT cpu1: 256KB 64b/line 8-way L2 cache cpu1: smt 0, core 1, package 0 cpu2 at mainbus0: apid 1 (application processor) cpu2: Intel(R) Core(TM) i7-2600S CPU @ 2.80GHz, 2793.66 MHz cpu2: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,NXE,LONG,LAHF,PERF,ITSC,SENSOR,ARAT cpu2: 256KB 64b/line 8-way L2 cache cpu2: smt 1, core 0, package 0 cpu3 at mainbus0: apid 3 (application processor) cpu3: Intel(R) Core(TM) i7-2600S CPU @ 2.80GHz, 2793.66 MHz cpu3: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,NXE,LONG,LAHF,PERF,ITSC,SENSOR,ARAT cpu3: 256KB 64b/line 8-way L2 cache cpu3: smt 1, core 1, package 0 ioapic0 at mainbus0: apid 0 pa 0xfec0, version 20, 24 pins acpimcfg0 at acpi0 addr 0xf800, bus 0-63 acpihpet0 at acpi0: 14318179 Hz acpiprt0 at acpi0: bus 0 (PCI0) acpiprt1 at acpi0: bus -1 (P0P1) acpiprt2 at acpi0: bus -1 (P0P2) acpiprt3 at acpi0: bus -1 (P0P3) acpiprt4 at acpi0: bus -1 (P0P4) acpiprt5 at acpi0: bus 1 (PEX0) acpiprt6 at acpi0: bus -1 (BR21) acpiprt7 at acpi0: bus 2 (PEX1) acpiprt8 at acpi0: bus -1 (PEX2) acpiprt9 at acpi0: bus -1 (PEX3) acpiprt10 at acpi0: bus -1 (PEX4) acpiprt11 at acpi0: bus -1 (PEX5) acpiprt12 at acpi0: bus -1 (PEX6) acpiprt13 at acpi0: bus -1 (PEX7) acpicpu0 at acpi0 0x800a4008 cnt:01 stk:00 package: 06 0x800a3a88 cnt:01 stk:00 integer: 6 0x8009fc08 cnt:01 stk:00 integer: 0 0x800a4d88 cnt:01 stk:00 integer: 0 0x800a4d08 cnt:01 stk:00 integer: fe 0x800a1508 cnt:01 stk:00 integer: 2 0x800a1308 cnt:01 stk:00 integer: 2 CSD r=0 d=0 c=fe n=2 i=2 : C3(350@104 mwait.3@0x20), C2(500@80 mwait.3@0x10), C1(1000@1 mwait.1), PSS acpicpu1 at acpi0 0x8009f188 cnt:01 stk:00 package: 06 0x8009f308 cnt:01 stk:00 integer: 6 0x800a1a08 cnt:01 stk:00 integer: 0 0x800a1e08 cnt:01 stk:00 integer: 0 0x800a1488 cnt:01 stk:00 integer: fe 0x8009f388 cnt:01 stk:00 integer: 2 0x800a4e08 cnt:01 stk:00 integer: 2 CSD r=0 d=0 c=fe n=2 i=2 : C3(350@104 mwait.3@0x20), C2(500@80 mwait.3@0x10), C1(1000@1 mwait.1), PSS acpicpu2
iwn wpaakms not being reset from 802.1x
Synopsis: synopsis of the problem (one line) wpaakms status on iwn0 doesn't seem to be reset Category: PR category (one line) Environment: System : OpenBSD 5.4 Details : OpenBSD 5.4-current (GENERIC.MP) #150: Thu Nov 14 00:30:57 MST 2013 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP Architecture: OpenBSD.amd64 Machine : amd64 Description: If, using my iwn adapter, I move from an 802.1x network (e.g. eduroam) to a PSK network, I seem unable to easily reset the wpaakms status. I have a reset script which does the following: sudo ifconfig iwn0 inet 0.0.0.0 sudo ifconfig iwn0 down sudo ifconfig iwn0 -bssid -chan media autoselect nwid -nwkey -wpa -wpakey sudo ifconfig iwn0 wpaakms psk After I've connected to an 802.1x network, and performed the reset, the adapter correctly responds to ifconfig iwn0 scan, but when I select a PSK network and do dhclient iwn0 it scans but never succeeds. No matter how many times I execute: sudo ifconfig iwn0 wpaakms psk afterwards, running dhclient iwn0 does not succeed. Weirdly, if I run that command while dhclient iwn0 is printing ... to stdout, dhclient is then able to get an address. I infer from this that somehow the wpaakms status is not being properly reset by the driver, though I may be mistaken as to the location of the issue. This has been happening for many months. How-To-Repeat: Fix: SENDBUG: Run sendbug as root if this is an ACPI report! SENDBUG: dmesg and usbdevs are attached. SENDBUG: Feel free to delete or use the -D flag if they contain sensitive information. dmesg: OpenBSD 5.4-current (GENERIC.MP) #150: Thu Nov 14 00:30:57 MST 2013 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 17041059840 (16251MB) avail mem = 16579293184 (15811MB) mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.6 @ 0xdae9c000 (64 entries) bios0: vendor LENOVO version 8DET68WW (1.38 ) date 04/11/2013 bios0: LENOVO 4287CTO acpi0 at bios0: rev 2 acpi0: sleep states S0 S3 S4 S5 acpi0: tables DSDT FACP SLIC SSDT SSDT SSDT HPET APIC MCFG ECDT ASF! TCPA SSDT SSDT UEFI UEFI UEFI acpi0: wakeup devices LID_(S3) SLPB(S3) IGBE(S4) EXP4(S4) EXP7(S4) EHC1(S3) EHC2(S3) HDEF(S4) acpitimer0 at acpi0: 3579545 Hz, 24 bits acpihpet0 at acpi0: 14318179 Hz acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: Intel(R) Core(TM) i5-2410M CPU @ 2.30GHz, 2292.87 MHz cpu0: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,NXE,LONG,LAHF,PERF,ITSC cpu0: 256KB 64b/line 8-way L2 cache cpu0: smt 0, core 0, package 0 cpu0: apic clock running at 99MHz cpu0: mwait min=64, max=64, C-substates=0.2.1.1.2, IBE cpu1 at mainbus0: apid 2 (application processor) cpu1: Intel(R) Core(TM) i5-2410M CPU @ 2.30GHz, 2292.56 MHz cpu1: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,NXE,LONG,LAHF,PERF,ITSC cpu1: 256KB 64b/line 8-way L2 cache cpu1: smt 0, core 1, package 0 ioapic0 at mainbus0: apid 2 pa 0xfec0, version 20, 24 pins acpimcfg0 at acpi0 addr 0xf800, bus 0-63 acpiec0 at acpi0 acpiprt0 at acpi0: bus 0 (PCI0) acpiprt1 at acpi0: bus -1 (PEG_) acpiprt2 at acpi0: bus 2 (EXP1) acpiprt3 at acpi0: bus 3 (EXP2) acpiprt4 at acpi0: bus 5 (EXP4) acpiprt5 at acpi0: bus 13 (EXP5) acpiprt6 at acpi0: bus -1 (EXP7) acpicpu0 at acpi0: C3, C1, PSS acpicpu1 at acpi0: C3, C1, PSS acpipwrres0 at acpi0: PUBS: resource for EHC1, EHC2 acpitz0 at acpi0: critical temperature is 99 degC acpibtn0 at acpi0: LID_ acpibtn1 at acpi0: SLPB acpibat0 at acpi0: BAT0 model 42T4861 serial 25468 type LION oem SANYO acpibat1 at acpi0: BAT1 not present acpiac0 at acpi0: AC unit online acpithinkpad0 at acpi0 acpidock0 at acpi0: GDCK not docked (0) cpu0: Enhanced SpeedStep 2292 MHz: speeds: 2301, 2300, 2000, 1800, 1600, 1400, 1200, 1000, 800 MHz pci0 at mainbus0 bus 0 pchb0 at pci0 dev 0 function 0 Intel Core 2G Host rev 0x09 vga1 at pci0 dev 2 function 0 Intel HD Graphics 3000 rev 0x09 intagp0 at vga1 agp0 at intagp0: aperture at 0xe000, size 0x1000 inteldrm0 at vga1 drm0 at inteldrm0 inteldrm0: 1366x768 wsdisplay0 at vga1 mux 1: console (std, vt100 emulation) wsdisplay0: screen 1-5 added (std, vt100 emulation) Intel 6 Series MEI rev 0x04 at pci0 dev 22 function 0 not configured em0 at pci0 dev 25 function 0 Intel 82579LM rev 0x04: msi, address f0:de:f1:a7:e4:89 ehci0 at pci0 dev 26 function 0 Intel 6 Series USB rev 0x04: apic 2 int 16 usb0 at ehci0: USB revision 2.0 uhub0 at usb0 Intel EHCI root hub rev 2.00/1.00 addr 1 azalia0 at pci0 dev 27 function 0 Intel 6 Series HD Audio
ahci timeout
Synopsis: ahci timesout Category: kernel Environment: System : OpenBSD 5.0 Details : OpenBSD 5.0-current (GENERIC.MP) #141: Fri Nov 25 00:16:26 MST 2011 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP Architecture: OpenBSD.amd64 Machine : amd64 Description: On occasions (roughly once a day), my machine effectively locks up, with none of the disks being available (often the machine appears to totally freeze; sometimes I get input/output error messagss if I e.g. do ls). All I can do is hard shutdown the machine, and wait for fsck to finish after switching the machine back on. On the few occasions I have been able to see console output I see this message: ahci0: stopping the port, softreset slot 31 was still active. ahci0: failed to reset port during timeout handling, disabling it I can't be 100% certain this happens every time (since I often can't switch from X to the console), but I've now seen this happen 6 or 7 times, so I'm semi-confident it's directly related to the freeze. How-To-Repeat: There appears to be no obvious trigger for these timeouts - they have occurred both under high and negligible load. Fix: dmesg: OpenBSD 5.0-current (GENERIC.MP) #141: Fri Nov 25 00:16:26 MST 2011 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 8492216320 (8098MB) avail mem = 8252018688 (7869MB) mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.7 @ 0xeb170 (52 entries) bios0: vendor Intel Corp. version BLH6710H.86A.0132.2011.1007.1505 date 10/07/2011 bios0: TranquilPC IXL acpi0 at bios0: rev 2 acpi0: sleep states S0 S3 S4 S5 acpi0: tables DSDT FACP APIC SSDT MCFG HPET acpi0: wakeup devices PS2K(S3) PS2M(S3) UAR1(S3) P0P1(S4) P0P2(S4) P0P3(S4) P0P4(S4) GBE_(S4) BR20(S3) EUSB(S3) USBE(S3) PEX0(S4) BR21(S4) PEX1(S4) PEX2(S4) PEX3(S4) PEX4(S4) PEX5(S4) PEX6(S4) PEX7(S4) SLPB(S0) PWRB(S3) 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) Core(TM) i7-2600S CPU @ 2.80GHz, 2794.04 MHz cpu0: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,SBF,SSE3,PCLMUL,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,SSE4.2,x2APIC,POPCNT,AES,XSAVE,AVX,NXE,LONG cpu0: 256KB 64b/line 8-way L2 cache cpu0: apic clock running at 99MHz cpu1 at mainbus0: apid 2 (application processor) cpu1: Intel(R) Core(TM) i7-2600S CPU @ 2.80GHz, 2793.66 MHz cpu1: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,SBF,SSE3,PCLMUL,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,SSE4.2,x2APIC,POPCNT,AES,XSAVE,AVX,NXE,LONG cpu1: 256KB 64b/line 8-way L2 cache ioapic0 at mainbus0: apid 0 pa 0xfec0, version 20, 24 pins acpimcfg0 at acpi0 addr 0xf800, bus 0-63 acpihpet0 at acpi0: 14318179 Hz acpiprt0 at acpi0: bus 0 (PCI0) acpiprt1 at acpi0: bus -1 (P0P1) acpiprt2 at acpi0: bus -1 (P0P2) acpiprt3 at acpi0: bus -1 (P0P3) acpiprt4 at acpi0: bus -1 (P0P4) acpiprt5 at acpi0: bus 1 (PEX0) acpiprt6 at acpi0: bus -1 (BR21) acpiprt7 at acpi0: bus 2 (PEX1) acpiprt8 at acpi0: bus -1 (PEX2) acpiprt9 at acpi0: bus -1 (PEX3) acpiprt10 at acpi0: bus -1 (PEX4) acpiprt11 at acpi0: bus -1 (PEX5) acpiprt12 at acpi0: bus -1 (PEX6) acpiprt13 at acpi0: bus -1 (PEX7) acpicpu0 at acpi0: C3, C2, C1, PSS acpicpu1 at acpi0: C3, C2, C1, PSS acpibtn0 at acpi0: SLPB acpibtn1 at acpi0: PWRB cpu0: Enhanced SpeedStep 2793 MHz: speeds: 2801, 2800, 2700, 2600, 2500, 2400, 2300, 2200, 2100, 2000, 1900, 1800, 1700, 1600 MHz pci0 at mainbus0 bus 0 pchb0 at pci0 dev 0 function 0 Intel Core 2G Host rev 0x09 vga1 at pci0 dev 2 function 0 Intel GT1 Video rev 0x09 wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation) wsdisplay0: screen 1-5 added (80x25, vt100 emulation) intagp0 at vga1 agp0 at intagp0: aperture at 0xe000, size 0x1000 inteldrm0 at vga1: apic 0 int 16 drm0 at inteldrm0 Intel 6 Series MEI rev 0x04 at pci0 dev 22 function 0 not configured em0 at pci0 dev 25 function 0 Intel 82579V rev 0x05: msi, address e0:69:95:2e:42:6d ehci0 at pci0 dev 26 function 0 Intel 6 Series USB rev 0x05: apic 0 int 16 usb0 at ehci0: USB revision 2.0 uhub0 at usb0 Intel EHCI root hub rev 2.00/1.00 addr 1 azalia0 at pci0 dev 27 function 0 Intel 6 Series HD Audio rev 0x05: msi azalia0: codecs: Realtek/0x0892, Intel/0x2805, using Realtek/0x0892 audio0 at azalia0 ppb0 at pci0 dev 28 function 0 Intel 6 Series PCIE rev 0xb5: msi pci1 at ppb0 bus 1 ppb1 at pci0 dev 28 function 1 Intel 6 Series PCIE rev 0xb5: msi pci2 at ppb1 bus 2 NEC xHCI rev 0x03 at pci2 dev 0 function 0 not configured ehci1 at pci0 dev 29 function 0 Intel 6 Series USB rev 0x05: apic 0 int 23 usb1 at ehci1: USB revision 2.0 uhub1 at usb1 Intel EHCI root hub rev 2.00/1.00 addr 1 pcib0 at
Re: kernel/6615: Latest snapshot not mounting root device
The following reply was made to PR kernel/6615; it has been noted by GNATS. From: Laurence Tratt lau...@tratt.net To: gn...@openbsd.org Cc: Joel Sing j...@sing.id.au Subject: Re: kernel/6615: Latest snapshot not mounting root device Date: Thu, 9 Jun 2011 17:32:09 +0100 Following a message on a related subject on misc@, I've now narrowed this problem down to v1.104 of ataascsi.c: http://www.openbsd.org/cgi-bin/cvsweb/src/sys/dev/ata/atascsi.c.diff?r1=1.103;r2=1.104 Reversing this patch (I had to do it by hand as the file's diverged too much for patch) causes my machine to boot again. Laurie
kernel/6491: amd64 kernel sometimes fails to boot on Thinkpad T410s
Number: 6491 Category: kernel Synopsis: amd64 kernel sometimes fails to boot on Thinkpad T410s Confidential: yes Severity: serious Priority: medium Responsible:bugs State: open Quarter: Keywords: Date-Required: Class: sw-bug Submitter-Id: unknown Arrival-Date: Fri Oct 15 19:40:01 GMT 2010 Closed-Date: Last-Modified: Originator: Release: Organization: Environment: System : OpenBSD 4.8 Details : OpenBSD 4.8-current (GENERIC.MP) #580: Thu Oct 14 09:34:09 MDT 2010 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP Architecture: OpenBSD.amd64 Machine : amd64 Description: Sometimes (perhaps 1/4 of the time) when I boot my T410s, it stalls during hardware detection, with the final line being: uhidev0 at uhub3 In other words, it seems to be probing uhub3, but not getting anywhere (the rest of the line that one would normally expect isn't printed). I've left this up to 15 minutes to see if there was a timeout issue, but it doesn't solve matters. How-To-Repeat: So far, this problem has only happened when I have rebooted the T410s from OpenBSD - it hasn't happened on a fresh boot. That may be coincidence though. Fix: The only solution I've found so far is to hard power off the machine and try booting again. So far it hasn't happened twice in a row. dmesg: OpenBSD 4.8-current (GENERIC.MP) #580: Thu Oct 14 09:34:09 MDT 2010 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 3138895872 (2993MB) avail mem = 3041480704 (2900MB) mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.6 @ 0xe0010 (78 entries) bios0: vendor LENOVO version 6UET53WW (1.33 ) date 09/02/2010 bios0: LENOVO 29123AG acpi0 at bios0: rev 2 acpi0: sleep states S0 S3 S4 S5 acpi0: tables DSDT FACP SSDT ECDT APIC MCFG HPET ASF! SLIC BOOT SSDT TCPA SSDT SSDT SSDT acpi0: wakeup devices LID_(S3) SLPB(S3) UART(S3) IGBE(S4) EXP1(S4) EXP2(S4) EXP3(S4) EXP4(S4) EXP5(S4) EHC1(S3) EHC2(S3) HDEF(S4) acpitimer0 at acpi0: 3579545 Hz, 24 bits acpiec0 at acpi0 acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: Intel(R) Core(TM) i5 CPU M 520 @ 2.40GHz, 2394.43 MHz cpu0: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,SBF,SSE3,PCLMUL,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,SSE4.2,POPCNT,AES,NXE,LONG cpu0: 256KB 64b/line 8-way L2 cache cpu0: apic clock running at 132MHz cpu1 at mainbus0: apid 4 (application processor) cpu1: Intel(R) Core(TM) i5 CPU M 520 @ 2.40GHz, 2394.00 MHz cpu1: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,SBF,SSE3,PCLMUL,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,SSE4.2,POPCNT,AES,NXE,LONG cpu1: 256KB 64b/line 8-way L2 cache ioapic0 at mainbus0: apid 1 pa 0xfec0, version 20, 24 pins acpihpet0 at acpi0: 14318179 Hz acpiprt0 at acpi0: bus 0 (PCI0) acpiprt1 at acpi0: bus -1 (PEG_) acpiprt2 at acpi0: bus 2 (EXP1) acpiprt3 at acpi0: bus 3 (EXP2) acpiprt4 at acpi0: bus -1 (EXP3) acpiprt5 at acpi0: bus 5 (EXP4) acpiprt6 at acpi0: bus -1 (EXP5) acpicpu0 at acpi0: C3, C1, PSS acpicpu1 at acpi0: C3, C1, PSS acpipwrres0 at acpi0: PUBS acpitz0 at acpi0: critical temperature 100 degC acpibtn0 at acpi0: LID_ acpibtn1 at acpi0: SLPB acpibat0 at acpi0: BAT0 model 42T4832 serial 30754 type LION oem SANYO acpibat1 at acpi0: BAT1 not present acpiac0 at acpi0: AC unit online acpithinkpad0 at acpi0 cpu0: Enhanced SpeedStep 2394 MHz: speeds: 2400, 2399, 2266, 2133, 1999, 1866, 1733, 1599, 1466, 1333, 1199 MHz pci0 at mainbus0 bus 0 pchb0 at pci0 dev 0 function 0 vendor Intel, unknown product 0x0044 rev 0x02 vga1 at pci0 dev 2 function 0 Intel Mobile HD graphics rev 0x02 wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation) wsdisplay0: screen 1-5 added (80x25, vt100 emulation) intagp0 at vga1 agp0 at intagp0: aperture at 0xd000, size 0x1000 inteldrm0 at vga1: apic 1 int 16 (irq 11) drm0 at inteldrm0 Intel 3400 MEI rev 0x06 at pci0 dev 22 function 0 not configured em0 at pci0 dev 25 function 0 Intel 82577LM rev 0x06: apic 1 int 20 (irq 11), address 00:26:2d:f9:45:58 ehci0 at pci0 dev 26 function 0 Intel 3400 USB rev 0x06: apic 1 int 23 (irq 11) usb0 at ehci0: USB revision 2.0 uhub0 at usb0 Intel EHCI root hub rev 2.00/1.00 addr 1 azalia0 at pci0 dev 27 function 0 Intel QS57 HD Audio rev 0x06: apic 1 int 17 (irq 11) azalia0: codecs: Conexant/0x5069, Intel/0x2804, using Conexant/0x5069 audio0 at azalia0 ppb0 at pci0 dev 28 function 0 Intel 3400 PCIE rev 0x06: apic 1 int 20 (irq 11) pci1 at ppb0 bus 2 ppb1 at pci0 dev 28 function 1 Intel 3400 PCIE rev 0x06: apic 1 int 21 (irq 11) pci2 at ppb1 bus 3 iwn0 at pci2 dev 0 function 0 Intel Centrino Ultimate-N 6300 rev 0x35: apic 1 int 17 (irq 11), MIMO 3T3R, MoW, address
