|
[RESOLVED] Chrome/Chromium does not work (pread64: Input/output error (5))
Does someone have a clue why Chrome or Chromium does not work on Liquorix kernel on my Debian 12 when I'm launching it as a normal user while they are working just fine under Debian stable/sid kernels?:
:: Code :: user@xxx:~$ chromium
[0905/204352.786436:ERROR:process_memory_linux.cc(49)] pread64: Input/output error (5) Bus error (core dumped) :: Code :: user@xxx:~$ google-chrome
[0905/204157.440930:ERROR:process_memory_linux.cc(49)] pread64: Input/output error (5) Bus error (core dumped) In strace, there is this happening: :: Code :: --- SIGBUS {si_signo=SIGBUS, si_code=BUS_ADRERR, si_addr=0x7fc58e200000} ---
gettid() = 10629 prctl(PR_GET_DUMPABLE) = 1 (SUID_DUMP_USER) prctl(PR_SET_PTRACER, 10644) = 0 rt_sigprocmask(SIG_BLOCK, [CONT], [BUS], 8) = 0 sendmsg(4, {msg_name=NULL, msg_namelen=0, msg_iov=[{iov_base="\1\0\0\0\1\0\0\0\250I\207\224\305\177\0\0\10\3463\0d/\0\0\0\0\0\0\0\0\0\0"..., iov_len=40}], msg_iovlen=1, msg_controllen=0, msg_flags=0}, MSG_NOSIGNAL) = 40 rt_sigtimedwait([CONT], [0905/204405.563561:ERROR:scoped_ptrace_attach.cc(27)] ptrace: Operation not permitted (1) {si_signo=SIGCONT, si_code=SI_TKILL, si_pid=10644, si_uid=549401103}, {tv_sec=5, tv_nsec=0}, 8) = 18 (SIGCONT) rt_sigprocmask(SIG_SETMASK, [BUS], NULL, 8) = 0 futex(0x2f640033e628, FUTEX_WAKE_PRIVATE, 2147483647) = 0 rt_sigaction(SIGBUS, {sa_handler=SIG_DFL, sa_mask=[], sa_flags=SA_RESTORER, sa_restorer=0x7fc592c5afd0}, NULL, 8) = 0 getpid() = 10629 gettid() = 10629 rt_tgsigqueueinfo(10629, 10629, SIGBUS, {si_signo=SIGBUS, si_code=BUS_ADRERR, si_addr=0x7fc58e200000}) = 0 rt_sigreturn({mask=[]}) = 140486469746688 --- SIGBUS {si_signo=SIGBUS, si_code=BUS_ADRERR, si_addr=0x7fc58e200000} --- +++ killed by SIGBUS (core dumped) +++ Bus error (core dumped) I also tried to reset Chromium settings by renaming .config/chromium => .config/chromium.bak, and starting Chromium again, but it still crashes. Kernel version: Linux 6.4.14-1-liquorix-amd64 #1 ZEN SMP PREEMPT liquorix 6.4-18.1~bookworm (2023-09-02) x86_64 GNU/Linux As a root user the Chromium launches OK. I've only the following sysctl parameters applied as my /home is mounted via NFS, nothing else (and I don't believe they cause this): :: Code :: # NFS optimizations
net.core.rmem_max = 16777216 net.core.wmem_max = 16777216 net.ipv4.tcp_rmem = 32768 262144 16777216 net.ipv4.tcp_wmem = 32768 262144 16777216 net.ipv4.tcp_window_scaling = 1 net.ipv4.tcp_sack = 1 net.ipv4.tcp_timestamps = 0 Update: This is related to my NFS mount: Chromium starts OK if I symlink my ~/.config/chromium to a directory that resides on my local SSD. But I think it's still an issue with the Liquorix kernel, because Chromium works on Debian stable/sid kernels just fine, even the ~/.config/chromium directory resides on a NFS share. Back to top |
|||||
|
I created a separate issue directly to the Zen kernel GitHub page: https://github.com/zen-kernel/zen-kernel/issues/326
Back to top |
|||||
|
I pushed out a new kernel syncing the NFS options from Arch Linux, can you try it? Should be v6.4.15 as the major+minor.
Back to top |
|||||
|
:: damentz wrote :: I pushed out a new kernel syncing the NFS options from Arch Linux, can you try it? Should be v6.4.15 as the major+minor.Just verified that on 6.4.15-2-liquorix-amd64 the problems are gone, thank you! Back to top |
|||||
|
Ok great! I'll point out the config changes I made on the github issue and have Jan update Zen Kernel appropriately.
Marking as resolved. Back to top |
|||||
|
All times are GMT - 8 Hours
|
|||||