search for: do_irq

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: 19.179 No irq handler for vector (irq -1) do_IRQ: 3.220 No irq handler for vector (irq -1) do_IRQ: 18.213 No irq handler for vector (irq -1) do_IRQ: 18.79 No irq handler for vector (irq -1) do_IRQ: 3...

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

...12 processors activated. (XEN) ENABLING IO-APIC IRQs (XEN) -> Using new ACK method (XEN) TSC is reliable, synchronization unnecessary (XEN) Platform timer appears to have unexpectedly wrapped 10 or more times. (XEN) Platform timer is 14.318MHz HPET (XEN) Allocated console ring of 32 KiB. (XEN) do_IRQ: 1.231 No irq handler for vector (irq -1) (XEN) Brought up 12 CPUs (XEN) do_IRQ: 2.231 No irq handler for vector (irq -1) (XEN) do_IRQ: 4.231 No irq handler for vector (irq -1) (XEN) do_IRQ: 3.231 No irq handler for vector (irq -1) (XEN) ... I''m stuck here and need some help resolving thi...

https://bugs.freedesktop.org/show_bug.cgi?id=30369 Summary: nvidia 8400GS G98 chip GPU lockup - switching to software fbcon Product: xorg Version: 7.5 Platform: x86-64 (AMD64) OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium Component: Driver/nouveau

I asked here a week or so ago, and referenced an older bug, but haven't seen any comments. Googling, I see others asking about the same. Datum: *every* one I've found is like this: they're all HP DL580's or DL380's, or such. This is being used for heavy-duty scientific computing. Does anyone know if it *will* it seriously affect throughput speed if I turn off irqbalance?

...00008 <5> 00000100013ebea8 00000100013ebde8 0000000000000001 00000000000000d1 <5> 0000000000000012 0000010073478680 <5> Call Trace:<IRQ> <ffffffff80138552>{printk+141} <ffffffff80112f4a>{handle_IRQ_event+41} <5> <ffffffff801131c4>{do_IRQ+197} <ffffffff80110833>{ret_from_intr+0} <5> <ffffffff8013c731>{__do_softirq+77} <ffffffff8013c7e5>{do_softirq+49} <5> <ffffffff80110bf5>{apic_timer_interrupt+133} <EOI> <ffffffff8011c21a>{flush_tlb_page+44} <5> <fffffff...

...ault+0xa6/0x100 Jun 10 10:28:59 shawarma kernel: [do_page_fault+263/1181] do_page_fault+0x107/0x49d Jun 10 10:28:59 shawarma kernel: [recalc_task_prio+139/384] recalc_task_prio+0x8b/0x180 Jun 10 10:28:59 shawarma kernel: [schedule+605/1056] schedule+0x25d/0x420 Jun 10 10:28:59 shawarma kernel: [do_IRQ+271/352] do_IRQ+0x10f/0x160 Jun 10 10:28:59 shawarma kernel: [do_page_fault+0/1181] do_page_fault+0x0/0x49d Jun 10 10:28:59 shawarma kernel: [error_code+45/64] error_code+0x2d/0x40 Jun 10 10:28:59 shawarma kernel: Jun 10 10:28:59 shawarma kernel: Code: 8b 00 f6 c4 08 74 06 8b 4a 24 ff 41 04 89 c8...

...ling while atomic [schedule+1682/1696] schedule+0x692/0x6a0 [sys_read+126/128] sys_read+0x7e/0x80 [work_resched+5/47] work_resched+0x5/0x2f scheduling while atomic [schedule+1682/1696] schedule+0x692/0x6a0 [do_softirq+155/160] do_softirq+0x9b/0xa0 [irq_exit+57/64] irq_exit+0x39/0x40 [do_IRQ+34/48] do_IRQ+0x22/0x30 [evtchn_do_upcall+190/320] evtchn_do_upcall+0xbe/0x140 [work_resched+5/47] work_resched+0x5/0x2f scheduling while atomic [schedule+1682/1696] schedule+0x692/0x6a0 [do_softirq+155/160] do_softirq+0x9b/0xa0 [irq_exit+57/64] irq_exit+0x39/0x40 [do_IRQ+34/48] do_IRQ...

