similar to: Unable to locate IOAPIC for GSI 2

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

Hi, Normally I?m using webmin to manage my firewall. Webmin fw however breaks the iptable rules invoked by libvirt. Is there a fw tool (beside iptables console command) which can be used without breaking libvirts? rules? -Hansa -------------- next part -------------- An HTML attachment was scrubbed... URL:

Hi Russell, Was there an underlying issue here (e.g. failure to boot or crash?) or were you just concerned by the messages? Are you able to test if this still happens with the 4.1 based hypervisor in Wheezy? Ian.

Package: xen-hypervisor-4.0-i386 Version: 4.0.0-2

I setup a CentOS 6 server to use with KVM/QEMU, and I am getting the following error a good bit, granted it doesn't seem to be causing any trouble. I figured I would post and see if anyone has any ideas on the issue, or if I can just dismiss it. If I look at my logging/dmesg, I see: do_IRQ: 19.217 No irq handler for vector (irq -1) do_IRQ: 3.178 No irq handler for vector (irq -1) do_IRQ:

hi,everybody There is a function do_IRQ() in file xen/arch/x86/irq.c, but where does do_IRQ() be called please? Thanks! _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

I attempted an upgrade of our production system from Asterisk/Zaptel 1.2 to 1.4 this weekend. Intially everything looked like it was working properly, but some time in the day following the upgrade, the system died to a kernel panic. I wasn't able to catch the entire kernel dump on the console unfortunately. I attempted to isolate the panic, and found that when 'service zaptel stop'

I hope this EIP can enlightend the developers: Jun 10 10:28:59 shawarma kernel: Unable to handle kernel NULL pointer dereference at virtual address 00000019 Jun 10 10:28:59 shawarma kernel: printing eip: Jun 10 10:28:59 shawarma kernel: c0181d47 Jun 10 10:28:59 shawarma kernel: *pde = 00000000 Jun 10 10:28:59 shawarma kernel: Oops: 0000 [#1] Jun 10 10:28:59 shawarma kernel: Modules linked in:

Hi all, my name is Hirofumi Tsujimura. We are porting and testing a PV-on-HVM in the IPF. This is a first time to send mail. I probably found the problem when I tested the VNIF. My operation for the test is following. 1. create a domain VTx and attach the VNIF in it. 2. create a domain U. 3. send a packet to the domain VTx from the domain U with ping command. Then, the domain VTx

When I came into work this morning the console had the following: bio_endio __end_that_request_first scsi_end_request scsi_io_completion scsi_finish_command scsi_softirq __do_softirq do_softirg do_irq command_interrupt default_idle cpu_idle start_kernel Panic I am running software RAID-1 on this machine. I had 2 IDE disks and the machine when down once in a while with similiar messages. I

Below is a kernel dump that I just got. This is a fresh new install of centos 5.1 on NVIDIA gigabyte MB-GA-M61P-S3. nothing extra has been added. I have not tried the irqpoll but I am surprised to get this. Also the machine keeps running just hod this show on the console... Any ideas??? Jerry Jan 8 05:20:00 localhost kernel: irq 169: nobody cared (try booting with the "irqpoll"

In-Reply-To: <20060509085157.070289000@sous-sol.org> On Tue, 09 May 2006 00:00:23 -0700, Chris Wright wrote: > Remove the limit of 256 interrupt vectors by changing the value > stored in orig_{e,r}ax to be the negated interrupt vector. > The orig_{e,r}ax needs to be < 0 to allow the signal code to > distinguish between return from interrupt and return from syscall. >

In-Reply-To: <20060509085157.070289000@sous-sol.org> On Tue, 09 May 2006 00:00:23 -0700, Chris Wright wrote: > Remove the limit of 256 interrupt vectors by changing the value > stored in orig_{e,r}ax to be the negated interrupt vector. > The orig_{e,r}ax needs to be < 0 to allow the signal code to > distinguish between return from interrupt and return from syscall. >

Hi all did anyone of you experience an error like "do_irq: stack overflow" in configuring a TE212P on Fedora core 6? The server immediately hangs, I don't know if this can be related to hardware configuration or kernel incompatibility... This problem arises when I try to configure the channels with the usual command "ztcfg" and it is strictly related to the presence of the

I''ve had domU''s hickup a few times with latest unstable, and I guess this can be expected. Is there a procedure in place to report these problems? For exampe: Unable to handle kernel paging request at virtual address c12b46c0 printing eip: cpanel cpanel.mydomain c02555f7 *pde = ma 7e9fc067 pa 00002067 *pte = ma 00000000 pa 55555000 Oops: 0002 [#1] PREEMPT SMP Modules

Hi, folks, I think it's just been since we did the latest upgrade and rebooted the other day that I've started seeing the error described in the bug - console spitting out "kernel: do_IRQ: 8.65 No irq handler for vector (irq -1)" occasionally - with the current std. kernel: 2.6.32-358.14.1.el6.x86_64 #1 SMP Tue Jul 16 23:51:20 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux Is

Greetings, I''ve been experiencing problems with HTB where the whole machine locks up. This usually happens when the whole qdisc is being removed and occasionally when a leaf is being removed. Common is that it always happens when some sort of removal is in progress. Console output I have captured is at the end of this message. The same behavior exists from vanilla 2.6.19.7 and above.

Hi, I used to experience kernel panics caused by CPUx hard lockup once almost everyday. I'm running Ubuntu 14.10 on vanilla linux kernel 3.19.2 on Core i7-3770 with Gallium 0.4 on NV108. The panic log looked like: [ 9227.509744] ------------[ cut here ]------------ [ 9227.509750] WARNING: CPU: 0 PID: 0 at kernel/watchdog.c:290 watchdog_overflow_callback+0x92/0xc0() [ 9227.509751] Watchdog

I have a couple of 64-Bit Xeon's with CentOS 4.2 x86_64 installed on them. They don't all have the same motherboards. I've having a difficult time getting CentOS 4.2 x86_64 to boot on some of them in SMP mode (UP works fine). After the installation of CD, it boots up but kernel panics with the following error: Badness in i8042_panic_blink at drivers/input/serio/i8042.c:992 This is