ChanServ changed the topic of #dri-devel to: <ajax> nothing involved with X should ever be unable to find a bar
mbrost_ has quit [Ping timeout: 480 seconds]
penguin42 has quit [Remote host closed the connection]
RAOF has quit [Remote host closed the connection]
ngcortes has joined #dri-devel
RAOF has joined #dri-devel
ngcortes_ has quit [Ping timeout: 480 seconds]
benjaminl has joined #dri-devel
<airlied>
okay how do I get a branch merged when CI times out marge every single time
<airlied>
dies time radeonsi-* has 4 jobs in flight
<airlied>
I'm tempted to bump the marge timeout, because merging anything that changes nir or spirv is mostly just timing out 5-10 mins before it succeeds
<zmike>
🤕
<zmike>
stoney
<airlied>
oh actually maybe this run will make it
<airlied>
cross fingers and toes
<airlied>
but I've had multiple runs in the spirv/nir space just die 5 mins off timeout boundaries
<airlied>
maybe I just got to pick a quiet time of day :-P
columbarius has joined #dri-devel
benjaminl has quit [Ping timeout: 480 seconds]
co1umbarius has quit [Ping timeout: 480 seconds]
<zmike>
that's key
<zmike>
then you can reassign immediately
swivel_ has left #dri-devel [#dri-devel]
swivel has joined #dri-devel
<kode54>
Maybe the CI system should just open itself up to being ddosed, by completely serializing jobs and only taking on one load at a time
jewins has quit [Ping timeout: 480 seconds]
libv_ has joined #dri-devel
libv has quit [Ping timeout: 480 seconds]
heat has joined #dri-devel
kxkamil2 has joined #dri-devel
kzd has quit [Quit: kzd]
kxkamil has quit [Ping timeout: 480 seconds]
ngcortes has quit [Ping timeout: 480 seconds]
mmx_in_orbit__ has quit []
Company has quit [Quit: Leaving]
yyds has quit [Remote host closed the connection]
yyds has joined #dri-devel
yyds has quit []
aswar002 has quit [Remote host closed the connection]
<kode54>
checking an apitrace log of D3D11, it appears resizing the window between fullscreen and windowed with my compositor is changing the D3D11 presentation surface size
<kode54>
I need to run an apitrace log on Xe.ko, where it crashes on startup
<kode54>
I already have a log of DXVK on i915.ko
heat has quit [Ping timeout: 480 seconds]
alpha-carinae has joined #dri-devel
idr has quit [Quit: Leaving]
Duke`` has joined #dri-devel
libv has joined #dri-devel
RAOF has joined #dri-devel
libv_ has quit [Ping timeout: 480 seconds]
Haaninjo has joined #dri-devel
ngcortes has joined #dri-devel
ngcortes has quit [Read error: Connection reset by peer]
crabbedhaloablut has joined #dri-devel
itoral has joined #dri-devel
YuGiOhJCJ has joined #dri-devel
Duke`` has quit [Ping timeout: 480 seconds]
tzimmermann has joined #dri-devel
frieder has joined #dri-devel
sima has joined #dri-devel
alpha-carinae has quit [Ping timeout: 480 seconds]
OftenTimeConsuming has quit [Remote host closed the connection]
OftenTimeConsuming has joined #dri-devel
itoral_ has joined #dri-devel
An0num0us has joined #dri-devel
fab has quit [Quit: fab]
YuGiOhJCJ has quit [Quit: YuGiOhJCJ]
xzhan34 has quit [Remote host closed the connection]
Haaninjo has quit [Quit: Ex-Chat]
fab has joined #dri-devel
lynxeye has joined #dri-devel
itoral_ has quit [Quit: Leaving]
sghuge has quit [Remote host closed the connection]
sghuge has joined #dri-devel
frieder has quit [Quit: Leaving]
bmodem has joined #dri-devel
frieder has joined #dri-devel
elongbug__ has joined #dri-devel
jmondi has quit [Ping timeout: 480 seconds]
elongbug_ has quit [Ping timeout: 480 seconds]
sima has quit [Ping timeout: 480 seconds]
bmodem has quit [Ping timeout: 480 seconds]
sarahwalker has joined #dri-devel
swalker_ has joined #dri-devel
swalker_ is now known as Guest2674
sarahwalker has quit [Ping timeout: 480 seconds]
pcercuei has joined #dri-devel
donaldrobson has joined #dri-devel
Ahuj has joined #dri-devel
rasterman has joined #dri-devel
sima has joined #dri-devel
apinheiro has joined #dri-devel
kts has joined #dri-devel
Leopold___ has quit [Remote host closed the connection]
oneforall2 has quit [Remote host closed the connection]
Leopold_ has joined #dri-devel
oneforall2 has joined #dri-devel
oneforall2 has quit [Remote host closed the connection]
oneforall2 has joined #dri-devel
BobBeck has joined #dri-devel
gerddie6 has joined #dri-devel
opotin65 has joined #dri-devel
bmodem has joined #dri-devel
itoral has quit [Remote host closed the connection]
vliaskov has joined #dri-devel
itoral has joined #dri-devel
danylo has joined #dri-devel
<karolherbst>
itoral: okay... I've dug a bit deeper and I'm less convinced about my last theory, and more convinced that the GPU is doing random read/writes. I have no idea where they come from, but generally the GPU threads are doing what they are supposed to do, but those read/writes clearly come from the launched work. It's kinda like if some threads see different/wrong values or if there is leftover state from somewhere and there are just random
<karolherbst>
things going on...
<karolherbst>
the threads generally see the right pointers (I think) and all those threads actually do write the correct/expected values. I've rewritten the test to use new buffers every time and despite those faults, it's all looking as expected
<karolherbst>
I've also added a second buffer to return the other buffers address and it's the same across all threads within a launch (and always the correct one)
<karolherbst>
it's super weird
cmichael has joined #dri-devel
kts has quit [Quit: Leaving]
kts has joined #dri-devel
<itoral>
yeah, not sure what to make of it
<itoral>
can you paste the code of the tests somewhere?
<karolherbst>
itoral: anyway, if you want to run CL stuff directly, the rusticl/v3d branch on my repo should have everything to run CL stuff with `RUSTICL_ENABLE=v3d` and then it should just work
<karolherbst>
the test is very trivial, and not much is going on
kts has joined #dri-devel
<itoral>
have you tried removing the call to clEnqueueReadBuffer? I wonder if the issue might be there rather tha in the shader
<karolherbst>
I was randomly seeing reads as well later on at the blitter buffer + 0x1000
<karolherbst>
it was kinda odd
<karolherbst>
(that's why I disabled the blitter)
<karolherbst>
but it _kinda_ feels like a problem in the shader
<karolherbst>
I've tried to replace `get_global_id(0)` with thinks like `get_local_linear_id()` to get rid of the umod lowering and then the issue I think disappeared... but then the result of the test is also wrong. Or maybe I didn't verify it enough, so I can't tell. But I wouldn't be surprirsed if there is some UB going on in the shader. It's still weird, because things seem to work :(
<karolherbst>
like... they don't seem to do anything they shouldn't do
<cheako>
tnt: Starfield just works on the steamdeck.
heat has joined #dri-devel
fab_ has joined #dri-devel
fab_ is now known as Guest2709
<tnt>
cheako: yeah, I finally got it to work on a RX6600 but had to downgrade mesa and downgrade kernel too ... apparently in recent mesa (23.1.7) they removed a workaround for amdgpu but the actual fix hasn't made it to released kernel pacakges ...
<mareko>
BG3 works too BTW
<karolherbst>
starfield has a few glitches, but not sure those are game bugs or driver/runtime ones
elongbug_ has joined #dri-devel
<cheako>
Good, then onto intel and starfield. The current state of things is the Xe driver loads the menu but not the game. Also the Xe driver does not seem stable enough for daily use. I'd like the focus to be on the i915 driver, as hopefully that's easier than getting a driver to be stable.
Peuc_ has quit [Ping timeout: 480 seconds]
<tnt>
karolherbst: heh, I had a lot of "amdgpu: SMU: I'm not done with your previous command: SMN_C2PMSG_66:0x00000028 SMN_C2PMSG_82:0x00000000" or "[drm:dc_dmub_srv_wait_idle [amdgpu]] *ERROR* Error waiting for DMUB idle: status=3" or " amdgpu 0000:07:00.0: amdgpu: GCVM_L2_PROTECTION_FAULT_STATUS:0x00000000"
fab has quit [Ping timeout: 480 seconds]
<karolherbst>
uhh.. I haven't checked dmesg at all
<tnt>
when trying to get it running, but finally found a combination of kernel/mesa that works.
<karolherbst>
I'm using proton experimental with that game btw
<karolherbst>
and didn't had to do anything
<tnt>
Oh, if you got those, you would have noticed ... it just hanged the whole GUI and had to reboot.
<karolherbst>
ahh..
<karolherbst>
no
<karolherbst>
the only issue I have is that the game randomly asserts
<karolherbst>
or crashes
Guest2709 has quit [Ping timeout: 480 seconds]
<tnt>
What kernel/mesa/gpu are you using btw ?
<karolherbst>
23.1 and 6.4 I think
<karolherbst>
maybe 6.5 built myself
<tnt>
cheako: AFAIK you should be able to fake most stuff using VKD3D env variables, question if to find what the game doesn't like. You said with i915 it said it complained about not meeting min requirements ?
<karolherbst>
6.4.13
<tnt>
23.1.0 ? or .7 ?
<karolherbst>
.7
<karolherbst>
ehh
<karolherbst>
.6 actually
<tnt>
Yeah, I had to downgrade to .6 because .7 doesn't work.
<karolherbst>
heh
<karolherbst>
maybe I shouldn't update then
<karolherbst>
I've tried with the nvidia driver, but it just freezes the game :D
<karolherbst>
like a few seconds after starting it
elongbug__ has quit [Ping timeout: 480 seconds]
<cheako>
tnt: I get a lot of things. Currently, I get a black "splash" screen and gnome telling me it's unresponsive... cpu idle.
<karolherbst>
maybe that's similiar to the nvidia problem
<tnt>
cheako: what does the proton log ends with ?
<cheako>
That's with kernel and mesa both from some git branch.
<cheako>
Has anyone ever tried using a mesa branch in a flatpak, or snap?
Ahuj has quit [Ping timeout: 480 seconds]
kts has quit []
shashanks has quit [Ping timeout: 480 seconds]
mauld has quit [Ping timeout: 480 seconds]
shashanks has joined #dri-devel
Haaninjo has joined #dri-devel
yuq825 has left #dri-devel [#dri-devel]
fab has joined #dri-devel
macromorgan has joined #dri-devel
mauld has joined #dri-devel
<mwalle>
I'm not sure it this is the correct channel, please direct me to another one you're the wrong audience. I have a dsi-to-lvds bridge (actually the TC358775) which needs to have its reset released while the DSI lanes are enabled and the data lanes are in LP-11. Is there a way to do it in linux?
An0num0us has quit [Ping timeout: 480 seconds]
kzd has joined #dri-devel
<tnt>
mwalle: that sounds like something that would be very SoC specific ...
<mwalle>
tnt: I can't follow, why should it be SoC specific? It should be fine to enable the DSI link but don't send anything on it, no?
<tnt>
mwalle: no, I meant the way to achieve this particular sequence of event :)
<mwalle>
tnt: well that was exactly my question. there is an .atomic_pre_enable, but according to the description, there is no DSI link yet. And there is a .atomic_enable which apparently has a link but it reads as that link will already stream the display content
sarnex has quit [Read error: No route to host]
<frieder>
mwalle: This is actually quite common as a requirement form those bridges. The SN65DSI84 also needs this. If the DSI host driver follows the spec and correctly implements pre_enable() and enable() you should be able to use the pre_enable_prev_first flag in the bridge driver to get the correct init order.
<mwalle>
frieder: thanks I'll try
sarnex has joined #dri-devel
<frieder>
mwalle: What is your DSI host?
<mwalle>
frieder: mediatek DSI
<frieder>
mwalle: Ok, no idea about how that is implemented.
<mwalle>
frieder: i guess it should be working correctly with the nxp one?
<frieder>
mwalle: I recently fixed it for the Samsung DSIM controller used in the i.MX8M SoCs.
a-865 has quit [Quit: ChatZilla 0.17 [SeaMonkey 2.53.17/20230727221859]]
tobiasjakobi has joined #dri-devel
tobiasjakobi has quit [Remote host closed the connection]
a-865 has joined #dri-devel
heat has quit [Remote host closed the connection]
heat has joined #dri-devel
ngcortes has joined #dri-devel
a-865 has quit [Quit: ChatZilla 0.17 [SeaMonkey 2.53.17/20230727221859]]
macromorgan has quit [Quit: Leaving]
ngcortes_ has joined #dri-devel
ngcortes_ has quit [Remote host closed the connection]
ngcortes has quit [Ping timeout: 480 seconds]
rasterman has quit [Quit: Gettin' stinky!]
Duke`` has quit [Ping timeout: 480 seconds]
gouchi has joined #dri-devel
Duke`` has joined #dri-devel
ngcortes has joined #dri-devel
crabbedhaloablut has quit []
mbrost has joined #dri-devel
heat_ has joined #dri-devel
heat has quit [Read error: No route to host]
gouchi has quit [Remote host closed the connection]
gouchi has joined #dri-devel
gouchi has quit []
gouchi has joined #dri-devel
bmodem has quit [Ping timeout: 480 seconds]
<Company>
who's the right person to pester if my new RPi 4 doesn't come up properly on F39
<Company>
unless I boot with nomodeset and use software rendering everywhere?
junaid has quit [Remote host closed the connection]
<Company>
I mean, I could try the Fedora people, but I'm tempted to blame Mesa
gouchi has quit [Remote host closed the connection]
gouchi has joined #dri-devel
<airlied>
Company: blame the kernel as well
<Company>
eglinfo: eglInitialize failed
<Company>
that doesn't sound too good
<Company>
surfaceless is available, and with the v3d driver
gouchi has quit [Quit: Quitte]
heat_ has quit [Remote host closed the connection]
heat has joined #dri-devel
An0num0us has joined #dri-devel
kts has joined #dri-devel
a-865 has joined #dri-devel
Haaninjo has quit [Quit: Ex-Chat]
a-865 has quit [Quit: ChatZilla 0.17 [SeaMonkey 2.53.17/20230727221859]]
a-865 has joined #dri-devel
elongbug_ has quit [Remote host closed the connection]
elongbug_ has joined #dri-devel
ngcortes has quit [Remote host closed the connection]
ngcortes has joined #dri-devel
alanc has quit [Remote host closed the connection]
alanc has joined #dri-devel
a-865 has quit [Quit: ChatZilla 0.17 [SeaMonkey 2.53.17/20230727221859]]
fab has quit [Quit: fab]
Duke`` has quit [Ping timeout: 480 seconds]
heat has quit [Remote host closed the connection]
sima has quit [Ping timeout: 480 seconds]
ngcortes has quit [Remote host closed the connection]
ngcortes has joined #dri-devel
idr has joined #dri-devel
An0num0us has quit [Ping timeout: 480 seconds]
ngcortes has quit [Ping timeout: 480 seconds]
ngcortes has joined #dri-devel
ngcortes has quit [Remote host closed the connection]
ngcortes has joined #dri-devel
<Company>
okay, I gave up
<Company>
the good news is that F38 works fine
<Company>
the bad news is that F38 has old Mesa
<kisak>
Fedora 38 has mesa 23.1.7 right now. That's the newest point release. By definition that's not old.
<penguin42>
Company: So, as airlied said - try blaming the kernel, try an F38 with a newer kernel or the other way
a-865 has joined #dri-devel
<Company>
oh, the mesa version on here is 23.0.1
<Company>
I guess I had assumed the F38 images are somewhat recent
<Company>
the image has 23.0.1
<Company>
I want VK_EXT_descriptor_indexing in llvmpipe, because then I can easily test support for it and non-support for it by switching the device
<HdkR>
llvmpipe descriptor indexing isn't even in a release yet is it?
<HdkR>
Since it was only merged two months ago
vliaskov has quit [Remote host closed the connection]
benjamin1 has joined #dri-devel
dviola has quit [Remote host closed the connection]
diego has joined #dri-devel
shashanks_ has joined #dri-devel
benjaminl has quit [Ping timeout: 480 seconds]
simon-perretta-img_ has joined #dri-devel
pcercuei has quit [Quit: dodo]
shashanks has quit [Ping timeout: 480 seconds]
<Company>
HdkR: I am about to find out - but I have no idea how this all works, because I suppose Mesa and Gnome/GTK use different policies for what gets released when and how
<Company>
when F38 went from 23.0.x to 23.1.x which means minors do get bumped, whatever that means
<HdkR>
Minors are quarterly releases
<HdkR>
23.2 should be out in a few weeks I think
simon-perretta-img has quit [Ping timeout: 480 seconds]
<Company>
yup, no descriptorIndexing for me
<Company>
but I managed to build mesa on my desktop, I can build it on an rpi
kts has quit [Quit: Leaving]
simon-perretta-img_ has quit [Read error: Connection reset by peer]