[Bug 1840359] [NEW] systemd-networkd-wait-online & two ethernet on board

2019-08-15 Thread Radek Secka
Public bug reported:

Since I've upgraded to 19.04 my boot was 3 minutes longer due to wait for 
network. I've tried many tricks, but today I have finally found the source = 
the bug.
My PC has motherboard AsRock Z370M-ITX/ac which has 2 Ethernet ports. When I 
connect Ethernet cable just to the "first" device "enp3s0" boot is quick, when 
I connect Ethernet cable just to the "second" device "enp0s31f6" boot is about 
3 minutes longer.

It simply waits for the "enp3s0" device.

Since there is no mark on the board or on the rear panel which port is
"first" and which is "second" it's clear that the failure is on Ubuntu
19.04 side. Ubuntu 18.04 LTS has no such problem.

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: systemd 240-6ubuntu5.3
ProcVersionSignature: Ubuntu 5.0.0-25.26-generic 5.0.18
Uname: Linux 5.0.0-25-generic x86_64
ApportVersion: 2.20.10-0ubuntu27.1
Architecture: amd64
CurrentDesktop: Unity:Unity7:ubuntu
Date: Thu Aug 15 21:55:12 2019
InstallationDate: Installed on 2017-12-22 (600 days ago)
InstallationMedia: Ubuntu-Server 17.10 "Artful Aardvark" - Release amd64 
(20171017.1)
MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-25-generic 
root=UUID=d383d414-f179-4df7-a8f3-890dacf8ca33 ro modprobe.blacklist=nouveau 
intel_iommu=on
SourcePackage: systemd
UpgradeStatus: Upgraded to disco on 2019-06-22 (54 days ago)
dmi.bios.date: 03/21/2018
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P2.10
dmi.board.name: Z370M-ITX/ac
dmi.board.vendor: ASRock
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP2.10:bd03/21/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ370M-ITX/ac:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.family: To Be Filled By O.E.M.
dmi.product.name: To Be Filled By O.E.M.
dmi.product.sku: To Be Filled By O.E.M.
dmi.product.version: To Be Filled By O.E.M.
dmi.sys.vendor: To Be Filled By O.E.M.

** Affects: systemd (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: 19.04 ethernet online systemd wait

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1840359

Title:
  systemd-networkd-wait-online & two ethernet on board

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1840359/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1840359] Re: systemd-networkd-wait-online & two ethernet on board

2019-08-16 Thread Radek Secka
No they don't have same MAC but the difference is just one bit.

I'm using network-manager and I didn't changed systemd-networkd configuration 
manually. 
May be it was changed during Upgrade LTS 18.04 -> 19.04

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1840359

Title:
  systemd-networkd-wait-online & two ethernet on board

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1840359/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1840359] Re: systemd-networkd-wait-online & two ethernet on board

2019-08-16 Thread Radek Secka
In syslog was just:
systemd-networkd-wait-online[4903]: Event loop failed: Connection timed out
apt-helper[4892]: E: Sub-process /lib/systemd/systemd-networkd-wait-online 
returned an error code (1)

In /etc/netplan/  just   01-netcfg.yaml (Attachment)
/etc/systemd/network is empty
In /run/systemd/network/  just 10-netplatn-enp3s0.network (Attachment)

** Attachment added: "01-netcfg.yaml and 10-netplan-enp3s0.network"
   
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1840359/+attachment/5282866/+files/network.7z

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1840359

Title:
  systemd-networkd-wait-online & two ethernet on board

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1840359/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1858319] [NEW] libvirt usb 3.1

2020-01-05 Thread Radek Secka
Public bug reported:

I'm trying to passthrough my USB Disk "Samsung Portable SSD T5" which is
USB 3.0 Device. But I've connected it to USB 3.1 Port.

Controller configuration:

  


Device configuration:

  


  
  


lsusb   
Bus 002 Device 006: ID 04e8:61f5 Samsung Electronics Co., Ltd Portable SSD T5

lsusb --tree
/:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/10p, 1M
|__ Port 1: Dev 6, If 0, Class=Mass Storage, Driver=uas, 1M

