#
…

2024-05-08

00:04alexaltea has joined #asahi
00:09alexaltea_ has quit [Ping timeout: 480 seconds]
00:50pb17 has quit [Ping timeout: 480 seconds]
01:00KxCORP5894 has quit [Quit: Bye!]
01:02KxCORP5894 has joined #asahi
01:06rvalue has joined #asahi
01:19pb17 has joined #asahi
01:25buroa2 has quit [Quit: The Lounge - https://thelounge.chat]
01:26buroa2 has joined #asahi
01:27denysonique31 has quit [Quit: .]
01:29buroa2 has quit []
01:29buroa2 has joined #asahi
01:29denysonique31 has joined #asahi
01:31ten1572377432463050 has quit [Remote host closed the connection]
01:31ten1572377432463050 has joined #asahi
01:35opticron has joined #asahi
01:43possiblemeatball_ has joined #asahi
01:43possiblemeatball_ has quit []
01:48possiblemeatball has quit [Ping timeout: 480 seconds]
01:53shiggitay has joined #asahi
01:57Brainium has quit [Quit: Konversation terminated!]
01:57Brainium has joined #asahi
01:57eroc1990 has quit [Quit: The Lounge - https://thelounge.chat]
01:58eroc1990 has joined #asahi
02:03KxCORP5894 has quit [Quit: Bye!]
02:03KxCORP5894 has joined #asahi
02:12ten15723774324630501 has joined #asahi
02:17ten1572377432463050 has quit [Ping timeout: 480 seconds]
02:17ten15723774324630501 is now known as ten1572377432463050
02:31shiggitay has quit [Remote host closed the connection]
02:37jeisom has quit [Ping timeout: 480 seconds]
02:39kode54 has quit [Quit: The Lounge - https://thelounge.chat]
02:39KDDLB has quit [Quit: The Lounge - https://thelounge.chat]
02:40kode54 has joined #asahi
02:42KDDLB has joined #asahi
02:59Brainium has quit [Quit: Konversation terminated!]
02:59pb17 has quit [Ping timeout: 480 seconds]
03:04pb17 has joined #asahi
03:05denysonique31 has quit [Quit: .]
03:05denysonique31 has joined #asahi
03:18chadmed_ has quit [Remote host closed the connection]
03:18chadmed_ has joined #asahi
03:22chadmed_ has quit []
03:22chadmed_ has joined #asahi
03:34shiggitay has joined #asahi
03:36marvin24 has joined #asahi
03:40marvin24_ has quit [Ping timeout: 480 seconds]
04:37pb17 has quit [Ping timeout: 480 seconds]
04:59bawj_ has joined #asahi
05:00pb17 has joined #asahi
05:01bawj_does anyone know if the asahi installed UEFI environment support the UEFI graphics output protocol?
05:14bawj_i wanna test whether custom UEFI applications like that uefiirc client can boot on the M1
05:18kode54it's possible that the uefiirc isn't built for ARM64, is it?
05:18kode54also it's possible that it can't talk to the Mac's hardware
05:19nicolas17well you'd have to compile it yourself definitely
05:19nicolas17but I think it doesn't have to talk to Mac's hardware, if it only uses UEFI services, question is if u-boot provides UEFI services for Mac's hardware
05:20nicolas17I guess networking is the least likely to work :D
05:28bawj_yea i found that Das U-Boot implements only a subset of the UEFI following EBBR specs which does not really say anything about the GraphicsOutputProtocol
05:30nicolas17bawj_: if u-boot supported all the APIs you need, it's still a separate question if Asahi's version of it has the hardware-specific implementations for those APIs
05:33bawj_that's true, i guess one way is to just try
05:37jannauI assume grub's gfx terminal uses the EFI graphics output protocol. if so it works
05:40bawj_i am writing a uefi application for the M1, but i dont own an M1 right now so ive just been using QEMU
05:40bawj_jannau if so thats very promising i will try checking out their source
05:52bawj_does the grub gfx terminal work with the Asahi installed uefi environment? I see that grub could run on other output modes as well
05:57benjinsmi has quit [Read error: Connection reset by peer]
05:57benjinsmi has joined #asahi
06:03bluetailHow would I go about checking memory on asahlinux? I tried the kernel param, but it didnt give me any logs
06:21ten1572377432463050 has quit [Remote host closed the connection]
06:22ten1572377432463050 has joined #asahi
06:27rvalue has quit [Remote host closed the connection]
06:28rvalue has joined #asahi
06:29Remmy has joined #asahi
06:37Remmy has quit [Quit: Leaving]
06:47shiggitay has quit [Ping timeout: 480 seconds]
07:08u154ss has joined #asahi
07:08u154ss has quit []
07:09ddxtanx has quit [Quit: Konversation terminated!]
07:22j`eybluetail: then maybe it was fine?
07:22bluetailj`ey it finished in 20 minutes
07:22bluetailIt cannot possibly had done a equivalent test
07:25PaulFertserThere's also "mtest" in u-boot.
07:27bluetailI'll try that!
07:28bluetailPaulFertser it says 'mtest' command not found when entered in m1ni
07:28PaulFertserAlso, if you do not load anything non-essential almost all of the memory will be available to Linux userspace, and you could try https://linux.die.net/man/8/memtester
07:29bluetailI try the memtester
07:29PaulFertserbluetail: probably this U-boot binary was compiled without this command, why not, U-boot is highly configurable.
07:30PaulFertserbawj_: btw, UEFI graphics is not so much a protocol rather static information about current linear framebuffer configuration.
07:30gladiac is now known as Guest4860
07:30gladiac has joined #asahi
07:33bluetailissued: sudo memtester 11G 1; # I will now wait if it finds anything.
07:35ten1572377432463050 has quit [Remote host closed the connection]
07:35PaulFertserbawj_: I think if you want networking for a UEFI app it's possible with U-Boot with one of the supported USB Ethernet adapters.
07:35ten1572377432463050 has joined #asahi
07:35PaulFertserbluetail: btw, why are you suspecting a hw issue?
07:35bluetailPaulFertser because two disks of my icybox kept being ejected and lots of USB errors. I never had this before.
07:36bluetailAlso it was fine when on archlinux
07:36bawj_PaulFertser: i will probably not need networking for the application i am building, just some way to display BMPs on the M1 screen
07:36bluetailIts since Fedora
07:36Guest4860 has quit [Ping timeout: 480 seconds]
07:37PaulFertserbawj_: btw, it's not like you can't use any popular ARM64 system in Qemu with U-boot to try to see how your app works with U-Boot's limited UEFI implementation.
07:37bluetailI am considering replacing my m1 mac, m1ni anyways has issues with it
07:38bluetailwith the icybox
07:38bluetailits a known issue, right now, theres a workaround implemented, which I hadnt had before
07:39bluetailin any case, glad to dump it, it's not a 'real machine', and apparently more issues than with a normal setup...
07:39PaulFertserbluetail: dump for what?
07:39PaulFertserI mean what's normal setup?
07:39bluetaila workstation
07:39bluetailmy m1 mac mini was just serving a nas purpose
07:39PaulFertserMac workstation?
07:40bluetailsome supermicro board with a xeon or a threadripper or so
07:40bluetailwhy are there no w680 type on 790 :/
07:40bluetailand of course, real ECC
07:42PaulFertserRack servers are nice for datacentres but too noisy for a living room.
07:42bluetailI dont want a rackserver
07:42bluetailI would get a big tower
07:43PaulFertserSo you want a big tower to use as a NAS? :)
07:43bluetailand maybe an external case for 40 hdd
07:43bluetailI am going to add it to one machine
07:43bluetailwith an HBA
07:44bluetailmaybe the m1 mac can be helpful if Fex runs wine runs java or something silly experiments like that
07:45stintelPaulFertser: so put it in the kitchen ;)
07:45bluetailPaulFertser I currently have a 5800x3D + AMD 6950XT
07:45PaulFertserbluetail: what's the workaround btw, can you share a link?
07:46bluetailPaulFertser the workaround? The team behind m1ni specifically handled the icybox
07:46bluetailinstead of crashing completely when its connected to a usb c port upon boot, it now probes all usb devices
07:46bluetailits a long well-known issue
07:47bluetailin any case, my usual mainrig doesnt have enough PCIe lanes
07:47pb17 has quit [Ping timeout: 480 seconds]
07:47PaulFertserbluetail: but once Linux is booted the hypervisor shouldn't affect any kind of interaction with the USB Host Controller anyhow, right? So how is this relevant?
07:48bluetailI probably should get a second GPU that does GPU partitioning so I can have smooth VMs
07:48bluetailPaulFertser I wouldn't know what kind of magic was implemented. In any case, if USB C was to be used, the device had to be attached after boot
07:49bluetailNow with Fedora running, I seem to get regular USB issues, I am currently running a repair run from my mainrig for that array, I do have lots of backups
07:49bluetailsuch a run takes easily a week
07:50bluetailjannau know anything? You were at least on that thread.
07:50PaulFertserbluetail: neither m1n1 source code nor commit log contain anything about "icy".
07:50bluetailthats awkward
07:51bluetailThen it may be Apples firmware update
07:51bluetailSince I reinstalled, I had chosen the latest base image
07:51bluetail( via idevicerestore )
07:51bluetailthen in mac os, I did the usual curl alx.sh | sh or similar
07:52PaulFertserbluetail: so did you file a ticket with kernel logs from those USB drop outs? Also are you sure it's not a power supply issue?
07:53bluetailPaulFertser I did not file anything. It seems to be btrfs protecting the data, which somehow causes usb errors to appear. But its unlikely that the HDD's are dead. Theres no SMART log. And its 2 disks for parity in the array.
07:54j`eyit would have been u-boot, not m1n1
07:54j`eythere were plenty of USB fixes in u-boot
07:54bluetailBasically, async page read <number> out of <number> or something like that
07:54PaulFertserj`ey: a fix is not a workaround and u-boot is completely out of the picture once the kernel boots, unlike m1n1.
07:55bluetailSorry for the wrong words, Paul
07:55PaulFertserbluetail: devil's in the details...
07:55bluetailIn any case, its strange, and those issues disappeared using a different device to handle the RAID...
07:55j`eyPaulFertser: the bit they said m1n1 fixed was about booting with USB devices attached
07:56bluetailMaybe there was degradation, and the issue in the RAID just wasnt fixed. But seeing each day that 2 disks are dropped, I just dont feel good about it
07:57bluetailbtrfs scrub never found anything, too
07:57bluetailI disabled all usb power saving stuffs, too
07:57bluetailIts the first thing I do before mounting
07:57PaulFertserUSB-level errors are no good ever but shouldn't be related to btrfs or anything like that
07:57PaulFertserBut without kernel log one can't be sure it's a USB error even.
07:57bluetailI also have replaced the usb cable, too
07:57bluetailI can provide a log, but it will be days old
07:58PaulFertserAre the disks essentially powered by mac itself or is there an additional power supply adapter?
07:58bluetailthere is a dedicated power supply for the 10 bay 3.5" usb disk enclosre
07:58bluetailiirc its around 400W
08:01PaulFertserbluetail: a log that's days old is still much better than no log at all.
08:02bluetailsomehow it doesnt like, finish
08:02bluetailjournalctl --since "2024-01-01" --until "2024-05-30" > logs.txt
08:02bluetailis there something wrong with it?
08:02bluetailwait, it finished finally
08:02stintelit grew so large, heavily fragmented, hence super slow to read
08:04bluetailIs that even the correct log.... https://0x0.st/X8mf.txt
08:08PaulFertserbluetail: I see no USB errors but I see "attempt to access beyond end of device sda: rw=524288, sector=39063650176, nr_sectors = 32"
08:08bluetailsimilar issues appeared in dmesg
08:08bluetailand afterwards, the disks just went offline
08:08bluetailand lots of usb errors
08:08bluetailbut it isnt recorded. Thats weird
08:08PaulFertserReading past end of device isn't supposed to not generate an error.
08:11bluetailsmartctl doesnt report anything useful, either
08:11bluetailthere are no corruption errors, either
08:13PaulFertserUSB packets have CRC so silent data corruptions on USB level shouldn't be practically possible.
08:16bluetailIn that case I am going to assume a btrfs issue and after the btrfs filesystem repair, I try again.
08:17bluetaildid you see: Apr 16 00:39:53 archm1 kernel: BTRFS info (device dm-4: state E): forced readonly
08:17PaulFertserThat's assuming your logs have full information. From what you show it looks like there's no issue detected at all anyhow on any level until suddenly access beyond the end is made.
08:18bluetailand before that ... "Apr 16 00:39:53 archm1 kernel: usb 4-1.4: USB disconnect, device number 10"
08:18bluetailthe thing is, this is a raid1c3 (three disks)
08:19PaulFertserHuh that's another day and another problem.
08:19PaulFertserApr 16 00:39:17 archm1 kernel: apple-dart 502f80000.iommu: translation fault: status:0x81000404 stream:1 code:0x404 (unknown) at 0xffda4080
08:19pb17 has joined #asahi
08:19PaulFertserIt might have started with that.
08:20PaulFertserAnd then 30 seconds later exactly the hell broke loose.
08:21PaulFertserThose apple-dart errors look scary and probably that's what you need to discuss with the devs.
08:24bluetailmemtester didnt found a issue
08:25bluetailI prob gonna make multiple runs ...
08:26PaulFertsertranslation faults are bad mkay?
08:26bluetailcan you elaborate? I could google this, if not.
08:27matteo has joined #asahi
08:28PaulFertserI guess you should report instances of those as a github ticket. It's strange they only affect the xhci controller in your testing but it's up to the real devs to judge what other data or tests might be useful.
08:29bluetailthe real devs are here
08:29PaulFertserThe devs here should be able to give a better advice, yes.
08:29bluetailBefore submitting a report, I'd like to know what else is needed
08:29bluetailI am here, anyways
08:29bluetailNot just leaving like those silly guests
08:33Mrmaxmeier has quit [Quit: The Lounge - https://thelounge.chat]
08:33Mrmaxmeier has joined #asahi
09:05bluetailI do wonder though
09:06bluetailI did force 4k pages for the disks since I also use it on a normal x86/x64 machine
09:06bluetailSince the m1 mac operates at 16k pages, it wouldn't be unthinkable that it tries to use 16k pages, even if specified at 4k
09:09PaulFertserbluetail: 4k should be good
09:10PaulFertserAnd now it's default either way
09:13aus7 has joined #asahi
09:14matteo has quit [Remote host closed the connection]
09:21aus has quit [Ping timeout: 480 seconds]
09:21aus7 is now known as aus
09:26ten1572377432463050 has quit [Remote host closed the connection]
09:26ten1572377432463050 has joined #asahi
09:37jannauyes, "apple-dart 502f80000.iommu: translation fault: status:0x81000404 stream:1 code:0x404 (unknown) at 0xffda4080" is bad on probably explains the errors. marcan was/is seeing this on a m2 mac mini used as ceph storage box. and there was another report (I think an issue on gh)
09:38jannaumarcan afaik also uses m1 and m2 pro as storage servers and doesn't see that there. my m1 storage server is fixe as well
09:42chadmed_i also use an m2 pro mini as a server and same no dart faults here
09:43pb17 has quit [Ping timeout: 480 seconds]
09:45bluetailthis is a m1 mac mini with 16gb RAM
09:45bluetailmy first m1 mac mini was faulty, 8GB model - firmware issue potentially
09:45chadmed_ has quit [Quit: Konversation terminated!]
09:45bluetailthere was a badge of bad units, I think apple messed up big time, but who knows
09:46PaulFertserIn this case it's "Apple Mac mini (M1, 2020)" running 6.6.3 Fedora
09:46bluetailessentially, the issue with the 8gb model was a kernel panic on use
09:49bluetailThanks Paul
09:49bluetailI do think apple eventually fixed aforementioned issue with the 8GB models with a firmware update ...
09:51chadmed has quit [Remote host closed the connection]
09:52chadmed has joined #asahi
09:58pb17 has joined #asahi
10:04rvalue has quit [Ping timeout: 480 seconds]
10:07maxmatteo has joined #asahi
10:08maxmatte_ has joined #asahi
10:09maxmatte_ has quit []
10:15maxmatteo has quit [Ping timeout: 480 seconds]
10:16matteo has joined #asahi
10:24f_ has joined #asahi
10:42chadmed has quit [Quit: Konversation terminated!]
10:43chadmed has joined #asahi
11:01f_ has quit [Quit: To contact me, PM f_[xmpp] or send an email. See https://vitali64.duckdns.org/.]
11:02aradhya7 has quit [Quit: Connection closed for inactivity]
11:07matteo has quit [Remote host closed the connection]
11:23bawj_PaulFertser: i tried what u mentioned, built uboot for qemu_arm64 and ran my uefi application through it, seems like it couldnt find the GraphicsOutputProtocol from calling locateProtocol.
11:23bawj_may have reached a dead end
11:28PaulFertserbawj_: probably your u-boot was built without it?
11:31PaulFertserSo you need to build with CONFIG_LCD and run on supported emulated board.
11:32matteo has joined #asahi
11:35rvalue has joined #asahi
11:37PaulFertserI think there should be an easy way to do that but I can't tell what exactly to choose in the options. Would be really surprising if Qemu didn't support at least one board which is also supported by U-boot video drivers.
11:37timokrgr has quit [Quit: User left the chat]
11:39ten15723774324630509 has joined #asahi
11:39timokrgr has joined #asahi
11:40bawj_but the uboot i built with qemu_arm64 config already sets that flag
11:41PaulFertserbawj_: right. So probably the DT you're using doesn't define a video device?
11:42pb17 has quit [Ping timeout: 480 seconds]
11:43matteo has quit [Remote host closed the connection]
11:45ten1572377432463050 has quit [Ping timeout: 480 seconds]
11:45ten15723774324630509 is now known as ten1572377432463050
11:45jeisom has joined #asahi
11:47matteo has joined #asahi
11:54bawj_PaulFertser: you may be right, i pasted the output from uboot's fdt print here, of the dtb file dumped from qemu, which i passed to the bootefi cmd if you're willing to take a look. I dont see a video device despite passing '-device virtio-gpu-pci', unless thats the pci device in the tree. https://pastebin.com/xfqAFWZL
11:56PaulFertserbawj_: I do not think U-boot supports virtio protocol, no. I expected qemu to have emulation for some simple on-chip "video card" as integrated in many SoCs.
12:02PaulFertserbawj_: u-boot docs suggest "-serial stdio -device VGA" https://docs.u-boot.org/en/latest/board/emulation/qemu-arm.html
12:13PaulFertserAnd probably that just works with VIDEO_VESA
12:19pb17 has joined #asahi
12:41timokrgr has quit [Quit: User left the chat]
12:42timokrgr has joined #asahi
12:45matteo has quit [Remote host closed the connection]
12:46matteo has joined #asahi
12:46matteo has quit [Remote host closed the connection]
12:46matteo has joined #asahi
12:54matteo has quit [Ping timeout: 480 seconds]
13:17Brainium has joined #asahi
13:19matteo has joined #asahi
13:23matteo has quit [Remote host closed the connection]
13:23matteo has joined #asahi
13:28bawj_PaulFertser: i tried that and it works!
13:35hexchain has joined #asahi
13:36hexchain has quit []
13:46rvalue has quit [Remote host closed the connection]
13:46rvalue has joined #asahi
14:03delsol has joined #asahi
14:03pb17 has quit [Ping timeout: 480 seconds]
14:06Sellerie has quit [Quit: bye bye - ich bin crazy fly]
14:09vx has quit [Quit: G-Line: User has been permanently banned from this network.]
14:09vx has joined #asahi
14:13PaulFertserbawj_: just -device VGA and no tricks, no recompiling anything?
14:18PaulFertserbawj_: anyway, glad to hear it worked. I think it's a solid indication same would work on mac.
14:18PaulFertser(provided your app supports the needed framebuffer parameters)
14:23JayBeeFOSS has quit [Ping timeout: 480 seconds]
14:24JayBeeFOSS has joined #asahi
14:31PaulFertserbawj_: looks like it might be either x8r8g8b8 or x2r10g10b10 or r5g6b5 depending on model.
14:33pb17 has joined #asahi
14:41delsol has quit [Remote host closed the connection]
14:46rvalue has quit [Ping timeout: 480 seconds]
14:51rvalue has joined #asahi
15:05Brainium has quit [Read error: Connection reset by peer]
15:05jlco_ has quit []
15:06jlco has joined #asahi
15:37Brainium has joined #asahi
15:45shiggitay has joined #asahi
15:47f_ has joined #asahi
15:51cylm has joined #asahi
16:00c512l has joined #asahi
16:01c512l has quit []
16:04bawj_PaulFertser: yea no recompiling needed thanks for all the ideas!
16:07shiggitay has quit [Ping timeout: 480 seconds]
16:10zalyx2 has quit [Quit: later alligator]
16:11zalyx2 has joined #asahi
16:11pb17 has quit [Ping timeout: 480 seconds]
16:13zalyx2 has quit []
16:24zalyx2 has joined #asahi
16:25ipatch has quit [Ping timeout: 480 seconds]
16:32ipatch has joined #asahi
16:46Sellerie has joined #asahi
16:47bawj_ has quit [Ping timeout: 480 seconds]
16:54pb17 has joined #asahi
17:01ipatch_ has joined #asahi
17:02ipatch has quit [Ping timeout: 480 seconds]
17:14c10l has joined #asahi
17:14lawrence has joined #asahi
17:16ipatch_ has quit [Ping timeout: 480 seconds]
17:24ipatch has joined #asahi
17:27matteo has quit [Remote host closed the connection]
17:30DarkShadow44 has quit [Quit: ZNC - https://znc.in]
17:30DarkShadow44 has joined #asahi
17:36lawrence has quit [Quit: The Lounge - https://thelounge.chat]
17:38matteo has joined #asahi
17:40lawrence has joined #asahi
17:46matteo has quit [Ping timeout: 480 seconds]
17:49cylm_ has joined #asahi
17:50f_ is now known as f_|afk
17:51cylm has quit [Ping timeout: 480 seconds]
17:52f_|afk is now known as f_
17:54matteo has joined #asahi
17:58Brainium has quit [Ping timeout: 480 seconds]
18:02matteo has quit [Ping timeout: 480 seconds]
18:13matteo has joined #asahi
18:22matteo has quit [Ping timeout: 480 seconds]
18:31DarkShadow44 has quit [Quit: ZNC - https://znc.in]
18:31DarkShadow44 has joined #asahi
18:40pb17 has quit [Ping timeout: 480 seconds]
18:41pb17 has joined #asahi
18:46matteo has joined #asahi
18:57matteo has quit [Ping timeout: 480 seconds]
19:00cylm_ has quit [Read error: Connection reset by peer]
19:03cylm has joined #asahi
19:06matteo has joined #asahi
19:10Luj has quit [Quit: Ping timeout (120 seconds)]
19:10Luj has joined #asahi
19:15matteo has quit [Ping timeout: 480 seconds]
19:29matteo has joined #asahi
19:43matteo has quit [Ping timeout: 480 seconds]
20:00nickchan has quit [Quit: ZNC 1.8.2+deb3.1 - https://znc.in]
20:00nickchan has joined #asahi
20:06f_ has quit [Quit: To contact me, PM f_[xmpp] or send an email. See https://vitali64.duckdns.org/.]
20:08matteo has joined #asahi
20:13hightower2 has joined #asahi
20:20matteo has quit [Ping timeout: 480 seconds]
20:34pb17 has quit [Ping timeout: 480 seconds]
20:42darkapex has quit [Remote host closed the connection]
20:42darkapex has joined #asahi
20:44___nick___ has joined #asahi
20:45matteo has joined #asahi
20:50cylm has quit [Quit: WeeChat 4.2.2]
20:51cylm has joined #asahi
20:53matteo has quit [Ping timeout: 480 seconds]
20:53roxfan2 has joined #asahi
20:57roxfan has quit [Ping timeout: 480 seconds]
20:58hightower2 has quit []
21:02matteo has joined #asahi
21:03pb17 has joined #asahi
21:03zzywysm_ has joined #asahi
21:08zzywysm has quit [Ping timeout: 480 seconds]
21:11matteo has quit [Ping timeout: 480 seconds]
21:19matteo has joined #asahi
21:31DarkShadow44 has quit [Quit: ZNC - https://znc.in]
21:31DarkShadow44 has joined #asahi
21:44matteo has quit [Ping timeout: 480 seconds]
21:45ddxtanx has joined #asahi
21:55matteo has joined #asahi
22:00cylm has quit [Ping timeout: 480 seconds]
22:01roxfan2 is now known as roxfan
22:05matteo has quit [Ping timeout: 480 seconds]
22:13matteo has joined #asahi
22:13hightower2 has joined #asahi
22:22matteo has quit [Ping timeout: 480 seconds]
22:27matteo has joined #asahi
22:56___nick___ has quit [Ping timeout: 480 seconds]
23:05pb17 has quit [Remote host closed the connection]
23:05pb17 has joined #asahi
23:13ten1572377432463050 has quit [Remote host closed the connection]
23:13ten1572377432463050 has joined #asahi
23:29hightower3 has joined #asahi
23:30buroa2 has quit [Ping timeout: 480 seconds]
23:34hightower2 has quit [Ping timeout: 480 seconds]
23:44matteo has quit [Remote host closed the connection]
23:55buroa2 has joined #asahi
…