ChanServ changed the topic of #linux-msm to:
jnn has joined #linux-msm
jn has quit [Ping timeout: 480 seconds]
jnn has quit [Ping timeout: 480 seconds]
jn has joined #linux-msm
marvin24_ has joined #linux-msm
marvin24 has quit [Ping timeout: 480 seconds]
cxl000 has joined #linux-msm
pevik has joined #linux-msm
pevik has quit [Read error: Connection reset by peer]
pevik has joined #linux-msm
pevik has quit []
prawn has quit [Server closed connection]
jhovold has joined #linux-msm
calebccff has quit [Server closed connection]
calebccff has joined #linux-msm
eodcat has quit [Server closed connection]
eodcat has joined #linux-msm
srinik has quit [Killed (NickServ (Too many failed password attempts.))]
srinik has joined #linux-msm
<pundir> hi.. am I the only one running into this sm8250 regression in v5.18 merge window? https://lore.kernel.org/all/CAMi1Hd2Sngya_2m2odkjq4fdV8OiiXsFMEX1bb807cWMC7H-sg@mail.gmail.com/
krzk has quit [Server closed connection]
krzk has joined #linux-msm
mort_ has quit [Server closed connection]
mort_ has joined #linux-msm
<Mis012[m]> aka_: hm, showing networks for a bit sounds like progress...
ajhalaney[m] has quit [Server closed connection]
ajhalaney[m] has joined #linux-msm
cmeerw[m] has quit [Server closed connection]
cmeerw[m] has joined #linux-msm
konradybcio has quit [Server closed connection]
konradybcio has joined #linux-msm
Newbyte has quit [Server closed connection]
Newbyte has joined #linux-msm
<aka_[m]> nah
pespin has joined #linux-msm
<bryanodonoghue> aka_[m]
<bryanodonoghue> looks like your firmware is crashing
<bryanodonoghue> [ 78.542374] qcom-wcnss-pil a204000.remoteproc: fatal error received: halPMU.c:64:haltACK bit not set even after 5 millisecs
<bryanodonoghue> [ 78.542406] remoteproc remoteproc1: crash detected in a204000.remoteproc: type fatal error
<bryanodonoghue> [ 78.542439] remoteproc remoteproc1: handling crash #3 in a204000.remoteproc
<bryanodonoghue> [ 78.542451] remoteproc remoteproc1: recovering a204000.remoteproc
<bryanodonoghue> are you 100% sure you are running the f/w version shipped by the vendor ?
<bryanodonoghue> I'd recommend extracting the files from the downstream image to be sure
<Mis012[m]> bryanodonoghue: do you realize that running f/w version *not* shipped by the vendor is pretty much impossible
aka_[m] has quit [Server closed connection]
aka_[m] has joined #linux-msm
alikateshethey[m] has quit [Server closed connection]
alikateshethey[m] has joined #linux-msm
fevv8[m] has quit [Server closed connection]
fevv8[m] has joined #linux-msm
<aka_[m]> It was working on 5.15 with same firmware package
<aka_[m]> And as Mis said most likely it won't load if it's not signed by vendor
jojo_autoboy[m] has quit [Server closed connection]
jojo_autoboy[m] has joined #linux-msm
z3ntu has quit [Server closed connection]
z3ntu has joined #linux-msm
mint[m] has quit [Server closed connection]
mint[m] has joined #linux-msm
Syboxez[m] has quit [Server closed connection]
Syboxez[m] has joined #linux-msm
undev[m] has quit [Server closed connection]
undev[m] has joined #linux-msm
vknecht[m] has quit [Server closed connection]
vknecht[m] has joined #linux-msm
wfranken[m] has quit [Server closed connection]
wfranken[m] has joined #linux-msm
shawnguo has joined #linux-msm
<konradybcio> Trying to load incorrect firmware would likely cause a "secure bite" and a hard reboot / hard stall on android devices
<konradybcio> Or at least that's my experience
<Mis012[m]> well, that's assuming that the incorrect firmware is not signed appropriately :P
<Mis012[m]> I mean why would it be, but still
pg12 has quit [Quit: pg12]
pg12 has joined #linux-msm
<bryanodonoghue> aka_[m] so this is with 5.17-xx ? versus 5.15 previous
<bryanodonoghue> can you point me at your kernel tree ?
pg12 has quit [Quit: pg12]
<aka_[m]> bryanodonoghue: I'm going to check something today, on 8953 there was comment for amdpu thing because it had issues with 3660b or something
<aka_[m]> Gonna try if u commenting changing anything
<aka_[m]> Stupid autocorrection destroy my msgs, gonna try if removing comment from amdpu will make diff
<bryanodonoghue> amdpu if it was a problem *should* only show up on an RX
<bryanodonoghue> what is pronto-v3
<bryanodonoghue> which silicon version does that cover ?
<aka_[m]> Pronto v3 seems to be used in msm8937, 56,76,53 atleast
<aka_[m]> Sireesh was about to send patches for that
<aka_[m]> I guess "new" msm8937 also sports it(429,439)
pg12 has joined #linux-msm
<Mis012[m]> bryanodonoghue: afaik Pronto is an arm9 core :P
<Mis012[m]> maybe it got upgraded to arm>9 at some point before they got rid of it, but it was arm9 on msm8.9.1.6 iirc
DavidHeidelberg[m] has quit [Server closed connection]
DavidHeidelberg[m] has joined #linux-msm
MartinBotka[m] has quit [Server closed connection]
MartinBotka[m] has joined #linux-msm
pespin has quit [Remote host closed the connection]
jhovold has quit [Ping timeout: 480 seconds]
<calebccff> qcom-q6v5-mss 4080000.remoteproc: watchdog received: DALSysLogEvent.c:172:DALLOG Device [0x0] Type [C13B2AF5] Log [C13B8C47]
<calebccff> this is a new one
<calebccff> 5.18 merge window has caused some weird crashdump issues, seemingly related to bpfloader
<bryanodonoghue> Mis012[m]
<bryanodonoghue> No I mean pronto-3
<bryanodonoghue> so far we have supported up to pronto-2
<bryanodonoghue> wcn3620, wcn3660, wcn3680
_whitelogger has joined #linux-msm