Looking further it seems that the root cause is that the CIRRUS driver
cannot be used in 12.04.3 because of this
[ 579.647] (EE) cirrus: The PCI device 0xb8 at 00@00:02:0 has a kernel module
claiming it.
[ 579.647] (EE) cirrus: This driver cannot operate until it has been unloaded.
It seems
Are you sure that the problem is between libcairo 1.12.2 and 1.12.4? I
recechecked with Ubuntu 12.04.3 LTS 64bit Desktop CDROM with is based on
libcario 1.10.2 and it also shows this bug.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
And has anyone tested this with a real Cirrus Logic graphic card? I
still wonder if this is an emulation bug in qemu or a driver problem.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1080674
Title:
Fix in vanilla kernel is released.
http://www.kernel.org/pub/linux/kernel/v3.0/ChangeLog-3.2.24
** Changed in: linux (Ubuntu)
Status: Confirmed = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
The patch is still not in 3.2-stable (but in 3.0-stable). I asked the
3.2 mainline kernel maintainer to add it. Can it be cherry picked for
inclusion in precise-updates meanwhile?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
just got info from ben hutchings that the patch went into 3.2.24-rc1
http://git.kernel.org/?p=linux/kernel/git/bwh/linux-3.2.y-queue.git;a=commit;h=d0551d1a37f8431e33d76573aa92998847614633
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Is this in precise in the meantime?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/985516
Title:
vhost: don't forget to schedule()
To manage notifications about this bug go to:
Public bug reported:
Please consider the above patch from linux 3.4-rc1 to be included in
oneiric and precise kernels. Otherwise the CPU executing a vhost thread
will get stuck under heavy load.
** Affects: linux-meta (Ubuntu)
Importance: Undecided
Status: New
--
You received
This bug is already confirm and a patch has been submitted to upstream
kernel.
** Changed in: linux (Ubuntu)
Status: Incomplete = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/985516
Its in:
http://www.kernel.org/pub/linux/kernel/v3.x/testing/patch-3.4-rc1.bz2
diff --git a/drivers/vhost/vhost.c b/drivers/vhost/vhost.c
index c14c42b95ab8..947f00d8e091 100644
--- a/drivers/vhost/vhost.c
+++ b/drivers/vhost/vhost.c
@@ -222,6 +222,8 @@ static int vhost_worker(void *data)
Sorry, I might have misunderstood your question I think. It has not yet
appeared in 3.2.x which is the long term kernel afaik.
However, I can confirm that in the latest 3.2.x kernel from kernel.org the
patch is not present.
I have encountered this bug when experimenting with vhost-net on the
** Changed in: linux (Ubuntu)
Status: Incomplete = Confirmed
** Tags removed: kernel-request-3.2.0-23.36
** Tags added: bot-stop-nagging
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/985516
I have not tested with NFS, but my newsserver test was also reliably
crashing without the NAPI patch.
I have seen Bruce's response. Will he take care of this patch going
upstream?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
just for the records. i have a binary newsfeed testserver with the napi patch
running stable for 52 days. it really seems that this
was the missing piece! more than 66TB data transferred.
root@ubuntu-newsfeed:~# uptime
13:00:49 up 52 days, 14:47, 2 users, load average: 2.32, 2.61, 2.69
I tested with kernels that include both of these patches, but they still
crashed.
I also think that the both patches you mentioned have been backported to Ubuntu
LTS.
How should we proceed? Contact the virtio developers and the developers from
Suse
why this patch never went upstream?
--
You
Can you patch the natty kernel with the napi patch to be absolutely
sure?
You might also use netcat to transfer files between your boxes or use
iperf. This might reduce the time to crash.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
It seems that virtio_net: Add schedule check to napi_enable call is the final
solution to the virtio_net crashes.
I have a newsserver (constantly 300-500mbit throughput) running a modified
kernel with this patch for almost one month
now.
Who can help getting this patch into ubuntu-lucid
It took about 5 days this time to crash an unpatches Ubuntu LTS 10.04.1 64-bit
server. I will now try my home built kernel with the virtio_net: Add schedule
check to napi_enable call patch included.
If this patch is the final solution can someone help with:
- getting this patch in the vanilla
This is weird. I remember when I last experiment with a vanilla 2.6.34
some time ago, it still crashed under heavy load. 2.6.34 should have all
the patches mentioned applied except for the yet unpublished napi fix
from SuSe.
I'm currently rebuilding my test setup (binary news spool server) and
Sergey, thank you very much for the summary. From what I can see all
patches made it to the stable kernel since 2.6.34, but not the third
patch virtio_net: Add schedule check to napi_enable call. Am I right
with that? That might be a reason why I still see the issue with recent
kernels (2.6.34+).
I can confirm this bug in Ubuntu Lucis LTS 10.04.1 64-bit Server.
This bug seems not to exists in an older kernel from opensuse 11.1 which I use
with heavy network i/o load.
Version is: Linux 2.6.27.48-0.2-default
So the bug seems to have been added somewhere in between.
--
Lost network in
21 matches
Mail list logo
