broadcom-sta 6.30.223.271-3~16.04.1 ADT test failure with linux-hwe-edge 4.13.0-16.19~16.04.3

Bug #1724865 reported by Seth Forshee on 2017-10-19
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
broadcom-sta (Ubuntu)
Undecided
Marcelo Cerri
Xenial
Undecided
Unassigned

Bug Description

[Impact]

Currently the DKMS package broadcom-sta fails to install in supported custom
kernels that are based on 4.11 or 4.13. That includes the current 4.11 hwe-edge
and the upcoming 4.13 hwe-edge kernels and some of the custom and cloud kernels
as well.

[Test Case]

Install the broadcom-sta package with the 4.13 hwe-edge kernel from -proposed.
The package installation should proceed without any errors.

[Regression Potential]

Although new patches were added, the regression risk is very low since the new
changes are conditionally compiled based on the kernel version.

Besides that the new package was tested with the following kernels in an amd64
environment:

- linux-generic 4.4
- linux-hwe 4.10
- linux-hwe-edge 4.11
- linux-hwe-edge 4.13 (from xenial-proposed)
- linux-azure 4.11
- linux-azure-edge 4.13 (which is in process of getting promoted to
  xenial-proposed)

[Original Description]

Testing failed on:
    amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/amd64/b/broadcom-sta/20171018_120722_62eb1@/log.gz
    i386: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/i386/b/broadcom-sta/20171018_121214_62eb1@/log.gz

Seth Forshee (sforshee) wrote :
tags: added: kernel-adt-failure
Seth Forshee (sforshee) on 2017-10-25
tags: added: kernel-adt-failure-hwe-edge-4.11
removed: kernel-adt-failure
tags: added: kernel-adt-failure-hwe-edge-4.13
removed: kernel-adt-failure-hwe-edge-4.11
Marcelo Cerri (mhcerri) on 2017-10-26
Changed in broadcom-sta (Ubuntu):
status: New → In Progress
assignee: nobody → Marcelo Cerri (mhcerri)
Marcelo Cerri (mhcerri) on 2017-10-27
description: updated

An upload of broadcom-sta to xenial-proposed has been rejected from the upload queue for the following reason: "Where did 6.30.223.271-3~16.04.2 go?".

Hello Seth, or anyone else affected,

Accepted broadcom-sta into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/broadcom-sta/6.30.223.271-3~16.04.2 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-xenial to verification-done-xenial. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-xenial. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

Changed in broadcom-sta (Ubuntu Xenial):
status: New → Fix Committed
tags: added: verification-needed verification-needed-xenial
Marcelo Cerri (mhcerri) on 2017-11-30
tags: added: verification-done verification-done-xenial
removed: verification-needed verification-needed-xenial
Brian Murray (brian-murray) wrote :

This needs verification details.

Changed in broadcom-sta (Ubuntu Xenial):
status: Fix Committed → Incomplete
Robie Basak (racb) on 2017-12-06
tags: added: verification-needed verification-needed-xenial
removed: verification-done verification-done-xenial
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Bug attachments