** Changed in: hwe-next
Status: Incomplete = Triaged
** Changed in: hwe-next
Importance: High = Medium
** Changed in: linux (Ubuntu)
Importance: High = Medium
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
The same root cause with bug#1243493,
please refer to,
https://bugs.launchpad.net/ubuntu/+source/linux-lts-raring/+bug/1243493/comments/2
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
I'm still affected by this bug, using Ubuntu 13.10
** Changed in: linux (Ubuntu)
Status: Expired = 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/1162372
Title:
** Changed in: linux (Ubuntu)
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/1151664
Title:
HP Pavilion g7 - FWTS failures when doing cert
** Changed in: linux (Ubuntu)
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/1148649
Title:
HP Pavilion G7 - FWTS HIGH errors during
1. before suspend, examine and remember all values of
/sys/devices/virtual/thermal/cooling_device*/cur_state
2. after suspend, restore all values mentioned above.
OR, for simplicity, just set the values of
/sys/devices/virtual/thermal/cooling_device*/cur_state periodically.
--
You received
Karl-Felix Glatzer, the next step is to fully commit bisect from Lucid
to Maverick, in order to identify the offending commit. Could you please
do this following https://wiki.ubuntu.com/Kernel/KernelBisection ?
** Changed in: linux (Ubuntu)
Status: Confirmed = Incomplete
--
You received
** Tags removed: kernel-bug-exists-upstream-v3.6-rc7
** Tags added: kernel-bug-exists-upstream-v3.12
--
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/1055506
Title:
Failed to boot after
J Bauer, it wouldn't hurt to have a commit bisect done from
2.6.32-43-server to 3.2.0.31-generic in order to identify the offending
commit following https://wiki.ubuntu.com/Kernel/KernelBisection .
Despite this, it looks like the upstream consensus is this issue is BIOS
driven, and they would
Liam Proven / Laurens Bosscher / Eustaquio Rangel, if you have a bug in Ubuntu,
the Ubuntu Kernel team, Ubuntu Bug Control team, and Ubuntu Bug Squad would
like you to please file a new report by executing the following in a terminal
while booted into a Ubuntu repository kernel (not a mainline
Ron, did this problem not occur in a release prior to Raring?
As well, in mainline testing, please ensure you are not testing the
daily folder (nightly as you called it), but the one at the bottom of
the list, as outlined in
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1226172/comments/18
** Description changed:
After reactivating PC from Sleep-Mode or Hibernate-Mode there is no
networkconnection. All network-devices are listed as DEACTIVATED. Re-
ACTIVATING doesn't help. Only Soution is to reboot computer.
- Only working workaround at this time is to send PC into
apport information
** Attachment added: ProcEnviron.txt
https://bugs.launchpad.net/bugs/1250321/+attachment/3909416/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
** Attachment added: kern.log
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1250321/+attachment/3909417/+files/kern.log
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
I'm currently on a live session of an Xubuntu 13.10 64-bit flash drive
which I was attempting to install over my Ubuntu 14.04 partition and
when it got to the installing grub2 portion it crashed and now I have a
log I can provide.
** Tags added: apport-collected
** Description changed:
System
** Attachment added: syslog
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1250321/+attachment/3909418/+files/syslog
** Attachment removed: ProcEnviron.txt
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1250321/+attachment/3909416/+files/ProcEnviron.txt
--
vroetman, as a potential WORKAROUND, could you instead hibernate via a terminal:
sudo pm-hibernate
As well, I would test the latest mainline kernel via
http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.12-trusty/ before
following
Maintainer Process -
https://wiki.ubuntu.com/Bugs/Upstream/kernel#KernelTeam.2BAC8-KernelTeamBugPolicies.Overview_on_Reporting_Bugs_Upstream
Mailing list - linux-input
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Angelos Sfakianakis / jradwans, if you have a bug in Ubuntu, the Ubuntu Kernel
team, Ubuntu Bug Control team, and Ubuntu Bug Squad would like you to please
file a new report by executing the following in a terminal while booted into a
Ubuntu repository kernel (not a mainline one) via:
Once again it has crashed at the same spot
Nov 15 11:13:27 xubuntu ubiquity: Setting up grub-efi-amd64-signed
(1.22.1+2.00-19ubuntu2.1) ...
Nov 15 11:14:29 xubuntu kernel: [ 1035.084269] CPU: 7 PID: 15508 Comm:
efibootmgr Tainted: GF D 3.11.0-12-generic #19-Ubuntu
Nov 15 11:14:29
I don't see any mentions of systemd-udevd or kthreadd in these logs like
I took in my screenshots (of which I don't remember seeing issues with
efibootmgr) so the bug with Xubuntu may or may not be related to the
issue I'm having here, although I would assume there is some sort of
connection
** Tags removed: 3.12.0-2-generic regression-potential
** Tags added: lucid
--
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/1164557
Title:
[Lenovo ThinkPad R60] Laptop to hot - VID to
Roland, the issue you are reporting is an upstream one. Could you please
report this problem through the appropriate channel by following the
instructions _verbatim_ at
https://wiki.ubuntu.com/Bugs/Upstream/kernel#KernelTeam.2BAC8-KernelTeamBugPolicies.Overview_on_Reporting_Bugs_Upstream
?
Please
Rainer, as WORKAROUNDs, in addition to maxing out your fan speed, I was
going to suggest using powersave governor setting. At this point, it
would be helpful if a powertop was run and the top power consuming
processes were identified. Could you please do this?
--
You received this bug
Fred Saunier, is this partially solved scenario reproducible in the
Trusty live environment via http://cdimage.ubuntu.com/daily-
live/current/ ?
** Changed in: linux (Ubuntu)
Status: Confirmed = Incomplete
--
You received this bug notification because you are a member of Kernel
Packages,
** Changed in: linux-lts-saucy (Ubuntu Precise)
Status: New = Invalid
** Changed in: linux-lts-saucy (Ubuntu Precise)
Importance: Undecided = Low
** Changed in: linux-lts-saucy (Ubuntu Saucy)
Status: New = Invalid
** Changed in: linux-lts-saucy (Ubuntu Saucy)
Importance:
Graeme Hewson, as per
http://www.asus.com/Motherboards/M4A88TDM_EVOUSB3/#support an update is
available for your BIOS (1801). If you update to this following
https://help.ubuntu.com/community/BiosUpdate , does it change anything?
If not, could you please both specify what happened, and provide
** Changed in: linux-armadaxp (Ubuntu Precise)
Status: New = Fix Committed
** Changed in: linux-armadaxp (Ubuntu Quantal)
Status: Fix Committed = Fix Released
** Changed in: linux-lts-quantal (Ubuntu Precise)
Status: Fix Committed = Fix Released
** Changed in:
** Changed in: linux (Ubuntu)
Status: Confirmed = Incomplete
--
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/1251333
Title:
System freezes after suspend to RAM
Status in “linux”
Not Fix Released as per previous comments.
** Changed in: linux (Ubuntu)
Status: Fix Released = Triaged
--
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/1244478
Title:
1814:3290
Its happen again
[ 111.128181] mei_me :00:03.0: unexpected reset: dev_state = RESETTING
[ 117.140090] mei_me :00:03.0: reset: connect/disconnect timeout.
[ 117.140111] mei_me :00:03.0: unexpected reset: dev_state = RESETTING
[ 123.152100] mei_me :00:03.0: reset:
Addition: it turned out that removing proprietary video driver was not
enough. Some problems disappeared but my laptop still sometimes didn't
wake up from sleep. So I tried to upgrade kernel to 3.12 and now it
looks like everything is all right again. I hope it will remain that way
for a while.
The apt fix for this should be backported to precise, and the linux-lts-
saucy HWE kernels have the new linux-tools scheme, so we can actually
retain them sanely via autoremove.
** Changed in: apt (Ubuntu Precise)
Status: Invalid = In Progress
** Changed in: apt (Ubuntu Precise)
Hello Andy, or anyone else affected,
Accepted apt into precise-proposed. The package will build now and be
available at
http://launchpad.net/ubuntu/+source/apt/0.8.16~exp12ubuntu10.16 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
I have compiled Mesa 10 master in /opt/mesa and added a conf file in
/etc/ld.so.conf.d.
Now glxinfo shows:
OpenGL version string: 3.0 Mesa 10.0.0-devel (git-69b425e)
OpenGL shading language version string: 1.30
OpenGL context flags: (none)
This is the first time I have built mesa.
--
You
Created attachment 88747
i915_error_state file after causing render ring hang in Google Maps
This is the i915_error_state file after updating my system with the
https://launchpad.net/~oibaf/+archive/graphics-drivers/ PPA (and
restarting X of course) and scrolling around a lot in Google Maps in
Created attachment 88969
i915_error_state
Still hang after playing hedgewars for nearly an hour, but it doesn't hang
continuously, just one time. Dmesg shows:
[ 3929.521951] [drm:i915_hangcheck_elapsed] *ERROR* stuck on render ring
[ 3929.521963] [drm:i915_hangcheck_elapsed] *ERROR* stuck on
(In reply to comment #33)
Created attachment 88969 [details]
i915_error_state
Still hang after playing hedgewars for nearly an hour, but it doesn't hang
continuously, just one time. Dmesg shows:
[ 3929.521951] [drm:i915_hangcheck_elapsed] *ERROR* stuck on render ring
[ 3929.521963]
Hardware Certification have begun testing this -proposed kernel.
** Changed in: kernel-sru-workflow/certification-testing
Status: Confirmed = In Progress
** Changed in: kernel-sru-workflow/certification-testing
Assignee: Canonical Hardware Certification (canonical-hw-cert) = Sylvain
Fixed in Mesa 9.2.3 (out today), the upcoming Mesa 10.0 release, or Mesa
master.
This fixes the Sandybridge-specific GPU hang where i915_error_state (aka
/sys/class/drm/card0/error) lists an IPEHR of 0x79050005.
If you experience a GPU hang and your IPEHR is not 0x79050005, that is a
different
** Branch linked: lp:ubuntu/precise-proposed/apt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-meta in Ubuntu.
https://bugs.launchpad.net/bugs/1205284
Title:
linux-tools naming is not scalable to multiple source packages
** Changed in: linux
Status: In Progress = Fix Released
** Bug watch added: freedesktop.org Bugzilla #71276
https://bugs.freedesktop.org/show_bug.cgi?id=71276
** Bug watch added: freedesktop.org Bugzilla #54226
https://bugs.freedesktop.org/show_bug.cgi?id=54226
--
You received
Hardware Certification have begun testing this -proposed 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/1250622
Title:
linux: 3.2.0-57.87 -proposed tracker
Status in Kernel SRU
Sorry to re-open but I wanted to include one more detail - either a
recent update fixed this for me, or a recent change I made to my BIOS
settings (changing my fan speed from normal to turbo in my
motherboard BIOS) has made me unable to reproduce this hang, even after
long periods of scrolling
Hardware Certification have begun testing this -proposed 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/1250592
Title:
linux: 2.6.32-54.116 -proposed tracker
Status in Kernel
I believe it did occur in Quantal, but I am not 100% certain. These
servers had Quantal for a very shot time (~1 day), because we required
kernel features present only in Raring+, for use with Ceph/Rados.
Raring was still 3-4 months from release, but we were pulling Raring
Kernels into Quantal.
Hardware Certification have begun testing this -proposed kernel.
** Changed in: kernel-sru-workflow/certification-testing
Status: Confirmed = In Progress
** Changed in: kernel-sru-workflow/certification-testing
Assignee: Canonical Hardware Certification (canonical-hw-cert) = Brendan
Public bug reported:
It Ocurrs when i was installing optimized netbook kernel
3.10.4-netbook_3.10.4_i386 (headers and image).
ProblemType: Package
DistroRelease: Ubuntu 13.10
Package: bcmwl-kernel-source 6.30.223.141+bdcom-0ubuntu1
ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6
Uname:
Public bug reported:
I'm getting this message every 5 seconds
[ 38.976076] mei_me :00:03.0: reset: connect/disconnect timeout.
[ 38.976085] mei_me :00:03.0: unexpected reset: dev_state = RESETTING
According https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1196155
it should be
** Changed in: linux-lts-saucy (Ubuntu Precise)
Status: New = Invalid
** Changed in: linux-lts-saucy (Ubuntu Precise)
Importance: Undecided = Medium
** Changed in: linux-lts-saucy (Ubuntu Saucy)
Status: New = Invalid
** Changed in: linux-lts-saucy (Ubuntu Saucy)
Importance:
This bug is missing log files that will aid in diagnosing the problem.
From a terminal window please run:
apport-collect 1251681
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 upstream stable kernel?
Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the
latest v3.11 stable kernel[0].
If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.
If the mainline kernel
Public bug reported:
After doing an update to Ubuntu 13.04, the laptop wwould go thru the
motions of shutting down but would NOT complete the shutdown. The drive
light continues to flicker and the 2 status lights on the front of the
laptop remain lit. I tried to correct this issue by installing
Hardware Certification have begun testing this -proposed 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/1250592
Title:
linux: 2.6.32-54.116 -proposed tracker
Status in Kernel
I was intending to rebuild the machine as just an Ubuntu machine but I
won't until it can shutdown cleanly.
--
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/1251684
Title:
13.10 shutdown
Can you post the newer linux-firmware version that resolves the bug?
** Tags added: kernel-da-key
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/1251256
Title:
Qualcomm
This bug is missing log files that will aid in diagnosing the problem.
From a terminal window please run:
apport-collect 1251684
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
You may need to run the following:
sudo apt-get install -f
sudo apt-get clean
sudo apt-get update
Then re-install the package.
If that does not resolve your issue, please mark the bug as Confirmed
** Changed in: linux (Ubuntu)
Importance: Undecided = Low
** Changed in: linux (Ubuntu)
Would it be possible for you to test the latest upstream stable kernel?
Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the
latest v3.11 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 stable kernel?
Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the
latest v3.11 stable kernel[0].
If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.
If the mainline kernel
git://kernel.ubuntu.com/ppisati/ubuntu-precise.git ti-omap4
** Summary changed:
- linux-ti-omap4: version to be filled -proposed tracker
+ linux-ti-omap4: 3.2.0-1441.60 -proposed tracker
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
Trying bisecting didn't work for me, as (according to the wiki's
translation of the output) it spans non-linear tags. My attempt to
build from a 3.10 mainline kernel produced an image that suffered from
the same issue, but that didn't provide a linux-image-extras package
which seems to be
** Changed in: kernel-sru-workflow/upload-to-ppa
Status: New = Confirmed
--
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/1251433
Title:
linux-ti-omap4: 3.2.0-1441.60
** Description changed:
This bug is for tracking the version to be filled 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
Thanks for the feedback, Ron. I updated that wiki page.
--
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/1226172
Title:
iostat: Cannot open /proc/stat: Cannot allocate memory
Status in
I built the next test kernel, up to the following commit:
f084dbb939070281be7c882db63a4a428c51fcf4
The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1242938
Can you test that kernel and report back if it has the bug or not. I
will build the next test kernel based on
I built the next test kernel, up to the following commit:
010e646ba2fdfc558048a97da746381c35836280
The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1107150
Can you test that kernel and report back if it has the bug or not. I
will build the next test kernel based on
I started a kernel bisect between v3.11.5 and v3.11.6. The kernel bisect
will require testing of about 7-10 test kernels.
I built the first test kernel, up to the following commit:
b340404549c872099aec7554439a1821c0708878
The test kernel can be downloaded from:
I built the next test kernel, up to the following commit:
a1c008db75b819e29a62ff3fbeffe493bf7ece93
The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1249880
Can you test that kernel and report back if it has the bug or not. I
will build the next test kernel based on
Seth Forshee, good news, bluntly restarting NetworkManager allowed me to
continue without the reboot:
$ sudo service network-manager restart
[sudo] password for sarnold:
network-manager stop/waiting
network-manager start/running, process 6165
I didn't see anything in my logs that suggests what
** Attachment added: 20131115_130257.jpg
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1212977/+attachment/3909619/+files/20131115_130257.jpg
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
From what I see in the logs there's not even an attempt to establish a
connection after resume, so I think the problem is likely with network-
manager. Reassigning.
** Package changed: linux (Ubuntu) = network-manager (Ubuntu)
--
You received this bug notification because you are a member of
I think I may have been able to reproduce this today with Trusty. The
system dropped to the busybox shell. It looked like there was a timeout
waiting to find the root filesystem by uuid. I took a digital picture
and will attach to the bug.
Daniel, can you also take a digital picture of your
** Changed in: linux-lts-saucy (Ubuntu Precise)
Status: New = Invalid
** Changed in: linux-lts-saucy (Ubuntu Precise)
Importance: Undecided = Low
** Changed in: linux-lts-saucy (Ubuntu Saucy)
Status: New = Invalid
** Changed in: linux-lts-saucy (Ubuntu Saucy)
Importance:
** Changed in: linux-lts-saucy (Ubuntu Precise)
Status: New = Invalid
** Changed in: linux-lts-saucy (Ubuntu Precise)
Importance: Undecided = Medium
** Changed in: linux-lts-saucy (Ubuntu Saucy)
Status: New = Invalid
** Changed in: linux-lts-saucy (Ubuntu Saucy)
Importance:
** Changed in: linux-lts-saucy (Ubuntu Precise)
Status: New = Invalid
** Changed in: linux-lts-saucy (Ubuntu Precise)
Importance: Undecided = Low
** Changed in: linux-lts-saucy (Ubuntu Saucy)
Status: New = Invalid
** Changed in: linux-lts-saucy (Ubuntu Saucy)
Importance:
** Changed in: linux-armadaxp (Ubuntu Precise)
Status: New = Fix Committed
** Changed in: linux-armadaxp (Ubuntu Quantal)
Status: Fix Committed = Fix Released
** Changed in: linux-lts-quantal (Ubuntu Precise)
Status: Fix Committed = Fix Released
** Changed in:
** Changed in: linux-armadaxp (Ubuntu Precise)
Status: New = Fix Committed
** Changed in: linux-armadaxp (Ubuntu Quantal)
Status: Fix Committed = Fix Released
** Changed in: linux-lts-quantal (Ubuntu Precise)
Status: Fix Committed = Fix Released
** Changed in:
I have prepared a test kernel for saucy and raring that may help Dell
XPS13 systems which experience black screen on boot and non-functional
backlight controls. (In particular, this case has been reported when
UEFI BIOS is enabled on XPS13's). This test kernel is _only_ relevant
for XPS13's.
If you are seeing the same message as me, can you try using the
rootdelay boot option?
From the GRUB prompt select e. Once there you can add the line
rootdelay=90 to the end of the line.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
I built the next test kernel, up to the following commit:
44b7400e6724f9a238f62bbeffd462a449d9a518
The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1245938
Can you test that kernel and report back if it has the bug or not. I
will build the next test kernel based on
** Changed in: linux-armadaxp (Ubuntu Precise)
Status: New = Fix Committed
** Changed in: linux-armadaxp (Ubuntu Quantal)
Status: Fix Committed = Fix Released
** Changed in: linux-lts-quantal (Ubuntu Precise)
Status: Fix Committed = Fix Released
** Changed in:
** Changed in: linux-armadaxp (Ubuntu Precise)
Status: New = Fix Committed
** Changed in: linux-armadaxp (Ubuntu Quantal)
Status: Fix Committed = Fix Released
** Changed in: linux-lts-quantal (Ubuntu Precise)
Status: Fix Committed = Fix Released
** Changed in:
** Changed in: linux-armadaxp (Ubuntu Precise)
Status: New = Fix Committed
** Changed in: linux-armadaxp (Ubuntu Quantal)
Status: Fix Committed = Fix Released
** Changed in: linux-ec2 (Ubuntu Lucid)
Status: Fix Committed = Fix Released
** Changed in: linux-lts-quantal
All builds are complete, packages in this bug can be copied to
-proposed.
** Changed in: kernel-sru-workflow/prepare-package
Status: In Progress = Fix Released
** Changed in: kernel-sru-workflow/promote-to-proposed
Status: New = Confirmed
** Description changed:
This bug is for
Any suggestion on the next steps?
--
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/1247967
Title:
nvidia optimus chipset disabled when running on battery, even in
discrete mode
Status
** Changed in: linux-armadaxp (Ubuntu Precise)
Status: New = Fix Committed
** Changed in: linux-armadaxp (Ubuntu Quantal)
Status: Fix Committed = Fix Released
** Changed in: linux-lts-quantal (Ubuntu Precise)
Status: Fix Committed = Fix Released
** Changed in:
** Changed in: linux-armadaxp (Ubuntu Quantal)
Status: Fix Committed = Fix Released
** Changed in: linux-lts-quantal (Ubuntu Precise)
Status: Fix Committed = Fix Released
** Changed in: linux-lts-saucy (Ubuntu Precise)
Status: New = Invalid
** Changed in: linux-lts-saucy
** Changed in: linux-armadaxp (Ubuntu Precise)
Status: New = Fix Committed
** Changed in: linux-armadaxp (Ubuntu Quantal)
Status: Fix Committed = Fix Released
** Changed in: linux-lts-quantal (Ubuntu Precise)
Status: Fix Committed = Fix Released
** Changed in:
hmm, the fedora 20 beta boots to X ok. going to retry booting the saucy
live image, and see how much of what i'm seeing running local kernels is
due to fglrx not compiling for 3.10 and above
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed
** Changed in: linux-armadaxp (Ubuntu Quantal)
Status: New = Fix Committed
** Changed in: linux-lts-saucy (Ubuntu Precise)
Status: New = Fix Committed
** Changed in: linux-lts-saucy (Ubuntu Precise)
Importance: Undecided = Medium
** Changed in: linux-lts-saucy (Ubuntu Saucy)
Ubuntu 14.04 already has the latest mainline kernel, and Ubuntu 13.04
works perfectly fine with every kernel from 3.8 to 3.12.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
** Changed in: linux-lts-saucy (Ubuntu Precise)
Importance: Undecided = Medium
** Changed in: linux-lts-saucy (Ubuntu Saucy)
Status: New = Invalid
** Changed in: linux-lts-saucy (Ubuntu Saucy)
Importance: Undecided = Medium
** Changed in: linux-lts-saucy (Ubuntu Lucid)
** Changed in: linux-lts-saucy (Ubuntu Precise)
Status: New = Fix Committed
** Changed in: linux-lts-saucy (Ubuntu Precise)
Importance: Undecided = Medium
** Changed in: linux-lts-saucy (Ubuntu Saucy)
Status: New = Invalid
** Changed in: linux-lts-saucy (Ubuntu Saucy)
This behaviour no longer occurs in 13.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/1232691
Title:
Automatic suspend / resume behaviour is poor
Status in “linux” package in
** Changed in: linux-lts-saucy (Ubuntu Precise)
Importance: Undecided = Medium
** Changed in: linux-lts-saucy (Ubuntu Saucy)
Status: New = Invalid
** Changed in: linux-lts-saucy (Ubuntu Saucy)
Importance: Undecided = Medium
** Changed in: linux-lts-saucy (Ubuntu Lucid)
** Changed in: linux-armadaxp (Ubuntu Precise)
Status: New = Fix Committed
** Changed in: linux-armadaxp (Ubuntu Quantal)
Status: Fix Committed = Fix Released
** Changed in: linux-lts-quantal (Ubuntu Precise)
Status: Fix Committed = Fix Released
** Changed in:
apport information
** Tags added: apport-collected
** Description changed:
I'm getting this message every 5 seconds
[ 38.976076] mei_me :00:03.0: reset: connect/disconnect timeout.
[ 38.976085] mei_me :00:03.0: unexpected reset: dev_state = RESETTING
According
apport information
** Attachment added: BootDmesg.txt
https://bugs.launchpad.net/bugs/1251681/+attachment/3910025/+files/BootDmesg.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: CurrentDmesg.txt
https://bugs.launchpad.net/bugs/1251681/+attachment/3910028/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
1 - 100 of 143 matches
Mail list logo
