![内核记录的错误信息,通过/var/log/kern.log排除定制内核故障](https://linux22.com/image/903955/%E5%86%85%E6%A0%B8%E8%AE%B0%E5%BD%95%E7%9A%84%E9%94%99%E8%AF%AF%E4%BF%A1%E6%81%AF%EF%BC%8C%E9%80%9A%E8%BF%87%2Fvar%2Flog%2Fkern.log%E6%8E%92%E9%99%A4%E5%AE%9A%E5%88%B6%E5%86%85%E6%A0%B8%E6%95%85%E9%9A%9C.png)
我正在尝试通过 /var/log/kern.log 命令排除定制内核故障。日志中显示与 gvfsd-metadata 相关的错误。这些错误会给 PC 造成任何问题吗?如何修复这些错误?我已将日志附加到下方
root@yash20-desktop:/home/yash20# tail -f /var/log/syslog
Sep 5 10:27:19 yash20-desktop kernel: [ 36.512190] init: plymouth-upstart-bridge main process ended, respawning
Sep 5 10:27:38 yash20-desktop kernel: [ 55.529151] audit_printk_skb: 42 callbacks suppressed
Sep 5 10:27:38 yash20-desktop kernel: [ 55.529154] type=1400 audit(1536123458.500:37): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/cups/backend/cups-pdf" pid=2423 comm="apparmor_parser"
Sep 5 10:27:38 yash20-desktop kernel: [ 55.529161] type=1400 audit(1536123458.500:38): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/sbin/cupsd" pid=2423 comm="apparmor_parser"
Sep 5 10:28:50 yash20-desktop kernel: [ 127.759992] gvfsd-metadata[4220]: segfault at 7ffb6405c000 ip 0000000000406885 sp 00007ffe99258ff0 error 4 in gvfsd-metadata[400000+11000]
Sep 5 10:28:51 yash20-desktop kernel: [ 128.035233] gvfsd-metadata[4244]: segfault at 7f4272d13000 ip 0000000000406885 sp 00007ffccb5eebf0 error 4 in gvfsd-metadata[400000+11000]
Sep 5 10:28:51 yash20-desktop kernel: [ 128.224081] gvfsd-metadata[4250]: segfault at 7f5a9ded4000 ip 0000000000406885 sp 00007fff06f5e270 error 4 in gvfsd-metadata[400000+11000]
Sep 5 10:28:51 yash20-desktop kernel: [ 128.367639] gvfsd-metadata[4275]: segfault at 7f21625eb000 ip 0000000000406885 sp
00007fffe68e08c0 gvfsd-metadata[400000+11000] 中发生错误 4 9 月 5 日 10:28:51 yash20-desktop 内核:[128.499979] gvfsd-metadata[4283]:7facae55e000 处发生段错误 ip 0000000000406885 sp 00007ffc36778990 gvfsd-metadata[400000+11000] 中发生错误 4
答案1
由 GNOME 虚拟文件系统gvfsd-metadata
软件包提供。gvfs
它应该与你的内核无关,它出现在你的日志中是因为它出现段错误,并且快速谷歌搜索显示一些(旧)错误。
您可以通过(临时)安装库存内核并重新启动系统来检查段错误是否与您的自定义内核有关,然后检查段错误是否消失。