This is fixed in mainline, but not sure if upstream stable have this fix or not. [ 48.065638] RIP: 0010:swiotlb_tbl_map_single+0x120/0x310 [ 48.065641] Code: 4c 8b 45 a8 4c 8b 1d af c7 a9 01 89 d3 45 31 d2 44 8b 4d a4 44 89 c7 41 89 dc 4b 8d 44 25 00 48 21 f0 48 01 f8 49 39 c7 72 0a <47> 39 0c a3 0f 83 cb 00 00 00 42 8d 04 33 48 89 c3 48 39 c1 41 0f [ 48.065643] RSP: 0018:ffffbed680f6b3c0 EFLAGS: 00010016 [ 48.065646] RAX: 0000000000000001 RBX: 0000000000000000 RCX: 0000000000000000 [ 48.065648] RDX: 0000000000000000 RSI: 00000000001fffff RDI: 0000000000000001 [ 48.065650] RBP: ffffbed680f6b420 R08: 0000000000000001 R09: 0000000000000001 [ 48.065652] R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000000 [ 48.065653] R13: 0000000000000000 R14: 0000000000000001 R15: 0000000000200000 [ 48.065656] FS: 00007f9e750f16c0(0000) GS:ffff96d53da00000(0000) knlGS:0000000000000000 [ 48.065659] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 48.065661] CR2: 0000000000000000 CR3: 0000000073114000 CR4: 00000000000006f0 [ 48.065662] Call Trace: [ 48.065669] swiotlb_map+0x6c/0x1c0 [ 48.065673] dma_direct_map_page+0xc5/0x160 [ 48.065679] b44_alloc_rx_skb+0x18e/0x3f0 [b44] [ 48.065683] b44_init_rings+0xbe/0x1b0 [b44] [ 48.065686] b44_open+0xfc/0x3f0 [b44] [ 48.065691] __dev_open+0xd4/0x170 [ 48.065694] __dev_change_flags+0x18f/0x200 [ 48.065698] dev_change_flags+0x27/0x60 [ 48.065701] do_setlink+0x31c/0xe30 [ 48.065707] ? __nla_parse+0x38/0x120 [ 48.065710] __rtnl_newlink+0x531/0x910 [ 48.065715] ? update_load_avg+0x4b6/0x590 [ 48.065719] ? __alloc_pages_nodemask+0x13f/0x2e0 [ 48.065726] ? _cond_resched+0x19/0x30 [ 48.065730] ? kmem_cache_alloc_trace+0x153/0x1d0 [ 48.065732] rtnl_newlink+0x48/0x70 [ 48.065735] rtnetlink_rcv_msg+0x213/0x300 [ 48.065737] ? rtnl_calcit.isra.31+0x100/0x100 [ 48.065741] netlink_rcv_skb+0x4f/0x120 [ 48.065744] rtnetlink_rcv+0x15/0x20 [ 48.065746] netlink_unicast+0x1a1/0x260 [ 48.065749] netlink_sendmsg+0x20d/0x3c0 [ 48.065753] sock_sendmsg+0x3e/0x50 [ 48.065756] ___sys_sendmsg+0x295/0x2f0 [ 48.065758] ? sock_destroy_inode+0x2f/0x40 [ 48.065762] ? destroy_inode+0x3e/0x60 [ 48.065764] ? evict+0x139/0x1a0 [ 48.065767] ? iput+0x148/0x210 [ 48.065769] ? _cond_resched+0x19/0x30 [ 48.065772] ? __dentry_kill+0x124/0x170 [ 48.065775] ? dentry_kill+0x52/0x1a0 [ 48.065778] __sys_sendmsg+0x5c/0xa0 [ 48.065781] __x64_sys_sendmsg+0x1f/0x30 [ 48.065785] do_syscall_64+0x5a/0x110 [ 48.065788] entry_SYSCALL_64_after_hwframe+0x44/0xa9
-- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1829310 Title: kernel 5 fails to start systemd-networkd on old Dell Inspiron 1720 Status in linux package in Ubuntu: Confirmed Bug description: linux kernel 5.0.0-13 Kubuntu 19.04 hardware: old Dell laptop Inspiron 1720 After upgrading an old Dell laptop Inspiron 1720 (from 2007 I think) from Kubuntu 18.10 to 19.04, the result is a broken system: booting takes + 5 minutes looking at the boot messages I see "Failed to start Dispatcher daemon for systemd-networkd" and consequently Network Manager fails to run. Eventually it reaches the desktop where it takes another 5 minutes to display the panel. In a terminal it fails to execute any network command (ifconfig, ip) as well as "sudo" and "lshw". If I boot with the previous kernel, the 4.18.0-18 of Kubuntu 18.10, it works without problem. For now I have set its grub to start by default the 4.18 kernel instead of the 5.0 one. I tried running "apport-cli -f -p linux --save kernel5.0onOldDellInspiron1720.apport" but that has been spitting out periods ("....") for 10 minutes now and still hasn't finished. dmesg output attached. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1829310/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
