robclark changed the topic of #aarch64-laptops to: Linux support for AArch64 Laptops (Chrome OS Trogdor Devices - Asus NovaGo TP370QL - HP Envy x2 - Lenovo Mixx 630 - Lenovo Yoga C630 - Lenovo ThinkPad X13s - and various other snapdragon laptops) - https://oftc.irclog.whitequark.org/aarch64-laptops
wookey has quit [Read error: Connection reset by peer]
abdberkana_ has joined #aarch64-laptops
abdberkana has quit [Ping timeout: 480 seconds]
abdberkana has joined #aarch64-laptops
abdberkana_ has quit [Ping timeout: 480 seconds]
abdberkana_ has joined #aarch64-laptops
abdberkana has quit [Ping timeout: 480 seconds]
abdberkana has joined #aarch64-laptops
abdberkana_ has quit [Ping timeout: 480 seconds]
abdberkana_ has joined #aarch64-laptops
abdberkana has quit [Ping timeout: 480 seconds]
abdberkana has joined #aarch64-laptops
abdberkana_ has quit [Ping timeout: 480 seconds]
abdberkana_ has joined #aarch64-laptops
abdberkana has quit [Ping timeout: 480 seconds]
mcbridematt has quit [Quit: Leaving]
mcbridematt has joined #aarch64-laptops
mcbridematt has quit []
abdberkana_ has quit [Ping timeout: 480 seconds]
hexdump0815 has joined #aarch64-laptops
hexdump01 has quit [Ping timeout: 480 seconds]
abdberkana has joined #aarch64-laptops
KREYREN_ has joined #aarch64-laptops
KREYREN_oftc has quit [Remote host closed the connection]
abdberkana_ has joined #aarch64-laptops
abdberkana has quit [Ping timeout: 480 seconds]
jglathe_sdbox2 has quit [Remote host closed the connection]
iivanov_ has quit [Remote host closed the connection]
iivanov has joined #aarch64-laptops
Guest2170 has quit [Quit: WeeChat 4.2.1]
jglathe_sdbox2 has joined #aarch64-laptops
jglathe_sdbox2 has quit [Remote host closed the connection]
martin has joined #aarch64-laptops
martin is now known as Guest2971
<jhovold>
steev: a single correctable error is not an issue, it's essentially expected
<jhovold>
the problem is the error rate on the CRD, which quickly fills the logs completely, and indicates a larger issue
<jhovold>
and the x13s wi-fi error rate is also too high
<jhovold>
steev: i can't access the log snippet you sent, but if you could read out a large amount of data and that triggers a lot of errors, then l0s may need to be disabled on the x13s for the nvme as well
<steev>
i'm not even sure what triggered it to be honest, i think maybe it was while i was building things
<steev>
but i've done a lot of builds today, as always
<steev>
that's the only one i'm even finding in my logs
<jhovold>
steev: does your nvme controller support ASPM L0s (unlike mine)?
<dgilmore>
steev: jhovold: anyone else: any recommendations for a replacement NVMe drive for the x13s? I am thinking I want to have one just for Linux, and leave the original for windows