Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 28 Sep 2020 10:24:07 +0000
From:      bugzilla-noreply@freebsd.org
To:        bugs@FreeBSD.org
Subject:   [Bug 249952] Networking stops working after warm reboot from Ubuntu Linux 19.04 on FreeBSD/amd64 12.1-RELEASE-p10
Message-ID:  <bug-249952-227@https.bugs.freebsd.org/bugzilla/>

next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D249952

            Bug ID: 249952
           Summary: Networking stops working after warm reboot from Ubuntu
                    Linux 19.04 on FreeBSD/amd64 12.1-RELEASE-p10
           Product: Base System
           Version: 12.1-RELEASE
          Hardware: amd64
                OS: Any
            Status: New
          Severity: Affects Some People
          Priority: ---
         Component: kern
          Assignee: bugs@FreeBSD.org
          Reporter: rajeev_v_pillai@yahoo.com

Machine: ASUS X202E laptop

After a warm reboot (Ctrl-Alt-Del) from Ubuntu Linux 19.04 into
FreeBSD/amd64 12.1-RELEASE-p10, networking stops working. The
kernel displays this message:

---
ubt0 on uhub4
ubt0: <Atheros Communications Bluetooth USB Host Controller, class 224/1, r=
ev
1.10/0.02, addr 3> on usbus1
WARNING: attempt to domain_add(bluetooth) after domainfinalize()
WARNING: attempt to domain_add(netgraph) after domainfinalize()
---

ping to any host on the network fails with a "host is down" error.

There is no error message like the above, and no networking problem, after a
cold
reboot (shutdown -P now, then switch on) from Linux.

I've noticed the same error message and the same networking not working iss=
ue
on another laptop.

Incidentally, warm rebooting from FreeBSD 12.1-RELEASE-p10 (on laptop) into
FreeBSD
12.2-BETA3 (on USB-stick) and doing a dmesg, shows the kernel logs from the=
 old
kernel as well as the new one.

--=20
You are receiving this mail because:
You are the assignee for the bug.=



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-249952-227>