Now I tried with the newest kernel 4.7.0-994-generic together with an
Xorg.conf.d fix from
https://github.com/linuxenko/ubuntu-skylake-i915-video-fix
It now works almost flawlessly over DP 4K 60hz.
--
You received this bug notification because you are a member of Kernel
Packages, which is subsc
Hi,
Im working now with 4.7.0-040700rc5-generic on Ubuntu 16.04 LTS.
no crashes since 4 days. Hurray!
Cheers,
Kevin
--
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/1589837
Title:
Kerne
FYI
I still have the issue on 3.13.0-91-generic (and 3.13.0-88-generic)
on a busy NFS server using XFS. I have this issue since 2015...
INFO: task kworker/1:2:31748 blocked for more than 120 seconds.
Not tainted 3.13.0-91-generic #138-Ubuntu
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs
@Hubert Of course it doesn't need a bisect when you already know the
commit the fixes it :) But i would sugest that we try to get it fixed in
xenial's kernel first. Unfortunately i can't assign the kernel team, can
you help out here?
** Changed in: linux (Ubuntu)
Status: Incomplete => Confi
I installed new BIOS but I also noticed on WD15 page that there is firmawer
update for dock also
http://www.dell.com/support/article/us/en/19/SLN301970 as stated there point 3
"Download and Install the Intel(R) Thunderbolt(TM) 3 Firmware Update."
sudo dmidecode -s bios-version && sudo dmidecode
On Lenovo Thinkpad X201 with docking station with two external monitors,
one on VGA, one on displayport effect is generally that the screen being
left just flickers slightly.
I have had the screen go black with flickering pixels on the side and
thought it was when crossing over slowly but just tri
Bisecting is proving problematic as 4.3 kernels don't boot.
--
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/1531768
Title:
[arm64] lockups some time after booting
Status in Auto Package
No, the hibernation takes place correctly and shuts the computer down.
As I restarted it, resuming worked correctly except for the transient graphical
glitch.
On a side note, yesterday evening my graphics card produced more and
more glitches and then simply crashed (it is to be replaced ; compute
Confirming this, using a Dell Latitude E5510 with Intel HD Graphics (on-
chip), together with a docking station PR02X and a two-monitor-setup (2x
BenQ GW2460, 1920x1080, DVI).
The problem occurs most of the time when scrolling in a full screen
application on the left screen using the scroll bar (c
Yes, I don't recall seeing this on 15.10 and I think that I had early
Alpha load of 16.04 this didn't occur on.
--
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/1599110
Title:
Blank screen
After more testing I can say that also the same screen on which I am
scrolling with the scroll bars can go black.
When the mouse switches between screens, I get a flickering in ~50% of
tries.
Please note that I'm using Kernel 4.4.0-28, which is newer than 4.4.0-24
which contains a fix for a simil
--- Comment From vaish...@in.ibm.com 2016-07-07 06:12 EDT---
*** Bug 143372 has been marked as a duplicate of 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/1572712
T
Tim, I've checked with kernel 3.13.0-92.139 from "proposed" and it solved
problem.
Thanks!
** Tags removed: verification-failed-trusty
** Tags added: verification-done-trusty
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubunt
** Tags added: needs-test-4.7-rc6
--
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/1568573
Title:
[Lenovo Thinkpad T460] Ultra Dock external displays not detected after
suspend/resume cy
Kevin, to clarify, how often would the kernel crash occur when using the
default Ubuntu 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/1589837
Title:
Kernel oops - BUG: unable to
You have been subscribed to a public bug:
* launch Ubuntu Cloud Image ami-6829ad7f on Amazon AWS (4.4.0-28-generic
#47-Ubuntu SMP Fri Jun 24 10:09:13 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux)
* login and check the /var/lib/cloud folder - all is ok, the
/var/lib/cloud/instance is linked to actual
bhat3, unfortunately, we don't know if the commit fixes it, as it hasn't
been tested on the original reporter's (Hubert Hesse) hardware.
** Changed in: linux (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Kernel
Packages, which i
Hubert Hesse, regarding your question, bisecting the Ubuntu kernel can
be tricky, hence you are better off refocusing onto the reverse bisect
of the mainline kernel to confirm the fix commit, and reverting it
causes the issue again.
--
You received this bug notification because you are a member o
You have been subscribed to a public bug:
* launch Ubuntu Cloud Image ami-6829ad7f on Amazon AWS (4.4.0-28-generic
#47-Ubuntu SMP Fri Jun 24 10:09:13 UTC 2016 x86_64 x86_64 x86_64
GNU/Linux)
* login and check the /var/lib/cloud folder - all is ok, the
/var/lib/cloud/instance is linked to actual i
I'd like to add: Same problem with left mouse button. Also, same,
extremely annoying, behaviour on X250.
--
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/1506817
Title:
left TPP/2 IBM Trac
Public bug reported:
* launch Ubuntu Cloud Image ami-6829ad7f on Amazon AWS (4.4.0-28-generic
#47-Ubuntu SMP Fri Jun 24 10:09:13 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux)
* login and check the /var/lib/cloud folder - all is ok, the
/var/lib/cloud/instance is linked to actual instance metadata, i
IbeeX, this bug report is being closed due to your last comment
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1599476/comments/10
regarding this being fixed with a BIOS update and dock firmware update.
For future reference you can manage the status of your own bugs by
clicking on the current
Public bug reported:
* launch Ubuntu Cloud Image ami-6829ad7f on Amazon AWS (4.4.0-28-generic
#47-Ubuntu SMP Fri Jun 24 10:09:13 UTC 2016 x86_64 x86_64 x86_64
GNU/Linux)
* login and check the /var/lib/cloud folder - all is ok, the
/var/lib/cloud/instance is linked to actual instance metadata, i.e
** Changed in: ubuntu-fan (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to ubuntu-fan in Ubuntu.
https://bugs.launchpad.net/bugs/1599816
Title:
Installing docker.io breaks cloud-init on Xenial
Stat
the kernel crash occured 3-5x in a working day (8.5 hours)
--
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/1589837
Title:
Kernel oops - BUG: unable to handle kernel NULL pointer dereferen
YS1, given you have hardware failure, let this report be closed.
However, if you have an issue with the new/modified setup, please file a
new report.
** Changed in: linux (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Kernel
Packa
Cliff Carson, 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
Kevin, the next step is to fully reverse commit bisect from kernel 4.4
to 4.7-rc5 in order to identify the last bad commit, followed
immediately by the first good one. Once this good commit has been
identified, it may be reviewed for backporting. Could you please do this
following
https://wiki.ubun
I enabled proposed and VMX is working fine using 4.4.0-30.49. Thanks!
--
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/1596557
Title:
Upstream patch "crypto: vmx - IV size failing on skcip
Still working it but here is the status on the bisect ...
Ubuntu 14.04 Latest Kernel = Good
Ubuntu 14.10 latest kernel = Bad
Breakdown of distro 14.10
kernel version 3.13.0-24.46 = good
kernel version 3.13.0-24.47 = good
kernel version 3.15.0-1.3 = bad, next into the commit tree
--
That would be a great test. I will also be out next week, so it would
be good timing for a week long run. The reverted test kernel can be
downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1470250/d215f91-reverted/trusty/
Before starting that test, can you test the upstream v3.14-rc1 kerne
fierabras66, please see comment #7 in this bug report for a workaround.
--
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/1550481
Title:
hpsa driver causing kernel panics on HP ProLiant DL3
@penalvch Thanks for the info, but can you assist us on how to test and
get a fix in xenial's kernel. I am out of kernel packaging since 2.6.33
and want to help to make xenial working on Thinkpads with docking
stations.
--
You received this bug notification because you are a member of Kernel
Pack
Tagging verification-done-xenial based on #3
** Tags removed: verification-needed-xenial
** Tags added: verification-done-xenial
--
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/1596557
Tit
** Changed in: mir
Milestone: 0.24.0 => 0.25.0
--
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/1552371
Title:
Unexpected display on
Status in Canonical System Image:
Incomplete
Sta
there is a IOMMU bug HP is debugging and for now you can disable IOMMU
and it should boot as well as should work fine. Once HP will identify
fix and release it we will integrate into Ubuntu 16.04.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscrib
Any chance that something is going to happen on this one. Having to
patch every kernel update is going to be a real pain if the provided
patch or something better does not get into the kernel.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed t
If we identify which commit from upstream fixed the issue, would it make
sense to release an update for Xenial?
Suspect it is this one but haven't tried to build yet:
https://github.com/torvalds/linux/commit/c8213a638f65bf487c10593c216525952cca3690
--
You received this bug notification because
--- Comment From balb...@au1.ibm.com 2016-07-06 20:56 EDT---
>From what I can see the following is the root cause of the issue
cgroup_threadgroup_rwsem almost serializes accesses on the system
1. stress-ng-brk has cgroup_threadgroup_rwsem held in read mode via
copy_process() and does a sc
** Tags added: kernel-da-key
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to ubuntu-fan in Ubuntu.
https://bugs.launchpad.net/bugs/1599822
Title:
Installing ubuntu-fan breaks cloud-init on Xenial
Status in ubuntu-fan package in Ubuntu:
Thank you for providing a patch, and making Ubuntu better.
Can you provide some information on the status of the patch with regards
to getting it merged upstream? Has it been sent upstream, what sort of
feedback has it received, is it getting applied to a subsystem
maintainer's tree, etc?
People
Thank you for providing a patch, and making Ubuntu better.
Can you provide some information on the status of the patch with regards
to getting it merged upstream? Has it been sent upstream, what sort of
feedback has it received, is it getting applied to a subsystem
maintainer's tree, etc?
People
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 th
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.7 kernel[0
Thank you for providing a patch, and making Ubuntu better.
Can you provide some information on the status of the patch with regards
to getting it merged upstream? Has it been sent upstream, what sort of
feedback has it received, is it getting applied to a subsystem
maintainer's tree, etc?
People
Thank you for providing a patch, and making Ubuntu better.
Can you provide some information on the status of the patch with regards
to getting it merged upstream? Has it been sent upstream, what sort of
feedback has it received, is it getting applied to a subsystem
maintainer's tree, etc?
People
Thank you for providing a patch, and making Ubuntu better.
Can you provide some information on the status of the patch with regards
to getting it merged upstream? Has it been sent upstream, what sort of
feedback has it received, is it getting applied to a subsystem
maintainer's tree, etc?
People
Thank you for providing a patch, and making Ubuntu better.
Can you provide some information on the status of the patch with regards
to getting it merged upstream? Has it been sent upstream, what sort of
feedback has it received, is it getting applied to a subsystem
maintainer's tree, etc?
People
Thank you for providing a patch, and making Ubuntu better.
Can you provide some information on the status of the patch with regards
to getting it merged upstream? Has it been sent upstream, what sort of
feedback has it received, is it getting applied to a subsystem
maintainer's tree, etc?
People
Thank you for providing a patch, and making Ubuntu better.
Can you provide some information on the status of the patch with regards
to getting it merged upstream? Has it been sent upstream, what sort of
feedback has it received, is it getting applied to a subsystem
maintainer's tree, etc?
People
Thank you for providing a patch, and making Ubuntu better.
Can you provide some information on the status of the patch with regards
to getting it merged upstream? Has it been sent upstream, what sort of
feedback has it received, is it getting applied to a subsystem
maintainer's tree, etc?
People
Thank you for providing a patch, and making Ubuntu better.
Can you provide some information on the status of the patch with regards
to getting it merged upstream? Has it been sent upstream, what sort of
feedback has it received, is it getting applied to a subsystem
maintainer's tree, etc?
People
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.7 kernel[0
Thank you for providing a patch, and making Ubuntu better.
Can you provide some information on the status of the patch with regards
to getting it merged upstream? Has it been sent upstream, what sort of
feedback has it received, is it getting applied to a subsystem
maintainer's tree, etc?
People
** Tags added: bot-stop-nagging
** Tags added: kernel-da-key
** Package changed: linux (Ubuntu) => ubuntu-touch-meta (Ubuntu)
** Changed in: ubuntu-touch-meta (Ubuntu)
Status: Confirmed => New
--
You received this bug notification because you are a member of Kernel
Packages, which is su
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
** Tags added: kernel-da-key
** Tags added: bot-stop-nagging
** Package changed: linux (Ubuntu) => ubuntu-touch-meta (Ubuntu)
** Changed in: ubuntu-touch-meta (Ubuntu)
Importance: Medium => Undecided
** Changed in: ubuntu-touc
** Tags added: kernel-da-key
** Changed in: linux-lts-trusty (Ubuntu)
Importance: Undecided => High
** Package changed: linux-lts-trusty (Ubuntu) => linux (Ubuntu)
** Also affects: linux (Ubuntu Trusty)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Trusty)
S
The commit that fixes this bug, may have introduced bug 1598197
** Changed in: linux (Ubuntu Trusty)
Assignee: (unassigned) => Gavin Guo (mimi0213kimo)
** Changed in: linux (Ubuntu)
Status: Confirmed => Fix Released
** 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.7 kernel[0
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.7 kernel[0
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 th
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.7 kernel[0
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.7 kernel[0
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.7 kernel[0
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.7 kernel[0
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.7 kernel[0
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.7 kernel[0
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.7 kernel[0
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 th
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.7 kernel[0
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 th
To perform a reverse bisect, we need to identify the last bad kernel
version and the first good one. We know that 4.4.14 is bad and 4.6
final is good.
Can you next test the upstream 4.5. kernel? It can be downloaded from:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.5-wily/
If it is also go
hi again Christopher,
Found some time to test various kernels as indicated. Here are the
results in correct chronological order:
0) 15.10 / kernel 4.2.0: last known good configuration
1) 16.04 / kernel 4.4.0: error found, bug reported
then tested:
2) v4.6-rc7-wily / 4.6.0: works as expected
3) v4
** Changed in: linux (Ubuntu Wily)
Status: In Progress => Fix Committed
** Changed in: linux (Ubuntu Vivid)
Status: In Progress => Fix Committed
** Changed in: linux (Ubuntu Trusty)
Status: In Progress => Fix Committed
** Changed in: linux (Ubuntu Precise)
Status: In
Thank you Joseph, I will test v4.7-rc6 mainline build.
This is another first for me, so I need some time to learn this, plus I
will set up and install Ubuntu 16.04 on a different machine to avoid
risks, and test the bug on another computer. Hopefully I will have this
all done within 24-48 hours.
tests ran: 10, failed: 1;
http://kernel.ubuntu.com/testing/3.19.0-65.73/modoc__3.19.0-65.73__2016-07-07_14-42-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/159663
Joseph,
thank you for your reply.
All the tests I've made were done starting from fresh install.
The issue persist on 4.7.0-040700rc6-generic (X64): at least 10 seconds before
have the keyboard working again.
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
** Tags added: k
I've restored the data and all kernels from Ubuntu-3.13.0-91.138 through
to the latest upstream v4.7-rc6 can attempt to mount the restored data
without oopsing the kernel. However, the data I have is definitely
broken and cannot be mounted, even btrfs-image -r on the image reports
a transid failu
Hi, I just wanted to keep this thread alive, as the bug seems still to be
present. I recently tried suspend with the Helix 2 and Ubuntu 16.04 and can
confirm the same behaviour.
This issue is being tracked on the kernel bugzilla:
https://bugzilla.kernel.org/show_bug.cgi?id=100171
There was a BIOS
tests ran: 2, failed: 0;
http://kernel.ubuntu.com/testing/3.19.0-65.73/modoc__3.19.0-65.73__2016-07-07_15-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/159663
Public bug reported:
To avoid git repo tag namespace collisions, the derivative kernel target
names should be embedded in their git 'release' tags, e.g. in the Ubuntu
Xenial git repo:
tag Ubuntu-raspi2-4.4.0-1017.23 instead of Ubuntu-4.4.0-1017.23
tag Ubuntu-snapdragon-4.4.0-1020.23 inst
** Description changed:
To avoid git repo tag namespace collisions, the derivative kernel target
names should be embedded in their git 'release' tags, e.g. in the Ubuntu
Xenial git repo:
tag Ubuntu-raspi2-4.4.0-1017.23 instead of Ubuntu-4.4.0-1017.23
tag Ubuntu-snapdragon-4.4.
tests ran: 18, failed: 3;
http://kernel.ubuntu.com/testing/3.19.0-65.73/modoc__3.19.0-65.73__2016-07-07_16-23-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/159663
Joseph,
Shotwell seems to be working across 3 Ubuntu machines now. Sometimes I
get a false-negative warning about the system not claiming the
device...but then the camera shows up somewhere else.
I think I'll skip the Upstream Kernel Test for now.
Thanks,
Richard
Time, upgrades & updates seem
** Summary changed:
- [FFe] ZFS pools should be automatically scrubbed
+ ZFS pools should be automatically scrubbed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1548009
Title:
ZFS
tests ran: 20, failed: 7;
http://kernel.ubuntu.com/testing/3.19.0-65.73/modoc__3.19.0-65.73__2016-07-07_17-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/159663
Here's the log from running `sudo unattended-upgrade --dry-run --debug`
in case it's helpful:
2016-07-07 16:58:53,281 INFO Initial blacklisted packages:
2016-07-07 16:58:53,282 INFO Starting unattended upgrades script
2016-07-07 16:58:53,282 INFO Allowed origins are:
['o=Ubuntu,a=precise-security
Public bug reported:
Below is result of perf report:
read_tsc /proc/kcore
│
│
│
│Disassembly of section load0:
│
│81037780 :
66,67 │ push
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/1599951
Title:
On read_tsc function issue.
S
Thanks guys, I really think the solution here will be to move onto the
lts-xenial kernel as all others lts- kernels will be end of life
shortly.
--
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
Exactly the same (and some more) problems are on my Lenovo X250
Broadwell machine with 4.4 kernel. I have tested 4.6.0, 4.6.3 and just
now 4.7-rc6. All issues disapeared.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
htt
Christopher, want to see if there is an additional failure after removing an
autostart desktop file. The journal indicates a problem in gnome-session and
indeed gsm-manager.c issues the failure message
"WARNING: Application 'at-spi-dbus-bus.desktop' failed to register before
timeout" after a 9
tests ran: 2, failed: 0;
http://kernel.ubuntu.com/testing/4.2.0-42.49/modoc__4.2.0-42.49__2016-07-07_18-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/1597053
tests ran: 18, failed: 3;
http://kernel.ubuntu.com/testing/4.2.0-42.49/modoc__4.2.0-42.49__2016-07-07_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/1597053
Started run on 3.14-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/1470250
Title:
[Hyper-V] Ubuntu 14.04.2 LTS Generation 2 SCSI Errors on VSS Based
Backups
Status in linux packag
** Changed in: linux (Ubuntu Trusty)
Status: In Progress => Fix Committed
--
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/1447485
Title:
serial: 8250_pci: Add support for 16 port E
tests ran: 3, failed: 1;
http://kernel.ubuntu.com/testing/4.4.0-30.49/ms10-35-mcdivittB0-kernel__4.4.0-30.49__2016-07-07_19-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.launchp
Same issue with the folowing BT headphones:
* Plantronic BackBeat FIT.
* Plantronic BackBeat PRO.
* B&O Beoplay H8.
The computer has a BT USB dongle:
Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)
CSR8510 A10
USB ID = 0a12:0001
The following procedure solved the problem for
Answer from asrock...
i think that this is more of an issue with the Kernel. I can ask the engineers
to look into it but as this OS is not on the tested list this does not warranty
an rma.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
Christopher,
Please find the post in the mailing list below
http://thread.gmane.org/gmane.linux.usb.general/144630/focus=144635
--
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/1534948
Titl
1 - 100 of 148 matches
Mail list logo
