The user-space tool that is responsible to set up fakeraid (except for
Intel MSM and DDS style meta-data). Make sure that package is still
installed and the dmraid command is still usable.
A rc1 mainline kernel is probably a bit too recent since the first
release candidate can always be unstable.
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]
** Changed in: linux (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]
** Changed in: linux (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]
** Changed in: linux (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
/scripts/init-top/udev: line 14: can't create /sys/kernel/uevent-helper:
Permission denied.
Gave up waiting for root device. Common problems:
- Boot args (cat /proc/cmdline)
- Check root delay= (did the system wait long enough?)
- Check root= (did the system wait for the right device?)
- Missing
I would also like to see this 'echo -e "-a"' fixed somehow as i also
used it as bell notification for remote ssh-jobs completing their
tasks... Thanks Anthony for asking the question!
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux
Sorry, I'm not able to boot my PC with kernel
4.8.0-040800rc1_4.8.0-040800rc1.201608072231.
The error message is as follows:
/scripts/init-top/udev: line 14: can't create /sys/kernel/uevent_helper:
permissions failed
--
You received this bug notification because you are a member of Kernel
tests ran: 136, failed: 0;
http://kernel.ubuntu.com/testing/4.6.0-10.12/onza__4.6.0-10.12__2016-08-10_02-34-00/results-index.html
--
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/1609913
** Tags removed: need-duplicate-check
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bcmwl in Ubuntu.
https://bugs.launchpad.net/bugs/1611587
Title:
package bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu2 failed to
install/upgrade:
Public bug reported:
i tried to install bdcomm software from additional software updates
section
ProblemType: Package
DistroRelease: Ubuntu 15.04
Package: bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu2
ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3
Uname: Linux 3.19.0-15-generic
This change was made by a bot.
** Changed in: linux (Ubuntu)
Status: New => Confirmed
--
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/1611583
Title:
Trackpad isn't recognized by
And the last one.
** Attachment added: "Xorg.0.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1611583/+attachment/4717916/+files/Xorg.0.log
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Looks like it only attached one of my files. Here is the next one.
** Attachment added: "xinput"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1611583/+attachment/4717915/+files/xinput
--
You received this bug notification because you are a member of Kernel
Packages, which is
Public bug reported:
I just got an ASUS F556UA-AS54 laptop and of course I immediately
deleted windows and installed ubuntu ;). Everything works fine, except
that the trackpad doesn't seem to be recognized properly. I am certain
that I have the bug on this page:
tests ran: 136, failed: 0;
http://kernel.ubuntu.com/testing/4.6.0-10.12/onibi__4.6.0-10.12__2016-08-10_01-35-00/results-index.html
--
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/1609913
tests ran: 136, failed: 0;
http://kernel.ubuntu.com/testing/4.6.0-10.12/onza__4.6.0-10.12__2016-08-10_01-18-00/results-index.html
--
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/1609913
--- Comment From balb...@au1.ibm.com 2016-07-17 21:43 EDT---
I tried the kernel at http://people.canonical.com/~kamal/lp1573062/lp1573062.1/
and it worked fine for me
--- Comment From balb...@au1.ibm.com 2016-07-19 01:04 EDT---
Looks like I got a failure with the run on
** Changed in: kernel-sru-workflow/prepare-package
Status: Confirmed => Fix Released
** Changed in: kernel-sru-workflow/prepare-package
Assignee: Canonical Kernel Team (canonical-kernel-team) => Stefan Bader
(smb)
** Changed in: kernel-sru-workflow/prepare-package-signed
** Changed in: kernel-sru-workflow/prepare-package-signed
Status: Confirmed => Fix Released
** Changed in: kernel-sru-workflow/prepare-package-signed
Assignee: Canonical Kernel Team (canonical-kernel-team) => Stefan Bader
(smb)
** Description changed:
This bug is for tracking the
** Changed in: kernel-sru-workflow/prepare-package
Status: Confirmed => Fix Released
** Changed in: kernel-sru-workflow/prepare-package
Assignee: Canonical Kernel Team (canonical-kernel-team) => Stefan Bader
(smb)
** Changed in: kernel-sru-workflow/prepare-package-signed
tests ran: 20, failed: 3;
http://kernel.ubuntu.com/testing/4.6.0-10.12/onibi__4.6.0-10.12__2016-08-09_23-48-00/results-index.html
--
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/1609913
tests ran: 20, failed: 2;
http://kernel.ubuntu.com/testing/4.6.0-10.12/onza__4.6.0-10.12__2016-08-09_23-30-00/results-index.html
--
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/1609913
tests ran: 136, failed: 0;
http://kernel.ubuntu.com/testing/4.6.0-10.12/dwalin__4.6.0-10.12__2016-08-09_23-08-00/results-index.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
This change was made by a bot.
** Changed in: linux (Ubuntu)
Status: New => Confirmed
--
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/1611552
Title:
package
** Tags removed: need-duplicate-check
--
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/1611552
Title:
package linux-image-4.4.0-34-generic 4.4.0-34.53 failed to
install/upgrade:
Public bug reported:
This error occurred when installing the most recent round of updates.
Running 'sudo dpkg -i /var/cache/apt/archives/linux-
image-4.4.0-34-generic_4.4.0-34.53_amd64.deb' then 'sudo apt-get install
-f' seemed to fix the problem.
Perhaps the installation of the kernel was
tests ran: 32, failed: 1;
http://kernel.ubuntu.com/testing/4.6.0-10.12/onibi__4.6.0-10.12__2016-08-09_22-12-00/results-index.html
--
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/1609913
Yakkety has 1.1.2 for utils and lib now.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to alsa-lib in Ubuntu.
https://bugs.launchpad.net/bugs/1565658
Title:
Upgrade to 1.1.2 that was released in August 2016
Status in alsa-lib package
This change was made by a bot.
** Changed in: linux (Ubuntu)
Status: New => Confirmed
--
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/1611536
Title:
Fan on full speed without
This change was made by a bot.
** Changed in: linux (Ubuntu)
Status: New => Confirmed
--
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/1611532
Title:
bluetooth USB dongle CSR8510
bp1@bp1-ThinkPad-X220:~/sandbox/rfcomm$ ./btscan
00:1F:CC:F4:25:E1 SGH-J700
00:06:66:7D:A9:D3 GN-ATTYS
bp1@bp1-ThinkPad-X220:~/sandbox/rfcomm$ ./btscan
00:06:66:7D:A9:D3 [unknown]
00:1F:CC:F4:25:E1 SGH-J700
bp1@bp1-ThinkPad-X220:~/sandbox/rfcomm$
Reported separate bug for noapic nolapic here:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1611536
--
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/1590154
Title:
System slow
tests ran: 35, failed: 4;
http://kernel.ubuntu.com/testing/4.6.0-10.12/onza__4.6.0-10.12__2016-08-09_21-36-00/results-index.html
--
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/1609913
Public bug reported:
Without adding noapic or nolapic to boot parameters the fan will run on
full speed, the system is sluggish (can almost see windows redrawing on
screen). On some kernel versions tested, rebooting also fails.
The parameter(s) were not required in Trusty. I also tested some
I can confirm 4.8.0 rc1 works great with noapic/nolapic and
"acpi_force_32bit_fadt_addr". Without the last parameter it uses 64-bit
FADT adress and the problem occurs.
Interestingly, mainline kernels 4.3.6, 4.2.8 and 4.1.29 seem not to
honor the parameter and use 64-bit adress no matter what.
--
Public bug reported:
- Do a rfcomm bind.
- Try a cat /dev/rfcomm0
In about 50% of cases the system completely freezes. In the other 40% the
rfcomm data is garbled. In the remaining 10% the data is fine.
The bt device at the other end is an RN42 which transmits text data.
When scanning for
tests ran: 3, failed: 1;
http://kernel.ubuntu.com/testing/4.6.0-10.12/onibi__4.6.0-10.12__2016-08-09_20-54-00/results-index.html
--
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/1609913
I did some further testing and it seems I have found a culprit and a
solution. In older kernel versions (3.19.8 and 4.0.9 worked flawlessly
without extra boot parameters) I get something like this when booting:
ACPI BIOS Warning (bug): 32/64X address mismatch in
FADT/Pm2ControlBlock:
tests ran: 136, failed: 0;
http://kernel.ubuntu.com/testing/4.6.0-10.12/modoc__4.6.0-10.12__2016-08-09_20-49-00/results-index.html
--
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/1609913
tests ran: 3, failed: 1;
http://kernel.ubuntu.com/testing/4.6.0-10.12/onza__4.6.0-10.12__2016-08-09_20-38-00/results-index.html
--
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/1609913
** Changed in: kernel-sru-workflow/prepare-package
Status: Confirmed => Fix Released
** Changed in: kernel-sru-workflow/prepare-package
Assignee: Canonical Kernel Team (canonical-kernel-team) => Stefan Bader
(smb)
--
You received this bug notification because you are a member of
tests ran: 35, failed: 4;
http://kernel.ubuntu.com/testing/4.6.0-10.12/dwalin__4.6.0-10.12__2016-08-09_20-24-00/results-index.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Workaround does not work on Xenial 16.04 in a Fusion 8.1.1 box:
sys/module/hid_apple does not exist and can not be created, even with
sudo.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
tests ran: 5, failed: 3;
http://kernel.ubuntu.com/testing/4.6.0-10.12/onza__4.6.0-10.12__2016-08-09_19-40-00/results-index.html
--
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/1609913
tests ran: 10, failed: 1;
http://kernel.ubuntu.com/testing/4.6.0-10.12/modoc__4.6.0-10.12__2016-08-09_19-36-00/results-index.html
--
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/1609913
tests ran: 10, failed: 1;
http://kernel.ubuntu.com/testing/4.6.0-10.12/onibi__4.6.0-10.12__2016-08-09_19-43-00/results-index.html
--
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/1609913
tests ran: 136, failed: 27;
http://kernel.ubuntu.com/testing/4.6.0-10.12/s2lp6g002__4.6.0-10.12__2016-08-09_19-43-00/results-index.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
tests ran: 19, failed: 7;
http://kernel.ubuntu.com/testing/4.6.0-10.12/s2lp6g002__4.6.0-10.12__2016-08-09_19-01-00/results-index.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
tests ran: 136, failed: 27;
http://kernel.ubuntu.com/testing/4.6.0-10.12/kernel02__4.6.0-10.12__2016-08-09_19-07-00/results-index.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
That is good news the 4.7 kernel does not exhibit the bug. We should be
able to perform a "Reverse" bisect to identify the commit that fixes the
bug.
We should next test the latest 4.4.16 upstream stable kernel to see if
the fix was already sent to upstream stable?
If 4.4.16 still has the bug,
tests ran: 35, failed: 4;
http://kernel.ubuntu.com/testing/4.6.0-10.12/modoc__4.6.0-10.12__2016-08-09_18-34-00/results-index.html
--
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/1609913
tests ran: 10, failed: 0;
http://kernel.ubuntu.com/testing/4.6.0-10.12/onibi__4.6.0-10.12__2016-08-09_18-21-00/results-index.html
--
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/1609913
tests ran: 10, failed: 0;
http://kernel.ubuntu.com/testing/4.6.0-10.12/onza__4.6.0-10.12__2016-08-09_18-09-00/results-index.html
--
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/1609913
tests ran: 32, failed: 1;
http://kernel.ubuntu.com/testing/4.6.0-10.12/s2lp6g002__4.6.0-10.12__2016-08-09_18-33-00/results-index.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** Changed in: kernel-sru-workflow/prepare-package-meta
Status: Confirmed => Fix Released
** Changed in: kernel-sru-workflow/prepare-package-meta
Assignee: Canonical Kernel Team (canonical-kernel-team) => Stefan Bader
(smb)
** Description changed:
This bug is for tracking the
** Changed in: kernel-sru-workflow/prepare-package-meta
Status: Confirmed => Fix Released
** Changed in: kernel-sru-workflow/prepare-package-meta
Assignee: Canonical Kernel Team (canonical-kernel-team) => Stefan Bader
(smb)
** Description changed:
This bug is for tracking the
tests ran: 32, failed: 2;
http://kernel.ubuntu.com/testing/4.6.0-10.12/kernel02__4.6.0-10.12__2016-08-09_18-26-00/results-index.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** Changed in: kernel-sru-workflow/prepare-package-meta
Status: Confirmed => Fix Released
** Changed in: kernel-sru-workflow/prepare-package-meta
Assignee: Canonical Kernel Team (canonical-kernel-team) => Stefan Bader
(smb)
** Description changed:
This bug is for tracking the
tests ran: 10, failed: 0;
http://kernel.ubuntu.com/testing/4.6.0-10.12/dwalin__4.6.0-10.12__2016-08-09_18-06-00/results-index.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
tests ran: 5, failed: 4;
http://kernel.ubuntu.com/testing/4.6.0-10.12/s2lp6g002__4.6.0-10.12__2016-08-09_18-11-00/results-index.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
1) It was fresh install on new laptop.
2) It look like amd64 arch is not affected by this bug
3) will try to retest i386 mainline tomorrow
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
I did get the system to boot in 4.4.0-34 without noapic and nolapic -
but the fan was running on full (separate issue?). However, the system
seemed even slower than when booting WITH said parameters.
4.8 rc1 failed to boot without noapic nolapic, however fan was also on
full.
--
You received
tests ran: 5, failed: 4;
http://kernel.ubuntu.com/testing/4.6.0-10.12/kernel02__4.6.0-10.12__2016-08-09_18-11-00/results-index.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
tests ran: 10, failed: 2;
http://kernel.ubuntu.com/testing/4.6.0-10.12/s2lp6g002__4.6.0-10.12__2016-08-09_17-59-00/results-index.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
tests ran: 10, failed: 2;
http://kernel.ubuntu.com/testing/4.6.0-10.12/kernel02__4.6.0-10.12__2016-08-09_18-00-00/results-index.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Noticed this happening since upgrading to 16.04. But, I also started using
a usb mouse on this particular computer around the same time. I'll give the
upstream kernels a try and report back.
On Tue, Aug 9, 2016, 12:45 Joseph Salisbury
wrote:
> Did this issue
Problem remains in 4.8 rc1.
** Tags removed: kernel-bug-exists-upstream-4.7-rc2
** Tags added: kernel-bug-exists-upstream-4.8-rc1
--
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/1590154
Hi,
This is a fresh install of Ubuntu 16.04 on this laptop so I don't have
any previous install known to be working.
I've tried the latest v4.8 kernel and exactly the same issue and logs:
$ uname -a
Linux X2 4.8.0-040800rc1-generic #201608072231 SMP Mon Aug 8 02:33:57 UTC 2016
x86_64 x86_64
@jsalisbury: Yes, as far as I can trust my results
Currently running 488347f (which is reasonably close to 71425a9)
If the current one doesnt fail I would test d215f91 next, then 71425a9 and the
4.8rc1 mainline
--
You received this bug notification because you are a member of Kernel
Packages,
Can you also give the 4.8-rc1 kernel a try? If it still exhibits the
bug, we can perform a kernel bisect. 4.8-rc1 can be downloaded from:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.8-rc1/
** Tags added: needs-bisect
--
You received this bug notification because you are a member of
Yes, you can remove the mainline kernel with dpkg --purge
--
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/1611277
Title:
Kernel Shipped With Ubuntu 16.04.1 Cannot Recognize fakeRaid
@faulpeltz, so it sounds like we can confirm the latest commit to pass
in 3.13.0-34 is 95d1181?
If that is the case, it might be worthwhile for me to build a test
kernel with d215f91 as tip of the tree and a second kernel with 71425a9
as the tip. Just let me know if you could test those two
tests ran: 1, failed: 1;
http://kernel.ubuntu.com/testing/4.4.0-30.49/s2lp6g002__4.4.0-30.49__2016-08-09_16-53-00/results-index.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
tests ran: 10, failed: 1;
http://kernel.ubuntu.com/testing/4.6.0-10.12/dwalin__4.6.0-10.12__2016-08-09_16-34-00/results-index.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
tests ran: 19, failed: 17;
http://kernel.ubuntu.com/testing/4.4.0-30.49/s2lp6g002__4.4.0-30.49__2016-08-09_16-46-00/results-index.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
tests ran: 10, failed: 2;
http://kernel.ubuntu.com/testing/4.4.0-30.49/kernel02__4.4.0-30.49__2016-08-09_16-25-00/results-index.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
tests ran: 32, failed: 32;
http://kernel.ubuntu.com/testing/4.4.0-30.49/s2lp6g002__4.4.0-30.49__2016-08-09_16-38-00/results-index.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Did this issue start happening after an update/upgrade? Was there a
prior kernel version where you were not having this particular problem?
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.8
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.8 kernel[0].
If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.
If the mainline kernel does not fix
Would it be possible for you to test the latest upstream stable kernel?
Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the
latest v4.4 stable kernel[0].
If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.
If the mainline kernel
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.8 kernel[0].
If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.
If the mainline kernel does not fix
You may need to run the following from a terminal:
sudo apt-get install -f
sudo apt-get clean
sudo apt-get update
Then re-install the package or updates.
If that does not resolve your issue, please mark the bug as "Confirmed"
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
**
Did this issue start happening after an update/upgrade? Was there a
prior kernel version where you were not having this particular problem?
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.8
Did this issue start happening after an update/upgrade? Was there a
prior kernel version where you were not having this particular problem?
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.8
Did this issue start happening after an update/upgrade? Was there a
prior kernel version where you were not having this particular problem?
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.8
You may need to run the following from a terminal:
sudo apt-get install -f
sudo apt-get clean
sudo apt-get update
Then re-install the package or updates.
If that does not resolve your issue, please mark the bug as "Confirmed"
** Changed in: linux (Ubuntu)
Importance: Undecided => Low
**
Did this issue start happening after an update/upgrade? Was there a
prior kernel version where you were not having this particular problem?
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.8
Did this issue start happening after an update/upgrade? Was there a
prior kernel version where you were not having this particular problem?
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.8
tests ran: 5, failed: 5;
http://kernel.ubuntu.com/testing/4.4.0-30.49/s2lp6g002__4.4.0-30.49__2016-08-09_16-31-00/results-index.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
You may need to run the following from a terminal:
sudo apt-get install -f
sudo apt-get clean
sudo apt-get update
Then re-install the package or updates.
If that does not resolve your issue, please mark the bug as "Confirmed"
** Changed in: linux (Ubuntu)
Importance: Undecided => Low
**
Did this issue start happening after an update/upgrade? Was there a
prior kernel version where you were not having this particular problem?
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.8
Is testing the upstream kernel able to reverse back to the original
state just like I install the 4.4.0-34-generic on Ubuntu 14.04.4?
After the trial, am I able to remove the upstream kernel with apt-get
remove and purge? Thanks.
--
You received this bug notification because you are a member of
git://kernel.ubuntu.com/rtg/ubuntu-trusty.git arm64-efi-lp1608854
I backported EFI functionality for arm64 and amd64 from Utopic (v3.16)
to Trusty (v3.13) because much of the arch dependent infrastructure in
v3.16 is required in order to support signed module enforcement with a
MOK managed key
tests ran: 10, failed: 10;
http://kernel.ubuntu.com/testing/4.4.0-30.49/s2lp6g002__4.4.0-30.49__2016-08-09_16-25-00/results-index.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Will attempt to capture some more logs when the card is working and when
goes into the problematic state.
--
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/1600624
Title:
MacBook wifi
Attached to this comment is a debug log (non-working-state_modprobe.txt)
from the brcmfmac module while loading it but network-card failing to
come up as it should.
Module loaded with:
$ cat /etc/modprobe.d/brcmfmac.conf
options brcmfmac debug=0xff roamoff=1
** Attachment added:
Adding log (nonworking-rmmod.txt) from when unloading the module too...
** Attachment added: "nonworking-rmmod.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1600624/+attachment/4717654/+files/nonworking-rmmod.txt
--
You received this bug notification because you are a member of
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.7 kernel[0].
If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.
If the mainline kernel does not fix
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.7 kernel[0].
If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.
If the mainline kernel does not fix
Comment #17 should have said the "latest v4.8 kernel"
--
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/1611277
Title:
Kernel Shipped With Ubuntu 16.04.1 Cannot Recognize fakeRaid
Status
1 - 100 of 174 matches
Mail list logo