search for: 573210

Displaying 5 results from an estimated 5 matches for "573210".

Did you mean: 573,10
2010 Mar 14
0
Processed (with 1 errors): My bugreport is duplicate, sorry
Processing commands for control at bugs.debian.org: > reassign 573210 linux-image-2.6.26-xen-amd64 Bug #573210 [xen-hypervisor-3.2-1-amd64] xen-hypervisor-3.2-1-amd64: Xen domU sometimes hogs CPU and doesn't respond Bug reassigned from package 'xen-hypervisor-3.2-1-amd64' to 'linux-image-2.6.26-xen-amd64'. Warning: Unknown package 'linux-image...
2010 Mar 12
0
Bug#573210: tracedumps from vcpus when domU crashed
Hi, today I had catched one domU crash and taken tracedumps from xen vcpus, see attachment. Hope it could help. Today I've got some problems with clocksource so I've upgraded to last 2.6.26-xen-amd64 kernel from security so I'll confirm if problem occurs there or not in some days. -- Ond?ej Kunc ---------------------------------------------------------------------- spr?vce
2010 Mar 12
0
Bug#573210: Latest kernel vulnerable too
Hi, Now I must confirm that bug is present in latest kernel from security updates. One domU locked about one minute after start. -- Ond?ej Kunc spr?vce serverov? farmy CZOL media interactive s.r.o. S?dlo: Moul?kova 2238/1, Praha 5, 15000 Kancel??e: Na Mor?ni 5357, Chomutov, 43001 Telefon: +420 723 137 981 E-mail: ondra at czol.eu URL: www.czol.eu, www.cz-hosting.com
2010 Mar 14
0
Bug#573210: Workaround: Using 2.6.18 leads to whole server crash
Hi, this night one domU crashed, so I managed to try workaround from Pasi to use kernel from etch ... but I need 2.6.26 in dom0 (drivers for sata controller) and so that I changed kernel only for domUs to 2.6.18-6-amd64. With this configuration server crashed after ten minutes. It was totally frozen so I had to restore previous state, but now I don't know what to do now. It's
2010 Mar 09
1
Bug#573210: xen-hypervisor-3.2-1-amd64: Xen domU sometimes hogs CPU and doesn't respond
Package: xen-hypervisor-3.2-1-amd64 Version: 3.2.1-2 Severity: normal *** Please type your report below this line *** Hi, Recently I've experienced some crashes of Xen domU (also debian Lenny, running same kernel as dom0 (linux-image-2.6.26-xen-amd64)). At xm top that domain appears as running, but hogs all CPUs, because this problem has appeared on two identic servers (Supermicro X7SBi,