Skip to content
GitLab
    • GitLab: the DevOps platform
    • Explore GitLab
    • Install GitLab
    • How GitLab compares
    • Get started
    • GitLab docs
    • GitLab Learn
  • Pricing
  • Talk to an expert
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
    Projects Groups Snippets
  • Sign up now
  • Login
  • Sign in
  • Firmware Firmware
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 20
    • Issues 20
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Releases
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Firmware-DeveloperFirmware-Developer
  • FirmwareFirmware
  • Issues
  • #16
Closed
Open
Issue created Oct 14, 2019 by Yaroslav Petrov@lankasterDeveloper

fastd segment fault beim boot

Betroffene Geräte: AVM FRITZ!Box 7360 SL firmware version:6.0.11 (und ich habe es auch bei R6220 & WR1200 gesehen)

Beim start kommt u.g. Fehlermeldung:

Mon Oct 14 20:15:22 2019 daemon.notice procd: /etc/rc.d/S99freifunk: ddmesh: boot start service openvpn
Mon Oct 14 20:15:22 2019 daemon.notice netifd: Network device 'priv' link is down
Mon Oct 14 20:15:22 2019 daemon.notice netifd: Interface 'privnet' has link connectivity loss
Mon Oct 14 20:15:22 2019 kern.info kernel: [   85.260092] br-lan: port 2(priv) entered blocking state
Mon Oct 14 20:15:22 2019 kern.info kernel: [   85.263998] br-lan: port 2(priv) entered disabled state
Mon Oct 14 20:15:22 2019 kern.info kernel: [   85.270239] device priv entered promiscuous mode
Mon Oct 14 20:15:22 2019 kern.info kernel: [   85.364400] br-lan: port 2(priv) entered blocking state
Mon Oct 14 20:15:22 2019 kern.info kernel: [   85.368324] br-lan: port 2(priv) entered listening state
Mon Oct 14 20:15:22 2019 daemon.notice netifd: Network device 'priv' link is up
Mon Oct 14 20:15:22 2019 daemon.notice netifd: Interface 'privnet' has link connectivity
Mon Oct 14 20:15:22 2019 user.notice ddmesh: network-hotplug net: [priv] add type:
Mon Oct 14 20:15:23 2019 kern.info kernel: [   85.826324] do_page_fault(): sending SIGSEGV to fastd for invalid read access from 0000001c
Mon Oct 14 20:15:23 2019 kern.info kernel: [   85.826334] do_page_fault(): sending SIGSEGV to fastd for invalid read access from 0000001c
Mon Oct 14 20:15:23 2019 kern.info kernel: [   85.826357] epc = 77f745ec in libc.so[77f26000+95000]
Mon Oct 14 20:15:23 2019 kern.info kernel: [   85.841952] epc = 77f745ec in
Mon Oct 14 20:15:23 2019 kern.info kernel: [   85.846764] ra  = 0040d4c1 in fastd[400000+15000]
Mon Oct 14 20:15:23 2019 kern.info kernel: [   85.847597] do_page_fault(): sending SIGSEGV to fastd for invalid read access from 0000001c
Mon Oct 14 20:15:23 2019 kern.warn kernel: [   85.849677]  libc.so[77f26000+95000]
Mon Oct 14 20:15:23 2019 kern.info kernel: [   85.854400] epc = 77f745ec in libc.so[77f26000+95000]
Mon Oct 14 20:15:23 2019 kern.info kernel: [   85.854457] ra  = 0040d4c1 in fastd[400000+15000]
Mon Oct 14 20:15:23 2019 kern.info kernel: [   85.876081] ra  = 0040d4c1 in fastd[400000+15000]
Mon Oct 14 20:15:23 2019 daemon.notice netifd: Network device 'tbb_fastd' link is down
Mon Oct 14 20:15:23 2019 daemon.notice netifd: Interface 'tbb_fastd' has link connectivity loss
Mon Oct 14 20:15:23 2019 daemon.notice netifd: Interface 'tbb_fastd' is now down
Mon Oct 14 20:15:23 2019 user.notice ddmesh: boot start service iperf3

Fehlermeldungen kommen nicht wieder. So weit ich sehen kann funktioniert fastd danach normal.

Assignee
Assign to
Time tracking