ChanServ changed the topic of #linux-rockchip to: Rockchip development discussion | IRC log http://irclog.whitequark.org/linux-rockchip | Community GH https://github.com/linux-rockchip | Rockchip GH https://github.com/rockchip-linux | ML https://groups.google.com/group/linux-rockchip
stikonas has quit [Ping timeout: 264 seconds]
kevery has joined #linux-rockchip
vstehle has quit [Ping timeout: 264 seconds]
kevery1 has joined #linux-rockchip
kevery has quit [Read error: Connection reset by peer]
kevery1 is now known as kevery
kaspter has joined #linux-rockchip
kaspter has quit [Excess Flood]
kaspter has joined #linux-rockchip
kaspter has quit [Ping timeout: 240 seconds]
camus1 has joined #linux-rockchip
camus1 is now known as kaspter
kevery1 has joined #linux-rockchip
kevery has quit [Ping timeout: 264 seconds]
kevery1 is now known as kevery
vstehle has joined #linux-rockchip
nlhowell has joined #linux-rockchip
field^Zzz2 has joined #linux-rockchip
archetech has quit [Quit: Konversation terminated!]
warpme_ has joined #linux-rockchip
kevery1 has joined #linux-rockchip
kevery has quit [Ping timeout: 246 seconds]
kevery1 is now known as kevery
vstehle has quit [*.net *.split]
kaspter has quit [*.net *.split]
mps has quit [*.net *.split]
mraynal has quit [*.net *.split]
mrueg has quit [*.net *.split]
dlezcano has quit [*.net *.split]
marvs has quit [*.net *.split]
mraynal has joined #linux-rockchip
kaspter has joined #linux-rockchip
mps has joined #linux-rockchip
vstehle has joined #linux-rockchip
marvs has joined #linux-rockchip
mrueg has joined #linux-rockchip
dlezcano has joined #linux-rockchip
kevery1 has joined #linux-rockchip
kevery has quit [Ping timeout: 265 seconds]
kevery1 is now known as kevery
stikonas has joined #linux-rockchip
vicencb has joined #linux-rockchip
<mps> samueldr: kernel 5.9-rc3 boots on gru-kevin after waiting two 'Waiting for uevents ...' about two minutes for each
<mps> maybe because new CONFIG_SPI_DYNAMIC=y
<mps> but with this option elm-oak (mediatek) boots fine
<mps> oh, and I see dead (D) udev process after boot in `ps -af`
stikonas has quit [Ping timeout: 264 seconds]
kevery has quit [Ping timeout: 240 seconds]
<urjaman> D is "waiting uninterruptibly in a syscall", not "dead" though if nothing is happening it might as well be "dead and you have a buggy kernel driver"
kevery has joined #linux-rockchip
<mps> urjaman: yes, but people usually call it dead
<mps> hmm, looks like sbs battery driver is problem
kevery has quit [Quit: kevery]
kevery has joined #linux-rockchip
kevery has quit [Client Quit]
lkcl_ has quit [Ping timeout: 264 seconds]
lkcl has joined #linux-rockchip
<mps> yes, blacklisting sbs_battery module fixed this boot wait too long
<mps> now 5.9-rc3 boots fine and work ok (uhm) on gru-kevin but no battery/charging info
kaspter has quit [Ping timeout: 240 seconds]
kaspter has joined #linux-rockchip
nlhowell has quit [Ping timeout: 264 seconds]
Leepty has joined #linux-rockchip
indy has quit [Read error: Connection reset by peer]
<eballetbo> mps: do you have more information about this sbs issue. I don't seem to have problems with it, and my system just boots normal as should be.
indy_ has joined #linux-rockchip
<mps> eballetbo: dmesg => sbs-battery 9-000b: I2C adapter does not support I2C_FUNC_SMBUS_READ_BLOCK_DATA.
<mps> Fallback method does not support PEC.
<mps> gru-kevin rk3399 chromebook
robmur01_ is now known as robmur01
<mps> your somewhat-stable-next works fine on elm-oak mediatek chromebook
<eballetbo> silly question, why this affects/blocks userspace? (this doesn't be the case with Debian)
kaspter has quit [Quit: kaspter]
<mps> I don't know really
<mps> could be difference between systemd udev and eudev
<eballetbo> maybe, anyway seems that proper way to fix is implement read block data for rockchip i2c controller
<mps> which I don't know how to do
<mps> I could try to disable (e)udev and see what will happen
<mps> actually I did few days ago with 5.9-rc2 but then just few modules are loaded on boot
lkcl_ has joined #linux-rockchip
lkcl has quit [Ping timeout: 240 seconds]
JohnDoe_71Rus has joined #linux-rockchip
kaspter has joined #linux-rockchip
camus1 has joined #linux-rockchip
kaspter has quit [Ping timeout: 240 seconds]
camus1 is now known as kaspter
vagrantc has joined #linux-rockchip
kaspter has quit [Read error: Connection reset by peer]
camus1 has joined #linux-rockchip
camus1 is now known as kaspter
<mps> seems related but I'm not sure
kaspter has quit [Read error: Connection reset by peer]
kaspter has joined #linux-rockchip
<samueldr> mps: I have issues with sbs-battery with scarlet, which causes udev to timeout
<samueldr> mps: which is unrelated to the other boot issues I talked about here
<samueldr> on bob, it's known to not be an issue though AFAIK
<samueldr> I figure you don't have a SuzyQ cable... but if you do on the third console (can't remember the name) you should get a good spam of messages if it's the sbs-battery driver doing unexpected things to the virtual battery driver of the chrome EC
fncapkle has quit [Ping timeout: 264 seconds]
<mps> samueldr: I don't have any cable connection, just display and keyboard on chromebook
<mps> but I've seen in dmesg that sbs_battery module is problem, blacklisted it and boot is fast as with kernels 5.8
kaspter has quit [Read error: Connection reset by peer]
camus1 has joined #linux-rockchip
<samueldr> right, sbs-battery on scarlet started causing trouble with 5.8
<mps> hm, on gru-kevin with 5.8 it works fine
<samueldr> not really surprising
<samueldr> I think the problem is a "marginal" issue
camus1 is now known as kaspter
<samueldr> hm, you'd need to get the chrome ec logs, which I'm not sure you can get from linux, but I think you should be able to
<mps> well, I don't see any data about battery in /sys/class/power_supply/sbs-9-000b, reading files there fails
<samueldr> that's the problem
<samueldr> though scarlet's case might have been just a bit more marginal than kevin's
<samueldr> /sys/kernel/debug/<cros-ec-device>/console_log apparently
<samueldr> I don't have my device powered on at the moment
<mps> not sure but I think I will report bug to maintainers of sbs_battery
<mps> I didn't enabled DEBUGFS
<samueldr> yeah, please do, I will do *too*, but you should really look at getting the chrome ec log as that's what talks to the battery AFAIUI and it should have definit proof of problems
<mps> not sure but this from dmesg 'Fallback method does not support PEC' is quite informative
fncapkle has joined #linux-rockchip
kaspter has quit [Read error: Connection reset by peer]
camus1 has joined #linux-rockchip
camus1 is now known as kaspter
JohnDoe_71Rus has quit [Ping timeout: 258 seconds]
kaspter has quit [Read error: Connection reset by peer]
camus1 has joined #linux-rockchip
camus1 has quit [Client Quit]
vicencb has quit [Quit: Leaving.]
vicencb has joined #linux-rockchip
field^Zzz2 has quit [Ping timeout: 258 seconds]
vstehle has quit [Quit: WeeChat 2.8]
vstehle has joined #linux-rockchip
_whitelogger has joined #linux-rockchip
stikonas has joined #linux-rockchip
stikonas has quit [Remote host closed the connection]
stikonas has joined #linux-rockchip
stikonas has quit [Remote host closed the connection]
stikonas has joined #linux-rockchip
stikonas has quit [Remote host closed the connection]