[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: issue with systemd-udev-settle



Am 29.04.2015 um 19:23 schrieb Christian Seiler:
Just for the purpose of debugging, could you increase RateLimitBurst to
10000 or so (i.e. 10x the default value) in /etc/systemd/journald.conf
and reboot? (Set it back again after you're done deubgging, else your
logs might get flooded.)

The 10000 value did not help. I deactivated any limits:
RateLimitInterval=0
RateLimitBurst=0


Here is what I found:
Start of log is at Apr 30 07:27:55

Apr 30 07:27:55 xxx systemd-udevd[60]: starting version 215

# then it is working on all partitions.
# sdc is an SSD
# sdc2 is swap
# sdb1 is lvm

Apr 30 07:27:55 xxx systemd-udevd[175]: device 0x7f6bbb28f7b0 has devpath '/devices/pci0000:00/0000:00:11.0/ata2/host1/target1:0:0/1:0:0:0/block/sdb/sdb1'
Apr 30 07:27:55 xxx systemd-udevd[175]: restoring old watch on '/dev/sdb1'
Apr 30 07:27:55 xxx systemd-udevd[175]: adding watch on '/dev/sdb1'

....

Apr 30 07:27:55 xxx systemd-udevd[175]: device 0x7f6bbb28f7b0 has devpath '/devices/pci0000:00/0000:00:11.0/ata3/host2/target2:0:0/2:0:0:0/block/sdc/sdc3'
Apr 30 07:27:55 xxx systemd-udevd[175]: restoring old watch on '/dev/sdc3'
Apr 30 07:27:55 xxx systemd-udevd[175]: adding watch on '/dev/sdc3'

....

# there are hundreds of udev message for the next 5 sec until 07:28:00
# then there are only a few udev messages for the next 50 sec until 07:28:50
# before hundreds of udev messages start again

....

Apr 30 07:28:01 xxx systemd-udevd[175]: seq 1598 queued, 'add' 'input'
Apr 30 07:28:01 xxx systemd-udevd[175]: seq 1599 queued, 'add' 'input'
Apr 30 07:28:01 xxx systemd-udevd[175]: seq 1600 queued, 'add' 'input'
Apr 30 07:28:01 xxx systemd-udevd[175]: seq 1601 queued, 'add' 'input'
Apr 30 07:28:01 xxx systemd-udevd[175]: seq 1602 queued, 'add' 'input'
Apr 30 07:28:04 xxx systemd-udevd[175]: validate module index
Apr 30 07:28:04 xxx systemd-udevd[175]: Check if link configuration needs reloading.
Apr 30 07:28:07 xxx systemd-udevd[175]: validate module index
Apr 30 07:28:07 xxx systemd-udevd[175]: Check if link configuration needs reloading.
Apr 30 07:28:10 xxx systemd-udevd[175]: validate module index
Apr 30 07:28:10 xxx systemd-udevd[175]: Check if link configuration needs reloading.
Apr 30 07:28:13 xxx systemd-udevd[175]: validate module index
Apr 30 07:28:13 xxx systemd-udevd[175]: Check if link configuration needs reloading.
Apr 30 07:28:16 xxx systemd-udevd[175]: validate module index
Apr 30 07:28:16 xxx systemd-udevd[175]: Check if link configuration needs reloading.
Apr 30 07:28:19 xxx systemd-udevd[175]: validate module index
Apr 30 07:28:19 xxx systemd-udevd[175]: Check if link configuration needs reloading. Apr 30 07:28:19 xxx systemd-journal[170]: Forwarding to syslog missed 3809 messages.
Apr 30 07:28:22 xxx systemd-udevd[175]: validate module index
Apr 30 07:28:22 xxx systemd-udevd[175]: Check if link configuration needs reloading.
Apr 30 07:28:25 xxx systemd-udevd[175]: validate module index
Apr 30 07:28:25 xxx systemd-udevd[175]: Check if link configuration needs reloading.
Apr 30 07:28:28 xxx systemd-udevd[175]: validate module index
Apr 30 07:28:28 xxx systemd-udevd[175]: Check if link configuration needs reloading. Apr 30 07:28:31 xxx systemd-udevd[175]: worker [196] /devices/pci0000:00/0000:00:12.2/usb1/1-4/1-4.4/1-4.4:1.0 timeout; kill it Apr 30 07:28:31 xxx systemd-udevd[175]: seq 1229 '/devices/pci0000:00/0000:00:12.2/usb1/1-4/1-4.4/1-4.4:1.0' killed
Apr 30 07:28:31 xxx systemd-udevd[175]: validate module index
Apr 30 07:28:31 xxx systemd-udevd[175]: Check if link configuration needs reloading.
Apr 30 07:28:34 xxx systemd-udevd[175]: validate module index
Apr 30 07:28:34 xxx systemd-udevd[175]: Check if link configuration needs reloading.
Apr 30 07:28:37 xxx systemd-udevd[175]: validate module index
Apr 30 07:28:37 xxx systemd-udevd[175]: Check if link configuration needs reloading.
Apr 30 07:28:40 xxx systemd-udevd[175]: validate module index
Apr 30 07:28:40 xxx systemd-udevd[175]: Check if link configuration needs reloading.
Apr 30 07:28:43 xxx systemd-udevd[175]: validate module index
Apr 30 07:28:43 xxx systemd-udevd[175]: Check if link configuration needs reloading.
Apr 30 07:28:46 xxx systemd-udevd[175]: validate module index
Apr 30 07:28:46 xxx systemd-udevd[175]: Check if link configuration needs reloading.
Apr 30 07:28:49 xxx systemd-udevd[175]: validate module index
Apr 30 07:28:49 xxx systemd-udevd[175]: Check if link configuration needs reloading. Apr 30 07:28:49 xxx systemd-journal[170]: Forwarding to syslog missed 22 messages. Apr 30 07:28:50 xxx kernel: usbcore: registered new interface driver snd-usb-audio
Apr 30 07:28:50 xxx systemd-udevd[175]: seq 1603 queued, 'add' 'sound'
Apr 30 07:28:50 xxx systemd-udevd[175]: seq 1604 queued, 'add' 'sound'
Apr 30 07:28:50 xxx systemd-udevd[175]: worker [196] exit
Apr 30 07:28:50 xxx systemd-udevd[175]: worker [196] terminated by signal 9 (Killed)
Apr 30 07:28:50 xxx systemd-udevd[175]: worker [196] cleaned up
Apr 30 07:28:50 xxx systemd-udevd[175]: seq 1605 queued, 'add' 'sound'
Apr 30 07:28:50 xxx systemd-udevd[175]: seq 1230 forked new worker [269]
Apr 30 07:28:50 xxx systemd-udevd[175]: seq 1606 queued, 'add' 'sound'
Apr 30 07:28:50 xxx systemd-udevd[269]: seq 1230 running
Apr 30 07:28:50 xxx systemd-udevd[269]: no db file to read /run/udev/data/+usb:1-4.4:1.1: No such file or directory Apr 30 07:28:50 xxx systemd-udevd[269]: device 0x7f6bbb2bfba0 has devpath '/devices/pci0000:00/0000:00:12.2/usb1/1-4/1-4.4' Apr 30 07:28:50 xxx systemd-udevd[269]: device 0x7f6bbb325c00 has devpath '/devices/pci0000:00/0000:00:12.2/usb1/1-4' Apr 30 07:28:50 xxx systemd-udevd[269]: device 0x7f6bbb3266d0 has devpath '/devices/pci0000:00/0000:00:12.2/usb1' Apr 30 07:28:50 xxx systemd-udevd[269]: device 0x7f6bbb3270e0 has devpath '/devices/pci0000:00/0000:00:12.2' Apr 30 07:28:50 xxx systemd-udevd[269]: device 0x7f6bbb327e20 has devpath '/devices/pci0000:00' Apr 30 07:28:50 xxx systemd-udevd[269]: IMPORT builtin 'hwdb' /lib/udev/rules.d/50-udev-default.rules:11

####

udev seems to pause for a long time with very few messages until it kicks in again at about 07:28:50. One of first message before it kicks in again is:

Apr 30 07:28:50 xxx kernel: usbcore: registered new interface driver snd-usb-audio
Apr 30 07:28:50 xxx systemd-udevd[175]: seq 1603 queued, 'add' 'sound'
Apr 30 07:28:50 xxx systemd-udevd[175]: seq 1604 queued, 'add' 'sound'

I am wondering if this can have something to do with my usb keyboard which happens to have a sound module with audio in and out for headset and mic. And it is also a USB hub where the mouse is connected:

52: USB 00.0: 10503 USB Mouse
  [Created at usb.122]
  Unique ID: __6e.ykItPQs8ue8
  Parent ID: Uc5H.TI3vE1oZtwF
  SysFS ID: /devices/pci0000:00/0000:00:12.2/usb1/1-4/1-4.1/1-4.1:1.0
  SysFS BusID: 1-4.1:1.0
  Hardware Class: mouse
  Model: "KYE NetScroll+ Traveler"
  Hotplug: USB
  Vendor: usb 0x0458 "KYE Systems"
  Device: usb 0x002e "NetScroll+ Traveler"
  Compatible to: int 0x0200 0x0001 "Generic USB Mouse"
  Driver: "usbhid"
  Driver Modules: "usbhid"
  Speed: 1.5 Mbps
  Module Alias: "usb:v0458p002Ed0000dc00dsc00dp00ic03isc01ip02in00"
  Driver Info #0:
    XFree86 Protocol: explorerps/2
    GPM Protocol: exps2
  Config Status: cfg=new, avail=yes, need=no, active=unknown
  Attached to: #62 (Hub)

53: USB 00.0: 10800 Keyboard
  [Created at usb.122]
  Unique ID: sFNz.BMubaYkkWv5
  Parent ID: Uc5H.TI3vE1oZtwF
  SysFS ID: /devices/pci0000:00/0000:00:12.2/usb1/1-4/1-4.3/1-4.3:1.0
  SysFS BusID: 1-4.3:1.0
  Hardware Class: keyboard
  Model: "Monterey International Keyboard"
  Hotplug: USB
  Vendor: usb 0x0566 "Monterey International Corp."
  Device: usb 0x3108
  Revision: "3.01"
  Driver: "usbhid"
  Driver Modules: "usbhid"
  Speed: 1.5 Mbps
  Module Alias: "usb:v0566p3108d0301dc00dsc00dp00ic03isc01ip01in00"
  Driver Info #0:
    XkbRules: xfree86
    XkbModel: pc104
  Config Status: cfg=new, avail=yes, need=no, active=unknown
  Attached to: #62 (Hub)

54: USB 00.1: 0000 Unclassified device
  [Created at usb.122]
  Unique ID: JRd1.wSzlx4YKRyF
  Parent ID: Uc5H.TI3vE1oZtwF
  SysFS ID: /devices/pci0000:00/0000:00:12.2/usb1/1-4/1-4.3/1-4.3:1.1
  SysFS BusID: 1-4.3:1.1
  Hardware Class: unknown
  Model: "Monterey International Unclassified device"
  Hotplug: USB
  Vendor: usb 0x0566 "Monterey International Corp."
  Device: usb 0x3108
  Revision: "3.01"
  Driver: "usbhid"
  Driver Modules: "usbhid"
  Speed: 1.5 Mbps
  Module Alias: "usb:v0566p3108d0301dc00dsc00dp00ic03isc00ip00in01"
  Driver Info #0:
    Driver Status: usbhid is active
    Driver Activation Cmd: "modprobe usbhid"
  Config Status: cfg=new, avail=yes, need=no, active=unknown
  Attached to: #62 (Hub)

55: USB 00.0: 0401 Multimedia audio controller
  [Created at usb.122]
  Unique ID: IO+7.DGe+0l9GPv1
  Parent ID: Uc5H.TI3vE1oZtwF
  SysFS ID: /devices/pci0000:00/0000:00:12.2/usb1/1-4/1-4.4/1-4.4:1.0
  SysFS BusID: 1-4.4:1.0
  Hardware Class: sound
  Model: "Elan Microelectronics USB Audio"
  Hotplug: USB
  Vendor: usb 0x04f3 "Elan Microelectronics Corp."
  Device: usb 0x0a11 "USB Audio"
  Revision: "1.00"
  Driver: "snd-usb-audio"
  Driver Modules: "snd_usb_audio"
  Speed: 12 Mbps
  Module Alias: "usb:v04F3p0A11d0100dc00dsc00dp00ic01isc01ip00in00"
  Driver Info #0:
    Driver Status: snd_usb_audio is active
    Driver Activation Cmd: "modprobe snd_usb_audio"
  Config Status: cfg=new, avail=yes, need=no, active=unknown
  Attached to: #62 (Hub)

58: USB 00.3: 0000 Unclassified device
  [Created at usb.122]
  Unique ID: fwlK.e6_dCN4Dx+9
  Parent ID: Uc5H.TI3vE1oZtwF
  SysFS ID: /devices/pci0000:00/0000:00:12.2/usb1/1-4/1-4.4/1-4.4:1.3
  SysFS BusID: 1-4.4:1.3
  Hardware Class: unknown
  Model: "Elan Microelectronics USB Audio"
  Hotplug: USB
  Vendor: usb 0x04f3 "Elan Microelectronics Corp."
  Device: usb 0x0a11 "USB Audio"
  Revision: "1.00"
  Driver: "usbhid"
  Driver Modules: "usbhid"
  Speed: 12 Mbps
  Module Alias: "usb:v04F3p0A11d0100dc00dsc00dp00ic03isc00ip00in03"
  Driver Info #0:
    Driver Status: usbhid is active
    Driver Activation Cmd: "modprobe usbhid"
  Config Status: cfg=new, avail=yes, need=no, active=unknown
  Attached to: #62 (Hub)


Does that help?

Matthias







Reply to: