#
…

2022-03-20

00:27phire has quit [Server closed connection]
00:27phire has joined #asahi-dev
00:32amw has quit [Server closed connection]
00:32amw has joined #asahi-dev
00:35_whitelogger has joined #asahi-dev
00:41rikkaa has joined #asahi-dev
00:59arekm has quit [Remote host closed the connection]
00:59arekm has joined #asahi-dev
01:03chadmed has joined #asahi-dev
01:12m6wiq has quit []
01:42aratuk has joined #asahi-dev
01:42aratuk has quit []
02:05robinp_ has joined #asahi-dev
02:07robinp_ is now known as robinp
02:52riker77_ has joined #asahi-dev
02:57riker77 has quit [Ping timeout: 480 seconds]
02:57riker77_ is now known as riker77
03:13PhilippvK has joined #asahi-dev
03:17phiologe has quit [Ping timeout: 480 seconds]
03:27kov has quit [Quit: Coyote finally caught me]
03:27kov has joined #asahi-dev
03:37nicolas17 has quit [Ping timeout: 480 seconds]
03:48swampertx[m] has joined #asahi-dev
03:55kylealanhale has joined #asahi-dev
04:10kylealanhale has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
04:26Dcow[m]1what dependency I forget ?
04:28Dcow[m]1that is macos, btw
04:28tpw_rulesmaybe you need xzcat?
04:29Dcow[m]1xzcat: (stdin): File format not recognized
04:31M0x8FF[m]0x8FF: Did you make sure your wifi firmware loaded? Mine did not on the first boot after install
04:32M0x8FF[m]Accident message
04:32M0x8FF[m]Sorry 😅
04:43Dcow[m]1probably something wrong with 7z, not sure
04:48Dcow[m]1but without -so it is unpacking it, so probably 7z is ok
04:56Dcow[m]1ok, solved
05:18PermissionDenied[m] has joined #asahi-dev
05:21winter has quit [Quit: The Lounge - https://thelounge.chat]
05:22winter has joined #asahi-dev
05:48kameks has joined #asahi-dev
06:24doggkrusehas anyone actually built chromium natively on asahi? the aarch64 native build chain is quite broken
06:24doggkrusebuilt in assumptions on cross compiling from x86_64
06:26Glanzmanndoggkruse: A few people did. I think tpw_rules did: See here: https://pbot.rmdir.de/Gnwc4Q-j3TAXCFyAaYnugA
06:37r0ni has quit [Quit: Textual IRC Client: www.textualapp.com]
06:46kameks has quit [Ping timeout: 480 seconds]
07:11doggkruse has quit [Quit: Konversation terminated!]
07:13doggkruse has joined #asahi-dev
07:16marcanGlanzmann: no, that's weird, that path isn't supposed to exist
07:17marcanat least not the way I set it up
07:17the_lanetly_052 has joined #asahi-dev
07:17marcanit does exist in macOS but it only contains the EFI booter
07:18marcanwait, is this <12.3?
07:18marcanit says 12.3 but I think older bless versions did that?
07:19GlanzmannThis was from a user yesterday.
07:28doggkruse has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
07:52aycippo[m] has joined #asahi-dev
07:57marcanturns out he was running Terminal.app under Rosetta
07:57marcanwhich causes `bless` to try to do the Intel thing instead of the Apple Silicon thing
07:57marcanthis failure mode is amazing :-)
08:01the_lanetly_052 has quit [Ping timeout: 480 seconds]
08:25kylealanhale has joined #asahi-dev
08:45riker77 has quit [Quit: Quitting IRC - gone for good...]
08:53j`eysven: are you sending out nvme today? (no pressure etc)
08:53sventhe kernel bot started screaming at me after I fixed that compile test makefile thing so I’ll have to check what I need to fix there
08:54svenand then maybe wait another ~5 hours or so to give it another chance to scream at me ;)
08:56j`eyusually missing linux/bits.h :P
08:56MajorBiscuit has joined #asahi-dev
08:56svenyeah, and restricting rtkit to 64Bit only
08:56svenand I think bitfield.h instead of bits.h this time
09:01riker77 has joined #asahi-dev
09:11rikkaa has quit [Quit: Connection closed for inactivity]
09:51the_lanetly_052 has joined #asahi-dev
09:58kameks has joined #asahi-dev
10:17Ry_Darcy_ has joined #asahi-dev
10:29Ry_Darcy_ has quit [Remote host closed the connection]
10:30svenj`ey: let's see if the bot is happier with this https://github.com/AsahiLinux/linux/commits/nvme-rfc. just need to finish the cover letter now
10:31svenhrm, and i guess that command issue lock could use a description
10:31j`eywe need some A/B testing on that :P
10:32sveni still don't understand why that lock is required. and i can't even reproduce the errors without that lock on my mini :/
10:35rikkaa has joined #asahi-dev
10:39PaterTemporalis has joined #asahi-dev
10:48m6wiq has joined #asahi-dev
10:56ExeciN[m] has joined #asahi-dev
11:09mazsven: I wonder if dma_wmb() properly orders things on this system. it expends as dmb(oshst), while the spin_lock() would have be an acquire in the IS domain.
11:10mazon its own, this lock doesn't provide much guarantee, but that's all I can think of to explain its (possible) effect.
11:14svenso the weird thing that all I should need at that point is the guarantee that the memcpy before is visible to the nvme controller. that writel there writes to a hardware FIFO anyway that should be large enough
11:15svenand without the lock on some machines the command still executes just fine (so the nvme controller saw it) but never generates a completion interrupt
11:17mazcan the nvme controller execute things without the writel() being issued if it was already processing commands?
11:17svenit can execute other commands
11:17sventhat writel tells it "please now start executing the command at index i in this array"
11:19mazso it could be that you are actually using the release effect of the unlock, forcing the write to be made visible to the controller.
11:19maz(well, not really forcing, but actually providing ordering)
11:21mazif you have an affected system at hand, I'd replace the lock/unlock with a dmb right after the writel(), just to see...
11:21sveni can't reproduce it on my systems unfortunately which makes this so much harder :(
11:22sveni'm also not sure I completely understand. what do I want to order against with an additional dmb after the writel?
11:22svenaxboe had a system that was affected though, maybe he can give it a try
11:23Axe has joined #asahi-dev
11:24mazyou want to order the writel and whatever comes after it. my hunch is that although you have ordered the write to memory with the subsequent writel(), the writel() itself can be moved far down the line as there is nothing to 'make it happen now'.
11:25mazthe unlock has *some* effects on that by only allowing sunsequen writes to be hoisted up into the lock, but the write itself is guaranteed tto be visible after the unlock.
11:27svenohh.. okay. let me think what the consequences would be if the writel happens far down the line
11:27PaterTemporalis has quit [Ping timeout: 480 seconds]
11:29kloenk has quit [Remote host closed the connection]
11:30Axe has quit [Remote host closed the connection]
11:32svenhrm, not sure there are any. I just submit a command there and then just wait until the controller puts it to the completion queue and fires an interrupt. i don't even care if the controller only sees the write seconds later.
11:33sveniirc the bug was then that the command appeard on the completion queue but no interrupt was triggered. it was only picked up after the 30 second timeout by polling that queue.
11:34mazthat's odd. if the lock solves anything, it has to be ordering, because this doesn't protect anything.
11:35svenmy other guess was that it was some kind of race condition and the lock just made it unlikely to lose that race
11:35svenbut I wasn't able to find any race
11:36sven(race condition as in "you can't submit a command when you do X with the nvme controller at the same time")
11:37svenbut then again, I can't reproduce this on my M1 at all. maybe it's just something strange that only happens on the Max/Pro
11:37mazhas anyone tried reading back from the FIFO instead of the lock?
11:38svendon't think so
11:39mazguess we need someone with an expensive laptop willing to experiment... :-/
11:39svenmarcan: ^--
11:40mazI'd offer my Studio, but I have to wait for another couple of months...
11:41svenso far I've managed to resist buying that studio ;)
11:41sveni'm glad they don't get shipped overnight. otherwise i'd have my excuse now :D
11:45chadmedim soooo tempted to flog off this j314s and buy a mac studio instead but i really need a machine i can haul to the lab :(
11:46Jamie[m]1i’m letting the sub-linear NUMA performance scaling dissuade me :)
11:46chadmedah so the M1U is NUMA already
11:47povikchadmed: you can't do that! asahi-audio depends on it
11:47chadmedah but if i got a mac studio i could make that sound nice instead!
11:47povikthere's nothing interesting unless you buy that expensive monitor
11:48povikand even then there may not be work for you
11:48chadmedthats true actually
11:48* mazis busy building a *second* serial adapter...
11:49chadmedi just want to replace my pathetic A1708-into-thunderbolt-dock "desktop" setup :P
11:50Jamie[m]1oh, do you need something tested on pro/max for that name thing sven?
11:51Jamie[m]1can try things or provide ssh if you want
11:52sventhat would be great! can you first try to just revert https://github.com/AsahiLinux/linux/commit/af81cf607423e842a6a0146e8cd35cbaf6aab178 on the asahi branch and see if nvme still works?
11:52j`eyI think axboe was running stuff like: find /, to stress it a bit?
11:54svenyeah, something like full desktop environment + compiling the kernel + find /
12:07j`eythis looks weird: devtree: 0xfffffe0012240000
12:07j`eyI cant (yet) tell what happens to the adt if you chainload
12:08j`eywell run_guest.py rather
12:08svenshould be just passed along
12:18j`eyah: virt_base: 0xfffffe0011240000
12:24kameks has quit [Ping timeout: 480 seconds]
12:25Glanzmannsven: Regarding the lock, I can reproduce it every time with that kernel config https://tg.st/u/config-2022-03-09-16k and run 'find / &> /dev/null'
12:26svenis that on a m1 or a m1 max/pro?
12:27kylealanhale has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
12:29Jamie[m]1booting the new kernel on pro now
12:29Glanzmannsven: I could reproduce it on the macbook air.
12:29Glanzmannsven: If you want I build the kernel with the spinlock removed and try to reproduce it.
12:29svenweird. I can’t reproduce it on my mini at all
12:30svenwould be interesting to see if it still happens when running under the m1n1 hv and trace_nvme.py
12:30j`eyGlanzmann: wait.. you can reproduce it with the spin lock enabled?
12:30Jamie[m]1update: not booting the new kernel, I think mkinitcpio disagrees with linux on what the modules directory should be called -_-
12:30sventhough I fear that might slow everything down too much
12:30Glanzmannj`ey: No with it **disabled**
12:31Glanzmannj`ey: I'm an early adopter so I ran into the issue very early.
12:31GlanzmannThan I raised it to axboe and he was giving me lock patch.
12:31j`eyGlanzmann: Im trying to understand if you reproduced it just now?
12:31svenwaaait…. maybe I could never reproduce it because I’m always running under the hv these daya
12:31Glanzmannj`ey: No. But if sven wants to be able to reproduce the issue **without** the lock, than I can give him a setup where he can do so.
12:32Glanzmannsven: I was running a full blown desktop. X started up but shortly after I lost all disk I/O.
12:32svenah. no. I couldn’t even reproduce it manually inside m1n1
12:32svenyeah, I can’t reproduce that on the mini
12:33Glanzmannsven: Should I try to reproduce on the mini and give you remote access or detailed instructions?
12:35Jamie[m]1sven: giving up for today, I don't understand arch's kernel/initramfs infrastructure and gotta sleep
12:37j`eysven: <3 m1n1 hv
12:37svenGlanzmann: can you try what happens when you have no spinlock but add a readl(q->sq_db); just after the writel(tag, q->sq_db);?
12:44Glanzmannsven: Okay, I'll try to reproduce the issue. If I can, I'll try that.
12:49darkapex1 has joined #asahi-dev
12:51darkapex has quit [Ping timeout: 480 seconds]
12:52chadmed has quit [Ping timeout: 480 seconds]
13:03darkapex2 has joined #asahi-dev
13:04BitcoinCandyWarrior has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
13:04darkapex1 has quit [Ping timeout: 480 seconds]
13:04BitcoinCandyWarrior has joined #asahi-dev
13:10darkapex2 is now known as darkapex
13:10BitcoinCandyWarrior has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
13:11BitcoinCandyWarrior has joined #asahi-dev
13:12Glanzmannsven: I never waited before that long, but it seems also to recover by itself: https://pbot.rmdir.de/AcIMdgAWlZpigSsaTO7Wpg
13:12svenSo that’s just without the lock, right?
13:12svencan you check what happens if you add that readl I mentioned above?
13:13Glanzmannsven: I applied this patch to reproduce the issue, that was correct? https://tg.st/u/0001-try-to-reproduce-svens-regression.patch
13:15svenmissing a ; at the end but yes
13:16GlanzmannJust noticed. Building.
13:19GlanzmannI can't reproduce it with the readl
13:21sveninteresting. can you try readl_relaxed instead of readl as well?
13:22Glanzmannsven: Like that I assume? tg.st/u/0001-13-37-sven-Glanzmann-can-you-try-what-happens-when-y.patch (press ctrl-r)
13:24qiuren[m] has joined #asahi-dev
13:26Glanzmannsven: Can't reproduce with readl_relaxed: https://pbot.rmdir.de/PF0qr6JfJv1X1sT7UPUk3A
13:27svenmaz: ^-- looks like you were correct, it's somehow ordering related. i'm still as confused as before though.
13:27BitcoinCandyWarrior has quit [Ping timeout: 480 seconds]
13:28Glanzmannsven / max: That means the cpu pipelining is reordering the instructions and issues the trigger before the data is there?
13:29svenno, the writel should ensure that the memcpy is visible to the device. the readl_relaxed afterwards just ensures that the writel is visible
13:29sveni just don't know _why_ that matters
13:30j`eysven: you can decode these right? L2C_ERR_STS: 0x11000ffc00000080
13:31svennot just me :-)
13:32j`eyah thanks
13:32Glanzmannsven: If we ever want to reproduce the issue, I put the script I used to reproduce it, here: https://tg.st/u/99989368b0df7bbaaa65816ff9f0715cbed53883a93ba65153069e7c4f89fce7_bootstrap.sh
13:32Glanzmannj`ey: So should I stay with the readl_relaxed and ping axboe if we get more iops now? :-)
13:33svenyeah, readl_relaxed should be much cheaper than disabling irqs locally. but i doubt we get more iops
13:34GlanzmannLet me test.
13:35sveni'm still confused why this makes a difference :/
13:36the_lanetly_052 has quit [Ping timeout: 480 seconds]
13:37Glanzmannsven: IIRC we had 11000 iops, now i only get avg=9734.91, but maybe I'm misrembering. Let me try my wifes laptop without the the patch.
13:44jannausven: judging by tracing dcpext/dispext are just dcp/disp instances which are not configured by iboot
13:45jannauI haven't yet managed to power the hdmi port on though
13:46Glanzmannsven: Bad news.
13:46GlanzmannOr good ones.
13:47Glanzmannsven: I just put my old kernel back and tried to reboot, guess what happened: https://tg.st/u/IMG_20220320_144608609_HDR.jpg that was with the readl_relaxed.
13:48svenjannau: nice!
13:48Glanzmannsven: And that was after I run find multiple times, did two fio runs, installed a new kernel ...
13:49JasonAntwi-Appah[m] has joined #asahi-dev
13:49Glanzmannsven: Should I work a while with the readl patch and see if I can trigger it_
14:06m6wiq1 has joined #asahi-dev
14:08m6wiq has quit [Read error: Connection reset by peer]
14:18m6wiq1 has quit [Remote host closed the connection]
14:19j`eymarcan: for RVBAR (cpu-impl-reg + 0x00) is that normal memory or MMIO?
14:22justeinkemp[m] has joined #asahi-dev
14:23j`eyyes seems so: Mapping MMIO range: 0x200000000 .. 0x300000000
14:24skipwich has quit [Quit: DISCONNECT]
14:25skipwich has joined #asahi-dev
14:47MajorBiscuit has quit [Ping timeout: 480 seconds]
14:51rikkaa has quit [Quit: Connection closed for inactivity]
15:06j`eyI have this weird u-boot thing when usin the hv, if I hit esc to stop auto boot, and then just hit enter, I always get 'Unknown command 'ry 'help''
15:06j`eyit;s like 'ry' is stuck in the hv uart
15:26kloenk has joined #asahi-dev
15:33brstream[m] has joined #asahi-dev
15:40marcanI think there's some issues with the vUART in general, Linux loses characters if I paste too fast
15:40marcanand I've also seen u-boot lose local keyboard characters?
16:26* poviktried sending files over vUART
16:26povikdidn't work
16:41cadawerum1[m] has joined #asahi-dev
16:47svenjannau: let’s maybe move this here
16:47svenso all you need to do is set atcphy->target_mode to usb3_dp
16:48svenand then there are some missing pokes that macOS does to bring up what it calls “dpphy” but they are obvious from a hv trace
16:48svenwhat I started with was literally the output of macOS debug serial + the MMIO trace copy and pasted into the driver :D
16:48svenso if you do that for the dpphy part as well it’ll probably work
16:53jannaumarcan: judging from hv trace dcpep looks very similar or identical
16:53marcanjannau: it should be 95% identical, I'm just wondering if there's a callback or two that could be added/removed
16:53marcanI mean not the ABI
16:53marcanthat is identical for sure
16:53marcanI mean what actually gets called
16:56AdwyzzOLEDEdition[m] is now known as AdryzzOLEDEdition[m]
17:02kylealanhale has joined #asahi-dev
17:07doggkruse has joined #asahi-dev
17:23nicolas17 has joined #asahi-dev
17:23jannauinteresting, dart-dispext0 has nothing mapped
17:25svenis it still locked?
17:25sveni guess xnu can use that property in the dcpext node to map the firmware data section
17:25svenbut that’s still weird that they don’t map it
17:27jannaudart-dcpext is locked and has 2 premapped regions, starting at 0 and the same size as dart-dcp
17:30svenohh… right, there’s a disp and a DCP dart
17:40alyssa has joined #asahi-dev
17:41alyssajannau: marcan: has been asking me about DCP licensing
17:41alyssaDo you agree to relicense your portions of DCP kernel to MIT?
17:41alyssa(And then when I agree, we'll change the headers and marcan will stop boycotting the patches :-p)
17:42marcanI'm not boycotting them! I just want to keep kettenis on our side :p
17:43jannaumarcan, alyssa: consider my changes to DCP as MIT licensed
17:44alyssaI, Alyssa Anne Rosenzweig, domiciled at [redacted], Ontario, hereby license my DCP driver as the "MIT" license used by other Asahi Linux kernel drivers.
17:44* alyssacuts ribbon
17:44marcanthank you!
17:45alyssawhat's keeping DCP out of asahi-dev at this point?
17:45alyssaI saw jannau did t600x bring up, and licensing is "fixed" now
17:45alyssaI guess need to agree on the m1n1 changes and fix u-boot so it works for the end users?
17:48marcantesting on everything, and I'm still not sure about that reserved regions stuff
17:49jannauthere's modeset bug resulting in 1 swap every 2 seconds or so and I'm not sure what we want to do about "HACK: increase vblank wait timeout"
17:49marcanand also just in general I might want to look at locked dart and have opinions on that :p
17:49jannauit's tested on mac mini, imac and macbook pro 14"
17:57alyssajannau: aaaand DCP is not working, yay
17:58alyssasounds like this will be "fun" to debug
18:01alyssawait PEBKAC
18:01alyssa(still not working but that one was PEBKAC)
18:04jannaualyssa: I push m1n1 (branch dcp) and linux (branch asahi-dcp) which work for me right now
18:04alyssawhat tense is 'push
18:05alyssaas in, just now and I should rebuild each?
18:06jannauas in right now, I think it's just rebases onto newer asahi upstream commits but it is the state currently working for me
18:07alyssaOn the Mini?
18:08jannauhow is it broken? I should be profficient in spotting the cause of the error by now
18:09alyssaScreen goes to black immediately, does not come back (but still backlit maybe)
18:09jannaum1 imac but except for the higher resolution I haven't seen a difference between mini and imac
18:09alyssaCorrectly boots otherwise (I can type commands "in the dark" and they work)
18:09j`eyjannau: did you get imac recently?
18:09alyssapulling a dmesg
18:09jannausounds like dart and crashed dcp
18:10alyssasounds right
18:10ore has joined #asahi-dev
18:11meenmachine has joined #asahi-dev
18:11alyssasMar 20 18:08:17 rootfs kernel: [ 3.552461] apple-dcp 231c00000.dcp: error (____ptrval____): Failed to boot RTKit: -62
18:11MikaB[m] has joined #asahi-dev
18:11alyssaMar 20 18:08:17 rootfs kernel: [ 3.554447] apple-dcp: probe of 231c00000.dcp failed with error 307044352
18:11alyssajannau: ^
18:11alyssathat's novel :v
18:12jannaubest way to find it is running it under HV with 'run_guest.py -m hv/trace_dcp.py'
18:12alyssathat's definitely something I know how to do *blink*
18:12jannaustill consistant with a crashed dart, rtkit doesn't starts
18:13alyssabut one very early on, no?
18:14alyssaI guess step 1 is disable DCP and get simple-fb to work
18:15jannauyes, happens for example if the dart setup is broken
18:15alyssa(Even with DRM_APPLE=n, simplefb doesn't work -- DART reserved mappings aren't working properly)
18:15jannaudmesg | grep 'apple-dart '
18:17meenmachine has quit [Read error: Connection reset by peer]
18:17alyssa(That's several boots worth)
18:18jannauI would have expected 'apple-dart 231304000.iommu: reserved region: IOVA [mem 0x013fc000-0x0bd07fff] PA [mem 0x9da4f0000-0x9e4dfbfff]', not sure which log level though
18:19jannaudev_info()
18:20alyssa_info, yeah
18:21alyssawill grab that..
18:21alyssawait but if the init messages are there, those should be too
18:22alyssawill grab more info
18:24jannaualyssa: you can check if the reserved mem regions are ing the dtb with 'dtc -I fs -O dts -o - /proc/device-tree | grep -A 50 reserved-memory'
18:25alyssadefinitely something I have a reasonable way to do with no monitors ;-D
18:27m6wiq has joined #asahi-dev
18:28jannauI assumed you can login via ssh
18:29alyssaOk, printk debugging and guru meditation--
18:30alyssathe reserved mappings are there, this check is failing:
18:30alyssa if (!of_device_is_compatible(iova_node, "iommu-mapping") ||
18:30alyssa !of_device_is_available(iova_node))
18:30nicolas17need to get audio fixed so you can beep debug info...
18:32alyssaprint where?
18:32alyssato linux.py?
18:46meenmachine has joined #asahi-dev
18:48King_InuYasha has joined #asahi-dev
18:56yuyichao_ has joined #asahi-dev
18:57meenmachine has quit [Quit: Textual IRC Client: www.textualapp.com]
18:57yuyichao has quit [Read error: Connection reset by peer]
18:57meenmachine has joined #asahi-dev
19:25jannausven: atc-WIP fails for me with 'dwc3 382280000.usb: failed to reinitialize core' when booted with usb device connected. both bare metal and HV
19:26svenm1 or m1 pro/max?
19:26jannaureplugging fixes it but the device is just detected as high speed device
19:26jannaumac mini
19:26sventhat's my machine as well where it just works :D
19:26sveni assume you merged the mini patch?
19:26svenand can you run it with tracing enabled and show me the dmesg
19:27sventp_printk trace_event=appletypecphy:*
19:27svenas bootargs
19:28svenand did you try both ports?
19:28svenso far i've only been using the one that doesn't have the USB PD debug crap
19:29jannauno, I forgot to merge the m1n1 change
19:29svenok. it still shouldn't fail with "failed to reinitialize core" though
19:30svenit should just fall back to usb2-only
19:34jannau"new SuperSpeed Plus Gen 2x1" after replugging, boot still fails with "failed to reinitialize core"
19:35svencan you show the full dmesg preferably with that trace_event stuff enabed?
19:36svenand I guess I should also clean up and push my m1n1 atc tracer
19:36jannauTiming O_DIRECT cached reads: 1516 MB in 2.00 seconds = 758.25 MB/sec
19:43svenphy-apple-atc 383000000.phy: tunables and/or fuses not available; only USB2 will be supported
19:43svenhow did i break that
19:44svenah, probably that one fuse that atcphy0 doesn't need
19:44sventhat's what I get for assuming my code just works there as well I guess
19:45jannauthis is with usb-pd/hw uart connected btw
19:46svenhrm, I wonder why it tries to shut down dwc3 so early
19:47meenmachine has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
19:49svenso that's why it doesn't want to do usb2 for atcphy0
19:50j`eywhat lne did you mean, it didnt link to one
19:50j`eyoh, it did, you just have to open the diff manually (line 1072)
19:50svenyeah, that one
19:51doggkruse has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
19:51j`eyif (ret == ENOENT), yeah, thats a hard one to spot
19:51sven<sven> that's what I get for assuming my code just works there as well I guess
19:51sveni've been doing this long enough, i know at this point that my code cannot be trusted :-P
19:52svenohh.... i also just realized that jannau's device is gen 2!
19:52svenso that works as well, nice.
19:52sveni was a bit concerned that gen 2 needs some of the magic pokes I've just skipped
19:53doggkruse has joined #asahi-dev
19:54svenso why does dwc3 fail to reinit the core :/
19:54svenor even more importantly, why does it even try to do that in early boot?
19:54sveni don't see any unplug event there so it shouldn't even go down that path
19:57jannau"tunables and/or fuses not available" is gone, otherwise unchanged behavior. Is it expected that it takes 5 seconds before the device is attached?
19:57svenhrm, i never checked how long it took for me
19:57sveni noticed it took a while but i assumed that was mostly because dwc3 has to recreate everything
19:58m6wiq has quit []
19:58sven~5-6 seconds for me as well, but this is a slow HDD that actually has to spin up
19:59jannauI'm asking because it's almost exactly 5 seconds
19:59svenhuh, it's actually ~5 seconds before it even says "new superspeed device". that seems wrong.
20:00jannau4.8 seconds for an usb stick
20:00svenyeah, that sounds wrong
20:01svenmaybe some of those missing pokes are required to make that part faster. i don't think there's any sleep(4.8s) anywhere in the code
20:03jannauno noticeable delay for fullspeed device and an usb-3 hub with integrated nic
20:06jannau"failed to reinitialize core" is gone when booting without usb device connected
20:06svenoh, maybe that's why I don't see it
20:06svenit's still weird that it even tries to do that though
20:09doggkruse has quit [Ping timeout: 480 seconds]
20:09sveni'll take a closer look tomorrow but it sounds like something with the usb role switch hack goes wrong
20:13m6wiq has joined #asahi-dev
20:23kylealanhale has quit [Quit: Textual IRC Client: www.textualapp.com]
20:32PaterTemporalis has joined #asahi-dev
20:38chengsun has quit [Quit: Quit]
20:38chengsun has joined #asahi-dev
20:38m6wiq has quit []
20:42meenmachine has joined #asahi-dev
21:14trouter has quit [Quit: ZNC 1.8.2 - https://znc.in]
21:16trouter has joined #asahi-dev
21:20m6wiq has joined #asahi-dev
21:42meenmachine has quit [Read error: Connection reset by peer]
21:52jannaumarcan: the minimal image has sydney and japan as mirrors in /etc/pacman.d/mirrorlist
21:54m6wiq has quit []
21:54marcanargh, is pacstrap doing that?
21:54marcandammit, yes
21:56marcanI'll have to push a hack to fix that for existing users...
21:57marcanrebuilding images now
21:58LuEvers[m]marcan: just out of interest: where does pacstrap take the url from?
21:58marcanit copies the host mirrorlist
21:58marcanI'd missed that
22:04pphilipss has joined #asahi-dev
22:11nicolas17heh good find
22:11sirn has quit [Server closed connection]
22:11sirn has joined #asahi-dev
22:23shenki has quit [Server closed connection]
22:23shenki has joined #asahi-dev
22:27abrasive has quit [Server closed connection]
22:28abrasive has joined #asahi-dev
22:34phire has quit [Server closed connection]
22:34phire has joined #asahi-dev
22:40robinp has quit [Server closed connection]
22:40robinp has joined #asahi-dev
22:41winteris that an issue since it's not using the Bunny mirror? weren't those at the bottom as fallbacks anyways?
22:43jannauthe alarm mirror list in /etc/pacman.d/mirrorlist not /etc/pacman.d/mirrorlist.asahi
22:44chengsun has quit [Quit: Quit]
22:44chengsun has joined #asahi-dev
22:57di1[m] has joined #asahi-dev
23:00yrlf has quit [Quit: The Lounge - https://thelounge.chat]
23:01yrlf has joined #asahi-dev
…