Have the same error on a HP Proliant G6 ML330 with Intel® Xeon(R) CPU
E5504 @ 2.00GHz × 4 and 10GB RAM. I also have 2 new 1TB, WD1002F9YZ in
it and configured a software RAID with Partions for SWAP (10GB), System
(100GB, ext4) und DATA (890GB, ext4)
--
You received this bug notification because
Public bug reported:
CID: 201402-14810 Dell Vostro 20 3015
Brightness control does not work on this AIO system
The brightness level indicator would change with hotkey events, but the
brightness itself does not.
Debugging information:
ubuntu@201402-14810:~$ ls /sys/class/backlight
acpi_video0
** Attachment added: fwts_method.log
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1395618/+attachment/4266590/+files/fwts_method.log
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** Attachment added: dsdt.dsl
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1395618/+attachment/4266588/+files/dsdt.dsl
--
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/1395618
** Attachment added: fwts.log
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1395618/+attachment/4266589/+files/fwts.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/1395618
Tweak:
acpi_backlight=vendor works, but
acpi_osi=\!Windows 2012\ does not.
--
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/1395618
Title:
[Dell Vostro 20 3015] Unable to control
** Also affects: hwe-next
Importance: Undecided
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/1395618
Title:
[Dell Vostro 20 3015] Unable to control brightness
This change was made by a bot.
** Changed in: linux (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1395618
Title:
[Dell Vostro 20 3015] Unable
Brightness control also works with 3.16 kernel
ubuntu@201402-14810:~$ uname -a
Linux 201402-14810 3.16.7-031607-generic #201410301735 SMP Thu Oct 30 17:37:43
UTC 2014 x86_64 x86_64 x86_64 GNU/Linux
--
You received this bug notification because you are a member of Kernel
Packages, which is
Public bug reported:
CID: 201306-13867 Dell Inspiron 7537
This bug should be fixed in Trusty, see bug 1339456,
however, the wireless key still not working on this system with 3.13.0-39.
Note that for another system reported in that bug, 201306-13869 Dell
Inspiron 7737, wireless key could work
** Changed in: hwe-next/trusty
Status: Fix Committed = Fix Released
--
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/1383138
Title:
New BT firmware for Intel 7265 D0
I've just installed against upstream 3.18.0-031800rc6 (linux-
image-3.18.0-031800rc6-generic_3.18.0-031800rc6.201411231935_amd64.deb,
linux-headers-3.18.0-031800rc6_3.18.0-031800rc6.201411231935_all.deb,
linux-
headers-3.18.0-031800rc6-generic_3.18.0-031800rc6.201411231935_amd64.deb)
and get the
This change was made by a bot.
** Changed in: linux (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1395662
Title:
[Dell Inspiron 7537] Wireless
Here's a screenshot to illustrate the problem. It's a terrible photo,
but you can hopefully see that what I type is being displayed at the top
left and focus is not going to the enter passphrase box. In this photo
I have typed a password and pressed enter. Nothing I can do makes
focus go to the
** Tags removed: verification-done-trusty verification-done-utopic
** Tags added: verification-done
--
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/1304001
Title:
xen:balloon errors in
Yes, ok - but what about the **forcepae** boot option ? lubuntu is working with
this option: see
https://help.ubuntu.com/community/PAE
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
The culprit is the upgrade to 3.13.0-35. Until -34 it works fine. I am
trying the mainline kernels to see when the regression happens there.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
It appears the .deb file is corrupt.
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
--
You received this bug notification because you are a
Can you provide some information on the status of the patch with regards
to getting it merged upstream? Has it been sent upstream, what sort of
feedback has it received, is it getting applied to a subsystem
maintainer's tree, etc?
** Changed in: linux (Ubuntu)
Importance: Undecided = Medium
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 kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v3.18 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
v3.18 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
Here is the link to the upstream patch.
http://www.spinics.net/lists/linux-bluetooth/msg55965.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1395465
Title:
[ASUS X200MA] Bluetooth
Tested kernel 3.17.3 providing no solution.
kernel-bug-exists-upstream
kernel-bug-exists-upstream-3.17.3
** Changed in: linux (Ubuntu)
Status: Incomplete = Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** Tags added: kernel-da-key
** Changed in: linux (Ubuntu)
Importance: Undecided = Medium
** Changed in: linux (Ubuntu)
Status: Confirmed = Triaged
** Also affects: linux (Ubuntu Vivid)
Importance: Medium
Status: Triaged
** Also affects: linux (Ubuntu Trusty)
Importance:
** Changed in: linux (Ubuntu Utopic)
Status: Triaged = In Progress
** Changed in: linux (Ubuntu Utopic)
Assignee: (unassigned) = Joseph Salisbury (jsalisbury)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
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)
On Sat, Nov 22, 2014 at 01:41:55AM -, Michael Heuberger wrote:
Ok, understood. Well, I spotted the error in my dmesg output. There was
something else trying to turn the powersave off which failed of course
and an error was printed. That confused me.
If I have power support disabled, then
No, I haven't submitted this upstream.
I though the channel to get this upstreamed will be the bug tracker of
the Linux distribution I'm using.
What lead me to are the links I included in the report above: Users of
Fedora and Opensuse reported similar quirks table additions via these
@dhruvahuja
Thanks, but I can reproduce this issue, so no need to collect any more
information.
Testing once I get a fix will be appreciated. : )
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
In the mainline kernel (not really mainline, because it is an extended
version maintained by Canonical), the problem occurs between 3.13.11.5
and 3.13.11.6. I checked the git logs, but I am not expert enough to
understand which commit may be the cause of the problem. I'll try to git
bisect when I
** Description changed:
This a request to get a quirk added upstream for the Synaptics ClickPad
(buttonless trackpad) of the Lenovo Edge E440 to the synaptics kernel
driver so the right coordinates for the surface corners are reported and
the pointer functionality is correct.
$
I built a Utopic test kernel with the patch from comment #2. Can you
test this kernel and see if it resolves this bug? If it does, we can
submit and SRU request for inclusion in Utopic.
The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1395465/
Note: You will have
I already tested it and also gave link to the kernel debs. It works.
And also a few people tested on various ASUS laptops with this bluetooth module.
There is a thread on ubuntuforums.
But I'll try yours, just to make sure.
--
You received this bug notification because you are a member of
** Also affects: linux (Ubuntu Trusty)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Trusty)
Status: New = In Progress
** Changed in: linux (Ubuntu Trusty)
Importance: Undecided = Medium
** Changed in: linux (Ubuntu Trusty)
Assignee: (unassigned) =
@Pilot6, thanks! I also have a Trusty test kernel building.
--
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/1395465
Title:
[ASUS X200MA] Bluetooth does not work
Status in “linux”
@Joseph
Yes. your build works as expected. But there is a small bug, which I think is
not directly kernel related.
Same is with my build.
When I boot first time with this kernel, there is no bluetooth indicator. I
test it like a common user.
Then I go to System settings - bluetooth and enable
@Joseph
Is it 3.13 or 3.16? I think there is no need to patch 3.13 as very soon
3.16 will be default in trusty 14.04.2 and lts-utopic will be suggested
for all trusty users. I tested it on trusty, because I do not have
utipic on this laptop. It makes no difference as it is a very simple
kernel
** Changed in: kernel-sru-workflow/promote-to-security
Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) = Chris J Arges
(arges)
** Changed in: kernel-sru-workflow/promote-to-updates
Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) = Chris J Arges
(arges)
--
You
** Changed in: kernel-sru-workflow/promote-to-security
Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) = Chris J Arges
(arges)
** Changed in: kernel-sru-workflow/promote-to-updates
Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) = Chris J Arges
(arges)
--
You
** Changed in: kernel-sru-workflow/promote-to-security
Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) = Chris J Arges
(arges)
** Changed in: kernel-sru-workflow/promote-to-updates
Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) = Chris J Arges
(arges)
--
You
** No longer affects: linux (Ubuntu Trusty)
--
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/1395465
Title:
[ASUS X200MA] Bluetooth does not work
Status in “linux” package in Ubuntu:
This bug was fixed in the package linux - 3.2.0-72.107
---
linux (3.2.0-72.107) precise; urgency=low
[ Luis Henriques ]
* Release Tracking Bug
- LP: #1390048
[ Upstream Kernel Changes ]
* Revert iwlwifi: dvm: don't enable CTS to self
- LP: #1389928
* regulatory:
*** This bug is a duplicate of bug 1390048 ***
https://bugs.launchpad.net/bugs/1390048
This bug was fixed in the package linux - 3.2.0-72.107
---
linux (3.2.0-72.107) precise; urgency=low
[ Luis Henriques ]
* Release Tracking Bug
- LP: #1390048
[ Upstream Kernel
This bug was fixed in the package linux - 3.2.0-72.107
---
linux (3.2.0-72.107) precise; urgency=low
[ Luis Henriques ]
* Release Tracking Bug
- LP: #1390048
[ Upstream Kernel Changes ]
* Revert iwlwifi: dvm: don't enable CTS to self
- LP: #1389928
* regulatory:
This bug was fixed in the package linux - 3.2.0-72.107
---
linux (3.2.0-72.107) precise; urgency=low
[ Luis Henriques ]
* Release Tracking Bug
- LP: #1390048
[ Upstream Kernel Changes ]
* Revert iwlwifi: dvm: don't enable CTS to self
- LP: #1389928
* regulatory:
This bug was fixed in the package linux - 3.2.0-72.107
---
linux (3.2.0-72.107) precise; urgency=low
[ Luis Henriques ]
* Release Tracking Bug
- LP: #1390048
[ Upstream Kernel Changes ]
* Revert iwlwifi: dvm: don't enable CTS to self
- LP: #1389928
* regulatory:
This bug was fixed in the package linux - 3.2.0-72.107
---
linux (3.2.0-72.107) precise; urgency=low
[ Luis Henriques ]
* Release Tracking Bug
- LP: #1390048
[ Upstream Kernel Changes ]
* Revert iwlwifi: dvm: don't enable CTS to self
- LP: #1389928
* regulatory:
This bug was fixed in the package linux - 3.2.0-72.107
---
linux (3.2.0-72.107) precise; urgency=low
[ Luis Henriques ]
* Release Tracking Bug
- LP: #1390048
[ Upstream Kernel Changes ]
* Revert iwlwifi: dvm: don't enable CTS to self
- LP: #1389928
* regulatory:
** Changed in: kernel-sru-workflow/promote-to-security
Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) = Chris J Arges
(arges)
** Changed in: kernel-sru-workflow/promote-to-updates
Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) = Chris J Arges
(arges)
--
You
This bug was fixed in the package linux - 3.13.0-40.69
---
linux (3.13.0-40.69) trusty; urgency=low
[ Luis Henriques ]
* Release Tracking Bug
- re-used previous tracking bug
[ Upstream Kernel Changes ]
* regmap: fix kernel hang on regmap_bulk_write with zero val_count.
This bug was fixed in the package linux - 3.13.0-40.69
---
linux (3.13.0-40.69) trusty; urgency=low
[ Luis Henriques ]
* Release Tracking Bug
- re-used previous tracking bug
[ Upstream Kernel Changes ]
* regmap: fix kernel hang on regmap_bulk_write with zero val_count.
This bug was fixed in the package linux - 3.13.0-40.69
---
linux (3.13.0-40.69) trusty; urgency=low
[ Luis Henriques ]
* Release Tracking Bug
- re-used previous tracking bug
[ Upstream Kernel Changes ]
* regmap: fix kernel hang on regmap_bulk_write with zero val_count.
This bug was fixed in the package linux - 3.13.0-40.69
---
linux (3.13.0-40.69) trusty; urgency=low
[ Luis Henriques ]
* Release Tracking Bug
- re-used previous tracking bug
[ Upstream Kernel Changes ]
* regmap: fix kernel hang on regmap_bulk_write with zero val_count.
This bug was fixed in the package linux - 3.13.0-40.69
---
linux (3.13.0-40.69) trusty; urgency=low
[ Luis Henriques ]
* Release Tracking Bug
- re-used previous tracking bug
[ Upstream Kernel Changes ]
* regmap: fix kernel hang on regmap_bulk_write with zero val_count.
This bug was fixed in the package linux - 3.13.0-40.69
---
linux (3.13.0-40.69) trusty; urgency=low
[ Luis Henriques ]
* Release Tracking Bug
- re-used previous tracking bug
[ Upstream Kernel Changes ]
* regmap: fix kernel hang on regmap_bulk_write with zero val_count.
This bug was fixed in the package linux - 3.13.0-40.69
---
linux (3.13.0-40.69) trusty; urgency=low
[ Luis Henriques ]
* Release Tracking Bug
- re-used previous tracking bug
[ Upstream Kernel Changes ]
* regmap: fix kernel hang on regmap_bulk_write with zero val_count.
This bug was fixed in the package linux - 3.16.0-25.33
---
linux (3.16.0-25.33) utopic; urgency=low
[ Luis Henriques ]
* Release Tracking Bug
- LP: #1389170
[ dann frazier ]
* [Config] Disable CONFIG_IPMI_SI_PROBE_DEFAULTS on armhf and arm64
- LP: #1388952
[ Duc
This bug was fixed in the package linux - 3.13.0-40.69
---
linux (3.13.0-40.69) trusty; urgency=low
[ Luis Henriques ]
* Release Tracking Bug
- re-used previous tracking bug
[ Upstream Kernel Changes ]
* regmap: fix kernel hang on regmap_bulk_write with zero val_count.
This bug was fixed in the package linux - 3.16.0-25.33
---
linux (3.16.0-25.33) utopic; urgency=low
[ Luis Henriques ]
* Release Tracking Bug
- LP: #1389170
[ dann frazier ]
* [Config] Disable CONFIG_IPMI_SI_PROBE_DEFAULTS on armhf and arm64
- LP: #1388952
[ Duc
This bug was fixed in the package linux - 3.16.0-25.33
---
linux (3.16.0-25.33) utopic; urgency=low
[ Luis Henriques ]
* Release Tracking Bug
- LP: #1389170
[ dann frazier ]
* [Config] Disable CONFIG_IPMI_SI_PROBE_DEFAULTS on armhf and arm64
- LP: #1388952
[ Duc
This bug was fixed in the package linux-meta - 3.16.0.25.26
---
linux-meta (3.16.0.25.26) utopic; urgency=low
[ Andy Whitcroft ]
* downgrade thermald to a Recommends: so that it can be removed when
it is not needed. (LP: #1387144)
[ Luis Henriques ]
* linux ABI
This bug was fixed in the package linux - 3.16.0-25.33
---
linux (3.16.0-25.33) utopic; urgency=low
[ Luis Henriques ]
* Release Tracking Bug
- LP: #1389170
[ dann frazier ]
* [Config] Disable CONFIG_IPMI_SI_PROBE_DEFAULTS on armhf and arm64
- LP: #1388952
[ Duc
This bug was fixed in the package linux - 3.13.0-40.69
---
linux (3.13.0-40.69) trusty; urgency=low
[ Luis Henriques ]
* Release Tracking Bug
- re-used previous tracking bug
[ Upstream Kernel Changes ]
* regmap: fix kernel hang on regmap_bulk_write with zero val_count.
This bug was fixed in the package linux - 3.16.0-25.33
---
linux (3.16.0-25.33) utopic; urgency=low
[ Luis Henriques ]
* Release Tracking Bug
- LP: #1389170
[ dann frazier ]
* [Config] Disable CONFIG_IPMI_SI_PROBE_DEFAULTS on armhf and arm64
- LP: #1388952
[ Duc
This bug was fixed in the package linux - 3.16.0-25.33
---
linux (3.16.0-25.33) utopic; urgency=low
[ Luis Henriques ]
* Release Tracking Bug
- LP: #1389170
[ dann frazier ]
* [Config] Disable CONFIG_IPMI_SI_PROBE_DEFAULTS on armhf and arm64
- LP: #1388952
[ Duc
This bug was fixed in the package linux - 3.16.0-25.33
---
linux (3.16.0-25.33) utopic; urgency=low
[ Luis Henriques ]
* Release Tracking Bug
- LP: #1389170
[ dann frazier ]
* [Config] Disable CONFIG_IPMI_SI_PROBE_DEFAULTS on armhf and arm64
- LP: #1388952
[ Duc
This bug was fixed in the package linux - 3.16.0-25.33
---
linux (3.16.0-25.33) utopic; urgency=low
[ Luis Henriques ]
* Release Tracking Bug
- LP: #1389170
[ dann frazier ]
* [Config] Disable CONFIG_IPMI_SI_PROBE_DEFAULTS on armhf and arm64
- LP: #1388952
[ Duc
This bug was fixed in the package linux - 3.16.0-25.33
---
linux (3.16.0-25.33) utopic; urgency=low
[ Luis Henriques ]
* Release Tracking Bug
- LP: #1389170
[ dann frazier ]
* [Config] Disable CONFIG_IPMI_SI_PROBE_DEFAULTS on armhf and arm64
- LP: #1388952
[ Duc
This bug was fixed in the package linux - 3.13.0-40.69
---
linux (3.13.0-40.69) trusty; urgency=low
[ Luis Henriques ]
* Release Tracking Bug
- re-used previous tracking bug
[ Upstream Kernel Changes ]
* regmap: fix kernel hang on regmap_bulk_write with zero val_count.
This bug was fixed in the package linux - 3.13.0-40.69
---
linux (3.13.0-40.69) trusty; urgency=low
[ Luis Henriques ]
* Release Tracking Bug
- re-used previous tracking bug
[ Upstream Kernel Changes ]
* regmap: fix kernel hang on regmap_bulk_write with zero val_count.
This bug was fixed in the package linux - 3.16.0-25.33
---
linux (3.16.0-25.33) utopic; urgency=low
[ Luis Henriques ]
* Release Tracking Bug
- LP: #1389170
[ dann frazier ]
* [Config] Disable CONFIG_IPMI_SI_PROBE_DEFAULTS on armhf and arm64
- LP: #1388952
[ Duc
This bug was fixed in the package linux - 3.13.0-40.69
---
linux (3.13.0-40.69) trusty; urgency=low
[ Luis Henriques ]
* Release Tracking Bug
- re-used previous tracking bug
[ Upstream Kernel Changes ]
* regmap: fix kernel hang on regmap_bulk_write with zero val_count.
This bug was fixed in the package linux - 3.13.0-40.69
---
linux (3.13.0-40.69) trusty; urgency=low
[ Luis Henriques ]
* Release Tracking Bug
- re-used previous tracking bug
[ Upstream Kernel Changes ]
* regmap: fix kernel hang on regmap_bulk_write with zero val_count.
This bug was fixed in the package linux - 3.16.0-25.33
---
linux (3.16.0-25.33) utopic; urgency=low
[ Luis Henriques ]
* Release Tracking Bug
- LP: #1389170
[ dann frazier ]
* [Config] Disable CONFIG_IPMI_SI_PROBE_DEFAULTS on armhf and arm64
- LP: #1388952
[ Duc
This bug was fixed in the package linux - 3.13.0-40.69
---
linux (3.13.0-40.69) trusty; urgency=low
[ Luis Henriques ]
* Release Tracking Bug
- re-used previous tracking bug
[ Upstream Kernel Changes ]
* regmap: fix kernel hang on regmap_bulk_write with zero val_count.
This bug was fixed in the package linux - 3.13.0-40.69
---
linux (3.13.0-40.69) trusty; urgency=low
[ Luis Henriques ]
* Release Tracking Bug
- re-used previous tracking bug
[ Upstream Kernel Changes ]
* regmap: fix kernel hang on regmap_bulk_write with zero val_count.
This bug was fixed in the package linux - 3.13.0-40.69
---
linux (3.13.0-40.69) trusty; urgency=low
[ Luis Henriques ]
* Release Tracking Bug
- re-used previous tracking bug
[ Upstream Kernel Changes ]
* regmap: fix kernel hang on regmap_bulk_write with zero val_count.
This bug was fixed in the package linux - 3.16.0-25.33
---
linux (3.16.0-25.33) utopic; urgency=low
[ Luis Henriques ]
* Release Tracking Bug
- LP: #1389170
[ dann frazier ]
* [Config] Disable CONFIG_IPMI_SI_PROBE_DEFAULTS on armhf and arm64
- LP: #1388952
[ Duc
This bug was fixed in the package linux - 3.16.0-25.33
---
linux (3.16.0-25.33) utopic; urgency=low
[ Luis Henriques ]
* Release Tracking Bug
- LP: #1389170
[ dann frazier ]
* [Config] Disable CONFIG_IPMI_SI_PROBE_DEFAULTS on armhf and arm64
- LP: #1388952
[ Duc
This bug was fixed in the package linux - 3.13.0-40.69
---
linux (3.13.0-40.69) trusty; urgency=low
[ Luis Henriques ]
* Release Tracking Bug
- re-used previous tracking bug
[ Upstream Kernel Changes ]
* regmap: fix kernel hang on regmap_bulk_write with zero val_count.
This bug was fixed in the package linux - 3.16.0-25.33
---
linux (3.16.0-25.33) utopic; urgency=low
[ Luis Henriques ]
* Release Tracking Bug
- LP: #1389170
[ dann frazier ]
* [Config] Disable CONFIG_IPMI_SI_PROBE_DEFAULTS on armhf and arm64
- LP: #1388952
[ Duc
This bug was fixed in the package linux - 3.16.0-25.33
---
linux (3.16.0-25.33) utopic; urgency=low
[ Luis Henriques ]
* Release Tracking Bug
- LP: #1389170
[ dann frazier ]
* [Config] Disable CONFIG_IPMI_SI_PROBE_DEFAULTS on armhf and arm64
- LP: #1388952
[ Duc
This bug was fixed in the package linux - 3.16.0-25.33
---
linux (3.16.0-25.33) utopic; urgency=low
[ Luis Henriques ]
* Release Tracking Bug
- LP: #1389170
[ dann frazier ]
* [Config] Disable CONFIG_IPMI_SI_PROBE_DEFAULTS on armhf and arm64
- LP: #1388952
[ Duc
I see that you already sent your patch upstream:
https://lkml.org/lkml/2014/11/23/78
Could you also send the patch with a CC to sta...@vger.kernel.org ?
That way it will make it's way into the upstream stable releases. There
is some info on this in the kernel tree documentation:
** Changed in: kernel-sru-workflow/package-testing
Status: Confirmed = Fix Released
--
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/1390176
Title:
linux-armadaxp:
@jsalisbury : We're talking here about a production fileserver. So, I'd
like to know a little bit more about the impact.
I'm not familiar with the status and stability of the mainline kernel.
Can I just download this kernel to /boot then add it to GRUB and run it from
there without risking my
*** This bug is a duplicate of bug 1390176 ***
https://bugs.launchpad.net/bugs/1390176
This bug was fixed in the package linux-armadaxp - 3.2.0-1641.59
---
linux-armadaxp (3.2.0-1641.59) precise; urgency=low
[ Ike Panhc ]
* Release Tracking Bug
- LP: #1390176
* Rebase
This bug was fixed in the package linux-armadaxp - 3.2.0-1641.59
---
linux-armadaxp (3.2.0-1641.59) precise; urgency=low
[ Ike Panhc ]
* Release Tracking Bug
- LP: #1390176
* Rebase to Ubuntu-3.2.0-72.107
[ Ubuntu: 3.2.0-72.107 ]
* Release Tracking Bug
- LP:
This bug was fixed in the package linux-armadaxp - 3.2.0-1641.59
---
linux-armadaxp (3.2.0-1641.59) precise; urgency=low
[ Ike Panhc ]
* Release Tracking Bug
- LP: #1390176
* Rebase to Ubuntu-3.2.0-72.107
[ Ubuntu: 3.2.0-72.107 ]
* Release Tracking Bug
- LP:
This bug was fixed in the package linux-armadaxp - 3.2.0-1641.59
---
linux-armadaxp (3.2.0-1641.59) precise; urgency=low
[ Ike Panhc ]
* Release Tracking Bug
- LP: #1390176
* Rebase to Ubuntu-3.2.0-72.107
[ Ubuntu: 3.2.0-72.107 ]
* Release Tracking Bug
- LP:
This bug was fixed in the package linux-armadaxp - 3.2.0-1641.59
---
linux-armadaxp (3.2.0-1641.59) precise; urgency=low
[ Ike Panhc ]
* Release Tracking Bug
- LP: #1390176
* Rebase to Ubuntu-3.2.0-72.107
[ Ubuntu: 3.2.0-72.107 ]
* Release Tracking Bug
- LP:
Public bug reported:
Today i installed the newest ubuntu and now the brightness control does
not work
ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: linux-image-3.16.0-25-generic 3.16.0-25.33
ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7
Uname: Linux 3.16.0-25-generic x86_64
@Joseph
CC to stable done, but it may be only 3.17, since 3.16 is EOL.
Did you receive my E-mail regarding the other patch?
--
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/1395465
Title:
Tim,
Should we also track this for 14.04.2, or, tracking for uTopic is enough
to track the inclusion on 14.04.2 (since 14.04.2 will use the same
utopic's kernel) ?
Thank you,
Breno
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux
This change was made by a bot.
** Changed in: linux (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1395782
Title:
brightness control
Status in
** Changed in: linux (Ubuntu)
Importance: Undecided = Medium
--
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/1395782
Title:
brightness control
Status in “linux” package in Ubuntu:
It seems that I'm plagued by this issue too.
Dell Inspiron N 4050 and Kubuntu 14.10. Upgraded from previous LTS where it
worked.
Intel Integrated Graphics card here.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Does this issue go away and brightness work again if you boot into the
last kernel version?
** Tags added: kernel-da-key regression-update
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
I see the following in ubuntu-utopic/master-next:
1b88860 powerpc/fadump: Fix endianess issues in firmware assisted dump handling
465f71e powerpc/pseries: Make CPU hotplug path endian safe
83b0775 powerpc/pseries/hvcserver: Fix endian issue in hvcs_get_partner_info
438b66c powerpc/pseries: Fix
1 - 100 of 227 matches
Mail list logo
