Dale wrote:
>
> OK. Between the two posts, I did the following. I found out that
> libxcb.so.1.1.0 belongs to x11-libs/libxcb so I reemerged it. I also
> got lucky when I did a ps aux and caught a kioworker process running
> which gave me the path. I couldn't do that the other day which made me
Mark Knecht wrote:
> On Fri, May 16, 2025 at 3:33 PM Dale wrote:
>> Howdy,
>>
>> I was looking at messages and ran up on this error. This is on my new
>> rig, Gentoo-1.
>>
>>
>>
>> May 16 17:20:16 Gentoo-1 kernel: kioworker[3084]: segfault at 0 ip
>> 7f95f17510e8 sp 7ffe1b492d50 error 4 i
On Fri, May 16, 2025 at 3:33 PM Dale wrote:
>
> Howdy,
>
> I was looking at messages and ran up on this error. This is on my new
> rig, Gentoo-1.
>
>
>
> May 16 17:20:16 Gentoo-1 kernel: kioworker[3084]: segfault at 0 ip
> 7f95f17510e8 sp 7ffe1b492d50 error 4 in
> libxcb.so.1.1.0[7f95f174
I believe the "segfault at" messages are emitted by the kernel when a
*userspace* process segfaults (possibly only when it's owned by root or
otherwise seems important). If a kernel thread had crashed, I think you'd see
an OOPS instead.
kioworker, despite its name, isn't a kernel process. My
Howdy,
I was looking at messages and ran up on this error. This is on my new
rig, Gentoo-1.
May 16 17:20:16 Gentoo-1 kernel: kioworker[3084]: segfault at 0 ip
7f95f17510e8 sp 7ffe1b492d50 error 4 in
libxcb.so.1.1.0[7f95f174f000+15000] likely on CPU 15 (core 7, socket 0)
May 16 17:20:16
5 matches
Mail list logo
