# Долгий процесс загрузки и старта wb-mqtt-serial

**URL:** <https://support.wirenboard.com/t/dolgij-proczess-zagruzki-i-starta-wb-mqtt-serial/7258>\
**Category:** Wiren Board 6\
**Created:** [March 4, 2021, 8:59am UTC](https://support.wirenboard.com/t/dolgij-proczess-zagruzki-i-starta-wb-mqtt-serial/7258 "2021-03-04T08:59:02Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Flagman](https://support.wirenboard.com/user_avatar/support.wirenboard.com/flagman/32/1081_2.png) [@Flagman](https://support.wirenboard.com/u/Flagman)\
**Post date:** [March 4, 2021, 8:59am UTC](https://support.wirenboard.com/t/dolgij-proczess-zagruzki-i-starta-wb-mqtt-serial/7258/1 "2021-03-04T08:59:02Z")

</div>

После очередного “жесткого” ребута возникли такие сообщения в логе:

> **messages.log**
>
> Mar 3 19:38:16 wirenboard-A6M76TLX user.err kernel: [980.947119] INFO: task cat:947 blocked for more than 120 seconds.  
> Mar 3 19:38:16 wirenboard-A6M76TLX user.err kernel: [980.953289] Tainted: G C 4.9.22-wb6 #2  
> Mar 3 19:38:16 wirenboard-A6M76TLX user.err kernel: [980.958750] “echo 0 \> /proc/sys/kernel/hung\_task\_timeout\_secs” disables this message.  
> Mar 3 19:38:16 wirenboard-A6M76TLX user.info kernel: [980.966589] cat D 0 947 730 0x00000000  
> Mar 3 19:38:16 wirenboard-A6M76TLX user.warn kernel: [980.972185] [] (\_\_schedule) from [] (schedule+0x48/0xa0)  
> Mar 3 19:38:16 wirenboard-A6M76TLX user.warn kernel: [980.979295] [] (schedule) from [] (schedule\_preempt\_disabled+0xc/0x10)  
> Mar 3 19:38:16 wirenboard-A6M76TLX user.warn kernel: [980.987609] [] (schedule\_preempt\_disabled) from [] (\_\_mutex\_lock\_slowpath+0xa0/0x154)  
> Mar 3 19:38:16 wirenboard-A6M76TLX user.warn kernel: [980.997230] [] (\_\_mutex\_lock\_slowpath) from [] (mutex\_lock+0x54/0x58)  
> Mar 3 19:38:16 wirenboard-A6M76TLX user.warn kernel: [981.005429] [] (mutex\_lock) from [] (irq\_find\_matching\_fwspec+0x20/0x110)  
> Mar 3 19:38:16 wirenboard-A6M76TLX user.warn kernel: [981.013997] [] (irq\_find\_matching\_fwspec) from [] (of\_irq\_get+0x48/0x68)  
> Mar 3 19:38:16 wirenboard-A6M76TLX user.warn kernel: [981.022490] [] (of\_irq\_get) from [] (i2c\_device\_probe+0x1e8/0x204)  
> Mar 3 19:38:16 wirenboard-A6M76TLX user.warn kernel: [981.030464] [] (i2c\_device\_probe) from [] (driver\_probe\_device+0x1fc/0x2b0)  
> Mar 3 19:38:16 wirenboard-A6M76TLX user.warn kernel: [981.039214] [] (driver\_probe\_device) from [] (bus\_for\_each\_drv+0x64/0x98)  
> Mar 3 19:38:16 wirenboard-A6M76TLX user.warn kernel: [981.047778] [] (bus\_for\_each\_drv) from [] (\_\_device\_attach+0xac/0x114)  
> Mar 3 19:38:16 wirenboard-A6M76TLX user.warn kernel: [981.056058] [] (\_\_device\_attach) from [] (bus\_probe\_device+0x84/0x8c)  
> Mar 3 19:38:16 wirenboard-A6M76TLX user.warn kernel: [981.064266] [] (bus\_probe\_device) from [] (device\_add+0x3c8/0x578)  
> Mar 3 19:38:16 wirenboard-A6M76TLX user.warn kernel: [981.072218] [] (device\_add) from [] (i2c\_new\_device+0x134/0x190)  
> Mar 3 19:38:16 wirenboard-A6M76TLX user.warn kernel: [981.079995] [] (i2c\_new\_device) from [] (of\_i2c\_register\_device+0xec/0x18c)  
> Mar 3 19:38:16 wirenboard-A6M76TLX user.warn kernel: [981.088726] [] (of\_i2c\_register\_device) from [] (of\_i2c\_notify+0xa0/0x104)  
> Mar 3 19:38:16 wirenboard-A6M76TLX user.warn kernel: [981.097368] [] (of\_i2c\_notify) from [] (notifier\_call\_chain+0x44/0x80)  
> Mar 3 19:38:16 wirenboard-A6M76TLX user.warn kernel: [981.105646] [] (notifier\_call\_chain) from [] (\_\_blocking\_notifier\_call\_chain+0x48/0x60)  
> Mar 3 19:38:16 wirenboard-A6M76TLX user.warn kernel: [981.115420] [] (\_\_blocking\_notifier\_call\_chain) from [] (blocking\_notifier\_call\_chain+0x18/0x20)  
> Mar 3 19:38:16 wirenboard-A6M76TLX user.warn kernel: [981.125983] [] (blocking\_notifier\_call\_chain) from [] (\_\_of\_changeset\_entry\_notify+0x80/0xd0)  
> Mar 3 19:38:16 wirenboard-A6M76TLX user.warn kernel: [981.136279] [] (\_\_of\_changeset\_entry\_notify) from [] (\_\_of\_changeset\_apply+0x58/0xc0)  
> Mar 3 19:38:16 wirenboard-A6M76TLX user.warn kernel: [981.145879] [] (\_\_of\_changeset\_apply) from [] (\_\_of\_overlay\_create+0x628/0x8d4)  
> Mar 3 19:38:16 wirenboard-A6M76TLX user.warn kernel: [981.154963] [] (\_\_of\_overlay\_create) from [] (create\_overlay+0x48/0xa4)  
> Mar 3 19:38:16 wirenboard-A6M76TLX user.warn kernel: [981.163347] [] (create\_overlay) from [] (cfs\_overlay\_item\_dtbo\_write+0x54/0x98)  
> Mar 3 19:38:16 wirenboard-A6M76TLX user.warn kernel: [981.172428] [] (cfs\_overlay\_item\_dtbo\_write) from [] (configfs\_release\_bin\_file+0x5c/0x94)  
> Mar 3 19:38:16 wirenboard-A6M76TLX user.warn kernel: [981.182464] [] (configfs\_release\_bin\_file) from [] (\_\_fput+0x88/0x1cc)  
> Mar 3 19:38:16 wirenboard-A6M76TLX user.warn kernel: [981.190768] [] (\_\_fput) from [] (task\_work\_run+0xc0/0xe4)  
> Mar 3 19:38:16 wirenboard-A6M76TLX user.warn kernel: [981.197943] [] (task\_work\_run) from [] (do\_work\_pending+0xb8/0xbc)  
> Mar 3 19:38:16 wirenboard-A6M76TLX user.warn kernel: [981.205876] [] (do\_work\_pending) from [] (slow\_work\_pending+0xc/0x20)

Это лечится?  
С чем связано?

---

<div class="post-metadata">

**Author:** ![BrainRoot](https://avatars.discourse-cdn.com/v2/letter/b/c2a13f/32.png) [@BrainRoot](https://support.wirenboard.com/u/BrainRoot)\
**Post date:** [March 4, 2021, 9:57am UTC](https://support.wirenboard.com/t/dolgij-proczess-zagruzki-i-starta-wb-mqtt-serial/7258/2 "2021-03-04T09:57:17Z")

</div>

> [@Flagman](#):
>
> user.warn kernel: [981.022490] (of\_irq\_get) from (i2c\_device\_probe+0x1e8/0x204

Добрый день.  
Проблема связана с тем что WBIO устойства могут при запуске контроллера “держать” IRQ линии.  
Фикс:

> [@Проблема с доступом к WB6 через Debug console на Ubuntu 20.04](https://support.wirenboard.com/t/problema-s-dostupom-k-wb6-cherez-debug-console-na-ubuntu-20-04/6905/22):
>
> Фикс готов: для установки Добавляем источник echo "deb http://releases.contactless.ru/experimental.15 stretch main" \> /etc/apt/sources.list.d/irq-test.list Обновляем систему с установкой пакетов: apt update && apt upgrade -y Тестируем версию wb-hwconf-manager: dpkg -s wb-hwconf-manager | grep Version Должно выдать “Version: 1.38.3” Веряию ядра: dpkg -s linux-image-4.9.22-wb6 | grep Version Должно выдать “Version: 4.9+wb20210202141020” Перезапускаем контроллер: reboot Прошу отписать…
