Public bug reported:
It was brought to my attention the follow kernel panic:
[3367068.076488] Code: 23 66 2e 0f 1f 84 00 00 00 00 00 83 fb 03 75 05 45 84 ed
75 66 f0 41 ff 4c 24 24 74 26 89 da 83 fa 04 74 3d f3 90 41 8b 5c 24 20 39 d3
74 f0 83 fb 02 75 d7 fa 66 0f 1f 44 00 00 eb d8 66 0f 1f
Can folks affected by this bug test the latest Vivid updates and see if
the bug still exists?
Thanks in advance!
** Changed in: linux (Ubuntu)
Status: Confirmed = Fix Committed
** Changed in: linux (Ubuntu Utopic)
Status: Confirmed = Fix Committed
--
You received this bug
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: qemu (Ubuntu Vivid)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1461012
Title:
Should be fixed as of the 3.19.0-8 kernel:
commit 9933a927ded632fde949e0ef6f7a201534d2add8
Author: Seth Forshee seth.fors...@canonical.com
Date: Fri Feb 20 11:45:11 2015 -0600
HID: i2c-hid: Limit reads to wMaxInputLength bytes for input events
git describe --contains 9933a92
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: qemu (Ubuntu Vivid)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu in Ubuntu.
I can reproduce this issue on Trusty.
** Changed in: libvirt (Ubuntu)
Status: Incomplete = Confirmed
** Changed in: libvirt (Ubuntu)
Importance: Undecided = Medium
** Also affects: libvirt (Ubuntu Trusty)
Importance: Undecided
Status: New
** Changed in: libvirt (Ubuntu
admin@test:~$ uname -a
Linux test 4.1.0-040100rc6-lowlatency #201506010235 SMP PREEMPT Mon Jun 1
02:39:09 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux
root@test:/home/admin# echo 129 /sys/block/vda/queue/nr_requests
bash: echo: write error: Invalid argument
root@test:/home/admin# cat
** Changed in: content-hub (Ubuntu)
Status: Fix Released = In Progress
** Changed in: content-hub (Ubuntu)
Assignee: (unassigned) = Ken VanDine (ken-vandine)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
No idea. I think can operate with the usual procedures: merge now with
0.5.0, and either merge or do an updated package once a new release is
available, provided it happens before Feature Freeze (August 20).
I'll include patches for the above bugs as I merge multipath-tools.
--
You received
Just to let subscribers know - there's a $60 bounty for this that can be
claimed at any time , as the bug is officially closed.
This means you'll receive a cheque for 90% of this bounty by cheque, through
the post if you so wish to.
** Changed in: linux (Ubuntu Trusty)
Importance: Undecided = Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1461620
Title:
NUMA task migration race condition due to stop task not being
No idea. I think can operate with the usual procedures: merge now with
0.5.0, and either merge or do an updated package once a new release is
available, provided it happens before Feature Freeze (August 20).
I'll include patches for the above bugs as I merge multipath-tools.
--
You received
You can follow my comments in LKML:
https://lkml.org/lkml/2015/3/6/484
Basically in kernel 3.13 we are getting the follow situation:
I have a core dump locked on the same place
(state machine for powering cpu down for the task swap) from a 3.13 (+
upstream patches) and this commit wasn't
To understand better if this bug was triggered easy I created the
following test case:
I've been using a KVM guest emulating a NUMA environment with 32
different domains (1 for each vCPU):
root@numa:~# numactl -H
available: 32 nodes (0-31)
node 0 cpus: 0
node 0 size: 237 MB
node 0 free: 82
*** Bug 86510 has been marked as a duplicate of this bug. ***
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1449051
Title:
Upower doesn't handle bluetooth mice properly
To manage notifications
But unfortunately I could not reproduce the issue (although I know it is
in there). I'll create a small logic similar to:
Commit a1d9a3231eac4117cadaf4b6bba5b2902c15a33e
Author: Kirill Tkhai tk...@yandex.ru
Date: Thu Apr 10 17:38:36 2014 +0400
sched: Check for stop task appearance when
** Also affects: linux (Ubuntu Trusty)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu)
Status: In Progress = Invalid
** Changed in: linux (Ubuntu Trusty)
Status: New = In Progress
** Changed in: linux (Ubuntu Trusty)
Assignee: (unassigned) = Rafael
It happens that the fix relies on checking if the stop worker needs task
selection re-start:
+ if (need_pull_dl_task(rq, prev)) {
pull_dl_task(rq);
+ /*
+* pull_rt_task() can drop (and re-acquire) rq-lock; this
+* means a stop
Public bug reported:
Sometime charge graph have some glitches (see screenshot), that's due
to the default method canvas use to join line and the fact that sometime
the curbe has several data point on the same x (see
https://bugreports.qt.io/browse/QTBUG-34339)
** Affects: ubuntu-system-settings
Hello Joseph!
Thanks a lot for the bisect work. As I mentioned earlier in the backlog,
I'm not at home with the troubling computer for 2 months, but I commit
to test this kernel as soon as I get back. I'm very interested to have
this issue sorted out (or at least debugged) so I will test the new
Public bug reported:
When Ubuntu 15.10 64bits ( btrfs ) got installed, i want to use
google-chrome-unstable 45.0.2414.0 (64-bit) on it.
But i found glitches that affect the whole interface, sometimes the context
menus
that's what i found in the terminal after using google-chrome-unstable
$
I can reproduce this issue on Trusty.
** Changed in: libvirt (Ubuntu)
Status: Incomplete = Confirmed
** Changed in: libvirt (Ubuntu)
Importance: Undecided = Medium
** Also affects: libvirt (Ubuntu Trusty)
Importance: Undecided
Status: New
** Changed in: libvirt (Ubuntu
901 - 922 of 922 matches
Mail list logo