--- Comment From cdead...@us.ibm.com 2015-09-29 06:00 EDT---
--
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/1478492
Title:
MFG:Firestone, Linux Error message: unable to open rtc
Default Comment by Bridge
** Tags removed: targetmilestone-inin---
** Tags added: targetmilestone-inin14043
** Attachment added: "Silence SYSPARAM warning on boot"
https://bugs.launchpad.net/bugs/1478513/+attachment/4478253/+files/0001-powerpc-powernv-Silence-SYSPARAM-warning-on-boot.patch
-
--- Comment From mainam...@in.ibm.com 2015-09-29 05:55 EDT---
As per my discussion with developer can you please retest with the current
latest kernel 14.04.03.
I think we don't see this issue with latest version of the kernel.
--
You received this bug notification because you are a memb
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]
** Changed in: linux (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bu
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]
** Changed in: linux (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bu
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
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 received
** 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
T
** 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
ins
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
.../linux-image-3.16.0-50-generi
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1500094/+attachment/4478107/+files/UdevDb.txt
--
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/1500094
apport information
** Attachment added: "RfKill.txt"
https://bugs.launchpad.net/bugs/1500094/+attachment/4478106/+files/RfKill.txt
--
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/1500094
apport information
** Attachment added: "PulseList.txt"
https://bugs.launchpad.net/bugs/1500094/+attachment/4478105/+files/PulseList.txt
--
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/
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1500094/+attachment/4478108/+files/WifiSyslog.txt
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages,
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1500094/+attachment/4478104/+files/ProcModules.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/b
apport information
** Attachment added: "JournalErrors.txt"
https://bugs.launchpad.net/bugs/1500094/+attachment/4478099/+files/JournalErrors.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.n
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1500094/+attachment/4478102/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/b
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1500094/+attachment/4478103/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1500094/+attachment/4478101/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/b
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1500094/+attachment/4478100/+files/Lspci.txt
--
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/1500094
apport information
** Attachment added: "AlsaInfo.txt"
https://bugs.launchpad.net/bugs/1500094/+attachment/4478095/+files/AlsaInfo.txt
--
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/15
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1500094/+attachment/4478097/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net
apport information
** Attachment added: "CRDA.txt"
https://bugs.launchpad.net/bugs/1500094/+attachment/4478096/+files/CRDA.txt
--
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/1500094
Ti
The problem was not fixed after BIOS update.
sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date
UX303LB.206
08/24/2015
And acpi_listen still doesn't get anything when pressing fn+f5 or fn+f6.
Also, the touchpad only worked by installing
sudo add-apt-repository ppa:hanipouspilo
apport information
** Attachment added: "IwConfig.txt"
https://bugs.launchpad.net/bugs/1500094/+attachment/4478098/+files/IwConfig.txt
--
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/15
You have been subscribed to a public bug:
"CPU Frequency could be throttled" dmesg is logged with critical log level when
the max frequency is clipped. This message should be logged to 'info' if the
frequency is throttled between nominal and turbo and not as critical.
Fix for this involves
** Changed in: kernel-development-workflow/prepare-package-signed
Status: New => Fix Released
** Changed in: kernel-development-workflow/prepare-package-signed
Assignee: Canonical Kernel Team (canonical-kernel-team) => Tim Gardner
(timg-tpi)
--
You received this bug notification bec
Laurent Martin-Borret, thank you for reporting this and helping make
Ubuntu better. Could you please test the latest upstream kernel
available from the very top line at the top of the page from
http://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D (the release
names are irrelevant for testing, and
** Package changed: ubuntu => linux (Ubuntu)
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Taco Screen team (taco-screen-team)
--
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
@Christopher, thank you for the offer! As it turns out, I don't think
the root cause is the kernel. If I switch back to lightdm, I'm able to
successfully start X, so I think the messages I'm seeing are the same in
this bug, but they aren't the root cause of my particular problem (no
greeter, no X).
On Tue, 2015-09-29 at 00:58 +, Christopher M. Penalver wrote:
> chris pollock, anything in kern.log during that timeframe (specifically
> a call trace)? If so, please attach uncompressed, and untarred.
>
I've attached the kern.log from 27/28 September 2015.
--
Chris
KeyID 0xE372A7DA98E6705C
** Attachment added: "kern.log from 27/28 September 2015"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1497627/+attachment/4478069/+files/kern.log
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.la
This bug was fixed in the package bcmwl - 6.30.223.248+bdcom-0ubuntu7
---
bcmwl (6.30.223.248+bdcom-0ubuntu7) wily; urgency=medium
* debian/bcmwl-kernel-source.modaliases: really fix matching for model 43b1,
apparently modaliases are case-sensitive, and changing ubuntu-drivers
Martin Smith, it will help immensely if you filed a new report via a terminal:
ubuntu-bug linux
Please feel free to subscribe me to it.
--
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/14927
** Changed in: kernel-development-workflow/prepare-package
Status: New => Fix Released
** Changed in: kernel-development-workflow/prepare-package
Assignee: Canonical Kernel Team (canonical-kernel-team) => Tim Gardner
(timg-tpi)
** Changed in: kernel-development-workflow/prepare-packa
chris pollock, anything in kern.log during that timeframe (specifically
a call trace)? If so, please attach uncompressed, and untarred.
--
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/149762
Nuno, as per https://www.asus.com/sa-
en/Notebooks/ASUS_ZENBOOK_UX303LB/HelpDesk_Download/ an update to your
computer's buggy and outdated BIOS is available (206). If you update to
this following https://help.ubuntu.com/community/BIOSUpdate does it
change anything?
If it doesn't, could you please
Another "me too" here. Decided since 15.10 was close to release that I'd
upgrade. I'm not stuck with X not starting at all, with "*ERROR*
mismatch in ips_enabled (expected 1, found 0)" just scrolling across the
logs. I'm not sure if it's the same as other reports, because I can't
start X _at all_,
Roman Vasilchenko, thank you for reporting this and helping make Ubuntu
better. As per http://us.acer.com/ac/en/US/content/drivers an update to
your computer's buggy and outdated BIOS is available (1.25). If you
update to this following https://help.ubuntu.com/community/BIOSUpdate
does it change an
I'm now stuck*
--
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/1492764
Title:
[drm:intel_pipe_config_compare [i915]] *ERROR* mismatch in ips_enabled
(expected 1, found 0)
Status in lin
Daniel Hahler, could you please test the patch to confirm it actually
fixes your issue? Instructions may be found at
https://wiki.ubuntu.com/Kernel/KernelBisection#Testing_a_newly_released_patch_from_upstream
.
--
You received this bug notification because you are a member of Kernel
Packages, whi
** Attachment added: "Todays syslog including the time in which the video was
frozen"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1497627/+attachment/4478021/+files/syslog9282015.xz
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribe
** Tags added: latest-bios-1603
--
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/1499978
Title:
BCM4352 not presented on Additional Drivers
Status in bcmwl package in Ubuntu:
New
Bug d
You have been subscribed to a public bug:
Hi,
I'm trying to connect an external screen to my thinkpad T420s. I'm running
Ubuntu 14.04 and here is the output of xrandr:
$ xrandr
Screen 0: minimum 320 x 200, current 1600 x 900, maximum 32767 x 32767
LVDS1 connected primary 1600x900+0+0 (normal lef
Today, at 15:54:11 the video froze on my system while opening a new tab
with Firefox 41.0. At the time of the freeze I was running kernel
3.19.0-28-generic #30~14.04.1-Ubuntu SMP Tue Sep 1 09:32:55 UTC 2015
x86_64 x86_64 x86_64 GNU/Linux and have since updated via an update to
kernel 3.19.0-30-gene
Michael Thayer, to clarify, is it still an issue in the latest Ubuntu kernel:
uname -a
Linux hostname 4.2.0-11-generic #13-Ubuntu SMP Mon Sep 21 21:33:10 UTC 2015
x86_64 x86_64 x86_64 GNU/Linux
** Tags added: kernel-fixed-upstream kernel-fixed-upstream-4.3-rc3
needs-reverse-bisect
--
You receiv
After the kernel update to 3.19.0-30.33, I found that my wifi card
wasn't working again. I decided to download the latest backports
(2015/09/03 instead of 2015/07/31). When I went to apply the patches
Diego mentioned, I found that the patches were already included in the
backports, with one inter
Andreas Schildbach, the next step is to fully commit bisect from kernel
3.11 to 3.13 in order to identify the last good kernel commit, followed
immediately by the first bad one. This will allow for a more expedited
analysis of the root cause of your issue. Could you please do this
following https:/
** Attachment added: "demesg from booting into newest 3.19-30 kernel"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1497627/+attachment/4478022/+files/dmesg
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https:
** Attachment added: "Xorg.0.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1497627/+attachment/4478023/+files/Xorg.0.log
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/14976
Rovanion, could you please test the latest upstream kernel available
from the very top line at the top of the page from
http://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D (the release
names are irrelevant for testing, and please do not test the daily
folder)? Install instructions are available
Christopher, please change the status back to Confirmed/Triaged,
according to my feedback.
--
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/1497520
Title:
Slow performance after resuming f
> did you confirm that the quoted commit does indeed fix your issue?
No, I am not building Linux from source currently, and have not tried
e.g. applying that patch/commit to the Ubuntu package.
I am now back using the Ubuntu kernel, since the workaround is trivial
in case it is required - once yo
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 compat
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
** C
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: kernel-sru-workflow/promote-to-update
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: kernel-sru-workflow/promote-
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
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 Pro
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 Pro
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 => 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 Pro
** 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 runni
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 hanging in amp.
Cont
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 the
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 the
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 the
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 the
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
- L
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
- L
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
- L
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 the
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 the
*** 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]
MFD_INTE
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 the
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 the
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 the
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 the
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 the
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 the
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 the
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 the
** 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 the
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 the
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"
-
** 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"
-
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
- L
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
- L
** 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 mem
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
** 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
--- 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, th
** 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
@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 of
** 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
1 - 100 of 160 matches
Mail list logo
