2024-08-09.log

+ vagrantc (~vagrant@2600:3c01:e000:21:7:77:0:50)00:26
^alexsdk 2 wants picotool 2, but picotool 2 refuses to find libusb D:00:28
- jacobk (QUIT: Ping timeout: 276 seconds) (~quassel@47-186-105-237.dlls.tx.frontiernet.net)00:40
+ jacobk (~quassel@47-186-105-237.dlls.tx.frontiernet.net)00:41
- vagrantc (QUIT: Ping timeout: 276 seconds) (~vagrant@2600:3c01:e000:21:7:77:0:50)00:43
- jacobk (QUIT: Quit: http://quassel-irc.org - Chat comfortably. Anywhere.) (~quassel@47-186-105-237.dlls.tx.frontiernet.net)01:54
joschslightly related, packaging picotool and picosdk in Debian is currently blocked by picolibc failing to build in unstable for over a week already: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=107745201:56
+ bkeys1 (~Thunderbi@45.134.140.153)02:51
- bkeys (QUIT: Ping timeout: 260 seconds) (~Thunderbi@45.134.140.153)02:52
* bkeys1 -> bkeys02:52
+ chrcav (~chrcav@user/chrcav)03:30
- nsc (QUIT: Ping timeout: 244 seconds) (~nicolas@i5C74DD26.versanet.de)03:34
+ nsc (~nicolas@i5C74DE92.versanet.de)03:36
- xktr (QUIT: Quit: leaving) (~xktr@user/xktr)03:56
+ xktr (~xktr@user/xktr)04:19
- bkeys (QUIT: Ping timeout: 265 seconds) (~Thunderbi@45.134.140.153)04:39
^alexohhhh the picotool that the sdk offers to build _specifically_ doesn't build with libusb. i guess because the sdk is using it for the elf2uf2 capacity in picotool205:20
^alex(upside down face emoji)05:20
- Gooberpatrol66 (QUIT: Ping timeout: 264 seconds) (~Gooberpat@user/gooberpatrol66)06:03
- colinsane (QUIT: Ping timeout: 255 seconds) (~colinunin@97-113-150-69.tukw.qwest.net)06:24
+ _justin_kelly7 (~justinkel@user/justin-kelly/x-6011154)07:00
- _justin_kelly (QUIT: Quit: The Lounge - https://thelounge.chat) (~justinkel@user/justin-kelly/x-6011154)07:18
* _justin_kelly7 -> _justin_kelly07:18
+ Gooberpatrol66 (~Gooberpat@user/gooberpatrol66)07:29
+ colinsane (~colinunin@97-113-70-61.tukw.qwest.net)08:17
joschminute: re "sorting is hard": maybe the patches should all be prefixed with a running counter of the form %04d as it is used by git-format-patch and in case of linux/patches6.10/rk3588-mnt-reform2/, have the first 99 reserved for collabora patches and have your patches start at 100 which makes them easily distinguishable10:14
joschor even have a linux/patches6.10/rk3588-0001-collabora directory and another linux/patches6.10/rk3588-0002-mnt directory10:15
joschbecause naming the directory "reform2" is not quite fitting as those patches apply to pocket and next as well and because it avoids having a magic "offset" to distinguish your patches from those by collabora10:15
minutejosch: yeah...10:17
minuteupgrading my rk3588 reform to 6.10.311:04
joschminute: you switched the reform-handbook default branch from master to main (thank you!) but all the merge requests are still against master11:05
joschthis means that the MR of mine to reduce the size which you set to auto-merge (thanks!) got merged into master and not the new default branch main11:05
minuteargh11:05
minuteyeah there were some issues preventing me from removing master in gitlab11:05
joschsorry11:06
joschi forgot that changing default branches does not automatically change the target branch of the open MRs11:06
minutehmm, 6.10.3 kills display on my rk3588 reform, will debug a bit later11:14
joschit's always something...11:14
minuteyeah :D11:15
joschminute: note, that i dropped two of your hdmi rk3588 patches because as far as i could tell they were upstreamed11:15
joschminute: in case you feel comfortable with that you can also (temporarily) give my account sufficient privileges for the reform-handbook repo and i can clean up the mess that my recent request of changing the default branch caused11:20
amospallaminute: what do you mean with "6.10 kills display" ?11:25
amospallaWith 6.10 Pocket (with stock motherboard) has display problems too (altough I recently changed the display so I was unsure what the cause was).11:26
amospalla(mine either boots, or Kernel prints only 3 lines and then goes blank, altough ocassionaly has done other things like kernel complaining and finally hang)11:29
minutejosch: ok, i will do that!11:34
minuteamospalla: that's an unrelated issue then as rk3588 has a different patch stack/drivers11:35
amospallayeah, that must be, if it was related I would not be alone with this.11:35
minutei need to do some more 6.10 testing today on imx8mp pocket11:36
amospallaIt must be me not connecting the ribbon correctly, I suspect.11:36
minutethe cable is fiddly yeah11:38
Zabayeah at least with some of those FFC connectors it can be pretty hard to tell if the cable is fully inserted11:40
joschminute: thank you, i lack privileges to change/delete branch properties but i was able to change the target branch of all MRs to "main" and put the size reduction commits into "main" as well11:43
joschnow re-running reform-debian-packages...11:43
- buckket (QUIT: Quit: buckket) (~buckket@vps.buckket.org)12:12
+ buckket (~buckket@vps.buckket.org)12:13
minutejosch: i made you "owner" now, does that help?12:57
joschyes! :D12:59
minuteok phew :313:00
minutenow testing 6.10.3+dsi build on rk3588 pocket13:02
minuteah :D W: unsupported machine: MNT Reform Next with RCORE RK3588 Module13:02
joschreform-handbook is all set up now :)13:03
joschhah!13:03
joschokay, sec...13:03
joschshall i add the pocket there as well now that i'm at it?13:04
joschwait, that's just a warning13:04
joschit used to be fatal but no longer13:04
joschbut lets add it nevertheless13:05
minuteyeah, it installed the wrong dtb now (the next one)13:05
minute(manually corrected that in /boot)13:05
joschthen it is missing in flash-kernel if the dtb is wrong?13:06
minuteah sorry, probably an error in my dts13:07
minuteohh, it freezes... maybe i forgot to disable vop_mmu13:07
joschit's missing in flash-kernel13:07
joschonly reform 2 and next are in the flask-kernel patch so far, not the pocket13:07
minutejosch: yes, but also in the pocket dts i wrote Next by accident13:07
minute(i mean, forgot to change to pocket)13:07
joschright13:08
joschi put rockchip/rk3588-mnt-pocket-reform.dtb into the flash-kernel patch now13:08
minutethanks13:08
joschminute: anything else you want to see in reform-tools? otherwise i do a new release right now13:09
minutejosch: not right now, release sounds good13:09
minutehmmmm, unfortunate that 6.10 doesn't work on the pocket rk358813:10
minutehmm > dw_hdmi_qp13:10
minutei think that's new, maybe that's what replaced partly the hdmi patches?13:11
minuteback to the drawing board13:12
joschpatch 0101-drm-panthor-Fix-IO-page-mmap-for-32-bit-userspace-on-64-bit-kernel.patch is the one i dropped13:12
minuteohh panthor, that's unrelated to hdmi13:13
minuteok, my old monolithic kernel works with the dtb from reform-debian-packages, so the lockup is driver related13:13
minutelets see if i have a similar lockup or what's up on my reform with rk3588 with the 6.10.3 kernel13:14
minute(i say old but that mono kernel is actually 6.11)13:14
minutehmm strange, no further output after [    1.615424] Run /init as init process13:21
minuteah, still console=tty1 in extlinux.conf13:22
chi was -just- gonna write "console=" correct? :)13:22
pandorai just noticed that my battery status in the swaybar doesn't update anymore after the last few updates (apt update/upgrade). Is that something known?13:22
minutepandora: on reform or pocket?'13:24
pandorapocket13:24
joschpandora: yes, there is a forum thread about it. Summary: waybar changed something which reveals a "bug" in the lpc firmware13:24
minuteyeah, we need to soon release pocket lpc firmware update13:24
minutewhich is in beta now13:24
minute> Timed out for waiting the udev queue being empty.13:25
minutesomething is very broken now @ rk3588 .__.13:25
joschch: yes, last october is when i learned that the last console= is the one that matters :) https://source.mnt.re/reform/reform-tools/-/commit/d9ee804f63720c550238c6790f80f0a0019c5cca13:25
minute> Begin: Loading essential drivers ... 13:25
minutebut no further output. i still can press return13:25
pandoraah thx ... gonna check the forum13:25
joschminute: being stuck at that point reminds me of this: file:///home/josch/tmp/mntre.com/reform-irc-logs/2024-07-11.log.html#t01:46:4513:26
joschpandora: https://community.mnt.re/t/after-apt-upgrade-today-battery-in-waybar-stuck-at-100/2299/2013:27
minutejosch: huh, weird13:28
minutemaybe some new essential driver is missing in initrd13:28
minutei will try to break into initramfs shell13:28
minuteaha13:30
minute> [    3.285210] Kernel panic - not syncing: Asynchronous SError Interrupt13:30
minutein > [    3.285291]  dw_hdmi_qp_update_power+0x424/0x698 [dw_hdmi_qp]13:30
minuteso it is related to hdmi driver changes13:32
minutejosch: maybe i was dreaming but didn't you say you dropped 2 hdmi related patches?13:38
joschyes, i did say it was 213:38
joschbut i checked and it seems to have been just one13:38
minutejosch: ah, and it was the 32 bit panthor fix?13:39
joschyes13:39
minuteok, then i need to look what changed in general about the hdmi driver, and where this qp driver comes from13:39
joschas usual the collabora 13:39
joschpatch stack changed everything13:39
joschlots of stuff got removed as well as added13:40
minuteaha, so i need to dig in their kernel13:40
minutedo you know which linux version they based it on?13:40
joschi didn't rebase their things, i took what they publish for 6.1013:40
joschthey have one branch per kernel release and every time there is a new release, i throw away their old patch stack and replace it by the new one13:41
minuteaha hmhm https://lore.kernel.org/all/20240807-b4-rk3588-bridge-upstream-v3-0-60d6bab0dc7c@collabora.com/13:41
minutejosch: ahhh i see13:41
minutethe new driver has > compatible = "rockchip,rk3588-dw-hdmi-qp",13:44
minutebut if i'm not mistaken our rk3588s.dtsi has compatible = "rockchip,rk3588-dw-hdmi";13:45
minuteyeah i think i see what the problem could be13:47
minutein the current 6.11 branch, rk3588s.dtsi is just 2 lines and includes a new rk3588-base.dtsi13:48
minuteand in that base dtsi you can see that the hdmi driver has changed to the -qp variant https://gitlab.collabora.com/hardware-enablement/rockchip-3588/linux/-/blob/rk3588/arch/arm64/boot/dts/rockchip/rk3588-base.dtsi?ref_type=heads#L140513:48
minutebut they forgot to update this in the 6.10 branch's rk3588s.dtsi13:48
minutehuh, but wait, the qp driver isn't in here https://gitlab.collabora.com/hardware-enablement/rockchip-3588/linux/-/tree/rk3588-v6.10/drivers/gpu/drm/rockchip?ref_type=heads13:50
minuteah, it is in the synopsys folder13:51
minutehmm ok the rockchip hdmi driver in the 6.10 stack still has a big if/else and uses compatible = "rockchip,rk3588-dw-hdmi",13:53
minuteaha! disabling hdmi1 makes it spring to life, so i probably have to adjust something about hdmi113:57
minuteok, my reform boots now with 6.10.3, that's a relief13:58
minuteok, fixing up hdmi1 node14:00
Twodisbetterminute: excellent glad things are working out14:00
minutei wonder why they didn't also just make hdmi1 compatible...14:10
minuteargh, they removed all functionality for hdmi1 from dw_hdmi-rockchip.c14:19
minuteso this is a regression14:19
minutejosch: i'm not yet sure how but we have a big issue now with the collabora patchstack starting with 6.10, they just removed all support for the second hdmi14:24
joschprobably time to contact them?14:24
joschmaybe there is some deeper context14:24
minuteyeah. i guess they just didn't think that someone needed it14:25
minutei will write to Cristian Ciocaltea and i need to revert my laptop to 6.914:25
minutemail sent14:38
joschwill u-boot be the same?14:47
joschif yes: https://source.mnt.re/reform/reform-rk3588-uboot/-/merge_requests/314:47
minutejosch: yeah14:48
joschminute: i pushed a new commit because i forgot to list the flash.bin as an artifact, you might need to re-enable the automatic-merging for that commit14:50
- bleb (QUIT: Ping timeout: 264 seconds) (~cm@user/bleb)14:53
minutejosch: there was a short discussion about rockchip hdmi1 stuff in #linux-rockchip15:06
minuteit looks like they don't wanna help with that now (different goals, wanting to make the driver smaller first to be upstreamable). we need to forward port the old version i guess15:06
joschbummer :/15:08
joschi pushed the changes needed to build pocket-reform-system-rk3588.img.gz to https://source.mnt.re/reform/reform-system-image/-/merge_requests/10515:09
minutejosch: thank you!15:10
minuteso with hdmi disabled, the pocket rk3588 stuff boots, but dsi display doesn't work yet. it's a bit complicated because i have 2 (3) different displays here that need different timings, and the success i had yesterday was with one that needs different timings than what we have in our modified jdi driver15:12
minutesre in #linux-rockchip encourages porting the hdmi bits from the 6.9 stack15:15
+ bkeys (~Thunderbi@45.134.140.153)15:15
minuteok, i'm kind of fed up with rk stuff atm, will do the 6.10. suspend testing on imx8mp now15:17
minuteresume does not work, same hang15:31
joschand rk3588-mnt-pocket-reform system image support needs a new tag in reform-rk3588-uboot and a new reform-tools release -- i'll do that later, afk now15:33
minutehmm also i had it hang twice at boot15:35
minutedidn't someone else report that 6.10.3 randomly hangs at boot on imx8mp pocket?15:36
minuteamospalla: with 6.10.3 it looks like i can successfully boot only sometimes, you have the same behavior?15:39
minuteamospalla: on imx8mp pocket15:39
amospallaminute: yes15:42
amospallaI could have downgraded kernel on my Pocket, didn't think about that.15:43
amospallaJust to test if it worked well again.15:44
minutei think 6.10.3 is definitely broken for imx8mp. i think we need to pull it and investigate @ josch before more people break their pocket reforms15:47
minuteit's weird because it seems random15:48
amospallaIt is.15:48
minutei'll delete the kernel package from the repo for now and stop repo sync process15:49
amospallaI barely use my pocket because lack of free time, feel free to ask for testing on mine if needed.15:49
amospallahaving linux-headers-6.9.12-mnt-reform-arm64 and linux-image-6.9.12-mnt-reform-arm64 installed, can I just remove the 6.10 packages and expect it to boot?15:49
minuteamospalla: i think so15:50
minutein worst case you can recover via microSD card15:50
amospallame too, yeah, let's try.15:50
minuteok, 6.10.3 packages disabled in repo15:51
minutenow having some food15:51
amospallagood profit15:51
amospallaminute: may be of your interest, on 6.10 /sys/class/power_supply/8xlifepo4/ moved to /sys/class/power_supply/BAT0/16:16
- aloo_shu (QUIT: Ping timeout: 252 seconds) (~aloo_shu@85.51.17.53)16:21
minuteamospalla: yep, that's correct and good16:24
amospallabetter :)16:24
+ aloo_shu (~aloo_shu@85.51.17.53)16:32
minuteaha, when you wait for 0.5-1 minute: 16:45
minute[   24.017317] watchdog: Watchdog detected hard LOCKUP on cpu 116:45
minute[   48.021309] watchdog: Watchdog detected hard LOCKUP on cpu 016:45
- hairu (QUIT: Remote host closed the connection) (m-uotkmd@user/hairu)16:51
+ hairu (m-uotkmd@user/hairu)16:53
minutei now have an extlinux.conf with loglevel=7 and break=modules16:55
minuteit can still hang then16:55
minutealso, i guess something is again amiss in terms of modules in the initrd. > platform 32f10000.blk-ctrl: deferred probe pending: imx8mp-blk-ctrl: failed to get noc entries16:59
minute> platform 32e60000.dsi: deferred probe pending: platform: supplier 32ec0000.blk-ctrl not ready16:59
- mjw (QUIT: Killed (erbium.libera.chat (Nickname regained by services))) (~mjw@gnu.wildebeest.org)16:59
* Guest2979 -> mjw16:59
minutealso, not sure if that's good > imx-pgc imx-pgc-domain.14: failed to power down ADB40016:59
+ Guest1027 (~mjw@gnu.wildebeest.org)17:00
minutethat's pgc_hdmimix17:01
minutelast time the fix for the noc entries stuff was this https://source.mnt.re/reform/reform-tools/-/merge_requests/71/diffs17:23
+ jacobk (~quassel@47-186-105-237.dlls.tx.frontiernet.net)17:24
minutealso, i'm rebooting source.mnt.re now17:24
minuteah, i probably had a very old reform-tools on that imx8mp machine17:31
minutethat's why some important modules did not get loaded in initramfs17:31
+ bkeys1 (~Thunderbi@45.134.140.153)17:42
- bkeys (QUIT: Ping timeout: 255 seconds) (~Thunderbi@45.134.140.153)17:43
* bkeys1 -> bkeys17:43
minuteaha, once i got a panic and the bt has [    4.287211]  imx8mp_blk_ctrl_power_on+0x3c/0x26017:50
minute> [    4.287098]  imx8mp_hdmi_power_notifier+0x3c/0xc017:50
minute> [    4.287090]  regmap_write+0x68/0x8817:50
+ andypiper (~andypiper@45.148.12.75)17:55
minutehmm something is odd, i get crash with imx8mp_hdmi_power_notifier in the trace, even if i removed hdmi_blk_ctrl: blk-ctrl@32fc0000 from dtsi18:03
+ vagrantc (~vagrant@2600:3c01:e000:21:7:77:0:50)18:09
minuteaha, wrong dtb filename m)18:21
joschminute: just read the backlog. Depending on how long you estimate you need with a fix, you might want to press the "keep" button on the last reprepro job from reform-debian-packages which produced the 6.9 kernel: https://source.mnt.re/reform/reform-debian-packages/-/jobs/525718:21
joschotherwise, the 6.9 kernel will vanish and it will be difficult to rebuild it because Debian unstable doesn't ship it anymore18:21
minutejosch: thanks, good call.. just pressed that button18:22
minutenuked all hdmi stuff from the pocket reform dts now here18:25
minuteaha, now it seems to not lock up during boot any longr18:28
minutebooted at least 5,6 times now and so far no hangs18:30
minuteyeah. it's definitely the new hdmi drivers18:32
^alexjust flashed sdk-2.0 versions of the pocket kbd and syscon firmware18:36
minuteneat18:36
^alexMR !6 in the pipe18:37
joschoh elf2uf2 is now in "picotool uf2 convert"18:42
josch^alex: thank you for testing version 2.0 of picosdk -- once picolibc builds again, i can upload it to debian as well18:44
^alexno worries18:45
josch^alex: but i don't understand why the 18:47
joschinstall-fw-dependencies.sh script is supposed to remove picotool18:47
joschi do not think that this is a good style as those who run this script might have picotool installed for other purposes18:47
^alexbecause it goes and installs picotool 2.0 into /usr/local18:47
^alexand we would rather not have two incompatible versions, one in /usr and the other in /usr/local18:48
joschi do not think that install-fw-dependencies.sh should have a "sudo make install" at all18:49
joschthe script should not have side-effects outside of the directory that it is run in other than those changes that are guarded by the package manager18:49
^alexminute, there was a set_sys_clock_48mhz() commented at the top of sysctl.c - we uncommented it and the syscon seems to run normally, was there any reason it was commented out?18:49
joschwhy not replace the "sudo apt install picotool" with "sudo apt satisfy picotool (>= 2.0)"18:49
joschthat way, it will make sure that a high-enough version of picotool is installed before proceeding18:50
^alexjosch, good question! we just reverted minute's commit to undo the picotool install, and the `sudo make install` was part of that. also we didn't know about `apt satisfy`, that's new to us :)18:50
minute^alex: at some point i had some instability that i thought was related, but it turned out not to be18:52
^alexah ok18:53
^alexi _think_ the easiest path to downclocking these 2040s is set_sys_clock_48mhz() and then using the 2.0 sdk `clock_configure_undivided` to reclock the system18:53
^alexthen we can consider powering down the system PLL and so forth18:54
^alexand that's where we're heading today18:54
^alexif our orange fluffer will step off of our keyboard :)18:55
minutenice18:56
^alexanother thing we were planning on making is a stdio driver that logs to a ring buffer, but on the keyboard that presents the problem of "how do we present it" - squeezing it onto the OLED screen a page at a time? the syscon can at least dump it via a command...18:58
^alextunnel it over the UART to the syscon?18:58
minute^alex: yeah maybe the keyboard could query log lines/pages with some offset parameter?19:00
minuteor just "give me another page"19:00
* mjw -> Guest682419:16
- Guest6824 (QUIT: Killed (copper.libera.chat (Nickname regained by services))) (~mjw@2001:1c06:2488:1400:4fd:39a7:74ac:7bae)19:16
* Guest1027 -> mjw19:16
+ Guest6824 (~mjw@2001:1c06:2488:1400:4fd:39a7:74ac:7bae)19:16
- andypiper (QUIT: Quit: My device has gone to sleep. Zzzz…) (~andypiper@45.148.12.75)19:20
+ andypiper (~andypiper@45.148.12.75)19:21
* andypiper -> andypiper[afk]19:21
* andypiper[afk] -> andypiper19:21
^alexjosch, updated the install-fw-dependencies script per comment19:55
josch^alex: thank you! Unrelated to your MR I'm also wondering about those pico_sdk_import.cmake files. As I understand it, those should be copied verbatim from upstream pico-sdk. Is my understanding correct? If yes, those could become a symlink to /usr/src/pico-sdk/external/pico_sdk_import.cmake20:09
^alexooh, we're getting pico-sdk as a package? :)20:10
joschit already exists20:10
^alexah20:10
joschbut it's not version 2.020:10
joschall blocked by https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=107745220:10
^alexgotcha20:10
minutei finally have working dsi display again with 6.10.3 on imx8mp, the issue was a bad mezzanine adapter here ;020:11
- andypiper (QUIT: Ping timeout: 252 seconds) (~andypiper@45.148.12.75)20:11
^alexevery time we hear that word, a clip from the film 'The Hudsucker Proxy' plays in our head: "forty-four!"/"not counting the mezzanine"20:12
minutehaha20:16
minuteok, i'm now turning hdmi things back on to narrow down what's causing freezes20:21
^alexjosch, personally we don't like squashing changes on merge, b/c we find the history of exploration to be important20:25
josch^alex: okay! i leave the decision up to you :)20:25
josch(unless minute has a strong opinion in either direction of course)20:25
minutenope20:30
minuteall good20:30
minuteok so hdmi is definitely the culprit @ freezing @ 6.10.3 imx8mp. 20:30
minutei wonder if and why that is happening only to us20:30
minuteor is it caused by the supposed suspend fix patch?20:31
^alexjosch, we'll probably wait to merge it until picotool 2 comes into apt20:32
minutei compared the following files in our stack to the current linux git version, and they're identical: imx8mp-hdmi-tx.c imx8mp-hdmi-pvi.c phy-fsl-samsung-hdmi.c20:42
minutebuilding a linux head kernel now with our remaining patches applied20:53
minuteto see if that also hangs20:54
- mesaoptimizer (QUIT: Ping timeout: 244 seconds) (~mesaoptim@user/PapuaHardyNet)21:00
+ mesaoptimizer (~mesaoptim@user/PapuaHardyNet)21:12
minuteso far it doesn't hang21:17
minuteand hdmi works21:17
minuteso... now the big question, what are the differences21:18
minutemonolithic vs modular kernel or actual code differences?21:18
minutehmm, imx8mp-hdmi.c is not a thing anymore21:23
minutethe 4 patches in our "hdmi" folder are now unnecessary https://source.mnt.re/reform/reform-debian-packages/-/merge_requests/5321:35
- colinsane (QUIT: Quit: bye) (~colinunin@97-113-70-61.tukw.qwest.net)21:52
minuteaha, our debian kernel, but built monolithic, also doesn't freeze21:54
+ colinsane (~colinunin@97-113-70-61.tukw.qwest.net)21:55
^alexoh no21:57
minuteso there's probably some race condition that happens due to module load order / synchronicity21:59
minutethat would explain the randomness21:59
minuteto combat this i will bake in more imx related modules into the kernel, especially those power domain related ones21:59
- jacobk (QUIT: Quit: http://quassel-irc.org - Chat comfortably. Anywhere.) (~quassel@47-186-105-237.dlls.tx.frontiernet.net)22:58
+ jacobk (~quassel@47-186-105-237.dlls.tx.frontiernet.net)23:16

Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!