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 Kerne
@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, w
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 x8
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
Ti
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 start happening after an update/upgr
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.
https://bugs.launchpad.net/bugs/16099
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.
https://bugs.launchpad.net/bugs/1609
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.
https://bugs.launchpad.net/bugs/16099
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 thi
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.
https://bugs.launchpad.net/bugs/1
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.
https://bugs.launchpad.net/bugs/1609
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.
https://bugs.launchpad.net/bugs/1609913
** 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 3.2.
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.
https://bugs.launchpad.net/bugs/16099
** 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 3.13
** 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 3.19
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.
https://bugs.launchpad.net/bugs/1609
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: 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: 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
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, w
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.
https://bugs.launchpad.net/bugs/1609
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.
https://bugs.launchpad.net/bugs/1609
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.
https://bugs.launchpad.net/bugs/160
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: 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: 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
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.
https://bugs.launchpad.net/bugs/12
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.
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 Ker
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
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
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: 0x8800/0x
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
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 device
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:
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
Main
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 unle
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
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$
-
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 c
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 noap
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 in
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
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 someh
** 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: subproce
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 linux-image-4.4.0-34-g
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.
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: 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
** 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
Statu
** 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
Statu
--- 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
http://pe
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
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
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.
https://bugs.launc
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 subscrib
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:
https://wiki.ubuntu.com/DebuggingT
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 k
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 x86_64
** 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: s
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
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
Packa
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
/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 m
[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.
https://bugs.launchpad.net/bu
[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.
https://bugs.launchpad.net/bu
[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.
https://bugs.launchpad.net/bu
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.
Sure, I've rolled back to the working kernel after the boot failed.
Thank you!
Is there any thing I can do to fix this bug?
--
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:
** Changed in: kernel-sru-workflow/prepare-package-lbm
Status: Confirmed => Fix Released
** Changed in: kernel-sru-workflow/prepare-package-lbm
Assignee: Canonical Kernel Team (canonical-kernel-team) => Stefan Bader
(smb)
** Changed in: kernel-sru-workflow/promote-to-proposed
** Summary changed:
- linux-armadaxp: -proposed tracker
+ linux-armadaxp: 3.2.0-1671.97 -proposed tracker
** Description changed:
- This bug is for tracking the upload package. This
- bug will contain status and testing results related to that upload.
+ This bug is for tracking the 3.2.0-1671.
Sure, those BIOS fakeraid boards are getting rare (meaning only you can
do tests and provide info). So you can (with the current 16.04.1 kernel)
check whether the dmraid package is still installed. If yes, try to run
it in various modes (there is one to only show things, but also one that
is suppos
Unfortunately, it's the same behavior. As with all other 4.x kernels, I
see the following errors when installing the deb packages:
update-initramfs: Generating /boot/initrd.img-4.8.0-040800rc1-generic
W: Possible missing firmware /lib/firmware/i915/kbl_dmc_ver1.bin for module i915
W: Possible miss
101 - 175 of 175 matches
Mail list logo