#
…

2021-11-18

00:21aidenfoxivey has joined #asahi
00:21aidenfoxivey has left #asahi [#asahi]
00:22marcanmps: did you follow the instructions to run step2.sh?
00:23marcanradnic: it does not remove m1n1 if you boot into macos
00:23marcanassuming you're using two partitions
00:23radnicRight, i thought it does because I did not see it anymore in the location I curled it to originally.
00:23marcanthe location does not matter
00:24marcankmutil will copy m1n1 to the Preboot volume and format it a certain way
00:24marcanthe original .macho file is only used when you run kmutil
00:24radnichmm, well, the original .macho is not there after a reboot
00:24marcanwhere was it originally?
00:25radnicUhhhh.. home folder of the console?
00:25marcanin 1TR? that's a ramdisk
00:25radnicAh, that explains it.
00:25radnicSo, I am poking around, out of curiousity, as to why I get that hpm0 issue, and the funny part is that it seems intial communication is OK with the chip, it only fails after it sends the SSPS command.
00:26marcanhm, that still kind of sounds like the old i2c problem :/
00:26radnicI barbarically added a bunch of extra printfs.
00:26marcanI mean that's how I debug this too :p
00:27radnicHah, I was spoiled and used with pretty debuggers.
00:27marcanwell, we have the hypervisor for that
00:27marcanthough the debug features are relatively bare-bones, it's more of a tracer
00:28marcanyou don't have the problem with hpm1, right?
00:28radnicNo, it's hpm0
00:28radnicBut they seem to be the same chip.
00:29marcanand you're connected to USB port 0? does it matter if you switch to 1?
00:29marcanthey are separate chips
00:29radnicRight, smae chip model, but different chips physically.
00:29radnicIt doesn't seem to matter.
00:29marcaninteresting
00:31marcanmaybe see if you can narrow down exactly where it fails, and also try adding some delays (delays aren't the solution but they might help reveal the nature of the problem)
00:32marcanI assume the error still happens if you chainload.py m1n1 again?
00:32marcan< radnic> Is there a simple way to update the m1n1 without thw whone tiersome boot cycle/curl/update? <- on disk no, for testing live, chainload.py
00:33radnicIt goes: ps6598x_command(dev, "SSPS", &data, 1, NULL, 0); and inside there it goes to read back the command and that is where it fails, it seems.
00:34radnicWhy would delays fix it?
00:34radnicI mean... we have 1 task.
00:34marcanlast time we had this problem it was an issue with not waiting for the read transaction to finish properly, someone added some delays and that "fixed" it (then I found the real cause)
00:34marcanif delays fix it it means we aren't waiting for something we need to wait for
00:34radnicNever chainloaded, currently I can't get it to start the USB connection.
00:34marcanbut hpm1 works?
00:35marcanso port 1 should work?
00:35radnicHmmm.. maybe? I understand only the Port 0 is the onew I can use for chainloading?
00:35marcanno, you can use any port
00:35marcanm1n1 doesn't care
00:36marcanport 0 only matters if you want serial (from another mac or a custom interface) or to DFU
00:36radnicAh, stupid me, yes, that works. :)) Did not try it so far.
00:37radnicWhere did you get the register names/locations for I2C? Reversed?
00:37marcanI'll be back later, but hopefully this helps your debugging :)
00:37marcanI2C is pasemi
00:38marcansame thing as in pasemi PowerPC chips
00:38marcanI actually have the hardware spec for it but it's not publicly available and I can't share it, unfortunately
00:38marcanbut it's the same thing in i2c-pasemi in linux (which we also use)
00:38marcanapple did make some changes though, I found a few new registers by poking around
00:39radnicCool, thanks! Will look into it.
00:53radnicHah, after chainload it looks like it's OK!
00:57radnicIt's interesting also that the I2C seems to answer with unexpected length. that is funny.
00:57radnicIt says wnat to read 4 bytes but the device wants to send 31
01:04Dcow has quit [Quit: My Mac Mini has gone to sleep. ZZZzzz…]
01:10yuyichao has quit [Ping timeout: 480 seconds]
01:59c10l has joined #asahi
02:03c10l has quit []
02:04c10l has joined #asahi
02:49yuyichao has joined #asahi
03:14bgb has joined #asahi
03:19bgb_ has joined #asahi
03:25bgb has quit [Ping timeout: 480 seconds]
03:34bgb_ has quit [Quit: WeeChat 3.3]
03:43phiologe has joined #asahi
03:47PhilippvK has quit [Ping timeout: 480 seconds]
04:48marvin24 has joined #asahi
04:51marvin24_ has quit [Ping timeout: 480 seconds]
05:09phiologe has quit [Ping timeout: 480 seconds]
06:11sailorek1234 has joined #asahi
06:40chamomile has quit [Ping timeout: 480 seconds]
07:54chamomile has joined #asahi
07:57svenfor which command?
07:57sven(or rather for which register)
07:58svenif it's for that DATA register that's expected
07:58svenbut i don't think we actually read from that one
08:08chamomile has quit [Ping timeout: 480 seconds]
08:13mpsmarcan: no, I didn't run step2.sh script. didn't know it exists and need to be run. I found it after boot to macos when looked at Linux partition and thought it was run automatically
08:14mpsI will try again when I finish my $day_job
08:16easontek has joined #asahi
08:18easontek has quit []
09:39bps has joined #asahi
09:40c10l has quit [Remote host closed the connection]
09:47marcanmps: when the installer tells you to choose the boot volume in the picker, after you do so it tells you about step2 and the steps needed to complete the installation
09:47marcandid that not show up somehow? or did the machine just reboot or shut down?
09:50mpsmarcan: I'm not sure that I saw this, maybe I didn't read all text carefully. at the end script told that everything is finished and I rebooted it
09:50Glanzmann has joined #asahi
09:50mpsin 1TR I see asahi logo with disk to select to boot from
09:50Glanzmannmarcan: I had the very same problem. I did only saw the notice for step2.sh after it rebooted, because the boot picker covered it up and rebooted afterwards.
09:50radnic@sven. I think it was the TPS_REG_CMD1 but it was like... just the once. most of the times, it does not say that. It seems to be inconsistent. This is why I suspect the device state is not always the same when we enter m1n1.
09:51mpsGlanzmann: ah, this also happened to me
09:52svenradnic: huh, TPS_REG_CMD1 should always only be 4 bytes
09:52FireFox317radnic, i had the same problem yesterday, and i'm trying to reproduce the issue but it is indeed really inconsistent. The m1n1 installed on my macbook is kinda old, so that could be a problem too.
09:52marcanmps: so when you clicked "reboot" the machine actually rebooted?
09:52mpsmarcan: yes
09:53marcanit's not supposed to do that, we do an (ugly) race to kill the boot picker before it reboots, assuming you didn't kill the installer
09:53svenfirefox317: marcan did fix some bug that resulted in the same issue a while ago so an old m1n1 would explain that
09:53marcanradnic: where exatly does it fail?
09:54marcanlike with what error code/message?
09:54mpsmarcan: I didn't 'killed' it, just selected asahi and clicked reboot
09:54marcanthe installer was still running in the terminal at that point?
09:55mpshmm, I think so, but not 100% sure now
09:55marcanif you closed it then of course it won't work
09:55marcanit's possible that sometimes it loses the race, but I've never seen it myself
09:55marcanit would be nice to find a way to abort the reboot more reliably...
09:56mpsmarcan: ok, I will try again later today when I finish with my $day_job and look more carefully at the process
09:57marcansven: I wonder if the two I2C ports are not properly interlocked
09:57marcanhypothesis: right now we do start-write-stop start-read-stop
09:57svenugh. that would be annoying
09:58FireFox317okay, i managed to get the error message again. however its super inconsistent
09:58marcannormally read txns would be more properly pipelined as start-write-repeatstart-read-stop
09:58svenat least in theory the second port is supposed to use CMD2 instead of CMD2
09:58sven*CMD2 instead of CMD1
09:58mps(my free time is 'eaten' by preparing some fixes and upgrades for next alpine linux release which will happen in a few days)
09:58marcanyes but if there is a shared register pointer, SMC could sneak in between our two transactions and change the register pointer
09:58radnicI can't reproduce it at the moment to confirm it 100% but basically, it fails when it reads back the TPS_REG_CMD1. I added extra prints, so the messages are not what you would expect.
09:58svenhrm, true
09:58FireFox317its also only ever hpm0 that fails
09:59marcanI can try changing that to do a repeatstart and see if that fixes it
09:59radnicSomeone else reported hpm1 failing as well.
10:00radnicNot sure if insisting on this issue is clever on my part though. I mean, most people don't have the issue and I can still connect on the other port, and maybe I'm stealing useful resources from somewhere else.
10:00radnicI jut think it's a fun puzzle.
10:00FireFox317radnic, it fails consistently for you?
10:00radnicSometimes it's ok.
10:01radnicchainloading leads to it being OK consistently.
10:01marcanradnic: try this in i2c_smbus_read:
10:01marcan- if (i2c_xfer_write(dev, addr, 1, 1, &reg, 1))
10:01marcan+ if (i2c_xfer_write(dev, addr, 1, 0, &reg, 1))
10:04marcan(I guess you'll have to rebuild and install it...)
10:05c10l has joined #asahi
10:19FireFox317sven, with an updated m1n1 is failing much more consistently. it looks like the same issue as radnic, i'm trying marcan s fix now
10:20palmer_ has joined #asahi
10:22palmer_ has quit [Remote host closed the connection]
10:23FireFox317marcan, with your change both hpm0 and hpm1 fail to init
10:26FireFox317oh interesting, the connection with my linux box works fine, also when hpm0/1 init fails
10:37kov has joined #asahi
10:48Glanzmann has quit [Quit: EOF]
10:51Dcow has joined #asahi
10:51Dcow has quit []
11:04palmer_ has joined #asahi
11:05palmer_ has quit [Remote host closed the connection]
11:10bpalmer4[m] has joined #asahi
11:11palmer_ has joined #asahi
11:11palmer_ has quit [Remote host closed the connection]
11:11palmer_ has joined #asahi
11:12palmer_ has quit [Remote host closed the connection]
11:14FireFox317kode54, you can install m1n1 with u-boot or linux as a payload, and in that case m1n1 just acts as a bootloader and immediately loads the next stage.
11:18radnicso I just tried it and, it seems that the error is not happening anyymore? Interesting.
11:18radnicI did 3x tries.
11:18radniclet me give it a couple more spins.
11:19radnicUhh, is there a way I can persuade it to enumareate consistenly as a ACM device with the same index?
11:19radnicUpdating the variable is annoying.
11:19FireFox317radnic, latest m1n1 with the patch that marcan send? and are you on a macbook air m1 (j313)?
11:19radnicUpdating the variable is annoying.
11:20radnicJ313 is a what now?\
11:21radnicAh, no, I saw it again.
11:21radnic5th try, there it was.
11:22radnicIt's an Air3. Can I make it show anywhere the codename?
11:23kovradnic, if it's an Air M1 it's j313
11:23FireFox317m1n1 also prints it iirc
11:24radnicYes it does, saw it in the console. I see it as a j313 so, yep, there it is.
11:28radnicOk, so... totally stupid question, but chainloading does NOT change the default .macho -
11:28radnicScratch my previous claim, I need to update it manually again.
11:28FireFox317radnic, correct.
11:30Dcow has joined #asahi
11:37radnicSooo, interestin. now I updated the m1n1 fo' real with the fix from marcan... and... I don't see it anymore.
11:37radnicabout 15 tried.
11:38radnicMaybe I got really lucky.
11:38radnicyesterday it was much easyer to reproduce it TBH, than now. Even without the change.
11:38radnicBut, well, did not see it.
11:45Dcow has quit [Quit: My Mac Mini has gone to sleep. ZZZzzz…]
11:46bgb has joined #asahi
11:50radnicBut, I am confused _why_ I checked the datasheet for the chip and it says that it kind of expects the stop byte. The one that was removed. So... how come it works then?
11:51radnicI mean the change from marcan.
11:51radnic<marcan> - if (i2c_xfer_write(dev, addr, 1, 1, &reg, 1))
11:51radnic<marcan> + if (i2c_xfer_write(dev, addr, 1, 0, &reg, 1))
11:51Dcow has joined #asahi
11:51marcanradnic: it does not.
11:51radnicThat removes the stop bit sending when telling it where you want to read data off the I2C device.
11:52marcanTPS65983B
11:52marcanSr -> repeated start
11:52marcanS Unique Address Wr A Register Number A Sr Unique Address Rd A ...
11:52marcanno stop bit
11:52radnicAh, I was looking at TPS65982
11:52marcanit's the same
11:53radnicHmmm, let me find that.
11:54marcanrepeat start is the more common way of doing it
11:55radnicAh, you are correct. I read the documentation backward.
11:55radnicOk, then... if that is the case, why did it _ever_ work?
11:56kettenis_chip caches the address from the last transaction
11:57radnicBut yeah, I understood the datasheet wrong, sorry marcan.
11:58marcanthe way this works is the chip has a pointer register
11:58marcanthe write sets the pointer, the read reads from the pointer
11:58marcanit doesn't care if you issue a stop or not
11:59marcanmy hypothesis was that the chip handles i2c transactions on both i2c ports with the *same* pointer register (and of course they are interlocked, so it will clock stretch transactions on one port while another one is busy)
11:59marcana repeat start will not release the lock, but a stop will
11:59marcanallowing the SMC interface to change the read pointer
11:59marcanwhat tipped me off was that you ended up reading more bytes than expected
11:59marcanwhich suggests you read the wrong register
11:59marcanI'm about to test that hypothesis now :p
12:01kettenis_even if that isn't what's happening, the fix is right ;)
12:03kettenis_ is now known as kettenis
12:04FireFox317i can just go into 1tr and use kmutil configure-boot to update m1n1 right?
12:16FireFox317With the change from marcan applied I get the following output on a Macbook Air (j313): https://paste.debian.net/1219923
12:16FireFox317With only one usb c-a cable connected to my linux box
12:16radnicHuh, that's _with_ the change? Straaaange.
12:18radnicEven stranger you get it after chainloading.
12:18radnicNever saw it after
12:18radnicConsistenly or ocassionally?
12:18marcanfirefox317: are you sure you made the right change?
12:18FireFox317marcan, i2c.c:131 should be 'if (i2c_xfer_write(dev, addr, 1, 0, &reg, 1))' right?
12:19marcanwell, that's weird because it definitely doesn't break for me on chainload...
12:19radnicYep, that is what I have.
12:19radnicIt seems it broke _both_ devices now.
12:20FireFox317marcan, did you install the latest m1n1? or are you just chainloading?
12:20FireFox317because it seems to matter
12:20marcanchainloading
12:20radnicI can confirm that.
12:21marcanok, I think I see what you mean
12:21radnicI ahve extra cnahges as in... extra prints.
12:21radnicBut that's it.
12:23FireFox317radnic, extra prints in the i2c code might add some delays and change the behavior maybe?
12:23radnicPossible.
12:27radnicOk, got in the same state as you.
12:27radnicI had an extra delay put in the system;. Removing that, I get the same result as you do.
12:28radnicAfter i2c_smbus_write(dev->i2c, dev->addr, TPS_REG_CMD1, (const u8 *)cmd, 4) I had a
12:28radnicmdelay(100);
12:28radnicremoving that, I get the same as you reported.
12:28radnicleaving that, I never got it in 20x boots.
12:29FireFox317with 20x boots do you mean chainloading 20 times, or rebooting manually?
12:29radnicmanually rebooting.
12:29radnicNot chainloading.
12:29radnicyou can try it if it's not too big of a pain.
12:31marcanI just added some debug prints and that makes it fail again
12:31marcanyaaay timing issues
12:31marcaner sorry, work again
12:32FireFox317yeah timing issues are super annoying, and this is definitely a timing issue :(
12:33FireFox317marcan, fortunately you can repro the issue now right?
12:34bgbseems mini rarely fails
12:35marcanehhh I bet I know what the problem is
12:35marcan while (val & PASEMI_RX_FLAG_EMPTY && --timeout)
12:35marcan val = read32(dev->base + PASEMI_FIFO_RX);
12:35marcanthis is completely broken
12:35marcan10000 iteration timeout with no delay
12:35marcanguess what, it doesn't take the CPU long to poll that register 10000 times...
12:35marcanit's just timing out early
12:38marcanwell, not just that, there's more than one problem here :p
12:41danielsif only there was some convenient kernel helper you could use to poll a value with a timeout!
12:42marcandaniels: this isn't the kernel, it's m1n1
12:43FireFox317that helper is even in m1n1 :p
12:43marcanit isn't
12:43marcanit's different
12:43marcanthe kernel helper is a macro, the m1n1 helper is a function that does *not* return the register value
12:43marcanthat's a bit of a problem when you're reading from a FIFO
12:43FireFox317ahh i see, my bad
12:44danielsmarcan: ah, I take it back
12:46X-Scale` has joined #asahi
12:46marcanradnic: okay, that delay makes it work and I don't know why. time to stick a scope on the i2c pins
12:46marcan(thankfully there is a magic USB-PD command to put those on the type C pins...)
12:51X-Scale has quit [Ping timeout: 480 seconds]
12:52FireFox317yeah the mdelay(100) also works on my machine
13:01radnicHah, accidental discoveries, got to love them.
13:13radnic(thankfully there is a magic USB-PD command to put those on the type C pins...) that is soo cool, so you can see the i2c off a split cable? :))
13:14marcanoh god I think I figured it out
13:14marcanwe're DoSing the damn chip
13:14marcanthe whole thing is firmware, right?
13:14marcanwe poll for command completion so fast it never actually completes
13:14marcanit needs a delay in the command poll loop
13:15radnicIs there firmware in the I2C peripherial?? That sounds... wierd.
13:16marcanof course there is
13:16marcanit's a USB-PD controller
13:16marcanit has a huge blob of firmware
13:16marcanboth a ROM and a pile of patches/app code loaded from SPI
13:16marcanthe datasheet tells you all about that too
13:16radnicNo, wait, I thouthg we're DoS'ing it hereval & PASEMI_RX_FLAG_EMPTY && --timeout
13:16marcanno, I mean the TPS
13:17marcanthe timeout thing is also broken but unrelated
13:17radnicAh, that do while.
13:18radnicOk, funnily enough, I saw this happen in another life on another chip. Makes sense.
13:18radnicThat's why the delay there let it pass. Managed to finish its stuff.
13:19marcanjust pushed a bunch of changes
13:19marcanlet me know if that finally fixes things :)
13:19slicey has joined #asahi
13:20radnicIsn't 10ms too much? Eh, never mind, probably doesn'
13:20radnicdoesn't matter*
13:21marcandepends on whether firmware is involved in that path, which it probably is (at least time to first byte)
13:23svenoh, ouch on that DoS
13:23marcanI think the repeat-start thing made it happen more often (after I patched it to always send the command, which was my way of reproing with chainload) because that gets rid of the wait for the stop condition, so it makes the timing of the polling even tighter
13:24marcanthis thing has the curse of USB
13:24marcanthere is no way a stupid I2C device should've caused us so much grief
13:24marcanbut since it's USB-related, well, it makes sense
13:24marcanthe curse spreads
13:24svenwell, it's related
13:25svenhrm, looks like the linux driver also does the tight command completion polling loop even though there is an interrupt it could use
13:25marcanheh, yeah
13:25marcanso I think what actually happens is that when we DoS it, it never executes the commandc
13:25marcanand then after ~1 second or so, a watchdog fires
13:25marcanand the chip resets
13:26radnicUhhh.. I still get the problem. :))
13:26marcanand *that* breaks the I2C bus/read/whatever
13:26marcanradnic: dammit
13:26svenand the USB curse strikes again!
13:26radnicboth 0 and 1 case
13:26marcanwhat machine is this?
13:26radnicLet me make sure before I lead you down a chase
13:26FireFox317yep for me it also breaks
13:27FireFox317I just reinstalled the new m1n1 on my m1 air (j313)
13:27marcanwait hold on
13:27marcanargh yeah it's still broken
13:27marcanbut maybe for a different reason?
13:28radnicwell, yeah, because you put the delay at the end.
13:28radnicIt will fail after the first poll.
13:28radnicAnd exit.
13:28radnicNever retrying again?
13:29FireFox317yeah it seems to timeout really fast
13:29marcanokay yeah I'm an idiot
13:29marcanlogic's backwards
13:30marcanfixed (force pushed :p)
13:30marcanI made that rework last and I think I didn't test it lol
13:34FireFox317It works :D
13:39marcanradnic: please tell me it works :-)
13:40radnicYes, works :)
13:40radnicone question though, in here:
13:40radnic return -1;
13:40radnic if (cmd_status == TPS_CMD_INVALID)
13:40radnic if (i2c_smbus_read32(dev->i2c, dev->addr, TPS_REG_CMD1, &cmd_status))
13:40radnic return -1;
13:40radnic udelay(100);
13:40radnic } while (cmd_status != 0);
13:40radnicif the commands fails to run ,you won't reitereate, you'll just exit.
13:40marcanthat's correct
13:41radnicWHat is the point of the do while.
13:41marcanthe valid values of that read are 0 and the command code
13:41marcanTPS_CMD_INVALID means the command was rejected
13:41marcanso loop while it's the command code (which means it's neither zero nor INVALID)
13:42marcanarguably that could be rewritten as while cmd_status == cmd or whatever instead, and then check for 0/INVALID/unknown at the end
13:45radnicBut I see no case when you woudl reaiterate. Either you try once and it's OK or you exit,
13:45radnic*reiterate
13:46marcancmd_status will be neither INVALID nor 0 while the command is in progress
13:46marcantherefore it will loop
13:46radnicAh... missed that.
13:46dottedmag has left #asahi [#asahi]
13:47radnicMakes sense. Silly me.
13:59aleasto has joined #asahi
14:02Dcow has quit [Quit: My Mac Mini has gone to sleep. ZZZzzz…]
14:13sailorek1234 has quit []
14:24Dcow has joined #asahi
14:53slicey has quit [Quit: cya]
14:57FireFox317do i have to enable a specific kernel option such that it recognizes the boot args when running under the hypervisor i.e. with run_guest.py?
14:57FireFox317it doesnt seem to recocnize the boot args that i specifiy
15:09FireFox317i guess i can just put them in the dts for now
15:46phiologe has joined #asahi
15:47sailorek1234 has joined #asahi
15:49yuyichao has quit [Ping timeout: 480 seconds]
15:51gladiac is now known as Guest6204
15:51gladiac has joined #asahi
15:55Dcow has quit [Quit: My Mac Mini has gone to sleep. ZZZzzz…]
15:56Guest6204 has quit [Ping timeout: 480 seconds]
16:01j_eyfirefox317: are you using the new boot args payload?
16:03sailorek1234 has quit []
16:03FireFox317j_ey, with run_guest.py you can specify bootargs after the payload. I tried to use that. However I also looked at the m1n1 code and it looks like it only changes the bootargs in the adt, not in the fdt.
16:05Dcow has joined #asahi
16:07yuyichao has joined #asahi
16:11Dcowhow is the linux running on the m1max comparing to the m1pro?
16:12Dcowis it same state except the second ANE or something else is there?
16:13mort_it's literally the same CPU except for the memory bandwidth (which is already more than high enough for CPU-only stuff on the Pro)
16:13mort_afaik you can't really use the GPU yet in linux
16:13mort_so the main difference would be that you have 16 extra GPU cores sitting around unused
16:14_jannau_the second ane doesn't exists. I doubt anyone has drivers or uses a M1 pro/max in way that the differences would be noticeable
16:15miniIs the ANE the same between M1, M1 Pro and M1 Max?
16:15miniit looks like it is
16:16mini(I've been using an app that uses it on macOS, and there's no performance difference at all between a M1 mac mini and a M1 Max 14" MBP)
16:21marcanfirefox317: those are the xnu bootargs, not the linux bootargs. they are unrelated.
16:22marcan_jannau_: the second ane definitely exists, and is definitely disabled for some reason
16:22FireFox317marcan, yeah thanks for the clarification, i figured that out xd
16:23Dcow has quit [Quit: My Mac Mini has gone to sleep. ZZZzzz…]
16:24Dcow has joined #asahi
16:27_jannau_that's what I ment. it is currently not useable under linux even ignoring the non-existing driver
16:37neobrain has quit [Remote host closed the connection]
16:37neobrain has joined #asahi
16:39cptcobalt has quit [Read error: Connection reset by peer]
16:39nkaretnikov has quit [Read error: Connection reset by peer]
16:39brinly has quit [Read error: Connection reset by peer]
16:39tom-w has quit [Remote host closed the connection]
16:39rann has quit [Read error: Connection reset by peer]
16:39jkkm has quit [Remote host closed the connection]
16:39Chainsaw has quit [Remote host closed the connection]
16:39sjg1 has quit [Read error: Connection reset by peer]
16:39Vaughn has quit [Remote host closed the connection]
16:39arnd_ has quit [Remote host closed the connection]
16:39robher has quit [Remote host closed the connection]
16:39ovf has quit [Read error: Connection reset by peer]
16:39stblassitude has quit [Read error: Connection reset by peer]
16:39eichin has quit [Read error: Connection reset by peer]
16:39austriancoder_ has quit [Read error: Connection reset by peer]
16:39steev has quit [Read error: Connection reset by peer]
16:43Vaughn has joined #asahi
16:48eichin has joined #asahi
16:48sjg1 has joined #asahi
16:49ovf has joined #asahi
16:50stblassitude has joined #asahi
16:50tom-w has joined #asahi
16:51robher has joined #asahi
16:54leah has quit [Quit: WeeChat 3.3]
16:57yuyichao_ has joined #asahi
16:58steev has joined #asahi
16:58arnd_ has joined #asahi
16:58cptcobalt has joined #asahi
16:58austriancoder_ has joined #asahi
17:00jkkm has joined #asahi
17:00Chainsaw has joined #asahi
17:00yuyichao has quit [Ping timeout: 480 seconds]
17:00rann has joined #asahi
17:04brinly has joined #asahi
17:07boardwalkTried to do an online resize2fs on my root partition on nvme (and on t6001) and it threw some errors: https://ersatsz.com/~boardwalk/resize2fs.jpeg
17:07yuyichao has joined #asahi
17:07boardwalkPartition was unwritable until reboot, but seems to be fine & was resized.
17:08nkaretnikov has joined #asahi
17:10boardwalkAlso haven’t been able to get pcie to not report “link didn’t come up”. Increased the timeout from 1/10s to 1s from where that log is generated, and now USB comes up (wasn’t before), but I still get “link didn’t come up”. And lspci only shows the pci bridges.
17:11yuyichao_ has quit [Ping timeout: 480 seconds]
17:24marcanboardwalk: WiFi/SD require an SMC command to turn on the PCIe devices
17:28boardwalkSo no devices showing up is expected, gotcha.
17:30Dcow has quit [Quit: My Mac Mini has gone to sleep. ZZZzzz…]
17:31Dcow has joined #asahi
17:40Dcow has quit [Quit: My Mac Mini has gone to sleep. ZZZzzz…]
17:42Dcow has joined #asahi
18:08svenHmmm… those nvme errors look odd. I know that the normal error handling doesn’t work too well with ANS. We’re there any errors before that or is that timeout the first one?
18:09svenThe unwritable until reboot is because I need to fix the error recovery paths
18:10svenAFAIK ANS just doesn’t support the nvme abort command but that would be opcode 8 and not 0
18:12svenWait.. that is a 8 in the “invalid opCode” message
18:12svenso that makes sense.
18:12boardwalkYeah, sorry for the fuzzy shot, heh.
18:13boardwalkI didn’t notice any other errors before doing the resize2fs. I’ll double check.
18:14svenMakes more sense now. Some command timed out and then it dies because the normal error recovery just doesn’t work
18:18svenWhich tree is that? t6000-bringup?
18:19PhilippvK has joined #asahi
18:21svenhrm… it also looks like it tried to send the abort command to the io queue?!
18:23boardwalkt6000-bringup-work. And I don’t see any other errors in the logs (I have everything up to ‘resizing…’ in the journal, which is in that pic).
18:23phiologe has quit [Ping timeout: 480 seconds]
18:24svenAh, yes, so maybe ans does support the normal abort command after all. I just accidentally send them to the IO instead of the admin queue. Whoops.
18:25svenOr so I… ugh… it’s been too long since I looked at that code
18:25sven*or do I
18:28svenAh, nope, i was just confused.
18:29svenso I think this fails so badly because some command times out and then the error recovery path just doesn’t work correctly for ANS
18:47bgb_ has joined #asahi
18:53bgb has quit [Ping timeout: 480 seconds]
19:07X-Scale has joined #asahi
19:10[X-Scale] has joined #asahi
19:12X-Scale` has quit [Ping timeout: 480 seconds]
19:16X-Scale has quit [Ping timeout: 480 seconds]
19:18chamomile has joined #asahi
19:42Dcow has quit [Quit: My Mac Mini has gone to sleep. ZZZzzz…]
20:11___nick___ has joined #asahi
20:13___nick___ has quit []
20:14___nick___ has joined #asahi
20:27aleasto has quit [Remote host closed the connection]
20:50helltraum has joined #asahi
20:51helltraum has quit [Remote host closed the connection]
20:54helltraum has joined #asahi
20:55helltraum has quit [Remote host closed the connection]
20:58helltraum has joined #asahi
20:59helltraum has quit [Remote host closed the connection]
21:03boardwalksven: I can try and track down what times out (not sure how much of an exception circumstance it is, if you have any debugging tips would be helpful). Would implementing the recovery path difficult? (i.e. Would it be reasonable for a kernel newb to try or is it not done for a good reason?)
21:03svenit's not done because i've been too lazy :D
21:04sventhat nvme code needs quite some cleanup anyway
21:05svenso the task is more "clean up nvme and while doing that do error recovery correctly"
21:08___nick___ has quit [Ping timeout: 480 seconds]
21:11PhilippvK has quit [Quit: No Ping reply in 180 seconds.]
21:12phiologe has joined #asahi
21:41torstenvl has joined #asahi
22:07palmer_ has joined #asahi
22:07palmer_ has quit [Remote host closed the connection]
22:12torstenv_ has joined #asahi
22:17torstenvl has quit [Read error: No route to host]
22:24torstenv_ has quit [Ping timeout: 480 seconds]
22:49radnic is now known as RealityVoid
23:40RealityVoidSo, I'm tryin gto build the kernel and when I try to run the build... config restarts for some reason.
23:40RealityVoidIs that normal?
23:41RealityVoidDoing something wrong?
23:44j_eydid you run the config and build lines with the same parameters?
23:44j_eydidnt accidentally leave off 'ARCH' for example
23:45RealityVoidI just ran this:
23:45RealityVoidmake ARCH=arm64 CROSS_COMPILE=aarch64-linux-gnu- oldconfig
23:45RealityVoidand the .config is the one from thewiki page, I placed it in the root of the linux folder
23:46j_eybut it builds afterwards right?
23:47RealityVoidWell, did not let it do that, because it asked me a bunch of configuration questions. Did not seem right.
23:47j_eyshould be fine
23:47RealityVoidJust enter enter enter?
23:48RealityVoidNaah, not building, besides, at the end it says that .config was overwritten.
23:49j_eyare you running make ARCH=arm64 CROSS_COMPILE=aarch64-linux-gnu- Image.gz?
23:50j_eyor just make ARCH=arm64 CROSS_COMPILE=aarch64-linux-gnu-, or only the one with 'oldconfig'?
23:50RealityVoidI tried both of these:make ARCH=arm64 CROSS_COMPILE=aarch64-linux-gnu- oldconfig
23:50RealityVoidmake ARCH=arm64 CROSS_COMPILE=aarch64-linux-gnu- -j8 Image dtbs
23:50RealityVoidbut bpth overwrite the config.
23:55RealityVoidWhen building.
23:56steevfatal error: openssl/bio.h
23:56steevyou're missing ssl headers
23:57steevif you're on a debian system, that's libssl-dev
23:57RealityVoidFound it. Thanks.
23:58RealityVoidYes, stupid of me, sorry.
23:58steevit's all good, not everyone is used to cross compiling :)
23:59steevor kernel compiling in general
…