#
…

2022-02-19

00:30boardwalk has quit [Quit: The Lounge - https://thelounge.chat]
00:31mrtoby[m] is now known as MrToby[m]
01:06yuyichao_ has quit [Ping timeout: 480 seconds]
02:00DragoonAethis has quit [Quit: hej-hej!]
02:00DragoonAethis has joined #asahi
02:20Emantor has quit [Quit: ZNC - http://znc.in]
02:20Emantor has joined #asahi
03:16yuyichao has joined #asahi
03:26PhilippvK has joined #asahi
03:29phiologe has quit [Ping timeout: 480 seconds]
03:48kov has quit [Quit: Coyote finally caught me]
03:51kov has joined #asahi
04:12axboe_ has quit [Quit: leaving]
04:47atka has quit [Ping timeout: 480 seconds]
05:28atka has joined #asahi
05:58Glanzmannkov: When you change anything in the partitioning through macos, the partition numbers will be ordered in the order they're on the disk. So if you use the debian installer or parted to create the paritions and later change something in macos (including reinstalling the stub) the partitions will be reordered.
05:59Glanzmannkov: However other than a new parition number won't happen. If you create the partitions for Linux using diskutil in macos the order will not change since it is alread in order.
06:00Glanzmannjmr2 / David[m]123456789: Or just open a shell in macos and type 'id'.
06:00GlanzmannBut i agree with jmr2, that is not your username.
06:38eroux has joined #asahi
06:43sirn- has joined #asahi
06:49GlanzmannI just had my first real power loss on the mini. Guess the electronic heater, electric kettle and coffee machine was a little bit to much for the fuse. No data loss. ;-)
06:49sirn has quit [Ping timeout: 480 seconds]
06:49sirn has joined #asahi
06:56sirn- has quit [Ping timeout: 480 seconds]
07:27rkjnsntpw_rules, if you use Firefox, I have found this extension to be eminently useful: https://addons.mozilla.org/firefox/addon/open-in-browser/
07:27willemml has joined #asahi
07:27rkjnsnIt lets you open any browser-supported file in the browser itself, regardless of the server-sent mime type or content disposition.
07:29rkjnsnGreat for quickly looking at PDF files that try to force you to download them, as well as viewing files that you know are plain text but the browser doesn't.
07:33Glanzmannrkjnsn: The 300-600 IOPS thingy is that with the new tree from axboe?
07:33GlanzmannI don't really care, because I'll work with the flush every second or minute mode.
07:34GlanzmannIf I had done more research earlier, I had used that for months by now.
07:34s1gtrap[m] has joined #asahi
07:34GlanzmannBut that is becase I use it mainly as a workstation, and I have all my data on remote systems, so I don't care if I loose a second. Also I have a battery ...
07:35eroux_ has joined #asahi
07:40eroux has quit [Ping timeout: 480 seconds]
07:42Misthios has quit [Quit: Ping timeout (120 seconds)]
07:42Misthios has joined #asahi
07:50rkjnsnThat was on macOS using F_BARRIERFSYNC instead of F_FULLFSYNC. If I understand correctly (which it sounds like maybe I don't…), whereas F_FULLFSYNC ensures the data is written to persistent storage F_BARRIERFSYNC, merely ensures that the data written before the sync hits persistent storage before data written after it, but it is still not guaranteed to be written when the call returns. My thinking was that if the underlying functionality used by
07:50rkjnsnF_BARRIERFSYNC was used for fsync instead of doing a flush, it could hopefully ensure that users of fsync would be guaranteed internal consistency of whatever made it to disk, even if there was the possibility for lost writes.
07:53Glanzmannmarcan: What is on your todo list before the first release?
07:54marcankernel tree cleanup, distro work, installer, maybe look at the SPMI driver a bit but it's not critical
07:55GlanzmannI see, nice.
07:58GlanzmannThanks to your rtc patch it is much more pleasent to install Debian, tested it yesterday with the latest spmi branch from jannau. Works pretty good.
08:02GlanzmannThe debian installer itself uses 'ntpdate' so that is not the issue, but once the fresh debian is installed, it had the wrong date and no ntpdate, so it was difficult to install new packages, but with the rtc that is now easy.
08:10sri has joined #asahi
08:21eroux_ has quit []
08:27willemml has quit [Quit: willemml]
08:58sri has quit [Quit: Leaving]
09:17psykose has quit [Remote host closed the connection]
09:18psykose has joined #asahi
10:27eroux has joined #asahi
10:44j`eyGlanzmann: if you missed it, the new asahi branch is out
10:53mpsbig diff in t8103.dtsi in current asahi branch and jannau's u-boot, but lets try
11:01mpsbooted on MBP, sound card is missing
11:02mpsapple-mca 238400000.mca: no tx0a DMA channel: 0
11:03Glanzmannj`ey: Thank you. I was afk, but I'll test it immediately.
11:22j`eyis scaling_cur_freq the right sysfs file to look at for current frequency?
11:24j`eyfrom that output, it does look like it scaled down to 600mhz
11:24j`eyI was surprised to see it at 600mhz locally, but if you've seen the same!
11:26Glanzmannj`ey: I always see it.
11:29povikmps: hmm
11:32povikmps: could you have disabled anything since last kernel build?
11:32povikare you running with t8103.dtsi from asahi branch?
11:34mpspovik: I'm booting with jannau's u-boot, I think I should sync DTS and build u-boot
11:34mpssorry for noise
11:34povikit's okay
11:35mpsI hope I'll finish this in 15-20 minutes
11:41Glanzmannpovik: No sound for me either. I'm using the old dtb.
11:41GlanzmannI install now the new dtb from the kernel and try again.
11:42povikyeah, don't try with old dt, that just won't work
11:42GlanzmannAlso something hangs for me on reboot, have to find out what though. Will report if I find it. It has something to do with the new kernel.
11:43mpspovik: yes, with syncing t8103.dtsi from kernel with u-boot audio card works, sorry again for false alarm
11:43povikgreat, np
11:44Glanzmannkettenis: Does this branch have the PCI for the mini for usb a ports?
11:44kettenisthat now has the DTs fully sunched with the asahi kernel branch
11:45Glanzmannj`ey: I tried power-off on the new asahi tree, it works on air.
11:47j`eyGlanzmann: cool, I realised it was SPMI it relied on (which I had left disabled for now)
11:48Glanzmannj`ey: Yep, that is what I spend a whole day on after marcan released rtc/reboot/power-off and janau did the missing device trees for t8103 devices.
11:48kettenisnote that now that the device trees are in sync, there is no downside of using the kernel DTs from the asahi kernel branch instead of the ones from u-boot
11:48Glanzmannkettenis: Perfect. My build scripts do it that way.
11:49kettenisfor that reason I didn't even bother adding the t600x DTs
11:50j`eycool poweroff working, with no change in size to the kernel, i guess it all fitted in some padding/alignment
12:05Glanzmannpovik: On the air I get 'https://pbot.rmdir.de/Le1TbtOudZPGvCodmhlW0g' when I start alsamixer. And alsamixer hangs.
12:07GlanzmannThis is with the device tree from the kernel and u-boot.
12:07j`eymarcan: just noticed from Glanzmann's dmesg "OF: Bad cell count for /soc/spmi@23d0d9300/pmu@f"
12:08povikGlanzmann: i will see if i can reproduce on the air you have set up for me
12:08mpsGlanzmann: also on MBP with kettenis's asahi u-boot branch sound card is not detected on boot, with dtbs from kernel and from u-boot
12:08povikmps: wait i thought it works for you
12:09Glanzmannpovik: Should I update the mini or leave it for the time being until the air works?
12:09mpspovik: it is detected with jannau's u-boot and dts copied from kernel there and rebuilt u-boot
12:10mpsand I overwrite this u-boot by mistake
12:11mpspovik: with kernel dtbs I got this `apple-mca 238400000.mca: bad or missing apple,mclk-range property`
12:11povikhmm? that means you are not running current asahi branch
12:11mpshm, uh
12:12mpslets reboot
12:14mpsI forgot to patch kettenis's u-boot to load compressed kernels
12:20mpspovik: now card is detected and alsamixer work but got this in dmesg with mpv playing audio https://tpaste.us/aZnN
12:20povikyeah, that's what Glanzmann sees too
12:21povikand no sound i presume?
12:22povikyou two will be running pulse, right?
12:22mpsno, I don't, plain alsa
12:22GlanzmannFor me pavucontrol and alsamixer nolonger start on air.
12:23GlanzmannI have pulse, it worked before.
12:25mpsfor me alsamixer works without issues
12:26poviki will look at this further in couple hours
12:26mpspovik: ok, no hurry (at least for me)
12:26GlanzmannBut alsamixer seems to try to connect to pulse: https://pbot.rmdir.de/qpevWGeqzyj2QFZiWhKkpg
12:27mpsI can always plug in usb audio card
12:49mpskettenis: jannau posted patch which enable loading compressed kernel by u-boot but I can't find url now
12:50mpsdoes it makes sense to add it to current u-boot asahi branch
12:54mpsjannau: that one, thanks
13:02kettenisI might pick that up if it gets submitted upstream
13:03kettenisstatus |= env_set_hex("kernel_comp_size", base + SZ_128M);
13:04kettenisthat doesn't make sense to me; shouldn't that be just SZ_128M?
13:04mpshm, right
13:06jannaualready fixed locally
13:06mpsI mean, your comment looks right
13:06jannaujust sent as part of v3 of "arm: apple: Switch to fully dynamic mem layout
13:35___nick___ has joined #asahi
13:37eroux has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
13:37___nick___ has quit []
13:39___nick___ has joined #asahi
13:40___nick___ has quit []
13:42___nick___ has joined #asahi
13:50kettenishmm, for some reason git am refused to apple that without the -3 option
13:50ketteniss/apple/apply/
13:50kettenisbut I've forced pushed the asahi branch with that included
14:11marcanj`ey: the bad cell count thing is "expected"
14:11marcanit doesn't break anything
14:11marcanbut yeah, I should propose something to fix that
14:13j`eymarcan: oh ok, I thought it was something wrong in the dts itself
14:13marcanit's trying to translate through an untranslatable boundary because stupid legacy broken dts reasons, or something
14:14marcanbut I need to poke robher about this story (hi :))
14:35joerg has joined #asahi
14:35joerg is now known as Guest293
14:36Guest293 has quit []
14:39tpw_ruleskettenis: do you need/plan to resync the device trees into your u-boot branch?
14:40tpw_rulesoh i see there is a new asahi branch. i guess that replaces the m1-m1n1-nvme branch?
14:40joerg1 has joined #asahi
14:41Glanzmannsound has issues on air and pro
14:42mpstpw_rules: u-boot from kettenis's asahi branch works now with dtb's from kernel
14:43joerg1 has quit []
14:43mpsand as Glanzmann pointed sound have issue but hope it will be fixed soon
15:11povikhmm, so far i can't reproduce the errors you get
15:11povikbut i am only doing doing speaker-test
15:12mpspovik: I noticed warning during kernel build about dma
15:13mpswarnings*
15:13mpswill build redirecting build log for file and post
15:14mpsspeaker-test also fails in my test
15:15povikmaybe i should start developing with WERROR
15:16mpsI have `# CONFIG_WERROR is not set` but still see this about dma and sound
15:17povikWERROR will make it refuse build with warnings
15:17povikso i would fix them right away
15:18axboe has joined #asahi
15:27mpspovik: build log is here http://ix.io/3Q3U
15:30povikthe mca warnings are the ones marcan ran into, but i don't see anything about dma
15:30povikatleast not about apple-admac
15:32mpsdev_err(&pdev->dev, "no %s DMA channel: %d\n"
15:32mps`sound/soc/apple/mca.c:951:41: note: in expansion of macro 'dev_err'` `dev_err(&pdev->dev, "no %s DMA channel: %d\n",`
15:33axboejust ran into that too when rebasing
15:33povikah right, those mention dma, i thought there were some outside of the mca driver
15:33povikokay i repent :-p
15:35* axboefixes and marches on
15:35axboetime to update this sucker!
15:35axboepovik: t600x support for audio yet, or is it still just t8x?
15:36povikt8x only at this point, the soc parts are the same but the codecs are different
15:37j`eyaxboe: good excuse not to join meetings!
15:37j`eyno audio, no mic, no cam
15:37axboej`ey: hah
15:37axboeI never do meetings on the laptop, need a bigger screen
15:38mpsj`ey: usb dongles ;)
15:38axboebrb, time to reboot into new kernel
15:38axboe has quit [Quit: leaving]
15:40axboe has joined #asahi
15:41axboedone, works for me
15:41axboeand drastically shrunk my on-top patch pile
15:42j`eyaxboe: we're still 18k lines on top of mainline though
15:43axboej`ey: yeah I know, just talking about the feature patches and fixes I stacked on top of 'asahi'
15:44axboelittle victories
15:45j`eyI heard that some vendor linux's have diffs of hundreds and thousands of lines
15:46axboe18k isn't much, still doesn't mean it won't take some time to flush it out
15:46axboethose vendors never target upstream, so they don't really care how they drift
15:47axboeand they often just abandon the tree once the product is shipped, it's not a long term maintained thing :/
15:47j`eyand how 'badly' they mangle stuff
15:47axboeyou need an eye wash station closeby for a lot of those, if you look at the changes/code
15:47axboevery different scenario from asahi, thankfully
15:48axboefwiw, I tested 16k vs 4k page size for my compilation test
15:48axboeand 4k is about 7% slower for me
15:49axboewould be nifty with some page cache stats that show you how much space you're wasting there with 16k pages
15:50axboethough I probably personally save more by just using FF instead of chromium than I waste in the page cache ;)
16:02grgy has quit [Quit: ZNC 1.8.2 - https://znc.in]
16:03grgy has joined #asahi
16:11poviki can't reproduce the sound errors
16:11povikthat's both on mini and the air
16:12povikand with speaker-test or mpv
16:12poviki am not running any desktop environment though
16:14mpspovik: as root run `speaker-test` and got https://tpaste.us/KMjB
16:14mpsno pulseaudio, pipeware or jack
16:15povikyeah, that's in line with the dmesg i saw
16:15povikas if a capture stream in parallel was holding the clocks
16:15povikbut i assume you are not doing any recording in background?
16:15povik(and even then, it should work, just limited to the same samplerate)
16:17povikbool clocks_in_use[SNDRV_PCM_STREAM_LAST];
16:17povikshould probably be STREAM_LAST+1
16:20axboepovik: man, that's a counter intuitive way to define LAST
16:20axboeidiomatic way is usually to have FOO_NR, where FOO_NR is indeed last-valid + 1
16:20axboewould also clean up those weird <= loops
16:21axboe(not your fault, looks like an alsa oddity)
16:26tpw_rulesaxboe: you have an m1 pro though don't you? and what are you compiling?
16:27axboetpw_rules: yep pro with 6 p cores, just compiling my for-next release kernel that I use in qemu for local testing
16:28tpw_rulesoh, huh. i got about 25% slower on the regular m1 mini. but for some reason once or twice it was only 10% slower
16:29axboetpw_rules: that's huge - since my compile is not that big, linking is probably skewing the numbers on my side in terms of raw compile speed differences
16:29tpw_rulesyeah, mine was for a full distro kernel type build. 20 vs 25 mins
16:30kettenispovik: we still nedd a way to express the speaker layout on the laptops in the device tree
16:32mpsalso I have slowdown about 20-25% when building kernel, but on some other things it as around 10%
16:33axboeI'll try a bigger compile, but that just makes the 16k page size even more compelling
16:33tpw_rulesyeah it really is
16:34axboemps: what's the baseline time for the kernel build you are doing?
16:34axboemine is small enough that it's around 85s for the whole thing
16:34tpw_rules(also it still takes nixos's infrastructure >1hr to compile)
16:34mpsaxboe: I have enabled a lot of drivers as modules
16:35mpson 16K it builds in about 4 minutes and few seconds, and on 4K it is about 6 minutes
16:36tpw_ruleskettenis: does your u-boot asahi branch have all the same stuff as the old m1-m1n1-nvme one?
16:36mpsthat is on earlier kernels, without your flush patch
16:36tpw_rulesi did my builds in a tmpfs fwiw
16:37axboemps: massive difference indeed
16:39kettenistpw_rules: no, pcie support is missing
16:39tpw_rulesso nvme will not work?
16:40kettenisnvme will work
16:40kettenisthe type-A ports on the mini will no longer work
16:44jannaukcbench 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)
16:45axboetiming allmodconfig, let's see how big of a difference it is here with all the crap enabled
16:46tpw_ruleshow is t600x support?
16:46tpw_rulesare there device trees for that in u-boot now?
16:48kettenist600x works; just use the asahi linux device trees now
16:48Glanzmannpovik: Should I reboot?
16:48jannautpw_rules: no, but you can use the dtbs from the kernel
16:49jannaurequires current m1n1 and kernel
16:49tpw_ruleshm ok, i'm not quite set up to do that yet
16:50Glanzmannjannau / j`ey / marcan: If you have a air hooked up to the mini, is it possible to issue reset using some magic thing?
16:50tpw_rulesGlanzmann: you can type `reboot` into the hypervisor console
16:50Glanzmannpovik: I don't know if you do, but you could run the kernel in the hypervisor, than you can reboot without my help.
16:55myon98 has quit [Ping timeout: 480 seconds]
16:56povikkettenis: i guess we do. i am closing in on bringing the laptop speakers up
16:56poviki don't know how alsa knows which channel is which when #channels > 2
16:57povikbut that actually isn't relevant here, is it :)
16:59svenyou can also use macvdmtool
17:00svenor write patches for the tps code to be able to issue the magic USB PD commands from Linux
17:00povikmacvdmtool is macos only, right?
17:00kettenispovik: my understanding that the canonical order is left right
17:01svenyes, but it shouldn’t be too hard to add support to the tipd driver in the kernel
17:01povikmine too :)
17:01svenmacvdmtool essentially accesses some of the registers
17:01svenyou just need to do that from linux
17:02svenThe harder part is figuring out how to do that in a sane way so that it can be upstreamed ;)
17:02povikkettenis: left right, but beyond that point i don't know
17:02povikbtw i can't bring up the laptop speakers with simple-audio-card or audio-graph-card as they are
17:02povikthe linux drivers are limited and the bindings are limiting too, i think
17:03povikso my plan is to do something with compatible="apple,macaudio"
17:03povikand post that as an RFC
17:03povikif there is special compatible for the mac's audio cards, then the order of speakers can be fixed i guess
17:04povikmeaning for a given amount of speakers, a specific layout is assumed and the speakers are placed in the layout based on their order in some sound-dai= list
17:05kettenisto me, the right approach would be to actually add a label to the tas5770l codecs to indicate their position
17:06povikinteresting, to me the right approach is to keep that with the sound card, not the codec
17:06povikbecause the codec driver doesn't care
17:06povikbut on the other hand the devicetrees are supposed to describe hardware, not drivers, i guess
17:07ketteniswell, I think or OpenBSD I would like to use the stereo downmix capability of the tas5770l
17:07poviki would assume there's some prior art on this
17:07kettenisstranegly it seems there isn't
17:08kettenisand even if the codec itself wouldn't look at it, the higher level stuff could
17:13poviki should do the RFC for other reasons beyond the binding, and doing it with the fixed speaker order initially is easiest
17:13povikso i propose i go ahead with it and we discuss the binding on the list
17:14poviksounds good?
17:14kettenisjust make sure you CC me as I'm not on any of the linux audio lists
17:15povikthat goes without saying
17:23Glanzmannsven: I see (about macvdmtool). I thought there was also a tool for Linux.
17:24svennot for two connected m1s
17:26tpw_rulesman i just have some kind of talent for finding u-boot and keyboard problems
17:28Glanzmanntpw_rules: I also have some keychron keyboard which does not work with u-boot.
17:28tpw_rulesthat sounds fancy and gamey?
17:29Glanzmanntpw_rules: I was looking for a clicky keyboard that is low. That is why I bought it and I like it.
17:29povikmps, Glanzmann: likely fix of audio: https://tpaste.us/DXyl
17:29povikstill i don't know why it doesn't manifest for me
17:29povikcould gcc and clang be laying out structures in memory differently?
17:29GlanzmannBut I also have some thinkpad usb keyboards with trackpoint I also like them a lot mainly due to the trackpoint.
17:29tpw_rulesGlanzmann: sorry, that wasn't a criticism. a lot of those fancy gaming keyboards use a different usb protocol. does it have a "bios mode" or something?
17:29povikthere's a bool array if that matters
17:32Glanzmannpovik: I see, here also some errors that should be fixed, but I think axboe already has a patch in his tree. https://pbot.rmdir.de/xcBEAa8KhcIkOJ0deCDnpw
17:33mpspovik: building
17:34mpscould we now build mca as module, would be easier to debug
17:34povikno, thanks for reminding to put that on my TODO
17:34Glanzmannpovik: Sound works. Tested on the other air.
17:43mpspovik: it works on MBP
17:45povikso that's that
17:46povikboth defects due to me building with clang
17:46kovGlanzmann, I have the same problem with the same product (bought for the same reason)
17:46poviki would switch but i am developing on macos for the time being
17:47j`eypovik: youre building the kernel on macos?
17:47j`eyI thought that wasnt supported
17:47povikit's not but it works well
17:47povikas long as you patch one of the in-tree tools
17:49Glanzmannkov: About the keychron. I'm using this settings, so that all the keys are where they belong: https://pbot.rmdir.de/3jMZHZgHUvFC6KKu2U5neQ
17:50kovGlanzmann, same - I do that for the air keyboard as well
17:51Glanzmannkov: Me, too. But what I did not manage at the moment on the air is that I can switch option and command key and at the same time to be able to type german umlauts by doing right alt + a u ...
17:52tpw_ruleswhat was the other sound patch?
17:52GlanzmannIf you ever figure out how to do that, let me know.
17:52poviktpw_rules: it's the warnings
17:52Glanzmanntpw_rules: Pasting in a second.
17:52tpw_rulesthank you both!
17:53Glanzmanntpw_rules: pushed the m1-debian repository.
17:54kovGlanzmann, hmm how did you switch command and option? I used gnome's tweak tool to selected that 'alt and win are swapped' option and I seem to be able to use the right-side option key for the special characters option + s => ß
17:54GlanzmannNo comes the hard part and talk marcan and to pulling them into linux-next. :-)
17:54kov(I use the us intl with dead keys layout)
17:54Glanzmannkov: I see, I purely use xorg config, since I'm running fvwm2.
17:54Glanzmannkov: All my keyboards are also us intl since 20 years.
17:55kovI wonder how tweak does it, I suppose it's libinput settings, but I know very little about this (more than I wanted to know already)
17:58kovhmm looks like it sets dconf keys, so need to look into gnome settings daemon probably https://github.com/GNOME/gnome-tweaks/blob/1aa39325396754476061f58ac3f3dc84a49bea0c/gtweak/tweaks/tweak_group_xkb.py#L137
17:59tpw_ruleskov: do you have the link to your webkitgtk patch handy?
18:01Glanzmanntpw_rules: In the debian repository under doc/notes.txt as well.
18:01mpskov: that is what I do https://tpaste.us/7V91
18:02Glanzmannmps: I should always ask you, we have such a similiar setup. :-)
18:02mpsFn is control and control is fn
18:02mpsGlanzmann: I had this similarly on an old intel macbook
18:03kovmps, hah nice, I didn't know there was an option to switch fn and control
18:04tpw_ruleskov: so that patch was applied, but the people at the bottom had criticisms?
18:04tpw_rulesftr i strongly disagree with Zan Dobersek there.
18:04kovand having opt/command as parameters to the module will be much better than using the tweaks trick ;D
18:05kovtpw_rules, yes! it's been applied and in theory has already been pulled into the stable branch as well
18:06mpsI use this setup with awesome wm, and I have two left-alt keys, lazy to assign one of them for something useful :)
18:06kovtpw_rules, yeah, I'm writing a comment about that idea of building specifically for M1, let me know if you want me to relay anything
18:07tpw_ruleskov: i mean basically i want to relay that the idea of having default binaries that break on M1 makes me sad. if you want to have a tweak to set it back to 4k if you want max performance or whatever and are building it yourself, then i suppose that's okay
18:08kovtpw_rules, yeah
18:08kovtpw_rules, I'm basically saying that it's more common to do custom builds for the embedded platforms than for m1
18:08poviklinux seems very unhappy if i hook up macbook's magsafe to one of the usb-c ports on mini
18:08povik> [ 18.252168] usb usb4: We don't know the algorithms for LPM for this host, disabling LPM.
18:08povikthat's on the mini side
18:09povikit repeats with a couple second period
18:09kovtpw_rules, looks like it did
18:09kovlet me check the code
18:10kovmcantarazzo works on fedora, probably did that for centos kernels
18:10tpw_ruleswhat was that deal about a 64KB page size crashing though?
18:10kovit went in, then out:
18:10kovkov@morango ~/P/WebKit (16k)> git grep PAGE_BLOCK Source/
18:10kovSource/WTF/ChangeLog: Remove USE_64KB_PAGE_BLOCK
18:10kovSource/WTF/ChangeLog-2021-03-18: Add new build option USE(64KB_PAGE_BLOCK)
18:10kovkov@morango ~/P/WebKit (16k)>
18:11tpw_rulesany cite as to why it left?
18:13tpw_rulesdoes the changelog say anything?
18:16svenpovik: that message is normal once, but not every few seconds
18:19Glanzmannsven: Do you know why axboe set the admin queue to 2 instead of 8?
18:19svenalmost all commands go through the io queue, no need to waste that space for the admin queue
18:20poviksven: here's a log snip if you want to look: https://tpaste.us/1Ere
18:21povikaround 498.092460 is when i plugged it in
18:21svenlooks like the cable is constantly reconnected for some reason
18:21kovtpw_rules, basically because they no longer needed it for RHEL and users were seeing it and enabling it without understanding what they were doing heh https://bugs.webkit.org/show_bug.cgi?id=227905
18:21kovin the end the change stuck, there was a fix for the crash
18:21povikthe other side is running macos, maybe it's trying to achieve something there
18:21Glanzmannsven: I see, thanks.
18:22tpw_ruleskov: isn't that ever the case...
18:22svenohh… maybe it’s trying to negotiate a thunderbolt connection?
18:22svenand then things go horribly wrong
18:22kovI haven't looked in detail on the reason for the crash but from their talking about bmalloc I'm wondering if it's related to some kind of alignment requirements
18:23svenerr… wait, the macOS side is connected to MagSafe?
18:23povikbut it's magsafe, i don't expect that to be able to carry thunderbolt
18:24svenyou can try to enable the tps trace points
18:24svenbut I kinda expect that you’ll just see a lot of “plug status changed” events
18:24povikthat's some file in /sys? or kernel recompile?
18:25svenI’ve always enabled them with bootargs because I usually don’t have any userland but I believe it’s also possible to enable them in sys
18:26kovtpw_rules, k, comment added
18:27poviksven: do i limit it to tps somehow or what should i do?
18:28povikif it's too involved we can drop it
18:28svendunno :D
18:28sveni always just enabled it for tps
18:28tpw_rulesGlanzmann: have you tried your new kernel config on the mini?
18:28tpw_rulesmy usb-c ports aren't working anymore
18:31GlanzmannI have not, because povik is using my mine and my wifes air to develop speaker support. But he is not logged in, so let me try.
18:37GlanzmannWorks for me
18:38tpw_rulesdo your usb-c ports work?
18:38Glanzmannhot plu also work.
18:38GlanzmannI tried both.
18:38Glanzmanntpw_rules: Forgot to use the new device tree?
18:38tpw_rulesmaybe i need to try jannau's u-boot
18:40Glanzmanntpw_rules: So I did replug my keyboard between usb-a and usb-c and typped a few characters to verify that it works.
18:41Glanzmanntpw_rules: This is with what is currently in bootstrap.sh I rebuild it with the latest sound and kernel warning patch. Also u-boot is coming from that (with the device tree from the kernel).
18:42tpw_rulesallegedly u-boot is using the same device trees as the kernel but maybe that is not the case
18:42Glanzmannpovik: Sound also works on the mini through the speakers. Now my daughter asks for her song ...
18:43kovtpw_rules, I'm doing some more reading on libpas (the bmalloc replacement, impressive how much work went in since I was active =P) and it seems to use 16k as the smaller page size it cares about, I guess it's no surprise Apple has basically started using 16k as *the* page size ;P
18:43povikyeah, i don't know enough about ftrace to do something useful with it
18:44poviksome other day...
18:44povikGlanzmann: well i hope you are putting the drivers to use then!
18:45GlanzmannOf course, small dance session here.
18:50tpw_rulesthis whole m1n1 and u-boot owning the device tree still really bothers me
18:52Glanzmannhrhr. Wait for m1n1 chainload support.
18:52j`eythink of the dtb like part of the firmware then :P
18:52willemml has joined #asahi
18:53tpw_rulesit's not firm enough yet though
18:58tpw_ruleshm, now my config boots okay but i get this strange "unexpected GFP" kernel warning: http://ix.io/3Q5e
18:59j`eyits on top of -next.. so possibly some new issue there
18:59tpw_rulesalso poweroff does not quite work, it hangs for like 5 seconds then resets
19:00j`eydo you have all the SPMI/NVMEM configs?
19:00Glanzmanntpw_rules: poweroff works for me
19:00tpw_rulesi didn't change my config at all, i thought it wouldn't be necessary because all the new stuff is default ARCH_APPLE
19:01j`eynot SPMI_APPLE
19:02tpw_rulesoh, i missed that one
19:02j`eymarcan: ^
19:03Glanzmanneveryone does the question is only how long you search for it. I searched long ...
19:14tpw_rulesgrr, something is unstable. i keep having random hangs and reboots. i assume there is a watchdog cause i don't see a kernel panic
19:16Glanzmanntpw_rules: Okay, I have no issues on the air other from sound and that is fixed.
19:16Glanzmanntpw_rules: Feel free to try my build artefacts.
19:16GlanzmannAnd see if the problem persists.
19:19Glanzmanntpw_rules: I'm streesing the mini by building Debian ...
19:20tpw_rulesso far it's only happened during boot
19:20tpw_rulesi wonder if it's related to that iso driver that's giving that gfp warning
19:22willemml has quit [Quit: willemml]
19:23sri has joined #asahi
19:24tpw_rulesso m1.tgz is your rootfs?
19:26tpw_rulesalso worth noting my stub is still 12.0.1
19:36jannauI see occasionally rcu stalls or hangs during boot, testing with dcp so that could be the cause here
19:37tpw_ruleswould that print something?
19:37tpw_rulesi just see a normal boot sequence, except it stops at some random point and 10 seconds later the machine resets
19:37jannauI don't think 12.0.1 iboot would be a problem
19:38jannauthe rcu stalls print something after a while (more than 10 seconds)
19:38kettenisso with the new u-boot you have to have the kernel driver for the WDT
19:39Glanzmanntpw_rules: yes
19:39tpw_rulesi have that
19:48Glanzmannsven: After upgrading the kernel, the mini does no longer detect the m1n1 proxy on the air, any ideas?
19:51sri has quit [Ping timeout: 480 seconds]
19:52sri has joined #asahi
19:53jannauwhich usb port do you use on the mqc mini? type-a or type-c? is usb hotplug on the usb-c connectors working?
19:55tpw_rulesmarcan: can you give some thought to m1n1 issue 159? that fixes a big problem for me
19:56tpw_rulesand yeah i just checked, i think the watchdog is working as designed. unfortunately
19:56tpw_rulesi'll turn it off and see if it eventually complains about something
19:57Glanzmannjannau: type-c with a superspeed cable.
19:57Glanzmannjannau: Yes, usb hotplug is working, tested with a usb keyboard.
19:58GlanzmannI'm currently downgrading so that povik can continue.
19:59bps has quit [Ping timeout: 480 seconds]
20:01willemml has joined #asahi
20:03le0n has quit [Quit: see you later, alligator]
20:03willemml has quit []
20:03GlanzmannDowngrading did not solve the issue
20:03le0n has joined #asahi
20:05GlanzmannSo the superspeed cable worked before, whole day. Now it does not.
20:05GlanzmannNow I used a usb-c to usb-a cable that came with google tv ...
20:05GlanzmannAnd that seems to work.
20:06GlanzmannNo idea what this is about. The superspeed cable came with an eizo monitor to use it as hdmi-over-usb-c cable and to my knowledge I did not replug or tocuh it.
20:07bps has joined #asahi
20:10boardwalk has joined #asahi
20:13tpw_rulesjannau: does the system halt completely when you get these stalls?
20:17svenand the usb curse strikes again!
20:17tpw_rulessven: is this related to what you were investigating? i just got an rcu stall message before the watchdog bit me
20:17Glanzmannsven: Is what I saw a usb curse?
20:17svenis there anything in dmesg with the broken cable?
20:18svenI was talking about Glanzmann’s issue
20:19jannautpw_rules: yes, it halts completely. The rcu stall is supposed to print a backtrace but doesn't. sometime it halts without rcu stall message
20:19GlanzmannAs you can see it worked later when I switched to the usb-a. But it messages which are above are all from usb-c tries. I tried several times by rebooting the air.
20:19tpw_rulesjannau: okay, looks like that's not dcp's fault. this is just on linux-asahi
20:19axboe has quit [Quit: leaving]
20:20svenstrange
20:20svenit looks as if it doesn’t even recognize the cable
20:21axboe has joined #asahi
20:22GlanzmannHopefully its the damn cable then. :-)
20:22jannauGlanzmann: does m1n1 print any usb-dwc3 messages when connected via usb-c
20:23GlanzmannThe usual messages that it opened two serial ports.
20:23Glanzmannpovik: Can I reboot the target, than I'll take a screenshot.
20:24povikone moment
20:25Glanzmanni hear somethoing
20:25jannauGlanzmann: not necessary, The messages I'm looking for are just printed to the serial console and not to the screen
20:25jannaupicture not necessary
20:48tpw_rulesGlanzmann: i am missing something about how to get the grub config to stick
20:48Glanzmanntpw_rules: reference quickstart.txt and execute the commands.
20:49Glanzmanntpw_rules: You have efi mounted in /boot/efi ?
20:49GlanzmannPut it in /etc/fstab?
20:49GlanzmannThan run the grub commands from quickstart.txt and reboot that's it.
20:49tpw_rulesyes, all the commands seemed to execute successfully but grub didn't come up with a menu
20:50tpw_rulesdo i need to tell dpkg-reconfigure anything or just accept all the defaults?
20:50GlanzmannOkay, can you paste me the output of 'lsblk; mount; find /boot'
20:50Glanzmanntpw_rules: Removeable media path yes; update nvram no
20:52tpw_rulesany kernel parameters?
20:53tpw_rulesoh, i see the m1debian.txt has different instructions to the quickstart.txt
20:53tpw_ruleslet me try the latter
20:54GlanzmannYep, that is obsolete.
20:54GlanzmannI should kill it.
20:54axboe has quit [Quit: reboot]
20:56axboe has joined #asahi
20:57axboetpw_rules: did allmodconfig and matches your results - 20.8m for 16k ps, 25.9m for 4k ps
20:58atka has quit [Quit: WeeChat 3.4]
20:58tpw_rulesaxboe: on an m1 pro? that's a bit sad, i had hoped it would be faster
20:58Glanzmannmps: Thank you for your /sys/module/hid_apple/parameters/ reminder. Now everything works for me (caps lock is control; german umlauts and meta alt swap)
20:59axboetpw_rules: yep, small one though, 6 p cores
20:59axboetpw_rules: I ran on a 5950x and 12900k for comparison, and x1 is completing it too (but that'll take a while)
20:59axboetpw_rules: 12900k does it in 12.45 min
20:59axboeI'd say 20.8m is very respectable
20:59axboenot this is allmodconfig x86, so it's basically all of it
21:00tpw_rulesok you probably compiled more than me then
21:00axboemy qemu kernel takes ~85s, and the one I run on the m1 takes ~3 min
21:00axboeI'd say it's pretty damn fast
21:01tpw_rulesand the 12900k has what, a 10x higher tdp?
21:02axboebase tdp 125W, turbo 241W
21:02Glanzmannaxboe: That are my 5950x numbers: linux 5.10 allmodconfig: Kernel: make -j 64 V=0 &> /dev/null 12184.35s user 1387.42s system 3075% cpu 7:21.31 total
21:03axboeGlanzmann: 541.5 secs here
21:03axboethis is my for-next branch, fwiw
21:03axboeand -j32
21:04axboeGlanzmann: these are test boxes, and I use them for peak runs hence disable mitigations, prune config etc
21:04axboewhat they run, I mean
21:04Glanzmannaxboe: Me, too.
21:04Glanzmannaxboe: Do you compile in ram or on nvme?
21:05axboeGlanzmann: hmm, is your ram clock right? sad to say I ran mine for quite a while before figuring out the bios set the ram speed way too low
21:05axboeGlanzmann: nvme
21:07___nick___ has quit [Ping timeout: 480 seconds]
21:10Glanzmannaxboe: I see. ram clock is right. I use the following configuration. RAM speed is maximum that I can get with 128 GB ram and that board:
21:10mpsGlanzmann: you are welcome
21:10GlanzmannThe board can detect ecc errors and has remote management board and the chassis is only 1U. That is why I choose it.
21:13axboeGlanzmann: figured you would have it right ;)
21:14axboeGlanzmann: oh actually yours are running 2600, mine a 3200
21:15Glanzmannaxboe: Do you only have 2 memory modules?
21:15axboeGlanzmann: yep, 2x8g
21:15GlanzmannThat explains it.
21:15axboesorry 2x16g
21:15GlanzmannI have 4x32g
21:17bps has quit [Ping timeout: 480 seconds]
21:33tpw_ruleshm, i can't get these stalls to happen with Glanzmann's stuff
21:33Glanzmanntpw_rules: Good and bad.
21:36Glanzmannpovik made the speakers work on the macbook air. There is no patch yet. Just noise. :-)
21:36Glanzmannleft *and* right.
21:42Glanzmanntpw_rules: The artefacts that you're using were compiled on Debian stable amd64 using a cross compiler.
21:42GlanzmannWith the bootstrap.sh
21:42tpw_rulesi am compiling using a cross-compiler too. i think there is a difference in the kernel config
21:42tpw_rulesthough i am using gcc 9 instead of 10. i hope the issue is not something that sensitive
21:43axboe(71.78 min for the x1 that finally finishes, fwiw)
21:43j`eyaxboe: sloooooooooow
21:43axboej`ey: but hot!
21:44tpw_rulesthat's really what gets me: compiling a kernel on the mini is silent
21:44Glanzmanntpw_rules: On the air is well, but sometimes it gets hot.
21:44tpw_ruleswell the air doesn't even have a fan does it?
21:45tpw_rulesmeanwhile my 6 core xeon thinkpad which is like 30% slower still is sitting here screaming and melting stuff on my desk
21:45tpw_rulesi lost a chocolate bar to it the other day...
21:45GlanzmannNo, it doesn't. Unless povik is doing sound tests that do not wake up the rest of the family int he same room.
21:45axboemy experience on my m1 laptop is that a "normal" compile (which is ~3 min) doesn't spin the fan at all
21:45j`eythe quicker it is, the less time for the fan to kick in :D
21:45axboethe allmodconfig does turn it in after 5 min or so, but it's still way less fan than on an x1 or (god forbid, I had one of these before) a p1
21:45tpw_rulesdo the fans actually turn off on it? they never turned off on my older intel one
21:45jannautpw_rules: I'm using gcc "Gentoo 10.3.0 p1", cross-compiled on x86_64
21:46Glanzmanntpw_rules: On the mini the fan is always on but you don't hear it.
21:47kovtpw_rules, Glanzmann one thing I noticed on my testing is that the M1 chips seem to prefer C++/Rust compilation to C
21:47tpw_rulesthose compilers probably have higher memory bandwidth requirements
21:47koverm axboe ^
21:48kovtpw_rules, yeah, I figure C++ and Rust need to keep a lot more state while compiling
21:48kovit certainly does use a lot of memory (and binaries are bigger usually)
21:49kovI tend to use building the rust compiler as my benchmark and the difference between the M1/M1 Max and my intel machines is massive
21:49axboekov: that just makes it even nuttier...
21:49axboekov: I should try that :)
21:50kovaxboe, that'd be great! I'd really like to see 5950x and 12th gen numbers if you have the time
21:50Glanzmannaxboe: OUt of curiosity, could you run this on your m1? taskset -c 0 sysbench --memory-oper=read --memory-block-size=128M --memory-total-size=128G --threads=1 memory run
21:50axboepartial to doing kernel compiles as a) that's what I do, and b) no real external requirements for cross compiling
21:51axboeGlanzmann: on the E core?
21:51kovthe thing that got me hooked originally was the compile times they were advertising for WebKit (I used to work on WebKitGTK)
21:51Glanzmannaxboe: Good point, probably on a p-core
21:51GlanzmannNow that you mention it, I also need to run it on a p-core.
21:51kovbut it carried on nicely to rust, which is what I'm doing mostly these days
21:52kovthe rust compiler is a nice benchmark for me because it's a mix of C++ and Rust
21:52Glanzmannaxboe: Thank you, you just doubled my number.
21:52axboeGlanzmann: 2.7906s, 46962.77 MiB/sec
21:52axboeGlanzmann: ;)
21:52j`eykov: there is the cranelift backend, for pure rust :P
21:52axboeGlanzmann: 6.7088s, 19533.98 MiB/sec <- E core
21:53axboekov: easy to cross compile?
21:53Glanzmannaxboe: For me it is 19910.95 vs 42604.49
21:53axboekov: guess we can do native, probably close enough
21:53kovj`ey, hah, but then I lose the C++ part (I still have to compile WebKit and Chrome for work - and for the 16k patches ;D)
21:54kovaxboe, yeah, I've done a cross-compile to x86-64 once to see if it made a difference, it's close enough
21:54jmr2 has joined #asahi
21:54Glanzmannaxboe: I compared that to my 5950x, but did not notice that I was running on an e-core and was a bit disappointed. My ryzen can go around 30 GB/s
21:54le0n has quit [Quit: see you later, alligator]
21:54le0n has joined #asahi
21:55axboeGlanzmann: 12900k is only ~23GB/sec
21:55axboeGlanzmann: 5950x gets me ~25GB/sec here
21:56axboekov: ok let's try it then
21:56GlanzmannI see. This is 5950x with the slow ram timing: https://pbot.rmdir.de/6WUvToakl4haXrcWWmRjRA
21:57axboeGlanzmann: hm
21:57jmr2Glanzmann: regarding your USB issue: how old is your version of m1n1? I'm wondering if commit e1a7deb could help you (it's not included in the installer yet). More details in issue 101.
21:57Glanzmannaxboe: This is with the fast ram timing on a system that has only 2 slots and no ecc ram: https://pbot.rmdir.de/occeGOdlOtnNDKmBYA3zVQ
21:58axboeGlanzmann: no ecc here either
21:58Glanzmannjmr2: I installed the newest m1n1 as of yesterday.
21:58kovaxboe, btw you probably want to do 2 runs, as it downloads a bunch of stuff, so what I did was I ran the build once, deleted build/{bootstrap,aarch64-unknown-linux-gnu}, then timed the second run (making sure no ccache or sccache was on the way of course hehe)
21:59axboekov: ok, will do a prime run, then a timed one
21:59jmr2Glanzmann: on a different topic, I'd suggest to add the following CONFIG_ to the wiki: GPIO_MACSMC CHARGER_MACSMC APPLE_PLATFORMS APPLE_SMC APPLE_SMC_RTKIT
21:59axboekov: what's the make clean equiv there?
22:00Glanzmannjmr2: Do you want to do it or should I do it?
22:00axboekov: oh nevermind, you literally wrote that
22:00tpw_rulesjannau: if i use CONFIG_PREEMPT instead of CONFIG_PREEMPT_VOLUNTARY, it works properly. i couldn't get it to hang in 15 or so boots, whereas with VOLUNTARY it hung every other boot or so
22:00jmr2I think I'll let you do it - you know which rules you've used to determine what to add and not so far.
22:00j`eytpw_rules: ouch
22:00tpw_rulesnot going to investigate why that is the case, i just want it fixed...
22:01Glanzmannjmr2: I add anything that I was once missing. So I'm adding them now.
22:01jmr2OK. Thanks.
22:01j`eyarm64 will support PREEMPT_DYNAMIC in the -next soon, tpw_rules
22:01j`eynot that it really helps you now :P
22:01tpw_rulesj`ey: i don't really know the differences
22:02Glanzmannjmr2: Done.
22:02jmr2Thanks
22:02j`eyPREEMPT means all(ish) kernel code is preemptable, preempt_voluntary means the kernel has some explicit preemption points
22:03j`ey(and PREEMPT_DYNAMIC means you can switch between all 3 preemption models at runtime)
22:03tpw_rulesvoluntary sounds like it is probably better?
22:03mpsthis is announced few months ago, iirc
22:04Glanzmanntpw_rules: Unless you want to find bugs. :-)
22:04tpw_rulesdo you think that is an upstream problem?
22:04j`eytpw_rules: the 'full' preemption is meant to be lower latency for interactiveness
22:04mpsvoluntary is good for long running task
22:04tpw_rulesGlanzmann's kernel does not have voluntary
22:05mps(forced) preemt is good for interactive usage
22:05mpspreempt*
22:08mpsI always use preempt (forced)
22:09jmr2 has quit [Quit: Page closed]
22:21axboekov: 5950x (8:53), m1 (16:11), 12900k (9:51)
22:22axboekov: hence 5950x 1.82x, 12900k 1.64x
22:22axboerougly same ratio as kernel compile for 12900k, m1 does proportionally better on rust c++ compile than the 5950x compared to the kernel C compile
22:23axboeoh 5950x g++ was 9.x, let's redo with 11.x like the others...
22:24kovaxboe, nice, thanks! that's the same time my standard m1 does on the mac fwiw
22:27kovand my xps 13 1185G7 did it in 44m if I'm not mistaken pff
22:28axboeain't nobody got time for that
22:31sri_ has joined #asahi
22:31sri has quit [Read error: No route to host]
22:32axboekov: 5950x (8:16) 1.96x
22:32axboekov: using g++11 to be more fair
22:32axboekov: same conclusion, just a bit closer
22:35kovaxboe, looks great, seems like more recent intel are much better than older ones (at least the ones that gobble power)
22:42kovaxboe, ok, found my notes here, I got 11:30 on macos and 15:23 on the linux 8-core VM running a standard distro kernel on my m1 max
22:43jannautpw_rules: confirmed, PREEMPT_VOLUNTARY was selected
22:44kov(I haven't put linux bare metal on the max yet, using the air for my testing for now xD)
22:50kovaxboe, btw you said you're running these with E cores disabled?
23:08kovjust repeated the build on my m1 mini, 21:50, the fact I got ~16m on macos makes me think there may be some more 'need to enable L3 cache' that haven't been found heh
23:09kovI doubt the single core boost would make such a big dent?
23:17kov(now I want to ask povik for his change to linux to build it on macos and compare xD)
23:21tpw_rulesit was almost exactly the same time for me when building in a linux VM using UTM
23:23kovtpw_rules, same time as which one? or do you mean the vm did it in the same time as linux bare metal?
23:23tpw_rulesiirc the 4k page size VM did it in almost exactly the same time as 16K bare metal but with no cpufreq driver
23:24kovyeah, now that I think about it, I think my test on a VM on the m1 mini did it in ~20m
23:24tpw_rulesi think macos was able to make up the time lost with 4k pages by actually speeding up the P-cores
23:25Gaspare has joined #asahi
23:30kovtpw_rules, hmm or is hvf able to hide the 4k somehow?
23:31kovI guess that would require cooperation from qemu though
23:40willemml has joined #asahi
23:41willemml has quit []
23:52axboekov: E cores disabled on the 12900k, all cores enabled on the m1
…