#
…

2023-06-01

00:00steven has quit [Quit: ZNC 1.8.2 - https://znc.in]
00:00steven has joined #asahi-dev
00:10brolin has quit [Ping timeout: 480 seconds]
00:21Jenzaah has joined #asahi-dev
00:23nsklaus has quit [Ping timeout: 480 seconds]
00:29Jenzaah has quit [Ping timeout: 480 seconds]
02:00gabuscus has quit []
02:19c10l4 has quit []
02:21gabuscus has joined #asahi-dev
03:20c10l4 has joined #asahi-dev
03:21nopeslide132 has joined #asahi-dev
03:27nopeslide13 has quit [Ping timeout: 480 seconds]
03:31stipa is now known as Guest1893
03:31stipa has joined #asahi-dev
03:33Guest1893 has quit [Ping timeout: 480 seconds]
03:52nopeslide1328 has joined #asahi-dev
03:58nopeslide132 has quit [Ping timeout: 480 seconds]
04:10nafod has quit [Quit: Ping timeout (120 seconds)]
04:10nafod has joined #asahi-dev
04:28Avaflow has quit [Ping timeout: 480 seconds]
04:42nopeslide13282 has joined #asahi-dev
04:45nopeslide1328 has quit [Ping timeout: 480 seconds]
04:46nopeslide1328 has joined #asahi-dev
04:52nopeslide13282 has quit [Ping timeout: 480 seconds]
05:05Avaflow has joined #asahi-dev
05:42TexasOct has joined #asahi-dev
05:42i509vcb has quit [Quit: Connection closed for inactivity]
06:20Jenzaah has joined #asahi-dev
06:30bisko has joined #asahi-dev
07:03kaazoo has joined #asahi-dev
07:08pjakobsson has quit [Ping timeout: 480 seconds]
07:09pjakobsson has joined #asahi-dev
08:06bps has joined #asahi-dev
08:10TexasOct has quit [Remote host closed the connection]
08:12eric_engestromhmm, are we aware of any fs corruption issue? I was compiling a project on my m2 air, and I stepped away for a couple of minutes to get some water, and when I came back the laptop had rebooted. I logged back in, and couldn't continue the compilation because my files aren't valid C anymore, and I couldn't `git status` because a bunch of git object files are empty
08:13eric_engestrom`git diff` is showing me a ton of files that have seemingly been truncated?
08:14eric_engestromI think those are all changes from a rebase I did a couple of minutes before I ran the compilation
08:15j`eywasnt there an xfs issue recently, but not sure if it's in any of asahi versions
08:16eric_engestromwait, I seem to recall some discussion about nvme or something that apple did weird with a flush hack on macos and we have a different hack or something?
08:16eric_engestromj`ey: ext4 here (forgot to say)
08:35_jannau_"apple-nvme: defer cache flushes by a specified amount"
08:41eric_engestromyeah, that's the one I was trying to remember
08:41eric_engestrom> flushes are delayed at most 1 second
08:42eric_engestromthere was definitely way more time than that, so I guess it wasn't that
09:35bps2 has joined #asahi-dev
09:41bps has quit [Ping timeout: 480 seconds]
10:00marcaneric_engestrom: those all sound like normal corruption issues you'd expect on ext4 if apps aren't doing the requisite flushes, and I doubt git flushes anything because that would probably kill performance
10:04marcanI would normally not expect much data loss along those lines though, I think /proc/sys/vm/dirty_writeback_centisecs defaults to 5 seconds?
10:05marcanbut yeah it just looks like you had a bunch of stuff in page cache and not flushed...
10:05j`eyso that means that if nothing flushes, the kernel flushes every 5s anyway?
10:06marcanit means the kernel tries to write out data every 5 seconds. it doesn't mean it won't fall further behind than that though.
10:06marcanbut like if your machine is otherwise idle, dirty pages should start to be written out within 5 seconds
10:07marcanso unless you have a high/saturating write workload, you'd expect it to stay caught up to within that time give or take
10:08marcanah but wait
10:08marcan/proc/sys/vm/dirty_expire_centisecs defaults to 30s
10:08marcanso that means the data will wait around 30 seconds before it gets flushed if nothing else flushes it
10:11Dementor has quit [Ping timeout: 480 seconds]
10:11marcaneric_engestrom: if you want to test the "clean NVMe shutdown, hard FS-level shutdown" case (i.e. the "this is totally not Apple's fault" case), hold down the power button. I'm pretty sure we have the NVMe driver doing a clean shutdown in that case.
10:11marcanif you get the same kind of issue, it's FS/app-level
10:11marcan(the power button sends multiple warning messages before hard shutdown, we use the last one to trigger a kernel shutdown)
10:26kaazoo has quit [Remote host closed the connection]
10:35nsklaus has joined #asahi-dev
10:39bisko has quit [Quit: Textual IRC Client: www.textualapp.com]
10:52whyirc has joined #asahi-dev
10:52whyircHello everyone
10:52whyircI'm trying to build newer u-boot version
10:52whyircGetting this cryptic error - https://pastebin.com/e1NeqFBP
10:53whyircLooks like other distros (alpine, official in dev branch) built u-boot v2023.04 without any problems
10:53whyircAny idea what's going on or tips to debug?
10:57j`eymaybe it's a dtc version issue?
10:57j`eyseems to be erroring on a floating point value
11:01whyirc has quit [Remote host closed the connection]
11:04whyirc has joined #asahi-dev
11:06whyircWhat can possibly cause this error?
11:08mpswhyirc: look in alpine APKBUILD what dependencies are needed
11:08Jenzaah has quit [Remote host closed the connection]
11:09Jenzaah has joined #asahi-dev
11:14j`eypretty weird, I can repro it with just calling dtc directly, so Im not sure how it works
11:15Dementor has joined #asahi-dev
11:15whyircYou have the same error? What version of dtc do you use?
11:16j`eyI just built the latest
11:17Jenzaah_ has joined #asahi-dev
11:17Jenzaah has quit [Read error: Connection reset by peer]
11:17whyircI found the source of error
11:18whyircLooks like the error is reproducible if you add DTC=dtc to make
11:18whyircNixOS's BuildUBoot derivation does this by default
11:19j`eyoh, so uboot has a custom dtc maybe??
11:19whyircI need to go
11:20whyircI'll be here in a 30-40 mins
11:27j`eyfor me, dtc fails on this dts file: /dts-v1/; / { a = <2.4>; };, so I don't get how it works for the kernel/uboot (not sure if Ive actually compiled these files every myself)
11:29CoD_Segfault has joined #asahi-dev
11:33jannauwhyirc: the gpu dts node needs dtc float support not upstream, you need the dtc from the linux or u-boot repo
11:33whyirc has quit [Quit: Page closed]
11:33nst has quit [Ping timeout: 480 seconds]
11:41eric_engestrommarcan: /proc/sys/vm/dirty_writeback_centisecs is 15sec on my old x86 and 60sec on my m2
11:42eric_engestromas for trying to hold shutdown, I don't really want to do this as it's my daily driver :]
11:44nst has joined #asahi-dev
11:44eric_engestromalso, it happened again, but this time I was looking at my computer: I ran `ninja`, and it started spewing compile errors (I should've taken a picture, I don't remember but I would expect it's truncated files again) and it froze; keyboard unresponsive (ctrl+alt+f2 didn't do anything), couldn't ssh in
11:44eric_engestromafter a few seconds (maybe 30?) it rebooted
11:45eric_engestromI'll try reverting to the previous kernel (I did the updates a couple of days ago)
11:45jannau30s would be the watchdog timeout
12:01whyirc has joined #asahi-dev
12:04Dementor has quit [Remote host closed the connection]
12:05Dementor has joined #asahi-dev
12:10Cyrinux9 has quit []
12:13whyirc has quit [Quit: Page closed]
12:14Cyrinux9 has joined #asahi-dev
12:36j`eyjannau: is that dtc patched in the asahi repo? or from upstream
12:37j`eyfound it, f91172ba2b71d40dc3a9a80f3ca10dd91c387436
12:37j`eyscripts/dtc: Add support for floating-point literals, from lina
13:03kettenisthat dtc patch is on the asahi-related branches of the Asahi u-boot repo
13:03kettenisbut it needs to go through whatever the upstream dtc repo is to end up in upstream u-boot
13:04j`eyI didnt realise that both uboot and kernel vendored dtc
13:06crabbedhaloablut has quit [Ping timeout: 480 seconds]
13:07crabbedhaloablut has joined #asahi-dev
13:14lynndotpy has quit [Quit: bye bye]
13:16lynndotpy has joined #asahi-dev
13:33pjakobsson has quit [Remote host closed the connection]
14:00skipwich has quit [Read error: Connection reset by peer]
14:00skipwich has joined #asahi-dev
14:20kettenisj`ey: I didn't realize it either; until I ran into the floating-point literals ;)
14:21j`eysounds familiar :p
14:21kettenisfortunately lina's diff applied without issues
14:30Jenzaah has joined #asahi-dev
14:30Jenzaah_ has quit [Read error: Connection reset by peer]
14:35bgb has joined #asahi-dev
14:46bgb has quit [Ping timeout: 480 seconds]
15:09sid-linux has joined #asahi-dev
15:09Jenzaah has quit [Remote host closed the connection]
15:10bps2 has quit [Ping timeout: 480 seconds]
15:12sid-linuxHi I was looking at commits via `git log` for tag `asahi-6.3-3` in the at github AsahiLinux/linux
15:12sid-linuxI saw this commit:
15:13sid-linuxcommit 42d199691b30bca60628fbdbcaf6662fd34fd3b8
15:13sid-linuxAuthor: Asahi Lina <lina@asahilina.net>
15:13sid-linuxDate: Wed Apr 26 20:05:17 2023 +0900
15:13sid-linux DO NOT MERGE: drm/asahi: Add an experimental UAPI extension
15:14sid-linuxMy question is
15:14sid-linux"DO NOT MERGE": Was this merged by mistake or is this message to ask for this commit not to get upstreamed to linux proper?
15:15psykosedo not merge to upstream
15:15sid-linuxcool. Just checking !
15:26Jenzaah has joined #asahi-dev
15:30Jenzaah_ has joined #asahi-dev
15:30Jenzaah has quit [Read error: Connection reset by peer]
15:34Jenzaah has joined #asahi-dev
15:34Jenzaah_ has quit [Read error: Connection reset by peer]
15:42Jenzaah has quit [Ping timeout: 480 seconds]
15:46sid-linuxIs there a way to know if asahi-dev edge is based on a point version i.e. gregkh's linux 6.3.y e.g. 6.3.4 or based off of linus torvald's plain 6.3
15:46j`eytheyre not based on stable branches
15:47sid-linuxi understand they have custom asahi stuff -- but what linux version are they built on top of?
15:47j`eygit merge-base origin/master asahi/asahi-wip, this gives 457391b0380335d5e9a5babdec90ac53928b23b4
15:47systwi has joined #asahi-dev
15:47j`eywhich is 6.3
15:48_jannau_doesn't uname report 6.3.0-asahi3-1
15:48j`ey(and btw edge and !edge are the same sources, just built with different configs)
15:49sid-linuxah indeed yes. uname does say 6.3.0-asahi-3-1-edge-ARCH
15:50Jenzaah has joined #asahi-dev
15:51sid-linuxinterestingly the `asahi` repo (not asahi-dev) installs a linux version whose uname is something like `6.2.asahi11-1`
15:52j`eyedge from the non-asahi-dev repo will also be 6.2
15:54sid-linuxYes edge is the same.
15:54sid-linuxThe point I'm making is that we have `6.2-asahi11-1`.. but now we say `6.3.0-asahi3-1` which is a slight inconsistency.
15:54j`eyoh, the .0
15:54amarioguy has joined #asahi-dev
15:55sid-linuxwhich is useful information in the case of 6.3 but leaves you a bit confused for 6.2
15:56sid-linuxbut technically linus does not give his versions a point anyways
15:56sid-linuxlinus always gives 6.1 , 6.2 , 6.3 etc and then gregkh brings out point releases
15:57jonny1996 has joined #asahi-dev
15:58sid-linuxthough this new slightly different naming scheme will allow marcan to conceivably bring out a 6.3.4-asahi-XXXX based on say the point release 6.3.4 for example
15:58Jenzaah has quit [Ping timeout: 480 seconds]
15:59jonny1996Regarding the kernel version on 6.3 I am curious as well as I use XFS on external storage and a corruption bug was in stable 6.3.0 to 6.3.3.
16:01j`eyyeah, that's what I thought might have happened with eric this morning, but different issue, but that sounds worth cherry-picking, if the next asahi release stays on 6.3
16:01marcanyeah I guess I should probably rebase on 6.3.4 this once
16:02marcanI normally don't care for stable point releases but corruption is kinda bad
16:03marcaneric_engestrom: if it's the watchdog timing out then we have a problem and that will not do a clean NVMe shutdown
16:03marcando a filesystem check, I'm curious whether anything bad happened at the metadata level
16:04marcanwe haven't ever seen that and I hard reboot my machines all the damn time, so that makes me pretty confident we don't have a major problem, but worth checking
16:04sid-linuxdistributions like fedora seem quite fastidious about churning point releases -- the impression I got was security updates and urgent bug fixes. gregkh always says something like "All users of the 6.3 kernel series must upgrade."
16:04j`eyit's 6.3.5 that has the fix
16:04sid-linuxbut i realize that asahi does not have the scale or capacity to do that
16:05marcanI mean we release kernels based on RCs sometimes
16:05marcanour downstream kernel tree does not claim to be stable
16:05marcanbut then again our use cases are usually a small fraction of the codebase
16:05jonny1996It makes sense to stick to a base as most of the bugs are platform specific.
16:05marcanmost bugs and issues and stable fixes are in random drivers people are unlikely to use on this platform
16:05marcanin rare cases when they do we cherry-pick
16:07marcanit's pretty easy for anyone downstream to rebase our patchset on stable point releases though, rarely do you get bad conflicts there
16:07sid-linuxTrue. Its not the stability that I'm worried about, its the (potential) security issues that get fixed. But I guess that probably does not make sense because Asahi itself is quite not mature yet
16:07marcan(though TBH, in my opinion, the stable kernel folks these days are *way* too eager to merge random crap)
16:07marcan(I regularly get patch merged for stable notifications for stuff I wrote that is absolutely not a bugfix and useless to stable kernel users and I didn't tag for stable and I have *no* idea why)
16:07j`eyAUTOSEL!
16:08Jenzaah has joined #asahi-dev
16:08marcansid-linux: security fixes on stable kernels are more relevant to *long-term stable* which we do not maintain
16:08marcanyou do not want to be stuck on some ancient kernel without security updates
16:09marcanwe reasonably closely track kernel releases so we get the security fixes in a reasonable timeframe by default
16:09sid-linuxcool, that makes sense
16:10marcan(I don't expect anyone to be using Asahi unmodified and not separately maintained to, like, run a cloud hosting platform or something where security is absolutely paramount)
16:11marcanpeople who need near 0-day security response are probably building their own kernels and have a team dedicated to that anyway :)
16:12marcansomething big enough to be immediate cause for concern would make the news and I'd cherry pick it in of course
16:13sid-linuxthanks -- appreciate your sentiment about this
16:16Jenzaah has quit [Ping timeout: 480 seconds]
16:17amarioguy has quit [Remote host closed the connection]
16:17salimterryli has quit [Remote host closed the connection]
16:18hightower3 has joined #asahi-dev
16:20marcancherry-picked the XFS fix into our tree (probably easier than a rebase on stable, especially since I think I saw most of the WiFi series get AUTOSEL'd and I really don't feel like wrangling that rebase right now)
16:23sid-linuxI'm noticing that I've got hardly any updates from core, community, extra this week. Usually updates are quite regular on arm arch linux
16:23sid-linuxIs there something blocked ? the package update stream has totally dried up it seems
16:23marcanthis is why I want to move away from ALARM...
16:24marcanthe QA/maintenance just keeps getting worse
16:24marcanlina just ran into a broken python package they forgot to rebuild earlier today
16:24Jenzaah has joined #asahi-dev
16:24hightower2 has quit [Ping timeout: 480 seconds]
16:26sid-linuxI'm pretty new to Asahi (default desktop install) and I must confess I do find Arch quite simple and grokkable. I decided not to try to install my own fedora or debian on M2 as I was not sure how whether those distro were getting enough care and attention ALARM is currently
16:27marcanArch itself is great, but unfortunately ALARM these days has a maintenance team of <1 person and it shows
16:27marcanit's not their fault, but without more people it just can't be a quality distro
16:28marcanwe will be announcing a new default distro option soonish
16:28marcan(ALARM packages/repos will remain maintained, but the idea is to recommend the new distro by default as a higher quality option)
16:30sid-linuxI have two difficult choices (1) Stick with ALARM. Core linux system maintained very well by Asahi folks. Updates not reliably available (2) Do it myself fedora/debian on Asahi. Better package updates but Asahi attention may not be as much (3) Sounds like you're going to be blessing a different distribution but its likely to be sometime away, right?
16:31jonny1996Glad to know the the Asahi ALARM repo will remain maintained. Probably will switch at some point after the switch, but good to know no rush.
16:32Jenzaah has quit [Ping timeout: 480 seconds]
16:33cylm has joined #asahi-dev
16:36marcansid-linux: tbh I wanted it to be out already but planning is hard and real life gets in the way sometimes :)
16:36marcanbut we're getting there
16:39Jenzaah has joined #asahi-dev
16:44sid-linuxmarcan: understandable. I'm actually suprised at how good Asahi Linux is already. As far as I'm concerned you're ahead of the curve !
16:44amarioguy has joined #asahi-dev
16:47Jenzaah has quit [Ping timeout: 480 seconds]
16:49marcanglad to hear that! we do try :)
16:52Jenzaah has joined #asahi-dev
17:00Jenzaah has quit [Ping timeout: 480 seconds]
17:05amarioguy has quit [Remote host closed the connection]
17:08Jenzaah has joined #asahi-dev
17:18Jenzaah has quit [Ping timeout: 480 seconds]
17:29Jenzaah has joined #asahi-dev
17:37Jenzaah has quit [Ping timeout: 480 seconds]
17:38Jenzaah has joined #asahi-dev
17:39jonny1996 has quit [Ping timeout: 480 seconds]
17:40brolin has joined #asahi-dev
17:47Jenzaah has quit [Ping timeout: 480 seconds]
17:49brolin has quit [Ping timeout: 480 seconds]
17:51sid-linux has quit [Quit: User exited]
17:55Jenzaah has joined #asahi-dev
18:03Jenzaah has quit [Ping timeout: 480 seconds]
18:04sid-linux has joined #asahi-dev
18:05Cyrinux9 has quit []
18:08Cyrinux9 has joined #asahi-dev
18:10eric_engestrommarcan: I can't fsck live, so I'll do that next time I can shutdown
18:11eric_engestrombut to me the bigger issue than "crash lead to fs corruption" is the crash itself
18:11Jenzaah has joined #asahi-dev
18:13eric_engestromwhy does compiling kill my machine? I'll try to have my old machine ssh'ed in and `dmesg -w` + `journalctl -f` to see if there's anything useful before it freezes
18:19sid-linux has quit [Quit: User exited]
18:21jannauthermal issues maybe? I haven't seen a crash with kernel builds on the m2 13" mb pro. fans spin on after a few minutes
18:21eric_engestromno it's cold, and the crash happens as soon as I start compiling
18:21Jenzaah has quit [Ping timeout: 480 seconds]
18:22Jenzaah has joined #asahi-dev
18:22jannaustill wouldn't explain why it was fine in 6.2. cpuidle could be factor
18:23jannaueric_engestrom: is this alarm, fedora or something else?
18:23eric_engestrom(on the -dev repo btw)
18:24eric_engestromI have to go now though
18:24eric_engestromI'll read the backlog later
18:24eric_engestromI'm pretty sure this is a regression from the update at the begining of the week
18:25eric_engestrombut I haven't reverted that to confirm yet
18:30Jenzaah has quit [Ping timeout: 480 seconds]
18:31jannauyes, using 6.3.0-asahi-3-1-edge-ARCH from the asahi-dev repo here. seems to work without issues with parallel kernl and mesa builds and a load over 16
18:35salimterryli has joined #asahi-dev
18:35jonny1996 has joined #asahi-dev
18:38Jenzaah has joined #asahi-dev
18:40jonny1996 has quit [Remote host closed the connection]
18:48Jenzaah has quit [Ping timeout: 480 seconds]
18:55jonny1996 has joined #asahi-dev
18:57Jenzaah has joined #asahi-dev
19:04dylanchapell has joined #asahi-dev
19:06c10l4 has quit []
19:12c10l4 has joined #asahi-dev
19:13Jenzaah has quit [Ping timeout: 480 seconds]
19:18brolin has joined #asahi-dev
19:22Jenzaah has joined #asahi-dev
19:27nullroute has quit [Quit: bai]
19:28nepeat_ has quit [Remote host closed the connection]
19:28brolin has quit [Ping timeout: 480 seconds]
19:28nullroute has joined #asahi-dev
19:28nepeat has joined #asahi-dev
19:29sid-linux has joined #asahi-dev
19:30Jenzaah has quit [Ping timeout: 480 seconds]
19:30cylm_ has joined #asahi-dev
19:32cylm has quit [Ping timeout: 480 seconds]
19:34sid-linuxHi -- I updated today to 6.3.0-asahi-3-1-edge-ARCH
19:34sid-linuxI have a perplexing issue... it seems that pulseaudio and other funny dmabuf stuff file descriptors seem
19:34sid-linuxto be polluting each process
19:34sid-linuxHere is a trivial script
19:35sid-linux(call it strange_fd.sh )
19:35sid-linux#!/bin/bash
19:35sid-linuxls -lh /proc/self/fd
19:35sid-linuxwhen you run this script
19:36sid-linuxyou get the following:
19:36sid-linuxlrwx------ 1 abcxyz abcxyz 64 Jun 2 00:59 0 -> /dev/pts/2
19:36sid-linuxlrwx------ 1 abcxyz abcxyz 64 Jun 2 00:59 1 -> /dev/pts/2
19:36sid-linuxlr-x------ 1 abcxyz abcxyz 64 Jun 2 00:59 100 -> /dmabuf:
19:36sid-linuxlr-x------ 1 abcxyz abcxyz 64 Jun 2 00:59 101 -> /dmabuf:
19:36sid-linuxlr-x------ 1 abcxyz abcxyz 64 Jun 2 00:59 102 -> /dmabuf:
19:36sid-linuxlrwx------ 1 abcxyz abcxyz 64 Jun 2 00:59 2 -> /dev/pts/2
19:36sid-linuxlr-x------ 1 abcxyz abcxyz 64 Jun 2 00:59 3 -> /proc/2399/fd
19:36sid-linuxlr-x------ 1 abcxyz abcxyz 64 Jun 2 00:59 31 -> /dmabuf:
19:36sid-linuxlr-x------ 1 abcxyz abcxyz 64 Jun 2 00:59 39 -> /dmabuf:
19:36sid-linuxlr-x------ 1 abcxyz abcxyz 64 Jun 2 00:59 45 -> anon_inode:inotify
19:36sid-linuxlr-x------ 1 abcxyz abcxyz 64 Jun 2 00:59 47 -> /dmabuf:
19:36sid-linuxlrwx------ 1 abcxyz abcxyz 64 Jun 2 00:59 58 -> '/memfd:pulseaudio (deleted)'
19:36sid-linuxlr-x------ 1 abcxyz abcxyz 64 Jun 2 00:59 74 -> /dmabuf:
19:36sid-linuxlr-x------ 1 abcxyz abcxyz 64 Jun 2 00:59 76 -> /dmabuf:
19:36sid-linuxlr-x------ 1 abcxyz abcxyz 64 Jun 2 00:59 78 -> /dmabuf:
19:36sid-linuxlr-x------ 1 abcxyz abcxyz 64 Jun 2 00:59 90 -> /dmabuf:
19:36sid-linuxlr-x------ 1 abcxyz abcxyz 64 Jun 2 00:59 92 -> /dmabuf:
19:36sid-linuxWhy am i seeing pulseaudio, dmabuf etc as file descriptors in this scripts /proc/self/fd ?
19:40Jenzaah has joined #asahi-dev
19:41sid-linuxAs a sanity check, expectedly, this "pollution" of pulseaudio, dmabuf fds is not present on an x86_64 setup that I just checked
19:42sid-linuxWhile I cant test asahi linux 6.2-asahi11-1 (I shifted from asahi to asahi-dev today) -- I don't think this issue is present there either.
19:43sid-linux(I only have indirect evidence for this though. Can anyone check what they get on 6.2 and 6.3 on their own machines)
19:43sid-linuxThey just need to run a trivial script (see above)
19:44jjanzic has quit [Ping timeout: 480 seconds]
19:49Jenzaah has quit [Ping timeout: 480 seconds]
19:50systwi_ has joined #asahi-dev
19:51brolin has joined #asahi-dev
19:56systwi has quit [Ping timeout: 480 seconds]
19:58Jenzaah has joined #asahi-dev
20:00sid-linux(Here is the script again for easy reference)
20:00sid-linux#!/bin/bash
20:00sid-linuxls -lh /proc/self/fd
20:03Jenzaah_ has joined #asahi-dev
20:04jonny1996I just have 0 1 2 3 in mine via ssh, but I disabled the sound driver as I added logging for something I am not using.
20:04jonny1996it added logging
20:05sid-linuxWhich kernel are you on?
20:05jonny19966.2.0-asahi-11-1-edge-ARCH
20:06sid-linuxThe problem seems to be in 6.3.0-asahi-3
20:06sid-linuxAs I guessed 6.2 should be OK and it is
20:06jjanzic has joined #asahi-dev
20:07Jenzaah has quit [Ping timeout: 480 seconds]
20:07sid-linux(I no longer have 6.2 on my system so I can't verify for my own setup)
20:08sid-linuxAnybody running 6.3.0-asahi ( on the asahi-dev repo )-- can they verify? does not matter if it edge or not
20:11Jenzaah_ has quit [Ping timeout: 480 seconds]
20:22Jenzaah has joined #asahi-dev
20:25Jenzaah_ has joined #asahi-dev
20:26Jenzaah has quit [Read error: Connection reset by peer]
20:35Jenzaah_ has quit [Ping timeout: 480 seconds]
20:36Jenzaah has joined #asahi-dev
20:44Jenzaah has quit [Ping timeout: 480 seconds]
20:52Jenzaah has joined #asahi-dev
20:59brolin has quit [Ping timeout: 480 seconds]
21:01Jenzaah has quit [Ping timeout: 480 seconds]
21:07sid-linuxThis issue with funny fds arises when I check stuff in KDE's konsole. When I ssh, then I don't get these also.
21:08Jenzaah has joined #asahi-dev
21:15annan_personsid-linux: is it just inhereting these fds from its parent?
21:15brolin has joined #asahi-dev
21:16Jenzaah has quit [Ping timeout: 480 seconds]
21:24Jenzaah has joined #asahi-dev
21:29brolin has quit [Ping timeout: 480 seconds]
21:33Jenzaah has quit [Ping timeout: 480 seconds]
21:40sid-linuxannan_person: yes that is a good guess, since we're in konsole, kde some of these weird fds (fds are not marked as close on exec)
21:41Jenzaah has joined #asahi-dev
21:41sid-linuxmust be coming from parent
21:42sid-linuxbut I'd like to compare 6.2 vs 6.3. If you are running konsole in kde, could you tell me what `ls -lh /proc/self/fd` says?
21:42sid-linux(of course don't type in the ` )
21:50Jenzaah has quit [Ping timeout: 480 seconds]
21:58Jenzaah has joined #asahi-dev
22:00brolin has joined #asahi-dev
22:04lawrence has quit [Quit: The Lounge - https://thelounge.chat]
22:04sid-linux has quit [Ping timeout: 480 seconds]
22:06Jenzaah has quit [Ping timeout: 480 seconds]
22:07lawrence has joined #asahi-dev
22:12Jenzaah has joined #asahi-dev
22:16brolin has quit [Ping timeout: 480 seconds]
22:18Jenzaah_ has joined #asahi-dev
22:22Jenzaah has quit [Ping timeout: 480 seconds]
22:27Jenzaah_ has quit [Ping timeout: 480 seconds]
22:36Jenzaah has joined #asahi-dev
22:43jonny1996 has quit [Ping timeout: 480 seconds]
22:44Jenzaah has quit [Ping timeout: 480 seconds]
22:48dylanchapell has quit [Remote host closed the connection]
22:52Jenzaah has joined #asahi-dev
23:00Jenzaah has quit [Ping timeout: 480 seconds]
23:08Jenzaah has joined #asahi-dev
23:10cylm has joined #asahi-dev
23:11cylm_ has quit [Ping timeout: 480 seconds]
23:16Jenzaah has quit [Ping timeout: 480 seconds]
23:19jonny1996 has joined #asahi-dev
23:25Jenzaah has joined #asahi-dev
23:34Jenzaah has quit [Ping timeout: 480 seconds]
23:36CME_ has quit [Remote host closed the connection]
23:36CME has joined #asahi-dev
23:41Jenzaah has joined #asahi-dev
23:49Jenzaah has quit [Ping timeout: 480 seconds]
23:53dylanchapell has joined #asahi-dev
23:58Jenzaah has joined #asahi-dev
…