A recent update has made this work flawlessly on every boot. No idea which update it was, but we're good now.
On Sat, Jun 4, 2016 at 2:46 PM, Christopher M. Penalver < christopher.m.penal...@gmail.com> wrote: > Greg Taylor, in order to allow additional upstream developers to examine > the issue, at your earliest convenience, could you please test the latest > upstream kernel available from > http://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D ? Please keep in > mind the following: > 1) The one to test is at the very top line at the top of the page (not the > daily folder). > 2) The release names are irrelevant. > 3) The folder time stamps aren't indicative of when the kernel actually > was released upstream. > 4) Install instructions are available at > https://wiki.ubuntu.com/Kernel/MainlineBuilds . > > If testing on your main install would be inconvenient, one may: > 1) Install Ubuntu to a different partition and then test this there. > 2) Backup, or clone the primary install. > > If the latest kernel did not allow you to test to the issue (ex. you > couldn't boot into the OS) please make a comment in your report about this, > and continue to test the next most recent kernel version until you can test > to the issue. Once you've tested the upstream kernel, please comment on > which kernel version specifically you tested. If this issue is fixed in the > mainline kernel, please add the following tags by clicking on the yellow > circle with a black pencil icon, next to the word Tags, located at the > bottom of the report description: > kernel-fixed-upstream > kernel-fixed-upstream-X.Y-rcZ > > Where X, and Y are the first two numbers of the kernel version, and Z is > the release candidate number if it exists. > > If the mainline kernel does not fix the issue, please add the following > tags: > kernel-bug-exists-upstream > kernel-bug-exists-upstream-X.Y-rcZ > > Please note, an error to install the kernel does not fit the criteria of > kernel-bug-exists-upstream. > > Also, you don't need to apport-collect further unless specifically > requested to do so. > > Once testing of the latest upstream kernel is complete, please mark this > report Status Confirmed. Please let us know your results. > > Thank you for your understanding. > > ** Tags added: latest-bios-01.02.00 > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1577113 > > Title: > 50/50 chance for BCM43602 to come up correctly during boot > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1577113/+subscriptions > -- 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/1577113 Title: 50/50 chance for BCM43602 to come up correctly during boot Status in linux package in Ubuntu: Incomplete Bug description: My BCM43602 has a 50/50 chance during boot of ever becoming "ready" and pulling an IP address. The problem seems to be this "link is not ready" and "already exists" loop. The log I sent was one of the cases where things eventually worked. If I get unlucky, it simply repeats the "already exists" / "not ready" loop indefinitely. I get a similar situation when suspending/resuming. I've already pulled the firmware and stuck it under /lib (see dmesg output for version). ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-21-generic 4.4.0-21.37 [modified: boot/vmlinuz-4.4.0-21-generic] ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC0: greg.taylor 2418 F.... pulseaudio CurrentDesktop: Unity Date: Sun May 1 01:11:42 2016 HibernationDevice: RESUME=UUID=efd205da-4a67-4d8a-9c0e-6f3036178157 InstallationDate: Installed on 2016-04-28 (3 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 0a5c:6410 Broadcom Corp. Bus 001 Device 003: ID 0c45:6713 Microdia Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 15 9550 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-21-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-21-generic N/A linux-backports-modules-4.4.0-21-generic N/A linux-firmware 1.157 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/07/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 01.02.00 dmi.board.name: 0N7TVV dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr01.02.00:bd04/07/2016:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA01:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 15 9550 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1577113/+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
