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
macromorgan has quit [Quit: Leaving]
CrashTestDummy2 has joined #armlinux
CrashTestDummy3 has quit [Ping timeout: 245 seconds]
torez has quit [Remote host closed the connection]
LeSpocky has quit [Ping timeout: 265 seconds]
LeSpocky has joined #armlinux
milkylainen_ has quit [Ping timeout: 265 seconds]
amitk has joined #armlinux
cdaudt has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
cdaudt has joined #armlinux
tudorel has quit [Ping timeout: 252 seconds]
cdaudt has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
tudorel has joined #armlinux
CrashTestDummy3 has joined #armlinux
CrashTestDummy3 has quit [Read error: Connection reset by peer]
CrashTestDummy3 has joined #armlinux
cdaudt has joined #armlinux
CrashTestDummy2 has quit [Ping timeout: 245 seconds]
milkylainen_ has joined #armlinux
cdaudt has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
<tlwoerner> broonie: javierm: i confirmed the problem exists in linus' tree (i built and ran 5.15-rc2)
<tlwoerner> javierm: if this is what you meant with the work-around you suggested, then it didn't work: https://paste.ee/p/a9iZK
guillaume_g has joined #armlinux
ardb has joined #armlinux
<javierm> tlwoerner: that's what I mean, yes. Then the regulators getting disabled may be a red herring as broonie mentioned
Amit_T has joined #armlinux
tre has joined #armlinux
Turingtoast has joined #armlinux
apritzel has joined #armlinux
iivanov has joined #armlinux
frieder has joined #armlinux
apritzel has quit [Ping timeout: 265 seconds]
dliviu has quit [Quit: Going away]
dliviu has joined #armlinux
shoragan[m] has quit [Quit: Bridge terminating on SIGTERM]
psydroid has quit [Quit: Bridge terminating on SIGTERM]
a3f has quit [Quit: Bridge terminating on SIGTERM]
mvaittin has quit [Quit: Bridge terminating on SIGTERM]
psydroid has joined #armlinux
prabhakarlad has quit [Quit: Client closed]
frieder_ has joined #armlinux
frieder has quit [Ping timeout: 245 seconds]
matthias_bgg has joined #armlinux
mvaittin has joined #armlinux
a3f has joined #armlinux
shoragan[m] has joined #armlinux
prabhakarlad has joined #armlinux
djrscally has joined #armlinux
elastic_dog has quit [Ping timeout: 264 seconds]
audgirka has joined #armlinux
elastic_dog has joined #armlinux
elastic_dog has quit [Ping timeout: 252 seconds]
elastic_dog has joined #armlinux
Turingtoast has quit [Ping timeout: 246 seconds]
Turingtoast has joined #armlinux
elastic_dog has quit [Ping timeout: 252 seconds]
elastic_dog has joined #armlinux
elastic_dog has quit [Ping timeout: 245 seconds]
monstr has joined #armlinux
elastic_dog has joined #armlinux
tre has quit [Remote host closed the connection]
CrashTestDummy2 has joined #armlinux
CrashTestDummy3 has quit [Ping timeout: 245 seconds]
torez has joined #armlinux
monstr has quit [Ping timeout: 245 seconds]
monstr has joined #armlinux
matthias_bgg has quit [Ping timeout: 252 seconds]
elastic_dog has quit [Ping timeout: 245 seconds]
elastic_dog has joined #armlinux
matthias_bgg has joined #armlinux
audgirka has quit [Quit: Leaving]
<mripard> robher: oooh, that new notification email when one adds new dtbs_check warnings is awesome
<robher> mripard: Thanks, it's been there a while in PW though I deduplicate the data.
unmanbearpig has quit [Quit: unmanbearpig]
unmanbearpig has joined #armlinux
<robher> mripard: I'm not always sending it. It takes some filtering esp. for common bindings (e.g. simple-panel) since you get lots of warnings.
<mripard> still, it's better that nothing :)
<broonie> tlwoerner: There's some potentially useful output from rdev_dbg() which it'd be helpful to collect. Based on what's on the console it's hard to say what's going on, or what changed. My best guess given that the remove/insert kicks things into life is some client driver or constraints issue.
<broonie> There's no logging of any deferral or anything (but then people are on a crusade to remove all deferred probe logging....).
<tlwoerner> javierm: (red herring) yes, i see. even with those 2 regulators left on, the eject/reinsert trick still works
<javierm> broonie: wonder if would make sense to have a global deferred probe debug output
<tlwoerner> broonie: if i try the eject/reinsert thing immediately as the kernel pauses, it doesn't (seem) to work. i have to wait for some period before it'll work. it felt like i had to wait for those regulators to get disabled, but this latest test (of leaving them on) proves those things are not related
<javierm> broonie: I also remember that the regulator core used to be more verbose
<tlwoerner> i'm more than happy to test any patches or suggestions
<broonie> I think dev_err_probe() has that mechanism but then people need to know about it and turn it on.
cdaudt has joined #armlinux
<broonie> The verbosity is still there, it's just at debug level.
<javierm> broonie: ah, I see
<ukleinek> broonie: also there is /sys/kernel/debug/devices_deferred which is quite helpful if you know about it.
macromorgan has joined #armlinux
<broonie> ukleinek: Assumng you get to userspace!
<ukleinek> broonie: agreed
* broonie goes back to working on new architecture features with no physical implementation
<broonie> tlwoerner: like I said above collecting the dev_dbg() level logs might show something.
<javierm> broonie: wonder if we should have devices_deferred in sysfs instead at this point (maybe a /sys/devices/deferred/ ?)
<javierm> broonie: when I added that you suggested debugfs to avoid bikeshedding and you proven to be right :)
<javierm> but it seems that's useful so probably good to have it even with no debugfs mounted
<broonie> Yeah, a farm of symlinks or something. Still only accessible from userspace though!
<javierm> broonie: well, we can also have a debug option to print the deferred list in the kernel log buffer
<javierm> none of these ideas help tlwoerner with their problem though
<tlwoerner> i can enable these messages by setting loglevel=8?
<broonie> probably, you might've compiled them out. Or just run dmesg once you get a shell.
<ukleinek> tlwoerner: you want to read about dynamic debug (and enable CONFIG_DYNAMIC_DEBUG)
<tlwoerner> ok
<tlwoerner> could it be a config issue? i'm using the in-kernel arm64 defconfig. maybe the generic config doesn't enable something i need?
<tlwoerner> for example i notice RTC_DRV_RK808 is a module
<tlwoerner> (the other rk808 stuff is =y)
<tlwoerner> in any case, here's my dmesg with loglevel=8 https://paste.ee/p/CfS51
<broonie> That's not added any of the debug messages I was expected from rdev_dbg(). Does look like there's a power problem for the SD card though.
rbutler1728 has joined #armlinux
rbutlerc1728 has joined #armlinux
rbutlerc1728p has joined #armlinux
<javierm> tlwoerner: silly question, but did you try with another uSD card ?
galak has joined #armlinux
<tlwoerner> how much would you hate me if i said that by using a different uSD card the problem goes away?
tempname1234 has joined #armlinux
rbutler1728 has quit [Killed (NickServ (GHOST command used by tempname1234))]
rbutler1728 has joined #armlinux
<tlwoerner> i'd like to point out, however, that the "bad uSD card" works with (roughly) 5.10.y-ish and before but only fails with newer with the patch i pointed out
<javierm> tlwoerner: won't be surprised really, SD cards are quite fragile in general
ardb has quit [Quit: Leaving.]
galak has quit [Quit: galak]
<tlwoerner> don't know if this makes a difference, the bad card:
tempname1234 has quit [Quit: Leaving]
<tlwoerner> dwmmc_rockchip fe320000.mmc: Successfully tuned phase to 182
<tlwoerner> mmc1: new ultra high speed SDR104 SDHC card at address 0001
rbutler1728 has quit [Quit: Leaving]
<tlwoerner> the good card:
<tlwoerner> dwmmc_rockchip fe320000.mmc: Successfully tuned phase to 184
rbutlerc1728p has quit [Quit: Leaving]
rbutlerc1728 has quit [Quit: Leaving]
<tlwoerner> mmc1: new ultra high speed SDR104 SDXC card at address 5048
rbutler1728 has joined #armlinux
rbutler1728 has quit [Client Quit]
rbutler1728 has joined #armlinux
galak has joined #armlinux
<javierm> tlwoerner: interesting. Could you please try the previous uSD card with commit df4e137299d ("mmc: dw_mmc-rockchip: Just set default sample value for legacy mode") reverted ?
<broonie> tlwoerner: I think to make progress with the dodgy card we need to understand what that commit changed for your system.
iivanov has quit [Quit: Leaving...]
CrashTestDummy2 has quit [Quit: Leaving]
CrashTestDummy has joined #armlinux
Pali has joined #armlinux
cdaudt has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
cdaudt has joined #armlinux
<tlwoerner> javierm: reverting commit df4e137299d doesn't make the "bad" uSD card succeed. it does change various clockings and whatnot
<tlwoerner> mmc_host mmc1: Bus speed (slot 0) = 2320312Hz (slot req 400000Hz, actual 386718HZ div = 3)
<tlwoerner> dwmmc_rockchip fe310000.mmc: Successfully tuned phase to 227
monstr has quit [Remote host closed the connection]
cdaudt has quit [Client Quit]
ardb has joined #armlinux
<tlwoerner> broonie: the commit that caused me issues simply adds an extra check that a regulator is… up? enabled? configured?
<broonie> s/enabled/present/
<tlwoerner> somehow, not having that check is okay, but when it's added in my SDHC card fails
<broonie> This may affect ordering somehow which may have knock on effects, it's hard to tell.
<tlwoerner> broonie: you suspected the DT might be faulty?
<broonie> Like I say to make progress we'll need to figure out what it actually changes in your system, at the minute I've no information that says it even kicked in.
<broonie> Yes, that's one thing that might cause it to have an impact.
matthias_bgg has quit [Ping timeout: 245 seconds]
macromorgan has quit [Read error: Connection reset by peer]
macromorgan has joined #armlinux
apritzel has joined #armlinux
apritzel has quit [Ping timeout: 245 seconds]
jlinton has quit [Quit: Client closed]
headless has joined #armlinux
tudorel has quit [Quit: tudorel]
galak has quit [Quit: galak]
frieder_ has quit [Remote host closed the connection]
ardb has quit [Quit: Leaving.]
headless_ has joined #armlinux
headless has quit [Ping timeout: 252 seconds]
prabhakarlad has quit [Quit: Client closed]
prabhakarlad has joined #armlinux
CrashTestDummy2 has joined #armlinux
CrashTestDummy has quit [Ping timeout: 245 seconds]
cdaudt has joined #armlinux
Amit_T has quit [Quit: Leaving]
amitk has quit [Quit: leaving]
ardb has joined #armlinux
Turingtoast has quit [Quit: My iMac has gone to sleep. ZZZzzz…]
torez has quit [Ping timeout: 245 seconds]
apritzel has joined #armlinux
torez has joined #armlinux
headless_ is now known as headless
jlinton has joined #armlinux
guillaume_g has quit [Quit: Konversation terminated!]
torez has quit [Ping timeout: 245 seconds]
torez has joined #armlinux
cdaudt has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
mcfrdy has quit [Quit: quit]
mcfrdy has joined #armlinux
tagr has quit [Remote host closed the connection]
tagr has joined #armlinux
headless has quit [Quit: Konversation terminated!]
jlinton has quit [Quit: Client closed]
LeSpocky has quit [Quit: reboot]
torez has quit [Quit: torez]
m4t has joined #armlinux
CrashTestDummy3 has joined #armlinux
CrashTestDummy2 has quit [Ping timeout: 252 seconds]
djrscally has quit [Quit: Konversation terminated!]
unmanbearpig has quit [Changing host]
unmanbearpig has joined #armlinux
ardb has quit [Quit: Leaving.]
cdaudt has joined #armlinux
cdaudt has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]