Jump to content
  • 0
OmegaTron

Unhandled kernel unaligned access

Question

Да когда же это закончится ...

Очередное падение и флуд в syslog :

Feb  9 15:25:52 ndm: Network::Interface::Switch: "FastEthernet0/1": switch link up at port 1.
Feb  9 18:20:38 ndm: kernel: Unhandled kernel unaligned access[#1]:
Feb  9 18:20:38 ndm: kernel: Cpu 0
Feb  9 18:20:38 ndm: kernel: $ 0   : 00000000 00000001 00000001 8029f980
Feb  9 18:20:38 ndm: kernel: $ 4   : 77867d98 83377d78 83377e68 803104e8
Feb  9 18:20:38 ndm: kernel: $ 8   : 00000001 00000002 802dfab7 00000000
Feb  9 18:20:38 ndm: kernel: $12   : 00000000 00000000 00000000 00000000
Feb  9 18:20:38 ndm: kernel: $16   : 77867d98 77867d98 65687445 00000000
Feb  9 18:20:38 ndm: kernel: $20   : 80cce4a0 83c18ea8 00000fa0 00a816c0
Feb  9 18:20:38 ndm: kernel: $24   : 00000000 00000000                  
Feb  9 18:20:38 ndm: kernel: $28   : 83376000 83377cc8 00000707 80186510
Feb  9 18:20:38 ndm: kernel: Hi    : 000000cb
Feb  9 18:20:38 ndm: kernel: Lo    : bc2b9fa6
Feb  9 18:20:38 ndm: kernel: epc   : 80183be4 dev_get_stats+0x1c/0x120
Feb  9 18:20:38 ndm: kernel:     Tainted: P           O
Feb  9 18:20:38 ndm: kernel: ra    : 80186510 dev_seq_printf_stats+0x24/0x1f4
Feb  9 18:20:38 ndm: kernel: Status: 1100ec03    KERNEL EXL IE 
Feb  9 18:20:38 ndm: kernel: Cause : 00800010
Feb  9 18:20:38 ndm: kernel: BadVA : 65687481
Feb  9 18:20:38 ndm: kernel: PrId  : 00019650 (MIPS 24KEc)
Feb  9 18:20:38 ndm: kernel: Modules linked in: fastvpn(PO) hw_nat(O) zram mt76x2_ap(O) rtsoc_eth(PO) usbextras(PO) nls_utf8 xt_IPMARK(O) xt_ACCOUNT(O) nls_cp1251 usb_storage xt_DNETMAP(O) xt_length2(O) arptable_filter sd_mod ohci_hcd sr_mod nls_cp437 xt_DELUDE(O) xt_CHAOS(O) sg ext4 xt_LOGMARK(O) xt_STEAL(O) nls_cp866 xt_ipp2p(O) xt_DHCPMAC(O) jffs2 xt_psd(O) ehci_hcd xt_TPROXY xt_RAWNAT(O) xt_SYSRQ(O) xt_TARPIT(O) usbcore xt_geoip(O) xt_iprange xt_NOTRACK ipt_ULOG ip6t_rt xt_connbytes xt_addrtype xt_recent lzo_decompress ip6t_mh xt_string cdrom resetnds(PO) hmac des_generic xt_iface(O) mtdoops_proc(O) nacct(PO) xt_comment nf_tproxy_core xt_helper nfnetlink_log xt_ecn xt_socket ipt_ECN ip_set_hash_ipportip compat_xtables(O) xt_fuzzy(O) ip_set_hash_net rt_timer_wdg xt_ipv4options(O) xt_esp xt_CT zlib_deflate iptable_rawpost(O) ipt_ah xt_NFQUEUE jbd2 nls_base ip_set_hash_ipport ip6t_ipv6header xt_hl xt_hashlimit xt_dscp lzo_compress nfnetlink_queue phr(PO) mbcache xt_length ip_set_hash_ipportnet ip_se [...]
Feb  9 18:20:38 ndm: kernel: Process ndm (pid: 305, threadinfo=83376000, task=830d6d40, tls=76c24960)
Feb  9 18:20:38 ndm: kernel: Stack : 00000002 83c37800 00000003 800b5efc 77867d98 83c18e80 83377f08 80186510
Feb  9 18:20:38 ndm: kernel:         00000000 80cce4a0 81470c00 00000000 00000000 00000000 00000000 00000000
Feb  9 18:20:38 ndm: kernel:         00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
Feb  9 18:20:38 ndm: kernel:         00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
Feb  9 18:20:38 ndm: Core::Syslog: last message repeated 2 times.
Feb  9 18:20:38 ndm: kernel:         ...
Feb  9 18:20:38 ndm: kernel: Call Trace:
Feb  9 18:20:38 ndm: kernel: [<80183be4>] dev_get_stats+0x1c/0x120
Feb  9 18:20:38 ndm: kernel: [<80186510>] dev_seq_printf_stats+0x24/0x1f4
Feb  9 18:20:38 ndm: kernel: [<801866f8>] dev_seq_show+0x18/0x44
Feb  9 18:20:38 ndm: kernel: [<800bbcfc>] seq_read+0x3d0/0x510
Feb  9 18:20:38 ndm: kernel: [<800e3e88>] proc_reg_read+0x44/0x90
Feb  9 18:20:38 ndm: kernel: [<8009be60>] vfs_read+0xa0/0x17c
Feb  9 18:20:38 ndm: kernel: [<8009c34c>] sys_read+0x50/0xb0
Feb  9 18:20:38 ndm: kernel: [<80011250>] stack_done+0x20/0x44
Feb  9 18:20:38 ndm: kernel: 
Feb  9 18:20:38 ndm: kernel: 
Feb  9 18:20:38 ndm: kernel: Code: afb20018  8c920114  00808825 <8e42003c> 1440001d  00a08025  8e420040  10400031  00000000 
Feb  9 18:20:38 ndm: kernel: ---[ end trace a254306d3c767974 ]---
Feb  9 18:21:37 ndm: Core::Watchdog: Statistics collector thread holds INTERFACE_PART (64) lock 60 seconds acquired Feb  9 18:20:37.
Feb  9 18:22:37 ndm: Core::Watchdog: Statistics collector thread holds INTERFACE_PART (64) lock 120 seconds acquired Feb  9 18:20:37.
Feb  9 18:23:37 ndm: Core::Watchdog: Statistics collector thread holds INTERFACE_PART (64) lock 180 seconds acquired Feb  9 18:20:37.
Feb  9 18:24:37 ndm: Core::Watchdog: Statistics collector thread holds INTERFACE_PART (64) lock 240 seconds acquired Feb  9 18:20:37.
Feb  9 18:25:37 ndm: Core::Watchdog: Statistics collector thread holds INTERFACE_PART (64) lock 300 seconds acquired Feb  9 18:20:37.
Feb  9 18:26:37 ndm: Core::Watchdog: Statistics collector thread holds INTERFACE_PART (64) lock 360 seconds acquired Feb  9 18:20:37.
Feb  9 18:27:37 ndm: Core::Watchdog: Statistics collector thread holds INTERFACE_PART (64) lock 420 seconds acquired Feb  9 18:20:37.
Feb  9 18:28:37 ndm: Core::Watchdog: Statistics collector thread holds INTERFACE_PART (64) lock 480 seconds acquired Feb  9 18:20:37.
Feb  9 18:29:37 ndm: Core::Watchdog: Statistics collector thread holds INTERFACE_PART (64) lock 540 seconds acquired Feb  9 18:20:37.
Feb  9 18:30:37 ndm: Core::Watchdog: Statistics collector thread holds INTERFACE_PART (64) lock 600 seconds acquired Feb  9 18:20:37.
Feb  9 18:31:37 ndm: Core::Watchdog: Statistics collector thread holds INTERFACE_PART (64) lock 660 seconds acquired Feb  9 18:20:37.
Feb  9 18:32:37 ndm: Core::Watchdog: Statistics collector thread holds INTERFACE_PART (64) lock 720 seconds acquired Feb  9 18:20:37.
Feb  9 18:33:37 ndm: Core::Watchdog: Statistics collector thread holds INTERFACE_PART (64) lock 780 seconds acquired Feb  9 18:20:37.

Тут в недавней теме винили во всех бедах entware и предлагали проверить наличие проблем без него. Только вот какая заковыка - сейчас syslog пишется в файл силами того самого entware. Так что если я от него откажусь, у меня не будет возможности снимать syslog в режиме 24/7. При возникновении проблем /ci/log.txt тупо не отдаётся и его загрузка уходит в loop. Посему у меня вопрос - что делать ?

Ну и до кучи пожелание - неплохо было бы иметь возможность писать системный лог на накопитель силами самого роутера.

Edited by OmegaTron

Share this post


Link to post
Share on other sites

0 answers to this question

There have been no answers to this question yet

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Recently Browsing   0 members

    No registered users viewing this page.

×