...(XEN) ..... host bus clock speed is 200.0096 MHz. (XEN) ..... bus_scale = 0x0000CCD7 (XEN) TSC is reliable, synchronization unnecessary (XEN) Platform timer appears to have unexpectedly wrapped 10 or more times. (XEN) Platform timer is 14.318MHz HPET ÿ(XEN) Allocated console ring of 128 KiB. (XEN) do_IRQ: 1.231 No irq handler for vector (irq -1) (XEN) microcode.c:73:d32767 microcode: CPU1 resumed (XEN) do_IRQ: 2.231 No irq handler for vector (irq -1) (XEN) microcode.c:73:d32767 microcode: CPU2 resumed (XEN) do_IRQ: 3.231 No irq handler for vector (irq -1) (XEN) microcode.c:73:d32767 microcode: CPU3...

...an 8 05:20:00 localhost kernel: Call Trace: Jan 8 05:20:00 localhost kernel: <IRQ> [<ffffffff800b5d77>] __report_bad_irq+0x30/0x7d Jan 8 05:20:00 localhost kernel: [<ffffffff800b5faa>] note_interrupt+0x1e6/0x227 Jan 8 05:20:00 localhost kernel: [<ffffffff800b54bc>] __do_IRQ+0xc7/0x105 Jan 8 05:20:00 localhost kernel: [<ffffffff8006a3bd>] do_IRQ+0xe7/0xf5 Jan 8 05:20:00 localhost kernel: [<ffffffff8005b615>] ret_from_intr+0x0/0xa Jan 8 05:20:00 localhost kernel: [<ffffffff80011cba>] __do_softirq+0x53/0xd5 Jan 8 05:20:00 localhost kernel: [<...

...ECX: 00000286 EDX: da676000 ESI: 000004e2 EDI: 0000000a EBP: c03c7fb8 DS: 007b ES: 007b CR0: 8005003b CR2: b7ee2044 CR3: 1a6af000 CR4: 000006d0 [<c0118f92>] __printk_ratelimit+0x8f/0x95 [<e08a6316>] xennet_get_responses+0xca/0x31c [xen_vnif] [<c0103dc2>] do_IRQ+0x70/0x7a [<e08a6851>] netif_poll+0x1c/0x60v [xen_vnif] [<c0103dc2>] net_rx_action+0x35/0x7d [<c011c47d>] __do_softirq+0x38/0x3f [<c0103e94>] do_softirq+0x38/0x3f ======================= [<c0103dc2>] do_IRQ+0x70/0x7a [<c0102...

...//www.nexusuk.org/pubkey.txt iD8DBQFA/sGl5zUOsIV3bqERAn7xAJ958s7dbVUa4rRAsXfModCS6S4yzgCgiYHN dzfCjiWTmqZFyFg/lwsp/R8= =iSGF -----END PGP SIGNATURE----- -------------- next part -------------- wcfxo: DAA mode is 'FCC' Found a Wildcard FXO: Wildcard X101P No ISA tormenta card found at d0000 do_IRQ: stack overflow: 48 Stack pointer is garbage, not printing trace do_IRQ: stack overflow: 48 Stack pointer is garbage, not printing trace Unable to handle kernel NULL pointer dereference at virtual address 00000069 printing eip: 0213fc86 *pde = 00000000 Oops: 0000 [#1] Modules linked in: wcfxo zapt...

...3_poll+119/356] tg3_poll+0x77/0x164 Dec 8 12:19:26 server kernel: [net_rx_action+164/368] net_rx_action+0xa4/0x170 Dec 8 12:19:27 server kernel: [__do_softirq+116/240] __do_softirq+0x74/0xf0 Dec 8 12:19:27 server kernel: [do_softirq+63/99] do_softirq+0x3f/0x63 Dec 8 12:19:27 server kernel: [do_IRQ+31/37] do_IRQ+0x1f/0x25 Dec 8 12:19:27 server kernel: [evtchn_do_upcall+132/192] evtchn_do_upcall+0x84/0xc0 Dec 8 12:19:27 server kernel: [hypervisor_callback+44/52] hypervisor_callback+0x2c/0x34 Dec 8 12:19:27 server kernel: [xen_idle+97/127] xen_idle+0x61/0x7f Dec 8 12:19:27 server kernel:...

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 switched to brand new 300 GIG SATA drives and now I am seeing the same kernel panic. What might be the pr...

...between return from interrupt and return from syscall. > With this change applied, NR_IRQS can be > 256. > > Xen extends the IRQ numbering space to include room for dynamically > allocated virtual interrupts (in the range 256-511), which requires a > more permissive interface to do_IRQ. > > Signed-off-by: Ian Pratt <ian.pratt@xensource.com> > Signed-off-by: Christian Limpach <Christian.Limpach@cl.cam.ac.uk> > Signed-off-by: Chris Wright <chrisw@sous-sol.org> > --- AFAIC this could go in anytime. It's simple, self-contained and makes sense ev...

...between return from interrupt and return from syscall. > With this change applied, NR_IRQS can be > 256. > > Xen extends the IRQ numbering space to include room for dynamically > allocated virtual interrupts (in the range 256-511), which requires a > more permissive interface to do_IRQ. > > Signed-off-by: Ian Pratt <ian.pratt@xensource.com> > Signed-off-by: Christian Limpach <Christian.Limpach@cl.cam.ac.uk> > Signed-off-by: Chris Wright <chrisw@sous-sol.org> > --- AFAIC this could go in anytime. It's simple, self-contained and makes sense ev...

...: PCI Interrupt 0000:07:0d.0[A] -> GSI > 17 (level, low) -> IRQ 20 > Dec 18 10:47:57 hive kernel: [__report_bad_irq+36/128] __report_bad_irq > +0x24/0x80 > Dec 18 10:47:57 hive kernel: [note_interrupt+162/256] note_interrupt > +0xa2/0x100 > Dec 18 10:47:57 hive kernel: [__do_IRQ+233/256] __do_IRQ+0xe9/0x100 > Dec 18 10:47:57 hive kernel: [do_IRQ+55/112] do_IRQ+0x37/0x70 > Dec 18 10:47:57 hive kernel: [__do_IRQ+179/256] __do_IRQ+0xb3/0x100 > Dec 18 10:47:57 hive kernel: [evtchn_do_upcall+146/256] > evtchn_do_upcall+0x92/0x100 > Dec 18 10:47:57 hive kernel:...

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 st...

...0] __insmod_wd_S.bss_L1376 [wd] 0x20 Mar 6 05:12:31 kanga kernel: [<c8842020>] __insmod_wd_S.bss_L1376 [wd] 0x20 Mar 6 05:12:31 kanga kernel: [do_softirq+83/160] do_softirq [kernel] 0x53 Mar 6 05:12:31 kanga kernel: [<c0119763>] do_softirq [kernel] 0x53 Mar 6 05:12:31 kanga kernel: [do_IRQ+156/176] do_IRQ [kernel] 0x9c Mar 6 05:12:31 kanga kernel: [<c01084cc>] do_IRQ [kernel] 0x9c Mar 6 05:12:31 kanga kernel: [call_do_IRQ+5/17] call_do_IRQ [kernel] 0x5 Mar 6 05:12:31 kanga kernel: [<c0211c54>] call_do_IRQ [kernel] 0x5 Mar 6 05:12:31 kanga kernel: [schedule+622/960] sc...

...] -> GSI > > 17 (level, low) -> IRQ 20 > > Dec 18 10:47:57 hive kernel: [__report_bad_irq+36/128] __report_bad_irq > > +0x24/0x80 > > Dec 18 10:47:57 hive kernel: [note_interrupt+162/256] note_interrupt > > +0xa2/0x100 > > Dec 18 10:47:57 hive kernel: [__do_IRQ+233/256] __do_IRQ+0xe9/0x100 > > Dec 18 10:47:57 hive kernel: [do_IRQ+55/112] do_IRQ+0x37/0x70 > > Dec 18 10:47:57 hive kernel: [__do_IRQ+179/256] __do_IRQ+0xb3/0x100 > > Dec 18 10:47:57 hive kernel: [evtchn_do_upcall+146/256] > > evtchn_do_upcall+0x92/0x100 > > Dec...