[P] Errors in syslog: "reset: init clients timeout hbm_state = 2"

cmonty14

Renowned Member
Mar 4, 2014
344
6
83
Hello!

I have installed Proxmox VE 3.3 successfully on a server with 3 NICs.

In addition, I have setup IPFire on a VM with automated startup.

After the VM is started, I can observer the following error messages in syslog:
Code:
Oct 12 09:03:31 pc6-gigabyte task UPID:pc6-gigabyte:00000A26:000007A0:543A27C3:qmstart:100:root@pam:: start VM 100: UPID:pc6-gigabyte:00000A26:000007A0:543A27C3:qmstart:100:root@pam:
Oct 12 09:03:31 pc6-gigabyte task UPID:pc6-gigabyte:00000A25:0000079E:543A27C3:startall::root@pam:: <root@pam> starting task UPID:pc6-gigabyte:00000A26:000007A0:543A27C3:qmstart:100:root@pam:
Oct 12 09:03:33 pc6-gigabyte kernel: [   21.207475] device tap100i0 entered promiscuous mode
Oct 12 09:03:33 pc6-gigabyte kernel: [   21.210744] vmbr0: port 2(tap100i0) entered forwarding state
Oct 12 09:03:33 pc6-gigabyte kernel: [   21.210749] vmbr0: port 2(tap100i0) entered forwarding state
Oct 12 09:03:33 pc6-gigabyte kernel: [   21.395713] device tap100i1 entered promiscuous mode
Oct 12 09:03:33 pc6-gigabyte kernel: [   21.399031] vmbr1: port 2(tap100i1) entered forwarding state
Oct 12 09:03:33 pc6-gigabyte kernel: [   21.399035] vmbr1: port 2(tap100i1) entered forwarding state
Oct 12 09:03:33 pc6-gigabyte kernel: [   21.583012] device tap100i2 entered promiscuous mode
Oct 12 09:03:33 pc6-gigabyte kernel: [   21.586276] vmbr2: port 2(tap100i2) entered forwarding state
Oct 12 09:03:33 pc6-gigabyte kernel: [   21.586282] vmbr2: port 2(tap100i2) entered forwarding state
Oct 12 09:03:33 pc6-gigabyte kernel: [   21.586290] IPv6: ADDRCONF(NETDEV_CHANGE): vmbr2: link becomes ready
Oct 12 09:03:37 pc6-gigabyte pvesh: <root@pam> end task UPID:pc6-gigabyte:00000A25:0000079E:543A27C3:startall::root@pam: OK
Oct 12 09:03:43 pc6-gigabyte kernel: [   31.762134] mei_me 0000:00:16.0: reset: init clients timeout hbm_state = 2.
Oct 12 09:03:43 pc6-gigabyte kernel: [   31.762158] mei_me 0000:00:16.0: unexpected reset: dev_state = RESETTING
Oct 12 09:03:48 pc6-gigabyte ntpd[2336]: Listen normally on 9 vmbr2 fe80::215:17ff:fe91:9cb9 UDP 123
Oct 12 09:03:48 pc6-gigabyte ntpd[2336]: Listen normally on 10 tap100i0 fe80::b833:62ff:fe28:2a47 UDP 123
Oct 12 09:03:48 pc6-gigabyte ntpd[2336]: Listen normally on 11 tap100i1 fe80::d4ed:95ff:fe4d:b21c UDP 123
Oct 12 09:03:48 pc6-gigabyte ntpd[2336]: Listen normally on 12 tap100i2 fe80::d807:31ff:fe29:17e6 UDP 123
Oct 12 09:03:48 pc6-gigabyte ntpd[2336]: peers refreshed
[COLOR=#ff0000]Oct 12 09:04:13 pc6-gigabyte kernel: [   61.833328] mei_me 0000:00:16.0: reset: init clients timeout hbm_state = 2.
Oct 12 09:04:13 pc6-gigabyte kernel: [   61.833352] mei_me 0000:00:16.0: unexpected reset: dev_state = RESETTING
Oct 12 09:04:43 pc6-gigabyte kernel: [   91.903997] mei_me 0000:00:16.0: reset: init clients timeout hbm_state = 2.
Oct 12 09:04:43 pc6-gigabyte kernel: [   91.904021] mei_me 0000:00:16.0: unexpected reset: dev_state = RESETTING
Oct 12 09:05:14 pc6-gigabyte kernel: [  121.974870] mei_me 0000:00:16.0: reset: init clients timeout hbm_state = 2.
Oct 12 09:05:14 pc6-gigabyte kernel: [  121.974893] mei_me 0000:00:16.0: unexpected reset: dev_state = RESETTING
Oct 12 09:05:44 pc6-gigabyte kernel: [  152.045930] mei_me 0000:00:16.0: reset: init clients timeout hbm_state = 2.
Oct 12 09:05:44 pc6-gigabyte kernel: [  152.045954] mei_me 0000:00:16.0: unexpected reset: dev_state = RESETTING
Oct 12 09:06:14 pc6-gigabyte kernel: [  182.117155] mei_me 0000:00:16.0: reset: init clients timeout hbm_state = 2.
Oct 12 09:06:14 pc6-gigabyte kernel: [  182.117179] mei_me 0000:00:16.0: unexpected reset: dev_state = RESETTING
Oct 12 09:06:44 pc6-gigabyte kernel: [  212.188524] mei_me 0000:00:16.0: reset: init clients timeout hbm_state = 2.
Oct 12 09:06:44 pc6-gigabyte kernel: [  212.188548] mei_me 0000:00:16.0: unexpected reset: dev_state = RESETTING
Oct 12 09:07:14 pc6-gigabyte kernel: [  242.260022] mei_me 0000:00:16.0: reset: init clients timeout hbm_state = 2.
Oct 12 09:07:14 pc6-gigabyte kernel: [  242.260045] mei_me 0000:00:16.0: unexpected reset: dev_state = RESETTING
Oct 12 09:07:44 pc6-gigabyte kernel: [  272.331639] mei_me 0000:00:16.0: reset: init clients timeout hbm_state = 2.
Oct 12 09:07:44 pc6-gigabyte kernel: [  272.331663] mei_me 0000:00:16.0: unexpected reset: dev_state = RESETTING
Oct 12 09:08:14 pc6-gigabyte kernel: [  302.403356] mei_me 0000:00:16.0: reset: init clients timeout hbm_state = 2.
Oct 12 09:08:14 pc6-gigabyte kernel: [  302.403380] mei_me 0000:00:16.0: unexpected reset: dev_state = RESETTING
Oct 12 09:08:44 pc6-gigabyte kernel: [  332.475159] mei_me 0000:00:16.0: reset: init clients timeout hbm_state = 2.
Oct 12 09:08:44 pc6-gigabyte kernel: [  332.475183] mei_me 0000:00:16.0: unexpected reset: dev_state = RESETTING
Oct 12 09:09:14 pc6-gigabyte kernel: [  362.547046] mei_me 0000:00:16.0: reset: init clients timeout hbm_state = 2.
Oct 12 09:09:14 pc6-gigabyte kernel: [  362.547070] mei_me 0000:00:16.0: unexpected reset: dev_state = RESETTING
Oct 12 09:09:44 pc6-gigabyte kernel: [  392.619007] mei_me 0000:00:16.0: reset: init clients timeout hbm_state = 2.
Oct 12 09:09:44 pc6-gigabyte kernel: [  392.619030] mei_me 0000:00:16.0: unexpected reset: dev_state = RESETTING
Oct 12 09:10:14 pc6-gigabyte kernel: [  422.691032] mei_me 0000:00:16.0: reset: init clients timeout hbm_state = 2.
Oct 12 09:10:14 pc6-gigabyte kernel: [  422.691056] mei_me 0000:00:16.0: unexpected reset: dev_state = RESETTING
Oct 12 09:10:44 pc6-gigabyte kernel: [  452.763110] mei_me 0000:00:16.0: reset: init clients timeout hbm_state = 2.
Oct 12 09:10:44 pc6-gigabyte kernel: [  452.763133] mei_me 0000:00:16.0: unexpected reset: dev_state = RESETTING
Oct 12 09:11:14 pc6-gigabyte kernel: [  482.835251] mei_me 0000:00:16.0: reset: init clients timeout hbm_state = 2.
Oct 12 09:11:14 pc6-gigabyte kernel: [  482.835274] mei_me 0000:00:16.0: unexpected reset: dev_state = RESETTING
Oct 12 09:11:44 pc6-gigabyte kernel: [  512.907425] mei_me 0000:00:16.0: reset: init clients timeout hbm_state = 2.
Oct 12 09:11:44 pc6-gigabyte kernel: [  512.907449] mei_me 0000:00:16.0: unexpected reset: dev_state = RESETTING
Oct 12 09:12:14 pc6-gigabyte kernel: [  542.979635] mei_me 0000:00:16.0: reset: init clients timeout hbm_state = 2.
Oct 12 09:12:14 pc6-gigabyte kernel: [  542.979658] mei_me 0000:00:16.0: unexpected reset: dev_state = RESETTING
Oct 12 09:12:44 pc6-gigabyte kernel: [  573.051886] mei_me 0000:00:16.0: reset: init clients timeout hbm_state = 2.
Oct 12 09:12:44 pc6-gigabyte kernel: [  573.051910] mei_me 0000:00:16.0: unexpected reset: dev_state = RESETTING
[/COLOR]Oct 12 09:12:58 pc6-gigabyte kernel: [  587.076632] usb 3-3: new full-speed USB device number 2 using xhci_hcd
Oct 12 09:12:58 pc6-gigabyte kernel: [  587.090987] usb 3-3: New USB device found, idVendor=046d, idProduct=c52b
Oct 12 09:12:58 pc6-gigabyte kernel: [  587.090989] usb 3-3: New USB device strings: Mfr=1, Product=2, SerialNumber=0
Oct 12 09:12:58 pc6-gigabyte kernel: [  587.090990] usb 3-3: Product: USB Receiver
Oct 12 09:12:58 pc6-gigabyte kernel: [  587.090991] usb 3-3: Manufacturer: Logitech
Oct 12 09:12:59 pc6-gigabyte kernel: [  587.197952] logitech-djreceiver 0003:046D:C52B.0003: hiddev0,hidraw0: USB HID v1.11 Device [Logitech USB Receiver] on usb-0000:00:14.0-3/input2
Oct 12 09:12:59 pc6-gigabyte kernel: [  587.201806] input: Logitech Unifying Device. Wireless PID:101b as /devices/pci0000:00/0000:00:14.0/usb3/3-3/3-3:1.2/0003:046D:C52B.0003/input/input14
Oct 12 09:12:59 pc6-gigabyte kernel: [  587.201865] logitech-djdevice 0003:046D:C52B.0004: input,hidraw1: USB HID v1.11 Mouse [Logitech Unifying Device. Wireless PID:101b] on usb-0000:00:14.0-3:1
Oct 12 09:12:59 pc6-gigabyte kernel: [  587.203891] input: Logitech Unifying Device. Wireless PID:2008 as /devices/pci0000:00/0000:00:14.0/usb3/3-3/3-3:1.2/0003:046D:C52B.0003/input/input15
Oct 12 09:12:59 pc6-gigabyte kernel: [  587.203935] logitech-djdevice 0003:046D:C52B.0005: input,hidraw2: USB HID v1.11 Keyboard [Logitech Unifying Device. Wireless PID:2008] on usb-0000:00:14.0-3:2
Oct 12 09:13:14 pc6-gigabyte kernel: [  603.124170] mei_me 0000:00:16.0: reset: init clients timeout hbm_state = 2.
Oct 12 09:13:14 pc6-gigabyte kernel: [  603.124318] mei_me 0000:00:16.0: unexpected reset: dev_state = RESETTING
Oct 12 09:13:18 pc6-gigabyte shutdown[3243]: shutting down for system reboot
Oct 12 09:13:18 pc6-gigabyte init: Switching to runlevel: 6
Oct 12 09:13:19 pc6-gigabyte rrdcached[2424]: caught SIGTERM
Oct 12 09:13:19 pc6-gigabyte rrdcached[2424]: starting shutdown
Oct 12 09:13:19 pc6-gigabyte spiceproxy[2591]: received terminate request
Oct 12 09:13:19 pc6-gigabyte spiceproxy[2591]: worker 2592 finished
Oct 12 09:13:19 pc6-gigabyte spiceproxy[2591]: server closing
Oct 12 09:13:19 pc6-gigabyte postfix/master[2432]: terminating on signal 15
Oct 12 09:13:19 pc6-gigabyte rrdcached[2424]: clean shutdown; all RRDs flushed
Oct 12 09:13:19 pc6-gigabyte rrdcached[2424]: removing journals
Oct 12 09:13:19 pc6-gigabyte rrdcached[2424]: removing old journal /var/lib/rrdcached/journal/rrd.journal.1413097407.059930
Oct 12 09:13:19 pc6-gigabyte rrdcached[2424]: goodbye
Oct 12 09:13:19 pc6-gigabyte pve-firewall[2525]: server closing
Oct 12 09:13:19 pc6-gigabyte pve-firewall[2525]: clear firewall rules
Oct 12 09:13:19 pc6-gigabyte pvesh: <root@pam> starting task UPID:pc6-gigabyte:00000D16:0000ED4E:543A2A0F:stopall::root@pam:
Oct 12 09:13:19 pc6-gigabyte task UPID:pc6-gigabyte:00000D17:0000ED4F:543A2A0F:qmshutdown:100:root@pam:: shutdown VM 100: UPID:pc6-gigabyte:00000D17:0000ED4F:543A2A0F:qmshutdown:100:root@pam:
Oct 12 09:13:19 pc6-gigabyte task UPID:pc6-gigabyte:00000D16:0000ED4E:543A2A0F:stopall::root@pam:: <root@pam> starting task UPID:pc6-gigabyte:00000D17:0000ED4F:543A2A0F:qmshutdown:100:root@pam:
Oct 12 09:13:20 pc6-gigabyte pmxcfs[2435]: [status] notice: RRDC update error /var/lib/rrdcached/db/pve2-node/pc6-gigabyte: -3
Oct 12 09:13:20 pc6-gigabyte pvepw-logger[2511]: received terminate request (signal)
Oct 12 09:13:20 pc6-gigabyte pvepw-logger[2511]: stopping pvefw logger
Oct 12 09:13:45 pc6-gigabyte kernel: [  633.196489] mei_me 0000:00:16.0: reset: init clients timeout hbm_state = 2.
Oct 12 09:13:45 pc6-gigabyte kernel: [  633.196763] mei_me 0000:00:16.0: unexpected reset: dev_state = RESETTING
Oct 12 09:14:06 pc6-gigabyte kernel: [  654.900104] vmbr0: port 2(tap100i0) entered disabled state
Oct 12 09:14:06 pc6-gigabyte kernel: [  654.971726] vmbr1: port 2(tap100i1) entered disabled state
Oct 12 09:14:06 pc6-gigabyte kernel: [  655.043229] vmbr2: port 2(tap100i2) entered disabled state
Oct 12 09:14:09 pc6-gigabyte ntpd[2336]: Deleting interface #12 tap100i2, fe80::d807:31ff:fe29:17e6#123, interface stats: received=0, sent=0, dropped=0, active_time=621 secs
Oct 12 09:14:09 pc6-gigabyte ntpd[2336]: Deleting interface #11 tap100i1, fe80::d4ed:95ff:fe4d:b21c#123, interface stats: received=0, sent=0, dropped=0, active_time=621 secs
Oct 12 09:14:09 pc6-gigabyte ntpd[2336]: Deleting interface #10 tap100i0, fe80::b833:62ff:fe28:2a47#123, interface stats: received=0, sent=0, dropped=0, active_time=621 secs
Oct 12 09:14:09 pc6-gigabyte ntpd[2336]: peers refreshed
Oct 12 09:14:09 pc6-gigabyte pvesh: <root@pam> end task UPID:pc6-gigabyte:00000D16:0000ED4E:543A2A0F:stopall::root@pam: OK
Oct 12 09:14:09 pc6-gigabyte pvestatd[2565]: server closing
Oct 12 09:14:09 pc6-gigabyte pveproxy[2570]: received terminate request
Oct 12 09:14:09 pc6-gigabyte pveproxy[2570]: worker 2573 finished
Oct 12 09:14:09 pc6-gigabyte pveproxy[2570]: worker 2571 finished
Oct 12 09:14:09 pc6-gigabyte pveproxy[2570]: worker 2572 finished
Oct 12 09:14:09 pc6-gigabyte pveproxy[2570]: server closing
Oct 12 09:14:09 pc6-gigabyte pvedaemon[2541]: received terminate request
Oct 12 09:14:09 pc6-gigabyte pvedaemon[2541]: worker 2543 finished
Oct 12 09:14:09 pc6-gigabyte pvedaemon[2541]: worker 2544 finished
Oct 12 09:14:09 pc6-gigabyte pvedaemon[2541]: worker 2545 finished
Oct 12 09:14:09 pc6-gigabyte pvedaemon[2541]: server closing
Oct 12 09:14:09 pc6-gigabyte pmxcfs[2435]: [main] notice: teardown filesystem
Oct 12 09:14:09 pc6-gigabyte iscsid: iscsid shutting down.

These error messages are written until server shutdown.

Question:
What's the root cause of this problem?

THX