ChanServ changed the topic of #armlinux to: ARM kernel talk [Upstream kernel, find your vendor forums for questions about their kernels] | https://libera.irclog.whitequark.org/armlinux
rvalue has quit [Ping timeout: 264 seconds]
nsaenz has joined #armlinux
nsaenz has quit [Ping timeout: 260 seconds]
heat_ has joined #armlinux
rvalue has joined #armlinux
apritzel has quit [Ping timeout: 256 seconds]
hanetzer has quit [Quit: WeeChat 4.1.3]
heat_ has quit [Ping timeout: 260 seconds]
jclsn has quit [Ping timeout: 268 seconds]
jclsn has joined #armlinux
sally has quit [Remote host closed the connection]
sally has joined #armlinux
cbeznea_ has joined #armlinux
amitk_ has joined #armlinux
amitk has quit [Ping timeout: 246 seconds]
monstr has joined #armlinux
mvaittin has joined #armlinux
tambarus has joined #armlinux
tambarus_ has joined #armlinux
qpla has quit [Remote host closed the connection]
qpla has joined #armlinux
iivanov has joined #armlinux
ezulian has joined #armlinux
headless has joined #armlinux
mripard has joined #armlinux
nact has quit [Remote host closed the connection]
matthias_bgg has joined #armlinux
sszy has joined #armlinux
iivanov has quit [Remote host closed the connection]
iivanov has joined #armlinux
matthias_bgg has quit [Ping timeout: 255 seconds]
nsaenz has joined #armlinux
frieder has joined #armlinux
amitk_ has quit [Remote host closed the connection]
amitk has joined #armlinux
prabhakar has quit [Quit: Connection closed]
prabhakar has joined #armlinux
prabhakarlad has joined #armlinux
Amit_T has joined #armlinux
nsaenz has quit [Remote host closed the connection]
nsaenz has joined #armlinux
nsaenz has quit [Remote host closed the connection]
nsaenz has joined #armlinux
headless has quit [Quit: Konversation terminated!]
biju has joined #armlinux
apritzel_ has joined #armlinux
<biju>
RZ/G2L plaform(arm64) doesn't boot with today's next. Not sure any seen the same issue?
<maz>
I've had a report related to the GIC, but I can't reproduce it so far.
matthias_bgg has joined #armlinux
<biju>
sorry I reverted this commit de1ff306dcf4546d6 ("genirq/irqdomain: Remove the param count restriction from select()") for fixing the boot issue on CA-55.
<biju>
maz: I will report aswell.
<maz>
please add the backtrace, a pointer to a configuration and to the DT for this machine.
<maz>
the original report didn't have much to go on (and they call that a CI infrastructure...)
<biju>
maz: Ok will do, currently I don't get any logs. will enable early prints.
<maz>
biju: are you using GICv2 ot GICv3 on your system?
<biju>
maz: gic 600 gicv3
qpla has quit [Ping timeout: 272 seconds]
<maz>
biju: ok. getting a proper backtrace would be useful.
<biju>
maz: Looks like i don't get any interrupts
<biju>
[ 0.000000] GICv3: GICv3 features: 16 PPIs
<biju>
[ 0.000000] GICv3: CPU0: found redistributor 0 region 0:0x0000000011940000
<biju>
[ 0.000000] rcu: srcu_init: Setting srcu_struct sizes based on contention.
<biju>
[ 0.000000] arch_timer: cp15 timer(s) running at 24.00MHz (virt).
<maz>
defconfig works for me here (tested in a kvmtool VM and bare-metal on SynQuacer)
<maz>
also tested in a QEMU VM (with KVM) with both ACPI and DT, no issue.
<maz>
so it is likely to be something that is relatively specific to your SoC.
<biju>
Maz: It was working till friday. that patch changes something different to gic-v3 causing issue. Anyway I will debug this issue and keep you updated.
<maz>
biju: thanks.
nsaenz has quit [Remote host closed the connection]
<broonie>
Relatively - there are some failures but not nearly so many and the arm64 ones are the debug defconfig.
<broonie>
(the GCC versions will be whatever Debian are shipping, still Debian oldstable IIRC).
monstr has joined #armlinux
sszy has joined #armlinux
heat_ has joined #armlinux
<maz>
ardb: it looks like the 52bit VA has an influence for some of the breakages. running in QEMU with defconfig explodes early in the GIC driver, while everything works if I stick to 48bits.
<biju>
maz: How fwspec->param_count is handled now? Earlier we skip fwspec->param_count == 0 for rc = h->ops->select(h, fwspec, bus_token);
olofj has quit [Ping timeout: 256 seconds]
<maz>
biju: no idea. all I can say is that it works for me, but I haven't followed the changes that tglx is making in the interrupt stack.
<biju>
OK I will report with my observation.
<maz>
the question is *why* do you pass anything that has param_count==0 the first place.
steev has quit [Ping timeout: 246 seconds]
<biju>
onmy debug, I can see arch time and lot drivers passing param_count=0 and bus_token = 1
<biju>
I guess param_count==0 is valid one
dtor has quit [Ping timeout: 268 seconds]
palmer has quit [Ping timeout: 256 seconds]
<maz>
I mean, look at the DT. not a single interrupt specifier has 0 parameters.
<maz>
so how can you end-up with that?
olofj has joined #armlinux
jluthra has quit [Ping timeout: 246 seconds]
jbowen has quit [Ping timeout: 268 seconds]
puranjaymohan has quit [Ping timeout: 260 seconds]
dianders has quit [Ping timeout: 268 seconds]
broonie has quit [Ping timeout: 246 seconds]
Tartarus has quit [Ping timeout: 268 seconds]
patersonc has quit [Ping timeout: 246 seconds]
sjg1 has quit [Ping timeout: 256 seconds]
khilman has quit [Ping timeout: 256 seconds]
mkorpershoek has quit [Ping timeout: 260 seconds]
Tartarus has joined #armlinux
dtor has joined #armlinux
jluthra has joined #armlinux
olofj has quit [Ping timeout: 268 seconds]
Forty-Bot has quit [Ping timeout: 268 seconds]
jbowen has joined #armlinux
drewfustini has quit [Ping timeout: 256 seconds]
kwilczynski has quit [Ping timeout: 246 seconds]
qyousef_ has quit [Ping timeout: 268 seconds]
khilman has joined #armlinux
palmer has joined #armlinux
dianders has joined #armlinux
nohit has quit [Ping timeout: 246 seconds]
jlinton has quit [Ping timeout: 268 seconds]
puranjaymohan has joined #armlinux
dtor has quit [Ping timeout: 264 seconds]
qyousef_ has joined #armlinux
drewfustini has joined #armlinux
robher has quit [Ping timeout: 256 seconds]
lvrp16 has quit [Ping timeout: 256 seconds]
patersonc has joined #armlinux
arnd has quit [Ping timeout: 246 seconds]
ardb has quit [Ping timeout: 246 seconds]
broonie has joined #armlinux
palmer has quit [Ping timeout: 260 seconds]
vigneshr has quit [Ping timeout: 260 seconds]
sally has quit [Remote host closed the connection]
robher has joined #armlinux
jlinton has joined #armlinux
Tartarus has quit [Ping timeout: 264 seconds]
qyousef_ has quit [Ping timeout: 256 seconds]
nohit has joined #armlinux
mvaittin has quit [Ping timeout: 260 seconds]
jbowen has quit [Ping timeout: 264 seconds]
linusw__ has quit [Ping timeout: 268 seconds]
arnd has joined #armlinux
ardb has joined #armlinux
qyousef_ has joined #armlinux
linusw__ has joined #armlinux
lvrp16 has joined #armlinux
palmer has joined #armlinux
kwilczynski has joined #armlinux
Forty-Bot has joined #armlinux
Tartarus has joined #armlinux
jluthra has quit [Ping timeout: 264 seconds]
steev has joined #armlinux
<biju>
maz: Does it mean there is an issue in IRQ subsystem as DT does not have 0 parameters?
<biju>
I see {0,1} followed by {3,1} for timer interrupts
dtor has joined #armlinux
jbowen has joined #armlinux
jluthra has joined #armlinux
olofj has joined #armlinux
heat has joined #armlinux
heat_ has quit [Ping timeout: 256 seconds]
<maz>
if that's what is happening, this looks pretty wrong. it looks like something was misbehaving before this change, and it is now obviously wrong.
lvrp16 has quit [Ping timeout: 246 seconds]
jluthra has quit [Ping timeout: 246 seconds]
olofj has quit [Ping timeout: 268 seconds]
steev has quit [Ping timeout: 256 seconds]
linusw__ has quit [Ping timeout: 246 seconds]
headless has joined #armlinux
steev has joined #armlinux
jbowen has quit [Ping timeout: 246 seconds]
Tartarus has quit [Ping timeout: 256 seconds]
lvrp16 has joined #armlinux
steev has quit [Ping timeout: 264 seconds]
jluthra has joined #armlinux
linusw__ has joined #armlinux
jbowen has joined #armlinux
Tartarus has joined #armlinux
sjg1 has joined #armlinux
steev has joined #armlinux
olofj has joined #armlinux
mkorpershoek has joined #armlinux
vigneshr has joined #armlinux
<biju>
Looks like of_phandle_args_to_fwspec count() is called after irq_find_matching_fwspec() is causing the issue.
<biju>
ie, fwspec->param_count=0 because of that
<biju>
maz: Looks like IRQ subsystem needs to fix this before applying this patch.
matthias_bgg has quit [Read error: Connection reset by peer]