#asahi · 2022-02-19 22:43
jannautpw_rules: confirmed, PREEMPT_VOLUNTARY was selected#asahi · 2022-02-19 21:45
jannautpw_rules: I'm using gcc "Gentoo 10.3.0 p1", cross-compiled on x86_64#asahi · 2022-02-19 20:25
jannaupicture not necessary#asahi · 2022-02-19 20:25
jannauGlanzmann: not necessary, The messages I'm looking for are just printed to the serial console and not to the screen#asahi · 2022-02-19 20:22
jannauGlanzmann: does m1n1 print any usb-dwc3 messages when connected via usb-c#asahi · 2022-02-19 20:19
jannautpw_rules: yes, it halts completely. The rcu stall is supposed to print a backtrace but doesn't. sometime it halts without rcu stall message#asahi · 2022-02-19 19:53
jannauwhich usb port do you use on the mqc mini? type-a or type-c? is usb hotplug on the usb-c connectors working?#asahi · 2022-02-19 19:38
jannauthe rcu stalls print something after a while (more than 10 seconds)#asahi · 2022-02-19 19:37
jannauI don't think 12.0.1 iboot would be a problem#asahi · 2022-02-19 19:36
jannauI see occasionally rcu stalls or hangs during boot, testing with dcp so that could be the cause here#asahi · 2022-02-19 16:49
jannaurequires current m1n1 and kernel#asahi · 2022-02-19 16:48
jannautpw_rules: no, but you can use the dtbs from the kernel #asahi · 2022-02-19 16:44
jannaukcbench was 10% slower with 4k pages on my 10 core m1 max, doing 21-23 build per hour, so 2.5 to 3 minutes per build (iirc all cores at 2 Ghz)#asahi · 2022-02-19 13:06
jannaujust sent as part of v3 of "arm: apple: Switch to fully dynamic mem layout#asahi · 2022-02-19 13:06
jannaualready fixed locally#asahi · 2022-02-19 12:51
jannaumps: https://github.com/jannau/u-boot/commit/d77f1997ec8e6ac696e81e5ce790cdc61ab83ca3#asahi · 2022-02-18 19:33
jannauGlanzmann: just fixing a regression after changing the way how the bootloader allocated framebuffer is handled#asahi · 2022-02-15 21:20
jannautry cpupower -c 4 frequency-info#asahi · 2022-02-15 21:19
jannauM12destroyer21[m]: cpupower doesn't seem to handle big-little systems#asahi · 2022-02-15 21:00
jannauI pushed cpufreq dts changes for t8103#asahi · 2022-02-15 20:59
jannauunlikely#asahi · 2022-02-15 20:59
jannauI think there was one new option which was not enabled by default, probably POWER_RESET_MACSMC though#asahi · 2022-02-15 20:57
jannaudo you have CONFIG_MFD_SIMPLE_MFD_SPMI enabled?#asahi · 2022-02-15 20:50
jannaumissing reboot and rtc, strange#asahi · 2022-02-15 20:36
jannauGlanzmann: cpufreq dts update is missing for t8103 as well#asahi · 2022-02-15 20:32
jannauGlanzmann: anything smc related in dmesg? cpufreq is not working on my mini either. I didn't check before#asahi · 2022-02-15 20:26
jannaucan you test on the mac mini? how does it not work? it reboots?#asahi · 2022-02-15 20:23
jannaudts looks correct "/soc/spmi@23d0d9300/pmu@f/legacy_nvmem@9f00/panic-count@2: duplicate unit-address (also used in node /soc/spmi@23d0d9300/pmu@f/legacy_nvmem@9f00/boot-error-count@2)"#asahi · 2022-02-15 19:21
jannautested on a mac mini, I haven't checked if chnages for other m1 systems are required but I would not expect that#asahi · 2022-02-15 19:09
jannauhttps://github.com/jannau/linux/commits/spmi/work has t8103 dts with working rtc and poweroff + a fix for the cpufreq driver#asahi · 2022-02-14 21:45
jannauyou probably have remove the disabled cores from the cpu map. the numbers in live cpu map reference the phandle property in the cpu nodes#asahi · 2022-02-14 21:43
jannauI suspect you will end up with 3 cpu@1010x and 3 cpu@1020x nodes, i.e. 3 cores per cluster#asahi · 2022-02-14 21:39
jannau`dtc -I fs -O dts -o - /proc/device-tree` will output the device-tree as seen by linux#asahi · 2022-02-14 21:35
jannauaxboe: m1n1 has no code to fix up the cpufreq related nodes for disabled cores#asahi · 2022-02-14 21:33
jannauaxboe: I suspect the disabled cores on your break the association with clusters#asahi · 2022-02-14 21:27
jannauaxboe: looks ok here on system without disabled cpu cores#asahi · 2022-02-14 18:20
jannaukde/plasam/wayland is also mostly idle as long as there no screen updates#asahi · 2022-02-14 18:09
jannaushould improve when we get the proper drm driver in shape#asahi · 2022-02-14 18:08
jannauaxboe: my best guess is that blinking cursors or similar are rendered at 30 or 60 Hz with full frame buffer updates with simpledrm#asahi · 2022-02-13 18:01
jannauas400[m]: did you try sven's patch? still strange that you're the only one seing this#asahi · 2022-02-13 15:59
jannauit's based on chromium#asahi · 2022-02-13 15:55
jannauqtwebengine will probably have the same issue#asahi · 2022-02-13 14:40
jannauI haven't looked into it assuming it will be rewritten soonish. I need to work on keyboard/trackpad#asahi · 2022-02-13 14:38
jannauremoving the power-domains fixes a crash on t600x, to avoid the missed nvme interrupts all mcc related bits from the cpufreq dts change needs to be removed#asahi · 2022-02-13 12:38
jannaukov: I'm ignoring conflicts git mergetool --tool=kdiff3 can resolve automatically#asahi · 2022-02-13 12:29
jannauI fear that's a common theme. Let's hope I revived the stalled reserved/pre-mapped mem regions series#asahi · 2022-02-13 12:24
jannauit has conflicts in MAINTAINER and the common clk Kconfig (compared to asahi) but is otherwise fine#asahi · 2022-02-13 12:15
jannausven: "nvme-apple 393cc0000.nvme: I/O 32(aq:0) timeout: completion polled"#asahi · 2022-02-13 12:12
jannaukov: merge https://github.com/AsahiLinux/linux/tree/cpufreq/v1 on M1 you're done, on M1 Pro/Max you need https://pastebin.com/dHEMCCY5 the memory controller changes seem to cause nvme stability issues so I removed them from the dts#asahi · 2022-02-13 10:09
jannauyes, I think my random 2% number is probably way to high