设为首页收藏本站

简体中文 繁體中文 English 日本語 Deutsch 한국 사람 بالعربية TÜRKÇE português คนไทย

切换到窄版

 找回密码
 立即注册

QQ登录

只需一步，快速开始

搜索
恩山无线论坛»论坛 › 无线设备软件相关板块 › Padavan › 请教Padavan的日志里有一些kernel的输出
广告投放联系QQ68610888
返回列表 发新帖
查看: 578|回复: 2

请教Padavan的日志里有一些kernel的输出

[复制链接]
cold***
| 显示全部楼层 |阅读模式
本帖最后由 coldsnap 于 2022-5-18 18:42 编辑

路由器是JCG Q20，刷了Hiboy大哥的padavan固件，最近总是在日志里看到一些kernel的log，请问大家是什么意思呀，是闪存有坏块吗
每隔几个小时就会有一些这样的输出，非常频繁
  1. May 18 18:31:58 kernel: Call Trace:[<805ea2a4>] 0x805ea2a4
  2. May 18 18:31:58 kernel: [<805ea2a4>] 0x805ea2a4
  3. May 18 18:31:58 kernel: [<802ab954>] 0x802ab954
  4. May 18 18:31:58 kernel: [<80314494>] 0x80314494
  5. May 18 18:31:58 kernel: [<80470380>] 0x80470380
  6. May 18 18:31:58 kernel: [<801e4c3c>] 0x801e4c3c
  7. May 18 18:31:58 kernel: [<803126b4>] 0x803126b4
  8. May 18 18:31:58 kernel: [<8029efdc>] 0x8029efdc
  9. May 18 18:31:58 kernel: [<803675a4>] 0x803675a4
  10. May 18 18:31:58 kernel: [<804f1190>] 0x804f1190
  11. May 18 18:31:58 kernel: [<8004d6d8>] 0x8004d6d8
  12. May 18 18:31:58 kernel: [<80201c78>] 0x80201c78
  13. May 18 18:31:58 kernel: [<8053c688>] 0x8053c688
  14. May 18 18:31:58 kernel: [<80014c68>] 0x80014c68
  15. May 18 18:31:58 kernel: [<8057e424>] 0x8057e424
  16. May 18 18:31:58 kernel: [<80201f20>] 0x80201f20
  17. May 18 18:31:58 kernel: [<801fdaec>] 0x801fdaec
  18. May 18 18:31:58 kernel: [<80202498>] 0x80202498
  19. May 18 18:31:58 kernel: [<8053c688>] 0x8053c688
  20. May 18 18:31:58 kernel: [<802cacb4>] 0x802cacb4
  21. May 18 18:31:58 kernel: [<804e509c>] 0x804e509c
  22. May 18 18:31:58 kernel: [<802caf40>] 0x802caf40
  23. May 18 18:31:58 kernel: [<802cdb58>] 0x802cdb58
  24. May 18 18:31:58 kernel: [<802d24f8>] 0x802d24f8
  25. May 18 18:31:58 kernel: [<80402844>] 0x80402844
  26. May 18 18:31:58 kernel: [<804090ac>] 0x804090ac
  27. May 18 18:31:58 kernel: [<80404f1c>] 0x80404f1c
  28. May 18 18:31:58 kernel: [<8040491c>] 0x8040491c
  29. May 18 18:31:58 kernel: [<8002d0a4>] 0x8002d0a4
  30. May 18 18:31:58 kernel: [<8002d640>] 0x8002d640
  31. May 18 18:31:58 kernel: [<80073900>] 0x80073900
  32. May 18 18:31:58 kernel: [<8006fb08>] 0x8006fb08
  33. May 18 18:31:58 kernel: [<8002d9ac>] 0x8002d9ac
  34. May 18 18:31:58 kernel: [<80013540>] 0x80013540
  35. May 18 18:31:58 kernel: [<80073bb8>] 0x80073bb8
  36. May 18 18:31:58 kernel: [<8000a80c>] 0x8000a80c
  37. May 18 18:31:58 kernel: [<80053308>] 0x80053308
  38. May 18 18:31:58 kernel: [<80073cc0>] 0x80073cc0
  39. May 18 18:31:58 kernel: [<8000c768>] 0x8000c768
  40. May 18 18:31:58 kernel: [<8000a410>] 0x8000a410
  41. May 18 18:31:58 kernel: [<80ae6050>] 0x80ae6050
  42. May 18 18:38:04 kernel: Call Trace:[<805ea2a4>] 0x805ea2a4
  43. May 18 18:38:04 kernel: [<805ea2a4>] 0x805ea2a4
  44. May 18 18:38:04 kernel: [<802ab954>] 0x802ab954
  45. May 18 18:38:04 kernel: [<80314494>] 0x80314494
  46. May 18 18:38:04 kernel: [<80470380>] 0x80470380
  47. May 18 18:38:04 kernel: [<804a15dc>] 0x804a15dc
  48. May 18 18:38:04 kernel: [<803126b4>] 0x803126b4
  49. May 18 18:38:04 kernel: [<8029efdc>] 0x8029efdc
  50. May 18 18:38:04 kernel: [<803675a4>] 0x803675a4
  51. May 18 18:38:04 kernel: [<803cd2ec>] 0x803cd2ec
  52. May 18 18:38:04 kernel: [<803ffcd0>] 0x803ffcd0
  53. May 18 18:38:04 kernel: [<80201c78>] 0x80201c78
  54. May 18 18:38:04 kernel: [<8058385c>] 0x8058385c
  55. May 18 18:38:04 kernel: [<80201f20>] 0x80201f20
  56. May 18 18:38:04 kernel: [<801fdaec>] 0x801fdaec
  57. May 18 18:38:04 kernel: [<80202498>] 0x80202498
  58. May 18 18:38:04 kernel: [<805357f0>] 0x805357f0
  59. May 18 18:38:04 kernel: [<80202d04>] 0x80202d04
  60. May 18 18:38:04 kernel: [<80204a8c>] 0x80204a8c
  61. May 18 18:38:04 kernel: [<802cacb4>] 0x802cacb4
  62. May 18 18:38:04 kernel: [<804e509c>] 0x804e509c
  63. May 18 18:38:04 kernel: [<802caf40>] 0x802caf40
  64. May 18 18:38:04 kernel: [<802cdb58>] 0x802cdb58
  65. May 18 18:38:04 kernel: [<802d24f8>] 0x802d24f8
  66. May 18 18:38:04 kernel: [<80402844>] 0x80402844
  67. May 18 18:38:04 kernel: [<80404f1c>] 0x80404f1c
  68. May 18 18:38:04 kernel: [<8002d0a4>] 0x8002d0a4
  69. May 18 18:38:04 kernel: [<8002d640>] 0x8002d640
  70. May 18 18:38:04 kernel: [<80073900>] 0x80073900
  71. May 18 18:38:04 kernel: [<8006fb08>] 0x8006fb08
  72. May 18 18:38:04 kernel: [<8002d9ac>] 0x8002d9ac
  73. May 18 18:38:04 kernel: [<80013540>] 0x80013540
  74. May 18 18:38:04 kernel: [<80073bb8>] 0x80073bb8
  75. May 18 18:38:04 kernel: [<8000a80c>] 0x8000a80c
  76. May 18 18:38:04 kernel: [<80053308>] 0x80053308
  77. May 18 18:38:04 kernel: [<80073cc0>] 0x80073cc0
  78. May 18 18:38:04 kernel: [<8000c768>] 0x8000c768
  79. May 18 18:38:04 kernel: [<8000a410>] 0x8000a410
  80. May 18 18:38:04 kernel: [<80ae6050>] 0x80ae6050
  81. May 18 18:38:05 kernel: Call Trace:[<805ea2a4>] 0x805ea2a4
  82. May 18 18:38:05 kernel: [<805ea2a4>] 0x805ea2a4
  83. May 18 18:38:05 kernel: [<802ab954>] 0x802ab954
  84. May 18 18:38:05 kernel: [<80314494>] 0x80314494
  85. May 18 18:38:05 kernel: [<80470380>] 0x80470380
  86. May 18 18:38:05 kernel: [<801e4c3c>] 0x801e4c3c
  87. May 18 18:38:05 kernel: [<803126b4>] 0x803126b4
  88. May 18 18:38:05 kernel: [<8029efdc>] 0x8029efdc
  89. May 18 18:38:05 kernel: [<803675a4>] 0x803675a4
  90. May 18 18:38:05 kernel: [<8007c878>] 0x8007c878
  91. May 18 18:38:05 kernel: [<800331b8>] 0x800331b8
  92. May 18 18:38:05 kernel: [<80201c78>] 0x80201c78
  93. May 18 18:38:05 kernel: [<8007ce0c>] 0x8007ce0c
  94. May 18 18:38:05 kernel: [<80201f20>] 0x80201f20
  95. May 18 18:38:05 kernel: [<801fdaec>] 0x801fdaec
  96. May 18 18:38:05 kernel: [<80202498>] 0x80202498
  97. May 18 18:38:05 kernel: [<804196d8>] 0x804196d8
  98. May 18 18:38:05 kernel: [<804e509c>] 0x804e509c
  99. May 18 18:38:05 kernel: [<804e3d34>] 0x804e3d34
  100. May 18 18:38:05 kernel: [<802cacb4>] 0x802cacb4
  101. May 18 18:38:05 kernel: [<804e509c>] 0x804e509c
  102. May 18 18:38:05 kernel: [<802cb0b0>] 0x802cb0b0
  103. May 18 18:38:05 kernel: [<802cdbb0>] 0x802cdbb0
  104. May 18 18:38:05 kernel: [<802d24f8>] 0x802d24f8
  105. May 18 18:38:05 kernel: [<80402844>] 0x80402844
  106. May 18 18:38:05 kernel: [<80404f1c>] 0x80404f1c
  107. May 18 18:38:05 kernel: [<8002d0a4>] 0x8002d0a4
  108. May 18 18:38:05 kernel: [<8002d640>] 0x8002d640
  109. May 18 18:38:05 kernel: [<80073900>] 0x80073900
  110. May 18 18:38:05 kernel: [<8006fb08>] 0x8006fb08
  111. May 18 18:38:05 kernel: [<8002d9ac>] 0x8002d9ac
  112. May 18 18:38:05 kernel: [<80013540>] 0x80013540
  113. May 18 18:38:05 kernel: [<80073bb8>] 0x80073bb8
  114. May 18 18:38:05 kernel: [<8000a80c>] 0x8000a80c
  115. May 18 18:38:05 kernel: [<80053308>] 0x80053308
  116. May 18 18:38:05 kernel: [<80073cc0>] 0x80073cc0
  117. May 18 18:38:05 kernel: [<8000c768>] 0x8000c768
  118. May 18 18:38:05 kernel: [<8000a410>] 0x8000a410
  119. May 18 18:38:05 kernel: [<80ae6050>] 0x80ae6050
