John, file a new bug mentioning that it's a regression and still there
in latest kernels, it should be easy to bisect if it happened between
-74..-76.
leaving ubuntu would not help, you'd have to leave linux ;)
--
You received this bug notification because you are a member of Kernel
Packages,
Kernel team,,
This is a high priority problem for IBM, can mark this bug importance as
high?
This is also affect both Ubuntu 15.10 (Kernel 4.2) and 16.04 (kernel
4.4). If you could cherry-pick on both versions, it would be ideal. :-)
Thank you!
** Changed in: linux (Ubuntu)
Status:
** Changed in: kernel-sru-workflow/automated-testing
Status: New => Confirmed
--
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/1548785
Title:
linux-lts-vivid:
** Tags removed: verification-needed-trusty
** Tags added: verification-done-trusty
--
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/1546320
Title:
crash starting at kernel
After an update, hdmi was not working anymore (no video and no sound).
So i did the command:
sudo gedit /etc/default/grub
and changed "GRUB_CMDLINE_LINUX_DEFAULT="NOMODESET"" into
"GRUB_CMDLINE_LINUX_DEFAULT="quiet splash radeon.audio=1""
then
sudo update-grub
it fixed the problem for me.
--
*** ATTENTION BUG REPORTERS ***
This bug report (#1548587) will ONLY be used to track the problem
relating to "VMWare won't show UI"!
- If you're experiencing a problem but you're not running under VMWare,
please file a separate bug.
- We have identified the cause of the problem, and are
I'll check if this helps on Skylake also.
--
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/1542934
Title:
hdmi not working
Status in linux package in Ubuntu:
Invalid
Bug description:
I have a ASUS ROG G552 and I added to following to my grub:
etc/default/grub
GRUB_CMDLINE_LINUX="acpi_osi=! acpi_backlight=native idle=nomwait"
I am running Ubuntu Mate 16.04
Kernel 4.4.0-7-generic
The above command restored my touchpad and detected it with full hw support.
--
You received
*** This bug is a duplicate of bug 1548587 ***
https://bugs.launchpad.net/bugs/1548587
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: linux (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
wily' to 'verification-done-wily'.
If verification is not done by 5 working days from
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
vivid' to 'verification-done-vivid'.
If verification is not done by 5 working days from
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
wily' to 'verification-done-wily'.
If verification is not done by 5 working days from
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
trusty' to 'verification-done-trusty'.
If verification is not done by 5 working days from
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
wily' to 'verification-done-wily'.
If verification is not done by 5 working days from
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
trusty' to 'verification-done-trusty'.
If verification is not done by 5 working days from
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
wily' to 'verification-done-wily'.
If verification is not done by 5 working days from
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
wily' to 'verification-done-wily'.
If verification is not done by 5 working days from
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
trusty' to 'verification-done-trusty'.
If verification is not done by 5 working days from
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
vivid' to 'verification-done-vivid'.
If verification is not done by 5 working days from
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
vivid' to 'verification-done-vivid'.
If verification is not done by 5 working days from
** Tags removed: targetmilestone-inin---
** Tags added: targetmilestone-inin14044
--
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/1542444
Title:
ib1: sendonly multicast join failed for
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
vivid' to 'verification-done-vivid'.
If verification is not done by 5 working days from
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
vivid' to 'verification-done-vivid'.
If verification is not done by 5 working days from
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
wily' to 'verification-done-wily'.
If verification is not done by 5 working days from
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
vivid' to 'verification-done-vivid'.
If verification is not done by 5 working days from
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
wily' to 'verification-done-wily'.
If verification is not done by 5 working days from
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
trusty' to 'verification-done-trusty'.
If verification is not done by 5 working days from
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
wily' to 'verification-done-wily'.
If verification is not done by 5 working days from
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
trusty' to 'verification-done-trusty'.
If verification is not done by 5 working days from
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
vivid' to 'verification-done-vivid'.
If verification is not done by 5 working days from
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
vivid' to 'verification-done-vivid'.
If verification is not done by 5 working days from
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
trusty' to 'verification-done-trusty'.
If verification is not done by 5 working days from
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
vivid' to 'verification-done-vivid'.
If verification is not done by 5 working days from
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
wily' to 'verification-done-wily'.
If verification is not done by 5 working days from
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
wily' to 'verification-done-wily'.
If verification is not done by 5 working days from
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
trusty' to 'verification-done-trusty'.
If verification is not done by 5 working days from
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
vivid' to 'verification-done-vivid'.
If verification is not done by 5 working days from
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
wily' to 'verification-done-wily'.
If verification is not done by 5 working days from
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
precise' to 'verification-done-precise'.
If verification is not done by 5 working days
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
trusty' to 'verification-done-trusty'.
If verification is not done by 5 working days from
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
wily' to 'verification-done-wily'.
If verification is not done by 5 working days from
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
vivid' to 'verification-done-vivid'.
If verification is not done by 5 working days from
The result of this bug is, some VMs on an affected host system will
receive some packets, but not all, so in the VM it appears that the
network doesn't work. This was specifically seen on Windows guests, in
this case.
--
You received this bug notification because you are a member of Kernel
I have been able to reproduce this issue, and the fix/patch provided
results in LRO being disabled automatically as described in post #1
above.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
tests ran: 170, failed: 2;
http://kernel.ubuntu.com/testing/4.2.0-31.36/onza__4.2.0-31.36__2016-02-25_06-09-00/results-index.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/1548579
--- Comment From frederic.bar...@fr.ibm.com 2016-02-25 02:19 EDT---
Patch for this has been sent to the linuxppc-dev mailing list and is being
reviewed:
http://patchwork.ozlabs.org/patch/587545
--
You received this bug notification because you are a member of Kernel
Packages, which is
This can be reproduced on any system with a nic that supports lro. For
example:
$ sudo ethtool -k eth5 | grep large-receive-offload
large-receive-offload: on
$ sudo modprobe bonding
$ sudo ifenslave bond0 eth5
$ sudo brctl addbr br0
$ sudo brctl addif br0 bond0
without the patch, lro will
Public bug reported:
When the phobe is connected to my cars bluetooth. I can play music
tracks with the built in music approval on the phone but cannot skip
tracks with the controls in the car.
I am using bq Aquaris 5 hd with oat 9.1
** Affects: bluez (Ubuntu)
Importance: Undecided
I can not as it says:
"It appears you are currently running a mainline kernel. It would be
better to report this bug upstream at http://bugzilla.kernel.org/ so
that the upstream kernel developers are aware of the issue. If you'd
still like to file a bug against the Ubuntu kernel, please boot
This bug was fixed in the package linux-mako - 3.4.0-7.44
---
linux-mako (3.4.0-7.44) xenial; urgency=low
[ Andy Whitcroft ]
* SAUCE: timeconst.pl -- fix use of defined on arrays
- LP: #1549677
linux-mako (3.4.0-7.43) xenial; urgency=low
[ Andy Whitcroft ]
* [Config]
This bug was fixed in the package linux-flo - 3.4.0-5.22
---
linux-flo (3.4.0-5.22) xenial; urgency=low
[ Andy Whitcroft ]
* SAUCE: timeconst.pl -- fix use of defined on arrays
- LP: #1549677
linux-flo (3.4.0-5.21) xenial; urgency=low
[ Andy Whitcroft ]
* [Config]
This bug was fixed in the package linux-flo - 3.4.0-5.22
---
linux-flo (3.4.0-5.22) xenial; urgency=low
[ Andy Whitcroft ]
* SAUCE: timeconst.pl -- fix use of defined on arrays
- LP: #1549677
linux-flo (3.4.0-5.21) xenial; urgency=low
[ Andy Whitcroft ]
* [Config]
This bug was fixed in the package linux-mako - 3.4.0-7.44
---
linux-mako (3.4.0-7.44) xenial; urgency=low
[ Andy Whitcroft ]
* SAUCE: timeconst.pl -- fix use of defined on arrays
- LP: #1549677
linux-mako (3.4.0-7.43) xenial; urgency=low
[ Andy Whitcroft ]
* [Config]
This bug was fixed in the package linux-hammerhead - 3.4.0-1.12
---
linux-hammerhead (3.4.0-1.12) xenial; urgency=low
[ Andy Whitcroft ]
* SAUCE: timeconst.pl -- fix use of defined on arrays
- LP: #1549677
linux-hammerhead (3.4.0-1.11) xenial; urgency=low
[ Andy
This bug was fixed in the package linux-hammerhead - 3.4.0-1.12
---
linux-hammerhead (3.4.0-1.12) xenial; urgency=low
[ Andy Whitcroft ]
* SAUCE: timeconst.pl -- fix use of defined on arrays
- LP: #1549677
linux-hammerhead (3.4.0-1.11) xenial; urgency=low
[ Andy
Thanks for your analysis Dexuan, I had not had a change to look at the
mainline differences yet.
--
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/1549601
Title:
[Hyper-V] x86,pageattr:
** Changed in: linux (Ubuntu)
Status: In Progress => 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/1540390
Title:
Backport more recent driver for SKL, KBL and BXT
** Changed in: linux (Ubuntu)
Status: In Progress => 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/1549494
Title:
arm64: guest hangs when ntpd is running
Status
** Tags removed: block-proposed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-mako in Ubuntu.
https://bugs.launchpad.net/bugs/1541917
Title:
kmod: merge debian 22-1
Status in kmod package in Ubuntu:
In Progress
Status in
** Changed in: kernel-sru-workflow/promote-to-proposed
Status: Confirmed => In Progress
** Changed in: kernel-sru-workflow/promote-to-proposed
Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Chris J Arges
(arges)
--
You received this bug notification because you are a
Hi.
I am having the same problem as amaguran on an HP Envy 14 (2010) after
upgrading to 4.2.0-30 on Ubuntu 14.04. The vivid branch of the kernel
works fine though.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Good catch Chris!
--
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/1549601
Title:
[Hyper-V] x86,pageattr: prevent overflow in slow_virt_to_phys() for
X86_PAE
Status in linux package in
Same problem on an Envy 14 2010 after upgrading to 4.2.0-30
--
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/1549197
Title:
Hard lockup on HP ENVY 13
Status in linux package in Ubuntu:
** Also affects: trusty (Ubuntu)
Importance: Undecided
Status: New
** Changed in: trusty (Ubuntu)
Status: New => Invalid
** Changed in: trusty (Ubuntu Wily)
Status: New => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which
Hi,
After updating to kernel 4.2.0.30 it freezes after login or in the login screen
if I wait for a few seconds.
I have Ubuntu 14.04.4 on HP Elitebook 850 G1 (AMD card).
I rolled back to kernel 4.2.0.27 and the problem is gone.
Thanks.
--
You received this bug notification because you are a
https://bugs.freedesktop.org/show_bug.cgi?id=92084
** Bug watch added: freedesktop.org Bugzilla #92084
https://bugs.freedesktop.org/show_bug.cgi?id=92084
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Hi,
I know it's a 15.10/4.2.0 thread, but I have the same problem with 14.04
LTS and 3.16.0-62 kernel in vmware. 3.16.0-60 is the last that worked.
Should I open a new bug report? If yes, what data should I send? But I'm
a Linux noob so be patient :)
--
You received this bug notification
I have a very similar problem on my Laptop running Xubuntu too.
So no VMWare. Just normal Xubuntu running directly on the laptop.
After updating to kernel 4.2.0.30, my laptop would still start to the login
screen.
Everything seemed to be working fine on the login screen.
Even remote access via
I also have trouble with the 4.2.0-30 kernel, but I am not running Ubuntu as
VMWare - just directly on my laptop.
- it freezes about 40 seconds after login screen (whether I login or not), I
can only work around this by using 4.2.0-27 kernel.
--
You received this bug notification because you
I tried the above suggestion. Now I do not see the bluetooth icon any
more. When I open the bluetooth manager, it shows "No Bluetooth adapters
found".
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
** Changed in: kernel-development-workflow/promote-to-proposed
Status: New => Fix Released
** Description changed:
This bug is for tracking the 4.4.0-8.23 upload package. This bug will
contain status and testing results related to that upload.
For an explanation of the tasks and
** Changed in: linux (Ubuntu)
Status: Incomplete => Fix Committed
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => David Henningsson (diwic)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
On Thu, 25 Feb 2016 09:37:05 +0100,
David Henningsson wrote:
>
> On one of the machines we enable, we found that the actual speaker volume
> did not always correspond to the volume set in alsamixer. This patch
> fixes that problem.
>
> This patch was orginally written by Kailang @ Realtek, I've
This also affects the Xenial Standard 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/1505948
Title:
Memory arena corruption with FUSE (was Memory allocation failure
crashes
** Description changed:
This bug is for tracking the 3.2.0-1663.87 upload package. This bug will
contain status and testing results related to that upload.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
** Changed in: kernel-sru-workflow/automated-testing
Status: Confirmed => Fix Released
** Description changed:
This bug is for tracking the 3.13.0-80.124~precise1 upload package. This
bug will contain status and testing results related to that upload.
For an explanation of the
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1549515/+attachment/4580652/+files/Lsusb.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/1549515
apport information
** Attachment added: "RfKill.txt"
https://bugs.launchpad.net/bugs/1549515/+attachment/4580658/+files/RfKill.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: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1549515/+attachment/4580654/+files/ProcEnviron.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: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1549515/+attachment/4580655/+files/ProcInterrupts.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: "JournalErrors.txt"
https://bugs.launchpad.net/bugs/1549515/+attachment/4580650/+files/JournalErrors.txt
--
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 wily
** Description changed:
Hello everybody,
Not sure if it's the right place but I'd like to report a bug.
I bought a Acer Aspire V3-372-53GG (brand new laptop released very recently
by Acer), installed Ubuntu alongside Windows
apport information
** Attachment added: "CRDA.txt"
https://bugs.launchpad.net/bugs/1549515/+attachment/4580647/+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/1549515
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1549515/+attachment/4580656/+files/ProcModules.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: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1549515/+attachment/4580653/+files/ProcCpuinfo.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: "IwConfig.txt"
https://bugs.launchpad.net/bugs/1549515/+attachment/4580649/+files/IwConfig.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: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1549515/+attachment/4580659/+files/UdevDb.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: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1549515/+attachment/4580660/+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: "Lspci.txt"
https://bugs.launchpad.net/bugs/1549515/+attachment/4580651/+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/1549515
apport information
** Attachment added: "PulseList.txt"
https://bugs.launchpad.net/bugs/1549515/+attachment/4580657/+files/PulseList.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/1549515/+attachment/4580648/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Public bug reported:
Can't use 'defined(@array)' (Maybe you should just omit the defined()?) at
/«PKGBUILDDIR»/kernel/timeconst.pl line 373.
make[3]: *** [kernel/timeconst.h] Error 255
/«PKGBUILDDIR»/kernel/Makefile:129: recipe for target 'kernel/timeconst.h'
failed
make[2]: *** [kernel] Error
** 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.
https://bugs.launchpad.net/bugs/1549601
Title:
[Hyper-V] x86,pageattr: prevent overflow in
** Tags added: qa-testing-passed
** Changed in: kernel-sru-workflow/verification-testing
Status: In Progress => Fix Released
** Changed in: kernel-sru-workflow/regression-testing
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of
On 2016-02-25 09:29, Takashi Iwai wrote:
> On Thu, 25 Feb 2016 09:13:21 +0100,
> David Henningsson wrote:
>>
>> On one of the machines we enable, we found that the actual speaker volume
>> did not always correspond to the volume set in alsamixer. This patch
>> fixes that problem.
>>
>> This patch
On one of the machines we enable, we found that the actual speaker volume
did not always correspond to the volume set in alsamixer. This patch
fixes that problem.
This patch was orginally written by Kailang @ Realtek, I've rebased it
to fit sound git master.
Cc: sta...@vger.kernel.org
BugLink:
It turns out the issue also exists in the latest mainline kernel!
The fix "x86, pageattr: Prevent overflow in slow_virt_to_phys() for X86_PAE" is
there, but a later patch "x86/mm: Fix slow_virt_to_phys() to handle large PAT
bit"
On Thu, 25 Feb 2016 09:13:21 +0100,
David Henningsson wrote:
>
> On one of the machines we enable, we found that the actual speaker volume
> did not always correspond to the volume set in alsamixer. This patch
> fixes that problem.
>
> This patch was orginally written by Kailang @ Realtek, I've
This bug is missing log files that will aid in diagnosing the problem.
>From a terminal window please run:
apport-collect 1549660
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
** Changed in: kernel-sru-workflow/security-signoff
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-lts-trusty in Ubuntu.
https://bugs.launchpad.net/bugs/1548759
Title:
linux-lts-trusty:
101 - 200 of 206 matches
Mail list logo
