Note: for most of kernels tested, the suspend seem to work, the screen
turn blank and cpu fan seem off, but the CD drive make a noise (same as
when I boot) and then the system resume (with certain kernels, there is
no way to resume).
With 4.7:
the login screen is a little strange: the mouse
I'll test 3.5 kernel (suspend working with ubuntu12.04) for fun.
Please tell me if I can do something to help to resolve this issue, I'm
still running 12.04 just because of that!
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
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/1606384
Title:
Ubuntu does not boot with
This bug was fixed in the package linux - 4.4.0-33.52
---
linux (4.4.0-33.52) xenial; urgency=low
[ Seth Forshee ]
* Release Tracking Bug
- LP: #1605709
* [regression] NFS client: access problems after updating to kernel
4.4.0-31-generic (LP: #1603719)
- SAUCE:
This bug was fixed in the package linux - 4.4.0-33.52
---
linux (4.4.0-33.52) xenial; urgency=low
[ Seth Forshee ]
* Release Tracking Bug
- LP: #1605709
* [regression] NFS client: access problems after updating to kernel
4.4.0-31-generic (LP: #1603719)
- SAUCE:
With "sudo pm-suspend" the system quickly auto-resume (nearly nothing happen).
No terminal output.
--
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/1606178
Title:
Can't suspend to ram,
This bug was fixed in the package linux - 4.4.0-33.52
---
linux (4.4.0-33.52) xenial; urgency=low
[ Seth Forshee ]
* Release Tracking Bug
- LP: #1605709
* [regression] NFS client: access problems after updating to kernel
4.4.0-31-generic (LP: #1603719)
- SAUCE:
I tried with the upstream kernel :
nborisov@fisk:~$ uname -a
Linux fisk 4.7.0-040700-generic #201607241632 SMP Sun Jul 24 20:34:30 UTC 2016
x86_64 x86_64 x86_64 GNU/Linux
In the meantime I managed to find a sequence which can trigger this 100%
of the time on the ubuntu kernel. The following
Is there a way to obtain a vmlinux image for the upstream kernel as
built by ubuntu (without having to compile locally) so that I can
compare the disassemblies of the ftrace_stub ?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
This bug was fixed in the package linux - 4.4.0-33.52
---
linux (4.4.0-33.52) xenial; urgency=low
[ Seth Forshee ]
* Release Tracking Bug
- LP: #1605709
* [regression] NFS client: access problems after updating to kernel
4.4.0-31-generic (LP: #1603719)
- SAUCE:
This bug was fixed in the package linux - 4.4.0-33.52
---
linux (4.4.0-33.52) xenial; urgency=low
[ Seth Forshee ]
* Release Tracking Bug
- LP: #1605709
* [regression] NFS client: access problems after updating to kernel
4.4.0-31-generic (LP: #1603719)
- SAUCE:
This bug was fixed in the package linux - 4.4.0-33.52
---
linux (4.4.0-33.52) xenial; urgency=low
[ Seth Forshee ]
* Release Tracking Bug
- LP: #1605709
* [regression] NFS client: access problems after updating to kernel
4.4.0-31-generic (LP: #1603719)
- SAUCE:
** Package changed: ubuntu-release-upgrader (Ubuntu) => linux (Ubuntu)
--
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/1584557
Title:
Seagate external drive causes SCSI bus resets when
*** This bug is a duplicate of bug 1605709 ***
https://bugs.launchpad.net/bugs/1605709
This bug was fixed in the package linux - 4.4.0-33.52
---
linux (4.4.0-33.52) xenial; urgency=low
[ Seth Forshee ]
* Release Tracking Bug
- LP: #1605709
* [regression] NFS client:
This bug was fixed in the package linux-raspi2 - 4.4.0-1019.25
---
linux-raspi2 (4.4.0-1019.25) xenial; urgency=low
[ Seth Forshee ]
* Release Tracking Bug
- LP: #1605715
[ Ubuntu: 4.4.0-33.52 ]
* Release Tracking Bug
- LP: #1605709
* [regression] NFS client:
This bug was fixed in the package linux - 4.4.0-33.52
---
linux (4.4.0-33.52) xenial; urgency=low
[ Seth Forshee ]
* Release Tracking Bug
- LP: #1605709
* [regression] NFS client: access problems after updating to kernel
4.4.0-31-generic (LP: #1603719)
- SAUCE:
This bug was fixed in the package linux-snapdragon - 4.4.0-1022.25
---
linux-snapdragon (4.4.0-1022.25) xenial; urgency=low
[ Seth Forshee ]
* Release Tracking Bug
- LP: #1605716
[ Ubuntu: 4.4.0-33.52 ]
* Release Tracking Bug
- LP: #1605709
* [regression] NFS
Public bug reported:
Ubuntu does not boot with systemd, it boots with upstart choice in grub.
Workaround - alt+f1 during start and then start lightdm manually.
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-31-generic 4.4.0-31.50
ProcVersionSignature: 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/1584557
Title:
Seagate external drive causes
** Changed in: xorg-server (Debian)
Status: Unknown => New
--
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/1606103
Title:
modeset driver does not detect all screen resolutions
Not sure how to submit the SRU request. The page linked above talks
about verifying patches, and there are none attached to 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/1606030
This bug was fixed in the package linux - 4.4.0-33.52
---
linux (4.4.0-33.52) xenial; urgency=low
[ Seth Forshee ]
* Release Tracking Bug
- LP: #1605709
* [regression] NFS client: access problems after updating to kernel
4.4.0-31-generic (LP: #1603719)
- SAUCE:
This bug was fixed in the package linux - 4.4.0-33.52
---
linux (4.4.0-33.52) xenial; urgency=low
[ Seth Forshee ]
* Release Tracking Bug
- LP: #1605709
* [regression] NFS client: access problems after updating to kernel
4.4.0-31-generic (LP: #1603719)
- SAUCE:
This bug was fixed in the package linux-snapdragon - 4.4.0-1022.25
---
linux-snapdragon (4.4.0-1022.25) xenial; urgency=low
[ Seth Forshee ]
* Release Tracking Bug
- LP: #1605716
[ Ubuntu: 4.4.0-33.52 ]
* Release Tracking Bug
- LP: #1605709
* [regression] NFS
This bug has been reported on the Ubuntu ISO testing tracker.
A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1591704
** Tags added: iso-testing
--
You received this bug notification because you are a member of Kernel
Packages, which
The bisect reported the following as the first bad commit:
commit 1302fcf0d03e6ea74846c7fee14736306ab2ce4b
Author: Bjorn Helgaas
Date: Sat Aug 30 07:23:01 2014 -0600
PCI: Configure *all* devices, not just hot-added ones
I built a Xenial test kernel with a revert of
This bug was fixed in the package linux - 4.4.0-33.52
---
linux (4.4.0-33.52) xenial; urgency=low
[ Seth Forshee ]
* Release Tracking Bug
- LP: #1605709
* [regression] NFS client: access problems after updating to kernel
4.4.0-31-generic (LP: #1603719)
- SAUCE:
*** This bug is a duplicate of bug 1588946 ***
https://bugs.launchpad.net/bugs/1588946
This bug was fixed in the package linux - 4.4.0-33.52
---
linux (4.4.0-33.52) xenial; urgency=low
[ Seth Forshee ]
* Release Tracking Bug
- LP: #1605709
* [regression] NFS client:
This bug was fixed in the package linux - 4.4.0-33.52
---
linux (4.4.0-33.52) xenial; urgency=low
[ Seth Forshee ]
* Release Tracking Bug
- LP: #1605709
* [regression] NFS client: access problems after updating to kernel
4.4.0-31-generic (LP: #1603719)
- SAUCE:
This bug was fixed in the package linux-raspi2 - 4.4.0-1019.25
---
linux-raspi2 (4.4.0-1019.25) xenial; urgency=low
[ Seth Forshee ]
* Release Tracking Bug
- LP: #1605715
[ Ubuntu: 4.4.0-33.52 ]
* Release Tracking Bug
- LP: #1605709
* [regression] NFS client:
This bug was fixed in the package linux - 4.4.0-33.52
---
linux (4.4.0-33.52) xenial; urgency=low
[ Seth Forshee ]
* Release Tracking Bug
- LP: #1605709
* [regression] NFS client: access problems after updating to kernel
4.4.0-31-generic (LP: #1603719)
- SAUCE:
This bug was fixed in the package linux-snapdragon - 4.4.0-1022.25
---
linux-snapdragon (4.4.0-1022.25) xenial; urgency=low
[ Seth Forshee ]
* Release Tracking Bug
- LP: #1605716
[ Ubuntu: 4.4.0-33.52 ]
* Release Tracking Bug
- LP: #1605709
* [regression] NFS
This bug was fixed in the package linux - 4.4.0-33.52
---
linux (4.4.0-33.52) xenial; urgency=low
[ Seth Forshee ]
* Release Tracking Bug
- LP: #1605709
* [regression] NFS client: access problems after updating to kernel
4.4.0-31-generic (LP: #1603719)
- SAUCE:
This bug was fixed in the package linux - 4.4.0-33.52
---
linux (4.4.0-33.52) xenial; urgency=low
[ Seth Forshee ]
* Release Tracking Bug
- LP: #1605709
* [regression] NFS client: access problems after updating to kernel
4.4.0-31-generic (LP: #1603719)
- SAUCE:
This bug was fixed in the package linux - 4.4.0-33.52
---
linux (4.4.0-33.52) xenial; urgency=low
[ Seth Forshee ]
* Release Tracking Bug
- LP: #1605709
* [regression] NFS client: access problems after updating to kernel
4.4.0-31-generic (LP: #1603719)
- SAUCE:
This bug was fixed in the package linux - 4.4.0-33.52
---
linux (4.4.0-33.52) xenial; urgency=low
[ Seth Forshee ]
* Release Tracking Bug
- LP: #1605709
* [regression] NFS client: access problems after updating to kernel
4.4.0-31-generic (LP: #1603719)
- SAUCE:
This bug was fixed in the package linux - 4.4.0-33.52
---
linux (4.4.0-33.52) xenial; urgency=low
[ Seth Forshee ]
* Release Tracking Bug
- LP: #1605709
* [regression] NFS client: access problems after updating to kernel
4.4.0-31-generic (LP: #1603719)
- SAUCE:
This bug was fixed in the package linux - 4.4.0-33.52
---
linux (4.4.0-33.52) xenial; urgency=low
[ Seth Forshee ]
* Release Tracking Bug
- LP: #1605709
* [regression] NFS client: access problems after updating to kernel
4.4.0-31-generic (LP: #1603719)
- SAUCE:
This bug was fixed in the package linux - 4.4.0-33.52
---
linux (4.4.0-33.52) xenial; urgency=low
[ Seth Forshee ]
* Release Tracking Bug
- LP: #1605709
* [regression] NFS client: access problems after updating to kernel
4.4.0-31-generic (LP: #1603719)
- SAUCE:
This bug was fixed in the package linux - 4.4.0-33.52
---
linux (4.4.0-33.52) xenial; urgency=low
[ Seth Forshee ]
* Release Tracking Bug
- LP: #1605709
* [regression] NFS client: access problems after updating to kernel
4.4.0-31-generic (LP: #1603719)
- SAUCE:
This bug was fixed in the package linux-raspi2 - 4.4.0-1019.25
---
linux-raspi2 (4.4.0-1019.25) xenial; urgency=low
[ Seth Forshee ]
* Release Tracking Bug
- LP: #1605715
[ Ubuntu: 4.4.0-33.52 ]
* Release Tracking Bug
- LP: #1605709
* [regression] NFS client:
This bug was fixed in the package linux - 4.4.0-33.52
---
linux (4.4.0-33.52) xenial; urgency=low
[ Seth Forshee ]
* Release Tracking Bug
- LP: #1605709
* [regression] NFS client: access problems after updating to kernel
4.4.0-31-generic (LP: #1603719)
- SAUCE:
This bug was fixed in the package linux - 4.4.0-33.52
---
linux (4.4.0-33.52) xenial; urgency=low
[ Seth Forshee ]
* Release Tracking Bug
- LP: #1605709
* [regression] NFS client: access problems after updating to kernel
4.4.0-31-generic (LP: #1603719)
- SAUCE:
This bug was fixed in the package linux-raspi2 - 4.4.0-1019.25
---
linux-raspi2 (4.4.0-1019.25) xenial; urgency=low
[ Seth Forshee ]
* Release Tracking Bug
- LP: #1605715
[ Ubuntu: 4.4.0-33.52 ]
* Release Tracking Bug
- LP: #1605709
* [regression] NFS client:
This bug was fixed in the package linux - 4.4.0-33.52
---
linux (4.4.0-33.52) xenial; urgency=low
[ Seth Forshee ]
* Release Tracking Bug
- LP: #1605709
* [regression] NFS client: access problems after updating to kernel
4.4.0-31-generic (LP: #1603719)
- SAUCE:
This bug was fixed in the package linux - 4.4.0-33.52
---
linux (4.4.0-33.52) xenial; urgency=low
[ Seth Forshee ]
* Release Tracking Bug
- LP: #1605709
* [regression] NFS client: access problems after updating to kernel
4.4.0-31-generic (LP: #1603719)
- SAUCE:
This bug was fixed in the package linux - 4.4.0-33.52
---
linux (4.4.0-33.52) xenial; urgency=low
[ Seth Forshee ]
* Release Tracking Bug
- LP: #1605709
* [regression] NFS client: access problems after updating to kernel
4.4.0-31-generic (LP: #1603719)
- SAUCE:
This bug was fixed in the package linux-snapdragon - 4.4.0-1022.25
---
linux-snapdragon (4.4.0-1022.25) xenial; urgency=low
[ Seth Forshee ]
* Release Tracking Bug
- LP: #1605716
[ Ubuntu: 4.4.0-33.52 ]
* Release Tracking Bug
- LP: #1605709
* [regression] NFS
You have been subscribed to a public bug:
Seagate STEA1000400 external USB hard disk (USB ID 0bc2:2322) causes
continuous SCSI bus resets by default. As a workaround, disabling UAS
causes the device to work fine.
To disable UAS, I created a file in /etc/modprobe.d with the following contents:
Hi Seth, for 16.04 "apt install" works on local *.deb files, invoking
dpkg ion the process. I have previously installed dozens of packages
from debs via dpkg -i, and from what I've seen there's no difference
between that and apt install on 16.04. I also confirmed that 4.7 was
installed via uname
Evy Karavatselou, would the latest 4.7 (not the rc's) allow a test? If
not, could you please advise on 4.7-rc5/rc6?
** Tags removed: kernel-bug-exists-upstream-4.5
** Tags added: kernel-bug-exists-upstream-4.7-rc5
** Tags removed: kernel-bug-exists-upstream-4.7-rc5
** Tags added:
no difference on that particular older kernel. I'm testing 4.7.0 generic
kernel, as that just exited rc7. I have no specific reason to believe
that I will have different results with this one.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed
Thanks Rocko (my fellow Perthian?). It seems you're right the modeset
driver is just not /inventing/ the fake modes you desire.
** Changed in: linux (Ubuntu)
Status: Incomplete => Invalid
** Changed in: xorg-server (Ubuntu)
Status: Incomplete => Confirmed
** Summary changed:
-
sasha1024, it will help immensely if you filed a new report with the Ubuntu
repository kernel (not mainline/upstream) via a terminal:
ubuntu-bug linux
Please feel free to subscribe me to it.
For more on why this is helpful, please see
https://wiki.ubuntu.com/ReportingBugs.
** Changed in: linux
** Tags removed: kernel-bug-exists-upstream kernel-bug-exists-upstream-4.3-rc2
** Tags added: kernel-fixed-upstream kernel-fixed-upstream-4.7
needs-reverse-bisect
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
--- 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
This is the output for kernel 4.6.4-040604-generic (running back on
Ubuntu 16.04, but I guess that shouldn't make any difference if we're
just reading the kernel info):
/sys/class/drm/card0-eDP-1/modes:3840x2160
(There's a bunch of other modes but they are all for the various
resolutions on the
Default Comment by Bridge
** Attachment added: "screen session log from successful test on 14.04"
https://bugs.launchpad.net/bugs/1573062/+attachment/4707061/+files/14.04.log
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
--- 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
Thanks. Already two people have offert their support for debugging that
issue on such a printer they own. Hopefully, that can be tackled soon
too.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to hwdata in Ubuntu.
The output is the same for the 4.7.0 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/1606103
Title:
modeset driver does not detect all screen resolutions
Status in linux package
This bug is by far really complete, if I take into acount info posted
upstream.
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Added a linux-lts-xenial variant to the PPA.
--
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/1568729
Title:
divide error: [#1] SMP in task_numa_migrate - handle_mm_fault
Status in
Hi guys. Great to hear some news about this blocking issue (for my use
case).
Like explained in comment 21
(https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1269883/comments/21)
I reported the bug upstream on the kernel bugzilla instance
https://bugzilla.kernel.org/show_bug.cgi?id=75381
I
** Summary changed:
- [i915_bpo][APL] Add support for Intel BXT graphic [8086:5a84]
+ [i915_bpo][APL][BXT] Add support for new Intel chip [8086:5a84]
** Description changed:
- i915_bpo in Xenial doesn't support BXT graphic in Apollo Lake. We either
- got black screen or hardware acceleration
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/1606178
Title:
Can't suspend to ram, since
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
** Changed in: hwe-next
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/1606147
Title:
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
** Changed in: hwe-next
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/1606129
Title:
** Tags added: originate-from-1602502 somerville
--
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/1606129
Title:
[i915_bpo][APL] Add support for Intel BXT graphic [8086:5a84]
Status in
Also still affects me on Ubuntu 16.04.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1094744
Title:
MS Sculpt Touch Mouse needs to be re-paired periodically
Status in GNOME Bluetooth:
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: blueman (Ubuntu Precise)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: blueman (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
Hi,
I think bug 1594202 is another data point for this:
Jun 20 01:49:24 omicron kernel: [ 962.491873] audit: type=1400
audit(1466380164.941:90): apparmor="ALLOWED" operation="sendmsg"
info="Failed name lookup - disconnected path" error=-13
profile="/usr/lib/dovecot/log"
Actually the dovecot profiles are in apparmor and not dovecot source
packages - so it would be an apparmor task then.
--
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/1373070
Title:
full
** Tags added: originate-from-1582486 somerville
--
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/1606147
Title:
[APL][SAUCE] System works slowly due to a monitor bug
Status in HWE Next:
I have been running the -29 kernel from
http://people.canonical.com/~smb/lp1568729/ for about two weeks now, so
far without triggering the bug. With the kernel from Tim, the bug could
still be triggered. So it seems there were different patches.
I'll try the -33 kernel from ppa as well, to see if
Public bug reported:
I can't suspend to ram since linux 3.11, with ubuntu12.04. Older version (3.8,
3.5 etc..) suspend perfectly.
So, I can't suspend with ubuntu 14.04 and 16.04. :(
Solutions from here (specially test newer kernels) don't work for me:
Hello, the 4.7-rc7 kernel cannot be installed. With the 4.7.0-040700rc4
kernel installed the problem remains.
Thank you.
Evy Karavatselou
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Please test the build at the link below and let me know if it fixes the
issue. Thanks!
http://people.canonical.com/~sforshee/lp1605344/
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Additional info with DEBUG_SECTION_MISMATCH:
WARNING: vmlinux.o(.text.unlikely+0x3201): Section mismatch in reference from
the function new_kmalloc_cache() to the variable .init.rodata:kmalloc_info
The function new_kmalloc_cache() references
the variable __initconst kmalloc_info.
This is often
--- Comment From thierry.fa...@fr.ibm.com 2016-07-25 11:30 EDT---
Code being complete, waiting for Kernel 4.8 to be out for test
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
This version is working.
--
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/1571798
Title:
Broadwell ECRC Support missing in Ubuntu
Status in linux package in Ubuntu:
In Progress
Status
sure, but I will be able to test this weekend.
Regards
--
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/1602371
Title:
Touchpad incorrectly detected as PS/2 mouse in 'HP Pavillion 340G1'
** Bug watch added: hacking a member #512958
https://bugzilla.redhat.com/cgi-bin/bugreport.cgi?bug=512958
** Also affects: linux via
https://bugzilla.redhat.com/cgi-bin/bugreport.cgi?bug=512958
Importance: Unknown
Status: Unknown
--
You received this bug notification because you
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1454656
--
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/1563110
Title:
No sound on Asus e200ha, intel sst with cx2072x codec
Status
This bug is missing log files that will aid in diagnosing the problem.
>From a terminal window please run:
apport-collect 1606147
and then change the status of the bug to 'Confirmed'.
If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a
This bug might need reassigning to the kernel instead.
I'm guessing that (like Mir) the mode-setting driver doesn't invent in-
between modes like Xorg drivers do (and like legacy VGA BIOS's do for
old CRTs)
Please run this command to see if the kernel is the one failing to report those
modes:
** Also affects: linux via
http://bugzilla.kernel.org/show_bug.cgi?id=135691
Importance: Unknown
Status: Unknown
--
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/1603230
Title:
We had something similar-looking again, filed as Bug #1606098
--
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/1568729
Title:
divide error: [#1] SMP in task_numa_migrate -
Public bug reported:
[Impact]
We've found a bug on some Apollo Lake system makes it runs very slow.
[Fix]
Upstream already provided a workaround[1] to fix this problem. This
patches haven't been merged in latest(v4.7) release but already in
linux-next.
To fix this issue in Xenial it also
** Description changed:
[Impact]
We've found a bug on some Apollo Lake system makes it runs very slow.
+ From upstream it is caused by following reason:
+
+ "Monitored cached line may not wake up from mwait on certain Goldmont
+ based CPUs. This patch will avoid calling
USN needed
** Changed in: kernel-sru-workflow/security-signoff
Status: In Progress => Fix Released
--
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/1605709
Title:
linux:
The bisect was stopped because the first good kernel was found to
actually be bad. We can restart the bisect if we can find a good and
bad kernel again.
@Mike, could you test the v4.7 kernel and see if the bug is fixed in it?
It can be downloaded from:
This is not any more a supported feature - changing status
** Changed in: linux (Ubuntu)
Status: Triaged => Invalid
** Changed in: linux (Ubuntu)
Assignee: Taco Screen team (taco-screen-team) => (unassigned)
--
You received this bug notification because you are a member of Kernel
--- 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
@Kees: I assume it also works if file is just named board.bin? Since
that's the way it would be installed if we ship it in linux-firmware ...
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
** Tags removed: targetmilestone-inin--- verification-needed
** Tags added: targetmilestone-inin16041 verification-done
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to makedumpfile in Ubuntu.
https://bugs.launchpad.net/bugs/1568952
*** This bug is a duplicate of bug 1416557 ***
https://bugs.launchpad.net/bugs/1416557
The bug can still be reproduced using mainline kernel version 4.7
installed from http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.7/
--
You received this bug notification because you are a member of
This is not any more a valid request - changing status to invalid
** Changed in: linux (Ubuntu)
Status: Incomplete => Invalid
** Changed in: linux (Ubuntu)
Assignee: Canonical Kernel Team (canonical-kernel-team) => (unassigned)
--
You received this bug notification because you are
I tested this (both IPv4 over Geneve and IPv6 over sit) as well as
looked at the proposed patch and everything looks good to me.
With a very simple setup (this does not go up to VMs so the full
performance difference is not there), I see correct packet aggregation
and improved performance:
1 - 100 of 169 matches
Mail list logo