similar to: how to debug random server reboots

Displaying 20 results from an estimated 8000 matches similar to: "how to debug random server reboots"

2008 Nov 15
3
how to debug hardware lockups?
Hi, We have a server which locks up about once a week (for the past 3 weeks now), without any warning, and the only way to recover it, is to reset the server. This causes unwanted downtime, and often software loss as well. How do I debug the server, which runs CentOS 5.2 to see why it locks up? The CPU is an Intel Q9300 Core 2 Quad, with 8 GB RAM, on an Intel Motherboard The last few entries
2011 Jan 19
1
[BUG] Problem Booting Xen 4.0.1 on 2.6.32.26/27
Hello, I''m attempting to boot Xen 4.0.1 on a SuperMicro H8DGi-F motherboard and having not much luck. I can boot the 2.6.32.26 (or .27) kernels alone, but when I add Xen into the mix, I get consistent boot failure. I''ve tried Xen 4.0.1-release, 4.0.2-rc1-pre and 4.0.2-rc2-pre, all get the same failure. xen/next-2.6.37 works and boots great, but since netback isn''t
2014 May 15
0
Bug#748052: Info received ( Bug#748052: Bug#748052: Bug#7480
Not sure I did the xen log correctly. I have this in /etc/default/grub now: GRUB_CMDLINE_XEN_DEFAULT="loglvl=all" And now here is xen dmesg: root at xen-3:~# xl dmesg (XEN) Xen version 4.3.0 (Debian 4.3.0-3+b1) (buildd-binet at buildd.debian.org) (gcc (Debian 4.8.2-8) 4.8.2) debug=n Wed Dec 4 07:43:54 UTC 2013 (XEN) Bootloader: GRUB 2.00-22 (XEN) Command line: placeholder
2009 Sep 30
3
Gathering information about RAM in sockets
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi list, I have an IBM xseries 345, running CentOS 5.3, hosting a few Xen domUs. However, I need more RAM -- but cannot remember if all (four) RAM sockets are populated (which would mean to buy higher capacity modules) or if there are two slots left to use. However, I'd like (and think that it's possible, but don't remember how) to
2011 Feb 11
4
Xen hypervisor failed to startup when booting CPUs
Hi Folks: I run into a problem when enabling Xen in next generation server platforms with Xen c/s is 21380. Xen reported "CPU Not responding" when booting up 32 CPUs( 2 sockets with 8 cores/16threads total). The log files belonging showed something wrong with APCI. So I added x2apic=0 in the xen grub line, but the symptom remained. However, Native RHEL5.5 can
2010 Nov 16
0
Bug#603713: xen-hypervisor-4.0-amd64: amd64 Dom0-Kernel crashes in early boot-stage
Package: xen-hypervisor-4.0-amd64 Version: 4.0.1-1 Severity: important The amd64 Dom0 crashes in early boot-stage. For debugging purpose I logged Kernel-Dump with minicom over Serial Console: System is: Dell Poweredge R710 2x Intel XEON X5650 96GB RAM Perc H200 SAS Controller 3x SAS-Drive I see a possible conjunction with Bug #600241 but acpi=off doesn't solve this problem. Regards,
2012 Jul 27
6
Failure to boot, Debian squeeze with 4.0.1 hypervisor, timer problems?
Hi, I have a system based on a Supermicro X8DTH-i motherboard and a Xeon E5506 CPU. It was previously running Debian lenny with xen-hypervisor-3.2-1-amd64 (3.2.1-2) / linux-image-2.6.26-2-xen-amd64 (2.6.26-29) without incident. I upgraded it to Debian squeeze, with xen-hypervisor-4.0-amd64 (4.0.1-4) / linux-image-2.6.32-5-xen-amd64 (2.6.32-45) and now it does not complete a boot of the dom0
2016 Feb 04
0
c7 xen-4.6 crash.
Installing xen on a fairly clean c7.2 system. I get a xen kernel panic. (XEN) Bad console= option 'tty' Xen 4.6.0-9.el7 (XEN) Xen version 4.6.0-9.el7 (mockbuild at centos.org) (gcc (GCC) 4.8.5 20150623 (Red Hat 4.8.5-4)) debug=n Wed Jan 20 12:25:53 UTC 2016 (XEN) Latest ChangeSet: Thu Jan 14 15:35:35 2016 +0000 git:6e8597a-dirty (XEN) Bootloader: GRUB 2.02~beta2 (XEN) Command line:
2014 May 16
4
Bug#748052: dom0 USB failing with "ehci-pci: probe of 0000:00:1d.0 failed with error -110"
(copying xen-devel, full logs are at bugs.debian.org/748052, this is Debian Jessie, Xen 4.3.0 and Linux 3.13 Mike also reported that Debian Wheezy Xen 4.1.4 didn't work either, not clear which kernel that was with though, Wheezy's 3.2 or Jessie's 3.13) On Thu, 2014-05-15 at 10:11 -0700, Mike Egglestone wrote: > Here are some results with (now) the latest BIOS version 41. (was >
2016 Feb 04
1
c7 xen-4.6 crash.
?I wrote about this a couple months back.? George asked me to submit to the Xen developers list, but I never had the time due to work demands on getting the new server set up.? In my case, I had to use a different server.? The new motherboard/CPU had no issues with the second CPU.? If you turn off and unplug the second CPU, it will work. Check the archives for my e-mail address and see
2006 Nov 18
1
Xen 3.0.3 with CentOS 4.4
I''ve installed Xen kernel for dom0 on a CentOS 4.4 but when i reboot the kernel says: _/\_\___|_| |_| |____(_)___(_)____(_)___/ http://www.cl.cam.ac.uk/netos/xenmdev = 59.12 University of Cambridge Computer Laboratory6 Sep 26 01:52 qemu-dm.6463.log Xen version 3.0.3.0 (root@uk.xensource.com) (gcc version 3.4.6 20060404 (Red Hastart qemu- -rw-r--r-- 1 root root t 3.4.6-3)) Mon Oct
2011 Feb 22
6
how to optimize CentOS XEN dom0?
Hi, I have a problematic CentOS XEN server and hope someone could point me in the right direction to optimize it a bit. The server runs on a Core2Quad 9300, with 8GB RAM (max motherboard can take, 1U chassis) on an Intel motherboard with a 1TB SATA HDD. dom0 is set to 512MB limit with a few small XEM VM''s running: root@zaxen01:[~]$ xm list Name ID
2007 Sep 10
3
Bug#441539: xen-hypervisor-3.0.3-1-amd64: Xen failing to boot with FATAL TRAP error
Package: xen-hypervisor-3.0.3-1-amd64 Version: 3.0.3-0-2 Severity: important about every 1 in 10 boots I am getting the following error: (XEN) ************************************ (XEN) CPU0 FATAL TRAP 6 (invalid opcode), ERROR_CODE 0000, IN INTERRUPT CONTEXT. (XEN) System shutting down -- need manual reset. (XEN) ************************************ This seems to happen in the CPU detection
2013 Mar 12
0
Bug#702892: xen-hypervisor-4.0-i386: Early fatal page fault during Xen boot
Package: xen-hypervisor-4.0-i386 Version: 4.0.1-5.8 Severity: normal Tags: upstream *** Please type your report below this line *** -- System Information: Debian Release: 6.0.7 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: i386 (i686) Kernel: Linux 2.6.32-5-xen-686 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8,
2013 Jun 19
4
e008:[<ffff82c480122353>] check_lock+0x1b/0x45 [konrad.wilk@oracle.com: FAILURE 3.10.0-rc6upstream-00061-g752bf7d(x86_64) 3.10.0-rc6upstream-00061-g752bf7d(i386): 2013-06-19 (tst007)]
Hey, It looks like one of the patches that went in Xen 4.1 blows up. This used to work over the weekend, so I can only surmise it is one the three patches. This is with a debug=y build (which has been working nicely for the last month or more). It looks like one of the patches that went in Xen 4.1 blows up. This used to work a day ago - that is c/s 23551 worked nicely. ----- Forwarded message
2013 Feb 20
8
crash in nvmx_vcpu_destroy
while doing "while xm migrate --live domU localhost;do sleep 1;done" I just got the crash shown below. And it can be reproduced. The guest has 2 vcpus and 512mb, it runs pvops 3.7.9 (XEN) ----[ Xen-4.3.26579-20130219.172714 x86_64 debug=n Not tainted ]---- (XEN) CPU: 14 (XEN) RIP: e008:[<ffff82c4c01dd197>] nvmx_vcpu_destroy+0xb7/0x150 (XEN) RFLAGS: 0000000000010282
2011 Nov 03
2
xen-unstable fails to boot on a system with Ivy Bridge stepping C0 cpu
Hi, I need a help with tracking down following issue: When trying to boot Xen on a system with Ivy Bridge stepping C0 CPU, it is stuck on CPU initialization. I''ve added some tracing to apic writes/reads and traced it so far to sending INIT IPI. (XEN) HVM: VMX enabled (XEN) HVM: Hardware Assisted Paging detected. (XEN) Setting warm reset code and vector. (XEN) apic_wrmsr (0x280,0x0)
2015 Dec 08
1
new install of Xen 4.6 hangs on Loading initial ramdisk
?Not sure if this actually made it to the list the first time.? Here is the SERIAL output (bottom of message after your questions).? Googling the error indicates it's something people ran into a few years back but was supposedly fixed.? Any ideas? I can verify that if I REMOVE the second CPU, it boots into Xen kernel no problem.? The CPU itself doesn't matter, as I can swap either
2006 Nov 24
0
Error: (12, ''Cannot allocate memory'')
Not sure if this is a Fedora Core 6 issue. I already post a message on their list but didn''t get an answer. So I am going to try here.. Does anyone has Windows Guest OS running successfully with the Dom0 has all the physical memory allocated? If I don''t lower the memory assign to Dom0 through grub, I will not be able to run a Windows Guest OS. This what I got Using
2010 Jan 26
1
Bug#567025: xen-hypervisor-3.4-amd64: unhandled page fault while initializing dom0
Package: xen-hypervisor-3.4-amd64 Version: 3.4.2-2 Severity: critical Justification: breaks the whole system -- Dump: (XEN) Xen version 3.4 (Debian 3.4.2-29 (XEN) Command line: com1=115200,8n1 console=com1,vga loglvl=all guest_loglvl=all noreboot (XEN) Video information: (XEN) VGA is text mode 80x25, font 8x16 (XEN) VBE/DDC methods: none; EDID transfer time: 1 seconds (XEN) EDID info not