I knew from my upgrading:
5.1.38-dfsg-0ubuntu1.16.04.3 (xenial) ok
5.2.32-dfsg-0~ubuntu18.04.1 (bionic) - fail
6.0.6-dfsg-1 (disco) - fail
I think but I'm not sure Bionic release (5.2.10 worked as well)
So I started a poor mans binary search with the upstream packages.
5.2_5.2.32-132073 - fail
5.2_5.2.28-130011 - fail
5.2_5.2.20-125813 - fail
5.2_5.2.16-123759 - ok
5.2_5.2.14-123301 - ok
5.2_5.2.4-119785 - dkms error on install
5.5.2_2.0-118431 - dkms error on install
---
5.1_5.1.38-122592 - ok
Unfortunately time ran out then .18 or .20 is the breaking point.
I can easily check that out next time.
But once I do so is there a common best practice to collect debug info to report that maybe upstream?
I knew from my upgrading: dfsg-0ubuntu1. 16.04.3 (xenial) ok dfsg-0~ ubuntu18. 04.1 (bionic) - fail
5.1.38-
5.2.32-
6.0.6-dfsg-1 (disco) - fail
I think but I'm not sure Bionic release (5.2.10 worked as well)
So I started a poor mans binary search with the upstream packages.
5.2_5.2.32-132073 - fail
5.2_5.2.28-130011 - fail
5.2_5.2.20-125813 - fail
5.2_5.2.16-123759 - ok
5.2_5.2.14-123301 - ok
5.2_5.2.4-119785 - dkms error on install
5.5.2_2.0-118431 - dkms error on install
---
5.1_5.1.38-122592 - ok
Unfortunately time ran out then .18 or .20 is the breaking point.
I can easily check that out next time.
But once I do so is there a common best practice to collect debug info to report that maybe upstream?
Or does that version level already ring a bell?