复制代码


padavan linux内核, padavan cups, padavan更新日志, padavan内核版本, padavan内核好旧

相关帖子

我的恩山、我的无线 The best wifi forum is right here.
回复

使用道具 举报

907***
| 显示全部楼层
同问，我的CR660X也有同样的情况，出现这个日志的瞬间WIFI会断，现在换了4.4的没有这个问题
我的恩山、我的无线 The best wifi forum is right here.
回复

使用道具 举报

Ja***
| 显示全部楼层
我也是这样
我的恩山、我的无线 The best wifi forum is right here.
回复

使用道具 举报

返回列表 发新帖
高级模式
B Color Image Link Quote Code Smilies
您需要登录后才可以回帖 登录 | 立即注册

本版积分规则

有疑问请添加管理员QQ86788181|手机版|小黑屋|Archiver|恩山无线论坛(常州市恩山计算机开发有限公司版权所有) ( 苏ICP备05084872号 )

GMT+8, 2024-4-27 13:49

Powered by Discuz! X3.5

© 2001-2024 Discuz! Team.

| 江苏省互联网有害信息举报中心 举报信箱：js12377 | @jischina.com.cn 举报电话：025-88802724 本站不良内容举报信箱：68610888@qq.com 举报电话：0519-86695797

快速回复 返回顶部 返回列表