Public bug reported:
Fetched 63.6 MB in 36s (1,765 kB/s)
Selecting previously unselected package linux-image-3.16.0-50-generic.
(Reading database ... 246351 files and directories currently installed.)
Preparing to unpack
** Tags removed: need-duplicate-check
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-lts-utopic in Ubuntu.
https://bugs.launchpad.net/bugs/1500696
Title:
package linux-image-extra-3.16.0-50-generic (not installed) failed to
I have a Aspire e5-573-56rg.
The 1.25 bios update prevents usage/installation of linux.
See: http://community.acer.com/t5/E-and-M-Series/Acer-Aspire-e5-573g-
You-can-not-install-any-one-Linux/td-p/386009
I think this particular wireless driver is just unsupported at the
moment.
--
You
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]
** Changed in: linux (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]
** Changed in: linux (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** Also affects: linux (Ubuntu Wily)
Importance: Undecided
Assignee: Taco Screen team (taco-screen-team)
Status: 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/1500672
7b3c0b652380893cdb8139045b093ce4b8e57264 ('UBUNTU: SAUCE: cpufreq:
powernv: Handle throttling due to Pmax capping at chip level') has been
applied since Ubuntu-4.2.0-6.6.
Applied:
cpufreq : powernv: Report Pmax throttling if capped below nominal frequency
cpufreq: powernv: Increase the verbosity
Thank you for taking the time to report this bug and helping to make
Ubuntu better. It seems that there was an error on your system when
trying to install a particular package. Please execute the following
command, as it will clear your package cache, in a terminal:
sudo apt-get clean
Then try
--- Comment From mro...@us.ibm.com 2015-09-28 19:24 EDT---
(In reply to comment #13)
> Kernel freeze is Oct 8. Any chance these will make it into 4.3 by then ?
It's still a possibility seeing as there is another rc round before
10/8.
I had heard previously that there was a 10/2 cutoff,
*** This bug is a duplicate of bug 1429250 ***
https://bugs.launchpad.net/bugs/1429250
Fixed released already in 14.04 per duplicated bug (#1429250)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to makedumpfile in Ubuntu.
Since Cert. testing passed on the Vivid kernel I'm going to ok the lts-v
kernel as well and mark this task as invalid.
** Changed in: kernel-sru-workflow/certification-testing
Status: In Progress => Invalid
--
You received this bug notification because you are a member of Kernel
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: bcmwl (Ubuntu)
Status: New => Confirmed
--
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/1438524
I don't want to hold up release of this kernel due to the issue stated
in comment #15 unless we know for sure that the problem is caused by
this kernel.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
I just talked to Tim, and the kernel with this fix should be promoted
to the -updates archive in a few days.
--
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/1487085
Title:
Ubuntu
** Changed in: linux-lts-vivid (Ubuntu)
Importance: Undecided => High
** Tags added: kernel-key
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-lts-vivid in Ubuntu.
https://bugs.launchpad.net/bugs/1497812
Title:
i40e bug: non
** Changed in: kernel-sru-workflow/promote-to-updates
Status: Confirmed => In Progress
** Changed in: kernel-sru-workflow/promote-to-updates
Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Chris J Arges
(arges)
** Changed in: kernel-sru-workflow/promote-to-security
This bug was fixed in the package linux-lts-trusty -
3.13.0-65.105~precise1
---
linux-lts-trusty (3.13.0-65.105~precise1) precise; urgency=low
[ Brad Figg ]
* Release Tracking Bug
- LP: #1498291
[ Upstream Kernel Changes ]
* net: Fix skb_set_peeked use-after-free bug
This bug was fixed in the package linux-lts-trusty -
3.13.0-65.105~precise1
---
linux-lts-trusty (3.13.0-65.105~precise1) precise; urgency=low
[ Brad Figg ]
* Release Tracking Bug
- LP: #1498291
[ Upstream Kernel Changes ]
* net: Fix skb_set_peeked use-after-free bug
This bug was fixed in the package linux-lts-trusty -
3.13.0-65.105~precise1
---
linux-lts-trusty (3.13.0-65.105~precise1) precise; urgency=low
[ Brad Figg ]
* Release Tracking Bug
- LP: #1498291
[ Upstream Kernel Changes ]
* net: Fix skb_set_peeked use-after-free bug
@romanbn, I followed the suggestions you made in post # 290. Your
solution worked like a charm, thanks so much! And thanks to everyone
who worked on this solution! I just want to say, all your efforts are
sincerely appreciated!!
--
You received this bug notification because you are a member
I understand that this fix didn't make the 3.19 SRU kernel, and might be
released in the next SRU cycle (in 3 weeks).
--
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/1487085
Title:
** Changed in: kernel-sru-workflow/upload-to-ppa
Status: New => Fix Released
--
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/1494006
Title:
linux-ti-omap4: 3.2.0-1471.92
** Changed in: kernel-sru-workflow
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/1498108
Title:
linux: 3.13.0-65.105 -proposed tracker
Kernel freeze is Oct 8. Any chance these will make it into 4.3 by 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/1499849
Title:
Add CAPI flash driver (cxlflash) patches to 15.10
** Changed in: linux (Ubuntu Trusty)
Status: New => 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/1500484
Title:
Trusty update to 3.16.7-ckt17 stable release
I can provide a patch for what I was saying in comment #16, but I think
it is just a one liner in the two postrm files. I think it would be
sensible for software-properties-gtk that the firmware is only deleted
when the package is purged. This, modaliases in comment #2 and a reboot
patch would
** Changed in: kernel-sru-workflow/promote-to-security
Status: New => Confirmed
** Changed in: kernel-sru-workflow/promote-to-updates
Status: New => Confirmed
** Description changed:
This bug is for tracking the 3.19.0-30.33~14.04.1 upload package. This
bug will contain status
** Changed in: linux (Ubuntu Vivid)
Status: New => 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/1500493
Title:
Vivid update to 3.19.8-ckt7 stable release
Status
This is an upstream Linux kernel bug, see here:
https://bugzilla.kernel.org/show_bug.cgi?id=101011
** Bug watch added: Linux Kernel Bug Tracker #101011
http://bugzilla.kernel.org/show_bug.cgi?id=101011
--
You received this bug notification because you are a member of Kernel
Packages, which
This bug was fixed in the package linux-lts-vivid - 3.19.0-30.33~14.04.1
---
linux-lts-vivid (3.19.0-30.33~14.04.1) trusty; urgency=low
[ Brad Figg ]
* Release Tracking Bug
- LP: #1498307
* Revert "[Config]
MFD_INTEL_LPSS/MFD_INTEL_LPSS_ACPI/MFD_INTEL_LPSS_PCI=m"
-
This bug was fixed in the package linux-lts-utopic -
3.16.0-50.66~14.04.1
---
linux-lts-utopic (3.16.0-50.66~14.04.1) trusty; urgency=low
[ Luis Henriques ]
* Release Tracking Bug
- LP: #1494371
[ Chris J Arges ]
* [Config] DEFAULT_IOSCHED="deadline" for ppc64el
-
** Changed in: kernel-sru-workflow/promote-to-updates
Status: Confirmed => In Progress
** Changed in: kernel-sru-workflow/promote-to-updates
Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Chris J Arges
(arges)
--
You received this bug notification because you are a
This bug was fixed in the package linux-lts-utopic -
3.16.0-50.66~14.04.1
---
linux-lts-utopic (3.16.0-50.66~14.04.1) trusty; urgency=low
[ Luis Henriques ]
* Release Tracking Bug
- LP: #1494371
[ Chris J Arges ]
* [Config] DEFAULT_IOSCHED="deadline" for ppc64el
-
** Changed in: kernel-sru-workflow/promote-to-updates
Status: Confirmed => In Progress
** Changed in: kernel-sru-workflow/promote-to-updates
Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Chris J Arges
(arges)
** Changed in: kernel-sru-workflow/promote-to-security
This bug was fixed in the package linux-lts-vivid - 3.19.0-30.33~14.04.1
---
linux-lts-vivid (3.19.0-30.33~14.04.1) trusty; urgency=low
[ Brad Figg ]
* Release Tracking Bug
- LP: #1498307
* Revert "[Config]
MFD_INTEL_LPSS/MFD_INTEL_LPSS_ACPI/MFD_INTEL_LPSS_PCI=m"
-
You have been subscribed to a public bug:
== Comment: #0 - Krishnaja Balachandran - 2015-09-02
05:01:44 ==
---Problem Description---
While running stress tests( IO BASE TCP NFS) on Firestone system "amp" I see
the following call traces in "dmesg". Also, few commands are
This bug was fixed in the package linux - 3.19.0-30.33
---
linux (3.19.0-30.33) vivid; urgency=low
[ Brad Figg ]
* Release Tracking Bug
- LP: #1498065
* Revert "[Config]
MFD_INTEL_LPSS/MFD_INTEL_LPSS_ACPI/MFD_INTEL_LPSS_PCI=m"
- LP: #1498137
* [Config] Disable
This bug was fixed in the package linux - 3.19.0-30.33
---
linux (3.19.0-30.33) vivid; urgency=low
[ Brad Figg ]
* Release Tracking Bug
- LP: #1498065
* Revert "[Config]
MFD_INTEL_LPSS/MFD_INTEL_LPSS_ACPI/MFD_INTEL_LPSS_PCI=m"
- LP: #1498137
* [Config] Disable
This bug was fixed in the package linux - 3.19.0-30.33
---
linux (3.19.0-30.33) vivid; urgency=low
[ Brad Figg ]
* Release Tracking Bug
- LP: #1498065
* Revert "[Config]
MFD_INTEL_LPSS/MFD_INTEL_LPSS_ACPI/MFD_INTEL_LPSS_PCI=m"
- LP: #1498137
* [Config] Disable
This bug was fixed in the package linux - 3.19.0-30.33
---
linux (3.19.0-30.33) vivid; urgency=low
[ Brad Figg ]
* Release Tracking Bug
- LP: #1498065
* Revert "[Config]
MFD_INTEL_LPSS/MFD_INTEL_LPSS_ACPI/MFD_INTEL_LPSS_PCI=m"
- LP: #1498137
* [Config] Disable
*** This bug is a duplicate of bug 1498065 ***
https://bugs.launchpad.net/bugs/1498065
This bug was fixed in the package linux - 3.19.0-30.33
---
linux (3.19.0-30.33) vivid; urgency=low
[ Brad Figg ]
* Release Tracking Bug
- LP: #1498065
* Revert "[Config]
This bug was fixed in the package linux - 3.19.0-30.33
---
linux (3.19.0-30.33) vivid; urgency=low
[ Brad Figg ]
* Release Tracking Bug
- LP: #1498065
* Revert "[Config]
MFD_INTEL_LPSS/MFD_INTEL_LPSS_ACPI/MFD_INTEL_LPSS_PCI=m"
- LP: #1498137
* [Config] Disable
This bug was fixed in the package linux - 3.19.0-30.33
---
linux (3.19.0-30.33) vivid; urgency=low
[ Brad Figg ]
* Release Tracking Bug
- LP: #1498065
* Revert "[Config]
MFD_INTEL_LPSS/MFD_INTEL_LPSS_ACPI/MFD_INTEL_LPSS_PCI=m"
- LP: #1498137
* [Config] Disable
This bug was fixed in the package linux - 3.19.0-30.33
---
linux (3.19.0-30.33) vivid; urgency=low
[ Brad Figg ]
* Release Tracking Bug
- LP: #1498065
* Revert "[Config]
MFD_INTEL_LPSS/MFD_INTEL_LPSS_ACPI/MFD_INTEL_LPSS_PCI=m"
- LP: #1498137
* [Config] Disable
** Changed in: kernel-sru-workflow/promote-to-updates
Status: Confirmed => In Progress
** Changed in: kernel-sru-workflow/promote-to-updates
Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Chris J Arges
(arges)
** Changed in: kernel-sru-workflow/promote-to-security
This bug was fixed in the package linux - 3.19.0-30.33
---
linux (3.19.0-30.33) vivid; urgency=low
[ Brad Figg ]
* Release Tracking Bug
- LP: #1498065
* Revert "[Config]
MFD_INTEL_LPSS/MFD_INTEL_LPSS_ACPI/MFD_INTEL_LPSS_PCI=m"
- LP: #1498137
* [Config] Disable
This bug was fixed in the package linux - 3.19.0-30.33
---
linux (3.19.0-30.33) vivid; urgency=low
[ Brad Figg ]
* Release Tracking Bug
- LP: #1498065
* Revert "[Config]
MFD_INTEL_LPSS/MFD_INTEL_LPSS_ACPI/MFD_INTEL_LPSS_PCI=m"
- LP: #1498137
* [Config] Disable
** Package changed: 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/1495863
Title:
ISST-KVM: R3-0: Firestone: PowerNV : Call traces w.r.t filesystem
while
This bug was fixed in the package linux - 3.19.0-30.33
---
linux (3.19.0-30.33) vivid; urgency=low
[ Brad Figg ]
* Release Tracking Bug
- LP: #1498065
* Revert "[Config]
MFD_INTEL_LPSS/MFD_INTEL_LPSS_ACPI/MFD_INTEL_LPSS_PCI=m"
- LP: #1498137
* [Config] Disable
This bug was fixed in the package linux - 3.19.0-30.33
---
linux (3.19.0-30.33) vivid; urgency=low
[ Brad Figg ]
* Release Tracking Bug
- LP: #1498065
* Revert "[Config]
MFD_INTEL_LPSS/MFD_INTEL_LPSS_ACPI/MFD_INTEL_LPSS_PCI=m"
- LP: #1498137
* [Config] Disable
This bug was fixed in the package linux - 3.19.0-30.33
---
linux (3.19.0-30.33) vivid; urgency=low
[ Brad Figg ]
* Release Tracking Bug
- LP: #1498065
* Revert "[Config]
MFD_INTEL_LPSS/MFD_INTEL_LPSS_ACPI/MFD_INTEL_LPSS_PCI=m"
- LP: #1498137
* [Config] Disable
This bug was fixed in the package linux-lts-utopic -
3.16.0-50.66~14.04.1
---
linux-lts-utopic (3.16.0-50.66~14.04.1) trusty; urgency=low
[ Luis Henriques ]
* Release Tracking Bug
- LP: #1494371
[ Chris J Arges ]
* [Config] DEFAULT_IOSCHED="deadline" for ppc64el
-
This bug was fixed in the package linux - 3.19.0-30.33
---
linux (3.19.0-30.33) vivid; urgency=low
[ Brad Figg ]
* Release Tracking Bug
- LP: #1498065
* Revert "[Config]
MFD_INTEL_LPSS/MFD_INTEL_LPSS_ACPI/MFD_INTEL_LPSS_PCI=m"
- LP: #1498137
* [Config] Disable
This bug was fixed in the package linux - 3.19.0-30.33
---
linux (3.19.0-30.33) vivid; urgency=low
[ Brad Figg ]
* Release Tracking Bug
- LP: #1498065
* Revert "[Config]
MFD_INTEL_LPSS/MFD_INTEL_LPSS_ACPI/MFD_INTEL_LPSS_PCI=m"
- LP: #1498137
* [Config] Disable
This bug was fixed in the package linux - 3.19.0-30.33
---
linux (3.19.0-30.33) vivid; urgency=low
[ Brad Figg ]
* Release Tracking Bug
- LP: #1498065
* Revert "[Config]
MFD_INTEL_LPSS/MFD_INTEL_LPSS_ACPI/MFD_INTEL_LPSS_PCI=m"
- LP: #1498137
* [Config] Disable
This bug was fixed in the package linux-lts-utopic -
3.16.0-50.66~14.04.1
---
linux-lts-utopic (3.16.0-50.66~14.04.1) trusty; urgency=low
[ Luis Henriques ]
* Release Tracking Bug
- LP: #1494371
[ Chris J Arges ]
* [Config] DEFAULT_IOSCHED="deadline" for ppc64el
-
This bug was fixed in the package linux-lts-utopic -
3.16.0-50.66~14.04.1
---
linux-lts-utopic (3.16.0-50.66~14.04.1) trusty; urgency=low
[ Luis Henriques ]
* Release Tracking Bug
- LP: #1494371
[ Chris J Arges ]
* [Config] DEFAULT_IOSCHED="deadline" for ppc64el
-
promote-to-updates is not set to one of the following (correct) states:
New, Confirmed, Incomplete, Fix Released,
promote-to-updates task was set to state In Progress
Further processing of this bug by Workflow Manager is halted.
** Changed in: kernel-sru-workflow
Status: In Progress =>
promote-to-security is not set to one of the following (correct) states:
New, Confirmed, Invalid, Incomplete, Fix Released,
promote-to-security task was set to state In Progress
Further processing of this bug by Workflow Manager is halted.
** Changed in: kernel-sru-workflow
Status: In
promote-to-security is not set to one of the following (correct) states:
New, Confirmed, Invalid, Incomplete, Fix Released,
promote-to-security task was set to state In Progress
Further processing of this bug by Workflow Manager is halted.
** Changed in: kernel-sru-workflow
Status: In
promote-to-security is not set to one of the following (correct) states:
New, Confirmed, Invalid, Incomplete, Fix Released,
promote-to-security task was set to state In Progress
Further processing of this bug by Workflow Manager is halted.
** Changed in: kernel-sru-workflow
Status: In
Promoted to updates:
linux| 3.19.0-30.33 | vivid-updates| source
linux-meta | 3.19.0.30.29 | vivid-updates| source
linux-signed | 3.19.0-30.33 | vivid-updates| source
** Changed in: kernel-sru-workflow/promote-to-security
Status: In Progress => Fix Released
**
Released to updates:
linux-lts-utopic| 3.16.0-50.66~14.04.1 | trusty-updates | source
linux-meta-lts-utopic | 3.16.0.50.41 | trusty-updates | source
linux-signed-lts-utopic | 3.16.0-50.66~14.04.1 | trusty-updates | source
** Changed in:
Released to updates:
linux-lts-trusty| 3.13.0-65.105~precise1 | precise-updates | source
linux-meta-lts-trusty | 3.13.0.65.57 | precise-updates | source
linux-signed-lts-trusty | 3.13.0-65.105~precise1 | precise-updates | source
** Changed in:
Released to updates:
linux-lts-vivid| 3.19.0-30.33~14.04.1 | trusty-updates | source
linux-meta-lts-vivid | 3.19.0.30.17 | trusty-updates | source
linux-signed-lts-vivid | 3.19.0-30.33~14.04.1 | trusty-updates | source
** Changed in: kernel-sru-workflow/promote-to-security
I had a few confirmations from ubuntuforums and askubuntu that it works.
I can't understand why it can't use /lib/firmware/ath10k/QCA6164/ for
the firmware, the thread http://ath10k.infradead.narkive.com/bahorD8v
/patch-rft-1-2-ath10k-add-qca6164-support says it is to avoid breaking
backward
I just found old-releases.ubuntu.com.
Ubuntu 13.10 (kernel 3.11.0-12-generic) is the last version that doesn't
have 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/1296224
--- Comment From cha...@us.ibm.com 2015-09-28 14:14 EDT---
Reposting reply for Canonical to see it:
> I'd like to see these patches at least make it into linux-next first.
These patches are critical bug fixes that need to make it in the 15.10
GA. We are working with the community on
I have discovered that while I thought I was affected by this bug, it is
in fact this one:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1359689
Fix mentioned in #49 on that thread worked around the issue for me.
--
You received this bug notification because you are a member of Kernel
This bug was fixed in the package linux - 3.13.0-65.105
---
linux (3.13.0-65.105) trusty; urgency=low
[ Brad Figg ]
* Release Tracking Bug
- LP: #1498108
[ Upstream Kernel Changes ]
* net: Fix skb_set_peeked use-after-free bug
- LP: #1497184
linux
This bug was fixed in the package linux - 3.13.0-65.105
---
linux (3.13.0-65.105) trusty; urgency=low
[ Brad Figg ]
* Release Tracking Bug
- LP: #1498108
[ Upstream Kernel Changes ]
* net: Fix skb_set_peeked use-after-free bug
- LP: #1497184
linux
This bug was fixed in the package linux - 3.13.0-65.105
---
linux (3.13.0-65.105) trusty; urgency=low
[ Brad Figg ]
* Release Tracking Bug
- LP: #1498108
[ Upstream Kernel Changes ]
* net: Fix skb_set_peeked use-after-free bug
- LP: #1497184
linux
This bug was fixed in the package linux - 3.13.0-65.105
---
linux (3.13.0-65.105) trusty; urgency=low
[ Brad Figg ]
* Release Tracking Bug
- LP: #1498108
[ Upstream Kernel Changes ]
* net: Fix skb_set_peeked use-after-free bug
- LP: #1497184
linux
*** This bug is a duplicate of bug 1498108 ***
https://bugs.launchpad.net/bugs/1498108
This bug was fixed in the package linux - 3.13.0-65.105
---
linux (3.13.0-65.105) trusty; urgency=low
[ Brad Figg ]
* Release Tracking Bug
- LP: #1498108
[ Upstream Kernel Changes
This bug was fixed in the package linux - 3.13.0-65.105
---
linux (3.13.0-65.105) trusty; urgency=low
[ Brad Figg ]
* Release Tracking Bug
- LP: #1498108
[ Upstream Kernel Changes ]
* net: Fix skb_set_peeked use-after-free bug
- LP: #1497184
linux
This bug was fixed in the package linux - 3.13.0-65.105
---
linux (3.13.0-65.105) trusty; urgency=low
[ Brad Figg ]
* Release Tracking Bug
- LP: #1498108
[ Upstream Kernel Changes ]
* net: Fix skb_set_peeked use-after-free bug
- LP: #1497184
linux
This bug was fixed in the package linux - 3.13.0-65.105
---
linux (3.13.0-65.105) trusty; urgency=low
[ Brad Figg ]
* Release Tracking Bug
- LP: #1498108
[ Upstream Kernel Changes ]
* net: Fix skb_set_peeked use-after-free bug
- LP: #1497184
linux
** Changed in: kernel-sru-workflow/promote-to-security
Status: Confirmed => Fix Released
** Changed in: kernel-sru-workflow/promote-to-security
Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Adam Conrad
(adconrad)
** Changed in: kernel-sru-workflow/promote-to-updates
This bug was fixed in the package linux - 3.13.0-65.105
---
linux (3.13.0-65.105) trusty; urgency=low
[ Brad Figg ]
* Release Tracking Bug
- LP: #1498108
[ Upstream Kernel Changes ]
* net: Fix skb_set_peeked use-after-free bug
- LP: #1497184
linux
** Description changed:
This bug is for tracking the 3.13.0-65.105 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
** Tags added: patch
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to kexec-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1496317
Title:
kexec fails with OOM killer with the current crashkernel=128 value
Status in kexec-tools
Public bug reported:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either
** Description changed:
+ SRU Justification
- SRU Justification
+ Impact:
+ The upstream process for stable tree updates is quite similar
+ in scope to the Ubuntu SRU process, e.g., each patch has to
+ demonstrably fix a bug, and each patch is vetted by upstream
+
Has anybody checked if this issue is still present in Ubuntu 15.05? This
version use Bluez version 5.
--
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/219057
Title:
Bluetooth does not
Many thanks to alarconj!
I finally got rid of interferences between my bluetooth mouse and my portable
4g router!
Just entered
echo "options iwlwifi 11n_disable=1 bt_coex_active=0 power_save=0
auto_agg=0 swcrypto=1" | sudo tee /etc/modprobe.d/iwlwifi.conf >
/dev/null
and rebooted.
I was
To sum it up:
3.8.0-19-generic: could not enable HDMI audio, though I believe it was possible
somehow
3.11.0-12-generic: WORKS FINE
3.13.0-18-generic: BUG
3.13.0-45-generic: BUG
3.19.0-28-generic: BUG
4.3-rc3: BUG
--
You received this bug notification because you are a member of Kernel
** Description changed:
+ SRU Justification
- SRU Justification
+ Impact:
+ The upstream process for stable tree updates is quite similar
+ in scope to the Ubuntu SRU process, e.g., each patch has to
+ demonstrably fix a bug, and each patch is vetted by upstream
+
Public bug reported:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either directly
I just tried the 20150903 backports and I didn't have to patch the code
(still need to copy the firmware and create /etc/modprobe.d/ath10k.conf.
Also, looking at the code from the backport, the firmware still needs to
be copied to QCA6174 (instead of QCA6164). Guess it's getting better
(maybe in
*** This bug is a duplicate of bug 624877 ***
https://bugs.launchpad.net/bugs/624877
Looks like this is bugging me on new Kali 2 (Debian) 32bit system.
System freezes every time for about 15 secs after apt-get install (or upgrade)
is done.
** Branch linked: lp:~ddormer/kali/kali-update
--
I've also tried to login to root at this "Welcome to emergency
mode." prompt and purged all nvidia drivers and rebooted twice. No
use, still exactly the same message...
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
I am on Kubuntu, with a hybrid Intel-NVIDIA card.
I have upgraded recently from 14.04->14.10->15.04, all in immediate
succession. Upgrade process went without a problem and I was able to use
the computer for a few days. Then once this "ACPI PCC probe failed"
message appeared, but the boot process
modprobe failed on my Ubuntu trusty environment, can anyone help take a
look?
[OS]
# uname -a
Linux juju-xianghui-machine-11 3.13.0-63-generic #103-Ubuntu SMP Fri Aug 14
21:42:59 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux
[TEST]
# modprobe uio_pci_generic
modprobe: FATAL: Module uio_pci_generic not
Paulo Molina, this has nothing to do with linux (Ubuntu) as it only
provides open source drivers. For more on this please see
https://help.ubuntu.com/community/WifiDocs/Driver/bcm43xx .
** Package changed: linux (Ubuntu) => bcmwl (Ubuntu)
** Changed in: bcmwl (Ubuntu)
Status: Confirmed =>
Tony Middleton, thank you for reporting this and helping make Ubuntu
better. As per http://www.gigabyte.com/products/product-
page.aspx?pid=4343#bios an update to your computer's buggy and outdated
BIOS is available (F3). If you update to this following
https://help.ubuntu.com/community/BIOSUpdate
I just tried Ubuntu 12.04.5 LTS (kernel 3.13.0-45-generic) and the
problem exists.
Where can I download images for the (now EOL'ed) Q, R and S releases?
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Kernel
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1363430/+attachment/4477400/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
I have tried to update the Bios but have been unsuccessful. I have
contacted Acer support for help but they answered my email stating they
do not recommend I update and would give me no information as to how I
can update. I have downloaded the files from their site but am unable to
open them. I am
on running command "sudo dmidecode -s bios-version && sudo dmidecode -s
bios-release-date" I get following information:
V1.07
09/11/2014
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Tags added: apport-collected vivid
** Description changed:
Frequent crashes giving the following abort message on the console:
(process:8065): GLib-CRITICAL **: g_slice_set_config: assertion
'sys_page_size == 0' failed
(firefox:8065): GLib-GObject-WARNING **:
1 - 100 of 158 matches
Mail list logo