Public bug reported:
This bug is for tracking the upload package. This
bug will contain status and testing results related to that upload.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
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
I built a Yakkety test kernel with that patch, which can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1632786/yakkety/
Can you test this kernel and see if it resolves this bug?
I'll also build P, T and X test kernels with this patch and post links
to them.
--
You received this
Steps to Reproduce:
- Cluster setup configuration (4x2)
- Windows server 2016
- Setup array for cluster
- Installed Failover Cluster and HyperV on all nodes.
- Created VMs and IOs volumes on both CSV and non-CSV (Cluster Shared Volume).
- Started I/O on VMs.
- Started graceful node failover test,
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
Derivative packages from packages here can be worked on, the following tracking
bugs were opened for them:
linux-ti-omap4 - bug 1632802
linux-armadaxp - bug 1632806
** Description changed:
This bug is for tracking the 3.2.0-112.154 upload package. This bug will
contain status and testing
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
After last update problem solved on MSI A75MA-P35 but problem still
persists on ASUS F1A75-V EVO
--
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/1515169
Title:
[i915_bpo][SKL-U] System
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
Dude, it's obviously not the BIOS.
--
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/1580311
Title:
Laptop boots only if external display connected
Status in linux package in Ubuntu:
Public bug reported:
This bug is for tracking the upload package. This
bug will contain status and testing results related to that upload.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
This tracking bug was opened to be worked from linux-3.2.0-112.154
update (bug 1632801)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-armadaxp in Ubuntu.
https://bugs.launchpad.net/bugs/1632806
Title:
linux-armadaxp: -proposed
This was taken from a live session, i wanted to install ubuntu on the SD
card because the internal storage has windows on it and its too small
for 2 OS. I tried the 16.04 LTS and it had this problem, then i tried
one of the daily builds(the bug report came from that).
I can try to test it with
** 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) => Seth Forshee
(sforshee)
** Description changed:
This bug is for
Will check tomorrow, with mainline kernel on test machine. However not
sure zfs modules will build against it. (containers run under zfs
backend)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** 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/1632829
Title:
bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu0.1: bcmwl kernel module
failed to
Public bug reported:
The laptop hangs completely and the screen goes black , there is nothing
i can do other than restart the computer
ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu0.1
ProcVersionSignature: Ubuntu
Unfortunately, zfs modules dkms failed with mainline 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/1631406
Title:
Wrong memory.stat values in container root cgroup
Status in
** 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) => Seth Forshee
(sforshee)
** Description changed:
This bug is for tracking
Public bug reported:
This bug is for tracking the 3.13.0-99.146 upload package. This bug will
contain status and testing results related to that upload.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
** Changed in: kernel-sru-workflow/prepare-package
Status: New => Confirmed
** Changed in: kernel-sru-workflow/prepare-package-meta
Status: New => Confirmed
** Changed in: kernel-sru-workflow/prepare-package-meta
Status: Confirmed => Fix Released
** Changed in:
Christopher, since bug report 153241 documents the bisecting the kernels
to isolate this problem, is there any reason for Raymond and I to do
likewise?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** Summary changed:
- linux-ti-omap4: -proposed tracker
+ linux-ti-omap4: 3.2.0-1490.117 -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
** Changed in: kernel-sru-workflow/promote-to-updates
Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Andy
Whitcroft (apw)
** Changed in: kernel-sru-workflow/promote-to-updates
Status: Confirmed => In Progress
** Changed in: kernel-sru-workflow/promote-to-security
Public bug reported:
I really have no idea. All I know is this happened when my computer was
attempting an auto-update. I don't know if that helpful or not but that
is about all the info I can give you. Sorry.
ProblemType: Package
DistroRelease: Ubuntu 14.04
Package:
The package has been published and the bug is being set to Fix Released
** Changed in: kernel-sru-workflow/promote-to-security
Status: In Progress => Fix Released
** Changed in: kernel-sru-workflow/promote-to-updates
Status: In Progress => Fix Released
** Changed in:
The package has been published and the bug is being set to Fix Released
** Changed in: kernel-sru-workflow/promote-to-security
Status: In Progress => Fix Released
** Changed in: kernel-sru-workflow/promote-to-updates
Status: In Progress => Fix Released
** Changed in:
Derivative packages from packages here can be worked on, the following tracking
bugs were opened for them:
linux-keystone - bug 1632846
Backport packages from packages here can be worked on, the following tracking
bugs were opened for them:
linux-lts-trusty (precise1) - bug 1632849
** Changed
Public bug reported:
This bug is for tracking the 3.13.0-99.146~precise1 upload package. This
bug will contain status and testing results related to that upload.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties
** Changed in: kernel-sru-workflow/prepare-package
Status: New => Confirmed
** Changed in: kernel-sru-workflow/prepare-package-meta
Status: New => Confirmed
** Changed in: kernel-sru-workflow/prepare-package-signed
Status: New => Confirmed
** Description changed:
This
It still doesnt work on my Asus Rog G751JT with Ubuntu 16.10
--
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/1598571
Title:
Audio-out on Asus X555 dont work
Status in linux package in
By the way this is almost certainly an upstream bug because headphone
jack is also not working on several other distributions I tested, none
of them are Ubuntu based so this bug goes beyond Ubuntu.
--
You received this bug notification because you are a member of Kernel
Packages, which is
It's got something to do with the kernel. Done a quick test using the
latest kernel 4.4.0-42-generic. Restarted my pc and logged in. Opened
terminal and mem usage was 1.8gb.
Done the same with the latest 4.8.1 kernel from ubuntu kernels page and
the usage was only 673mb.
Crazy!
--
You received
** 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) => Seth Forshee
(sforshee)
** Description changed:
This bug is for tracking
** Changed in: kernel-sru-workflow/prepare-package
Status: Confirmed => Fix Released
** Changed in: kernel-sru-workflow/prepare-package
Assignee: ubuntu-armel-kernel (ubuntu-armel-kernel) => Seth Forshee
(sforshee)
--
You received this bug notification because you are a member of
Not sure if this helps, but I was having similar issues on my Dell
Precision 7510. I edited /etc/grub/default as listed in this link and it
is now working: http://askubuntu.com/questions/58627/resume-from-
suspend-occasionally-causes-a-restart
--
You received this bug notification because you
There should be a Trusty test kernel soon. I've had to identify 13
prereq commits to get the two patches to apply and build properly.
For Xenial and newer, there has been positive test results from Emsi and
faulpeltz with Alexs' patch and the one from faulpeltz. Are we
comfortable with
** Changed in: kernel-development-workflow/prepare-package-meta
Status: Confirmed => Fix Released
** Changed in: kernel-development-workflow/prepare-package-meta
Assignee: Canonical Kernel Team (canonical-kernel-team) => Seth Forshee
(sforshee)
** Changed in:
--- Comment From pt...@cn.ibm.com 2016-10-12 01:45 EDT---
We can reproduce this bug with 4.8.0-22-generic. When the patch will be
applied, please?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
@Khurshid Alam
Well, I do confirm that adding the 4.4.0-22 kernel, there was a drop in
the memory usage.
Initially, the system started with 1.2 gb.
I disabled evolution processes as suggested above.
cd /usr/share/dbus-1/services
sudo ln -snf /dev/null
It sounded to me the old value would be around 41 or so, and the
motivation to increase was a need to have it only slightly bigger?
Meanwhile, the Qt patch is about freeing "2 more bits" so maybe 46 or 47
would work too, unless 48 is the magical "good" value that is wanted to
be had.
--
You
This issue disappear for Ubuntu16.10-desktop64-beta2 when test ESX6.0GA
and ESXi6.5 build 4491798.
--
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/1566708
Title:
Failed to boot when
This issue disappear for Ubuntu16.10-desktop64 when test ESX6.0GA and
ESXi6.5 build 4491798.
--
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/1566708
Title:
Failed to boot when install
The kernel running on the builders is a custom fork at the moment, which
isn't a good long-term situation, so please don't mark the kernel task
here as Fix Released.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
I tested the kernel tip from your debs and the issue is very much alive.
Here is the requested dump: http://paste.ubuntu.com/23312351/
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
--- Comment From laurent.duf...@fr.ibm.com 2016-10-12 05:12 EDT---
*** Bug 146776 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.
--- Comment From cdead...@us.ibm.com 2016-10-12 11:10 EDT---
The severity of defect SW355349 was increased from 2 to 1
because defect SW368742 was rejected as the duplicate of defect SW355349 and
the severity of defect SW368742 was higher than 2
--
You received this bug notification
--- Comment on attachment From geral...@de.ibm.com 2016-09-06 10:25
EDT---
Debian kernel package with genwqe-bad-page.patch applied.
** Attachment added: "linux-image-4.4.0-33.52+_4.4.0-33.52+-6_s390x.deb"
3296990ec94af7bc63af3eef065f148326a86bf5 ('UBUNTU: SAUCE: security,perf:
Allow further restriction of perf_event_open') was released in
Ubuntu-4.8.0-7.8
** Changed in: linux (Ubuntu Yakkety)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a
commit 05a05872c8d4b4357c9d913e6d73ae64882bddf5 ('lpfc: fix oops in
lpfc_sli4_scmd_to_wqidx_distr() from lpfc_send_taskmgmt()') was released
in Ubuntu-4.4.0-35.54 and Ubuntu-4.8.0-7.8
** Also affects: linux (Ubuntu Yakkety)
Importance: Medium
Status: Triaged
** Changed in: linux
--- Comment From cdead...@us.ibm.com 2016-10-12 11:03 EDT---
There is also another defect opened (SW360179) on a glacier park logging a
miscompare on another ubuntu 16.04 guest, but on a ubuntu 16.04 KVM host.
State: Assigned by: cde00 on 12 October 2016 09:54:03
--
You
--- Comment From cdead...@us.ibm.com 2016-10-12 11:26 EDT---
The severity of defect SW355349 was increased from 2 to 1
because defect SW368742 was rejected as the duplicate of defect SW355349 and
the severity of defect SW368742 was higher than 2
--
You received this bug notification
As a reference, 4.4.0-42.62 works fine with LUKS on the XPS13 9350 512GB SSD.
Maybe something else than NVMe this time... :/
--
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/1628546
Title:
Public bug reported:
[Impact]
The X-Gene Merlin board will hang and then crash.
[Test Case]
Have both the 1G and 10G interfaces connected, configured, and up. Bring down
the 1G interface via 'ifconfig eth0 down'. Start the iperf server, i.e. iperf
-s. From a separate system on the same 10G
The backtrace was added at bug creation.
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Craig Magina (craig.magina)
--
You received this bug notification because you are a member of Kernel
Packages, which is
The driver seems not to work in modern Ubuntu distros; I'm using 14.04,
and the presence of the 5602 ALi Corp. Video Camera Controller is
recognized, but neither Cheese nor Skype can access the image capture
(capture frame shows a black image).
Any ideas?
--
You received this bug notification
BTW, I'm using the Xenial kernel (4.4.0-42)
--
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/55567
Title:
m560x webcam doesn't work
Status in linux package in Ubuntu:
Invalid
Status in
** Changed in: kernel-development-workflow/prepare-package
Status: New => Confirmed
** Changed in: kernel-development-workflow/prepare-package-meta
Status: New => Confirmed
** Changed in: kernel-development-workflow/prepare-package-signed
Status: New => Confirmed
**
Bug #1632322 - about computers with _only_ an NVIDIA card refusing to
boot with proprietary drivers, because of GDM3 - was declared a
duplicate of this bug yesterday and further discussion was to be
conducted here. Hence my posting here to point out that bug #1632322 is
_not_ a duplicate.
Bug
--- Comment From cha...@us.ibm.com 2016-10-12 10:47 EDT---
(In reply to comment #25)
> I cannot tell what kernel version caused this stack dump, but
> Ubuntu-4.4.0-42.62 has yet to be uploaded.
OK. Thanks. I was going by the 4.4.0-42-generic #62-Ubuntu in the kernel
oops output.
---
Ok, problem solved, nothing related to the kernel, sorry for the post :(
in short: I install new ram the day before, around 15 boot crash with testing,
it he process I lost pam.d/common-auth file and /etc/crypttab ...
This missing file let me think I have the same bug.
Now 4.4.0-42.62 is
Nish - is this bug still present ? The daily ISO can be found at
http://cdimage.ubuntu.com/ubuntu-server/daily/current/yakkety-server-
powerpc.iso
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
This bug is missing log files that will aid in diagnosing the problem.
>From a terminal window please run:
apport-collect 1632739
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
commit 135e8c9250dd5c8c9aae5984fde6f230d0cbfeaf ('sched/core: Fix a race
between try_to_wake_up() and a woken up task') was released in
Ubuntu-4.8.0-7.8
** Also affects: linux (Ubuntu Yakkety)
Importance: Undecided
Assignee: Taco Screen team (taco-screen-team)
Status: New
**
Public bug reported:
This bug is for tracking the 4.8.0-24.26 upload package. This bug will
contain status and testing results related to that upload.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
** Affects:
Hi Tim,
Discussed this with Josh Powers and it seems at least this particular
issue is now fixed, sorry for the delay on my end.
-Nish
** Changed in: linux (Ubuntu Yakkety)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Kernel
*** This bug is a duplicate of bug 1632749 ***
https://bugs.launchpad.net/bugs/1632749
** This bug has been marked a duplicate of bug 1632749
linux: 4.8.0-24.26 -proposed tracker
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
I faced the problem via another reported bug for Gajim which tries to read teh
/proc files on startup.
https://bugs.launchpad.net/ubuntu/+source/gajim/+bug/1452006
The workaround for the Gajim issue was by restricting access to root as
suggested in above bug description.
My affected system is
** Also affects: linux (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Xenial)
Status: New => Fix Committed
** Changed in: linux (Ubuntu Xenial)
Importance: Undecided => High
** Changed in: linux (Ubuntu Xenial)
Assignee: (unassigned) =>
Like 1st post, exactly the same for me with new kernel 4.4.0-42.62
Hardware: Dell E5410/4GB i5/512Gb SSD, 16.04.1 LTS 64b full root
encryption.
Drop to initramfs without prompting to enter luks password.
Boot back with previous 4.4.0-38.57 is fine, no solution with update-initramfs
-u
Can I
This bug is duplicate of LP #1632462
--
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/1632466
Title:
STC860:Tuleta-L:KVM:iap03:HTX logs miscompares on multiple adapters on
ubuntu 16.04
Hi:
4.4.0-38: My computer was working perfectly.
4.4.0-41 and 4.4.0-42: My computer is "crashing" quite often.
When I go back to 4.4.0-38, my computer does not crash anymore.
When I see a crash, It's like having the nve drive disconnected.
All my environment crashes. If I do a "ls", I see that
Finally, I had time to test it with linux 4.8.0-040800.201610022031
amd64 and with the 4.8.0-22 versions. In both cases the problem still
exists. However, the content of the black rectangle has changed. It now
includes the first line of the console frame buffer (in a slightly
distorted way).
The
** Changed in: kernel-sru-workflow
Status: Fix Released => In Progress
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-ti-omap4 in Ubuntu.
https://bugs.launchpad.net/bugs/1626154
Title:
linux-ti-omap4: 3.2.0-1489.116
** No longer affects: linux (Ubuntu Wily)
** No longer affects: linux (Ubuntu Vivid)
--
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
** Changed in: kernel-sru-workflow
Status: Fix Released => In Progress
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-armadaxp in Ubuntu.
https://bugs.launchpad.net/bugs/1626155
Title:
linux-armadaxp: 3.2.0-1674.100
** Changed in: kernel-sru-workflow/promote-to-updates
Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Andy
Whitcroft (apw)
** Changed in: kernel-sru-workflow/promote-to-updates
Status: Confirmed => In Progress
** Changed in: kernel-sru-workflow/promote-to-security
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Joseph Salisbury (jsalisbury)
** Changed in: linux (Ubuntu)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to kexec-tools in Ubuntu.
** Changed in: linux (Ubuntu)
Status: Fix Committed => Fix Released
** Changed in: hwe-next
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Public bug reported:
There's a commit add device ids to support new i219 Lan-on-motherboard:
commit deaa1d226af725d4e3a56527cdb506c3c30f9fd0
e1000e: Initial support for KabeLake
[Impact]
Add support for devices [8086:15e3], [8086:15d7], [8086:15d6],
[8086:15d8]. This patch only add device
** Tags added: originate-from-1596773 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/1632578
Title:
Add support for KabeLake i219-LOM chips
Status in HWE Next:
New
Status
This bug is missing log files that will aid in diagnosing the problem.
>From a terminal window please run:
apport-collect 1632578
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
Would it be possible for you to test the latest 4.4 based upstream
stable kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds .
Please test the latest v4.4 stable kernel[0].
Thanks in advance.
[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.4.24
--
You received this bug
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 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
Did this issue start happening after an update/upgrade? Was there a
kernel version where you were not having this particular problem? This
will help determine if the problem you are seeing is the result of a
regression, and when this regression was introduced. If this is a
regression, we can
This affects 16.10, 16.04, 14.04, and 12.04. Please apply this patch to
the HWE kernels for the LTS releases.
--
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/1632786
Title:
[Hyper-V] do
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 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
Did this issue start happening after an update/upgrade? Was there a
kernel version where you were not having this particular problem? This
will help determine if the problem you are seeing is the result of a
regression, and when this regression was introduced. If this is a
regression, we can
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 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
--- Comment From cha...@us.ibm.com 2016-10-12 14:29 EDT---
Ok. 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/1626222
Title:
STC860:alpine-pdq:alpdq5p03: kernel panic
There are not test kernel for the other releases. They can be
downloaded from:
Precise: http://kernel.ubuntu.com/~jsalisbury/lp1632786/precise
Trusty: http://kernel.ubuntu.com/~jsalisbury/lp1632786/trusty
Xenial: http://kernel.ubuntu.com/~jsalisbury/lp1632786/xenial
--
You received this bug
** 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) => Seth Forshee
(sforshee)
--
You received this bug notification because you are a member
The linux firmware has been updated and the usbduxsigma firmware as
well. However it's still the _old_ firmware.
See the diff between the kernel git and what ubuntu has:
bp1@bp1-Precision-WorkStation-T5400:/tmp/linux-firmware$ diff
usbduxsigma_firmware.bin /lib/firmware/usbduxsigma_firmware.bin
Ok, I think I've found the problem... Please update to the latest pulse
package from my yakkety PPA, ppa:themuso/ppa. Let me know if it makes a
difference.
I've re-applied the touch bluez patches, but removed one problematic
hunk that was probably needed for vivid, but not for >= xenial.
--
You
** 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) => Seth Forshee
(sforshee)
--
You received this bug notification because you are a member
** Changed in: kernel-development-workflow/prepare-package
Status: Confirmed => Fix Released
** Changed in: kernel-development-workflow/prepare-package
Assignee: Canonical Kernel Team (canonical-kernel-team) => Seth Forshee
(sforshee)
** Description changed:
This bug is for
1 - 100 of 157 matches
Mail list logo