lsusb -v -d 04e8:61f5 
Bus 002 Device 006: ID 04e8:61f5 Samsung Electronics Co., Ltd Portable SSD T5
Couldn't open device, some information will be missing
Device Descriptor:
  bLength18
  bDescriptorType 1
  bcdUSB   3.10
  bDeviceClass0 
  bDeviceSubClass 0 
  bDeviceProtocol 0 
  bMaxPacketSize0 9
  idVendor   0x04e8 Samsung Electronics Co., Ltd
  idProduct  0x61f5 Portable SSD T5


Error starting domain: internal error: qemu unexpectedly closed the monitor: 
2020-01-05T08:31:16.434028Z qemu-system-x86_64: -device 
usb-host,hostbus=2,hostaddr=6,id=hostdev4,bus=usb.0,port=4: Warning: speed 
mismatch trying to attach usb device "Portable SSD T5" (unknown speed) to bus 
"usb.0", port "4" (full+high+super speed)
2020-01-05T08:31:16.593173Z qemu-system-x86_64: -device 
usb-host,hostbus=2,hostaddr=6,id=hostdev4,bus=usb.0,port=4: failed to open host 
usb device 2:6

** Affects: libvirt (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1858319

Title:
  libvirt usb 3.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1858319/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1858319] Re: libvirt usb 3.1

2020-01-06 Thread Radek Secka
Thank you for your response.
I've tested all USB 3.1 ports and there is the same problem everywhere. 
Passthrough of the device works just fine on any USB 3.0 port.

dmesg -w (USB 3.1)
.. (same as USB 3.0 here ) ..
[ 1200.920167] sd 8:0:0:0: [sdf] Synchronizing SCSI cache
[ 1201.181831] sd 8:0:0:0: [sdf] Synchronize Cache(10) failed: Result: 
hostbyte=DID_ERROR driverbyte=DRIVER_OK
[ 1201.370153] usb 2-2: reset SuperSpeedPlus Gen 2 USB device number 11 using 
xhci_hcd
[ 1201.395813] scsi host8: uas
[ 1201.396751] scsi 8:0:0:0: Direct-Access Samsung  Portable SSD T5  0
PQ: 0 ANSI: 6
[ 1201.397646] sd 8:0:0:0: Attached scsi generic sg5 type 0
[ 1201.398655] sd 8:0:0:0: [sdf] 976773168 512-byte logical blocks: (500 GB/466 
GiB)
[ 1201.398915] sd 8:0:0:0: [sdf] Write Protect is off
[ 1201.398920] sd 8:0:0:0: [sdf] Mode Sense: 43 00 00 00
[ 1201.401815] sd 8:0:0:0: [sdf] Write cache: enabled, read cache: enabled, 
doesn't support DPO or FUA
[ 1201.402039] sd 8:0:0:0: [sdf] Optimal transfer size 33553920 bytes
[ 1201.407550]  sdf: sdf1 sdf2 sdf3 sdf4
[ 1201.409912] sd 8:0:0:0: [sdf] Attached SCSI disk
[ 1201.482029] usb 1-1.2.2.4: reset full-speed USB device number 13 using 
xhci_hcd
[ 1201.698108] usb 1-1.2.2.1: reset full-speed USB device number 12 using 
xhci_hcd
[ 1201.801695] input: RAPOO RAPOO 5G Wireless Device as 
/devices/pci:00/:00:14.0/usb1/1-1/1-1.2/1-1.2.2/1-1.2.2.1/1-1.2.2.1:1.0/0003:24AE:2002.000E/input/input46
[ 1201.859114] hid-generic 0003:24AE:2002.000E: input,hidraw4: USB HID v1.10 
Keyboard [RAPOO RAPOO 5G Wireless Device] on usb-:00:14.0-1.2.2.1/input0
[ 1201.862701] input: RAPOO RAPOO 5G Wireless Device Mouse as 
/devices/pci:00/:00:14.0/usb1/1-1/1-1.2/1-1.2.2/1-1.2.2.1/1-1.2.2.1:1.1/0003:24AE:2002.000F/input/input47
[ 1201.862984] input: RAPOO RAPOO 5G Wireless Device System Control as 
/devices/pci:00/:00:14.0/usb1/1-1/1-1.2/1-1.2.2/1-1.2.2.1/1-1.2.2.1:1.1/0003:24AE:2002.000F/input/input48
[ 1201.921962] input: RAPOO RAPOO 5G Wireless Device Consumer Control as 
/devices/pci:00/:00:14.0/usb1/1-1/1-1.2/1-1.2.2/1-1.2.2.1/1-1.2.2.1:1.1/0003:24AE:2002.000F/input/input49
[ 1201.922181] hid-generic 0003:24AE:2002.000F: input,hiddev0,hidraw5: USB HID 
v1.10 Mouse [RAPOO RAPOO 5G Wireless Device] on usb-:00:14.0-1.2.2.1/input1
[ 1203.046366] bridge0: port 2(vnet0) entered disabled state
[ 1203.052019] device vnet0 left promiscuous mode
[ 1203.052021] bridge0: port 2(vnet0) entered disabled state
[ 1203.412619] audit: type=1400 audit(1578340093.392:115): apparmor="STATUS" 
operation="profile_remove" profile="unconfined" 
name="libvirt-2b4d62e5-b589-4f59-a48e-9a6e91052200" pid=10968 
comm="apparmor_parser"

