segfault error

[alirezaimi]

Hi
I get this type of error some times and every thing just reset

Code: Select all

Nov  8 00:01:24 alilap kernel: [14046.328637] caja[13766]: segfault at 4 ip 0000563945ac5c34 sp 00007ffdd7b3e570 error 4 in caja[563945a9d000+114000]
Nov  8 00:01:24 alilap kernel: [14046.328648] Code: 00 e8 c0 8c fd ff 48 89 ef 48 89 c6 48 89 c3 e8 c2 7b fd ff 48 89 e2 4c 89 e6 48 89 c7 e8 94 b6 fd ff 85 c0 75 0f 48 8b 3c 24 <83> 7f 04 1e 75 26 e8 a1 9a fd ff 48 8b 44 24 08 64 48 33 04 25 28 
Nov  8 00:01:31 alilap kernel: [14053.474865] caja[14715]: segfault at 4 ip 000056087c64ec34 sp 00007fff153677a0 error 4 in caja[56087c626000+114000]
Nov  8 00:01:31 alilap kernel: [14053.474873] Code: 00 e8 c0 8c fd ff 48 89 ef 48 89 c6 48 89 c3 e8 c2 7b fd ff 48 89 e2 4c 89 e6 48 89 c7 e8 94 b6 fd ff 85 c0 75 0f 48 8b 3c 24 <83> 7f 04 1e 75 26 e8 a1 9a fd ff 48 8b 44 24 08 64 48 33 04 25 28 
Nov  8 00:04:56 alilap kernel: [14259.201979] INFO: task pool:14712 blocked for more than 120 seconds.
Nov  8 00:04:56 alilap kernel: [14259.201988]       Tainted: G           O      4.18.0-2-amd64 #1 Debian 4.18.10-2
Nov  8 00:04:56 alilap kernel: [14259.201991] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Nov  8 00:04:56 alilap kernel: [14259.201995] pool            D    0 14712      1 0x00000000
Nov  8 00:04:56 alilap kernel: [14259.202000] Call Trace:
Nov  8 00:04:56 alilap kernel: [14259.202016]  ? __schedule+0x2b7/0x880
Nov  8 00:04:56 alilap kernel: [14259.202019]  ? __switch_to_asm+0x34/0x70
Nov  8 00:04:56 alilap kernel: [14259.202022]  ? __switch_to_asm+0x40/0x70
Nov  8 00:04:56 alilap kernel: [14259.202026]  schedule+0x28/0x80
Nov  8 00:04:56 alilap kernel: [14259.202030]  schedule_timeout+0x1ee/0x380
Nov  8 00:04:56 alilap kernel: [14259.202034]  ? __schedule+0x2bf/0x880
Nov  8 00:04:56 alilap kernel: [14259.202038]  io_schedule_timeout+0x19/0x40
Nov  8 00:04:56 alilap kernel: [14259.202043]  wait_for_completion_io+0x12c/0x190
Nov  8 00:04:56 alilap kernel: [14259.202049]  ? wake_up_q+0x70/0x70
Nov  8 00:04:56 alilap kernel: [14259.202057]  submit_bio_wait+0x5b/0x80
Nov  8 00:04:56 alilap kernel: [14259.202064]  blkdev_issue_flush+0x7c/0xb0
Nov  8 00:04:56 alilap kernel: [14259.202071]  blkdev_fsync+0x2f/0x40
Nov  8 00:04:56 alilap kernel: [14259.202079]  do_fsync+0x38/0x60
Nov  8 00:04:56 alilap kernel: [14259.202085]  __x64_sys_fsync+0x10/0x20
Nov  8 00:04:56 alilap kernel: [14259.202091]  do_syscall_64+0x55/0x110
Nov  8 00:04:56 alilap kernel: [14259.202096]  entry_SYSCALL_64_after_hwframe+0x44/0xa9
Nov  8 00:04:56 alilap kernel: [14259.202104] RIP: 0033:0x7f7599233b17
Nov  8 00:04:56 alilap kernel: [14259.202104] Code: Bad RIP value.
Nov  8 00:04:56 alilap kernel: [14259.202111] RSP: 002b:00007f75948ae5d0 EFLAGS: 00000293 ORIG_RAX: 000000000000004a
Nov  8 00:04:56 alilap kernel: [14259.202113] RAX: ffffffffffffffda RBX: 000000000000000e RCX: 00007f7599233b17
Nov  8 00:04:56 alilap kernel: [14259.202114] RDX: 0000000000000000 RSI: 0000560f07b75ee0 RDI: 000000000000000e
Nov  8 00:04:56 alilap kernel: [14259.202115] RBP: 000000000000000e R08: 0000000000000000 R09: 0000560f07b21650
Nov  8 00:04:56 alilap kernel: [14259.202116] R10: 0000000000000000 R11: 0000000000000293 R12: 0000560f07b382e0
Nov  8 00:04:56 alilap kernel: [14259.202117] R13: 0000560f07b75ee0 R14: 00007f758801a640 R15: 0000560f07afcc70

this is with caja that i want safe remove some usb device.
why is this error happened to me more often ?

[bw123]

That's not a good error to get. When I see segfault, it's usually because I seriously broke debian by intentionally installing something from outside the distribution. I have also occasionally seen this when messing around in /var/lib and trying to manually link things for graphics, or when mixing debian stable with other sources.

Have you installed anything from outside the debian repository? Have you mucked about with the system? Did you websearch any of the error msgs from the output you posted?

On the other hand, since you are using testing, it could be something important that people might want to know. I really don't know what to ask, or how to help. It might be easier if you add some history and confirm the problem does not happen on debian stable.

[Head_on_a_Stick]

https://wiki.debian.org/HowToGetABacktrace