dmesg -w (USB 3.0)
.. (same as USB 3.1 here ) ..
[ 2733.614412] sd 8:0:0:0: [sdf] Synchronizing SCSI cache
[ 2733.876194] sd 8:0:0:0: [sdf] Synchronize Cache(10) failed: Result: 
hostbyte=DID_ERROR driverbyte=DRIVER_OK
[ 2743.168421] usb 2-10: reset SuperSpeed Gen 1 USB device number 13 using 
xhci_hcd
[ 2743.396440] usb 2-10: reset SuperSpeed Gen 1 USB device number 13 using 
xhci_hcd
[ 2743.604300] usb 1-1.2.2.1: reset full-speed USB device number 12 using 
xhci_hcd
[ 2743.872348] usb 1-1.2.2.1: reset full-speed USB device number 12 using 
xhci_hcd
[ 2744.168449] usb 1-1.2.2.4: reset full-speed USB device number 13 using 
xhci_hcd
[ 2744.464433] usb 1-1.2.2.4: reset full-speed USB device number 13 using 
xhci_hcd
[ 2746.448056] bridge0: port 2(vnet0) entered learning state
[ 2751.664228] usb 2-10: reset SuperSpeed Gen 1 USB device number 13 using 
xhci_hcd
[ 2751.816250] usb 2-10: reset SuperSpeed Gen 1 USB device number 13 using 
xhci_hcd
[ 2752.040255] usb 1-1.2.2.1: reset full-speed USB device number 12 using 
xhci_hcd
[ 2752.232268] usb 1-1.2.2.1: reset full-speed USB device number 12 using 
xhci_hcd
[ 2752.456282] usb 1-1.2.2.1: reset full-speed USB device number 12 using 
xhci_hcd
[ 2752.684371] usb 1-1.2.2.1: reset full-speed USB device number 12 using 
xhci_hcd
[ 2752.888310] usb 1-1.2.2.4: reset full-speed USB device number 13 using 
xhci_hcd
[ 2753.112281] usb 1-1.2.2.4: reset full-speed USB device number 13 using 
xhci_hcd
[ 2753.328278] usb 1-1.2.2.4: reset full-speed USB device number 13 using 
xhci_hcd
[ 2753.560224] usb 1-1.2.2.4: reset full-speed USB device number 13 using 
xhci_hcd

virsh nodedev-list (USB 3.1)
usb_2_2
usb_2_2_1_0

virsh nodedev-list (USB 3.0)
usb_2_10
usb_2_10_1_0

virsh nodedev-dumpxml  .. are same, just / and 
/ are different
virsh nodedev-dumpxml usb_2_2 (UBS 3.1)

  usb_2_2
  /sys/devices/pci:00/:00:14.0/usb2/2-2
  /dev/bus/usb/002/023
  usb_usb2
  
usb
  
  
2
23
Portable SSD T5
Samsung Electronics Co., Ltd
  


virsh nodedev-dumpxml usb_2_2_1_0 (USB 3.1)

  usb_2_2_1_0
  /sys/devices/pci:00/:00:14.0/usb2/2-2/2-2:1.0
  usb_2_2
  
uas
  
  
0
8
6
98
  


Ubuntu: 19.10
Kernel: Linux 5.3.0-24-generic
Architecture: x86-64

-- 
You received this bug notifi