similar to: NMI received for unknown reason

Hi, I''m using xen 3.3.1 with kernel 2.6.18-8-xen x86_64 compiled with pcibackend support and VT-d activated on a HP dc7900 (Q45 chipset). I''m trying to use a pci acquisition card (NI-6221) in a windows XP HVM. Device is recognized under XP and look functionnal until I try to use it. If I try to acquire data or generate a signal (with National Instrument official tools) nothing

I have read thru what other users have tried in this list when they have experienced seemingly similar issues to what I have, without success. I suspect there might be an issue regarding both the X100P and TDM04b cards being used in an Intel SE7525GP2 motherboard, as I had to even wait for a BIOS update from Intel in order to utilize my 3ware 9500 SATA raid controller on it (3ware Kb -->

As part of patching a cluster which has two DL580G5 login nodes ( 4X Intel 7300 DC cpus) & 24 HP DL160G5 compute nodes ( 2x Intel 5272 DC cpus) we encountered an issue that I would like to record: I upgraded both DL580s to Centos 4.7 via yum but only rebooted one initially- this node, previously bomb-proof, started to hang randomly with no obvious messages logged to help with diagnosis.

Hi All I'm having some serious kernel panic while using digium cards. It may be related to IRQ shared. Can this cause a lot of drop call and bad voice quality ? Do you guys know if there is a way I can assign one IRQ for each digium card ? Thanks a lot. Here is the output of /var/log/syslog kernel: [ 3821.982893] Uhhuh. NMI received for unknown reason 20. kernel: [

Nov 12 08:54:27 steerpike kernel: Uhhuh. NMI received for unknown reason a0 on CPU 0. Nov 12 08:54:27 steerpike kernel: You have some hardware problem, likely on the PCI bus. Nov 12 08:54:27 steerpike kernel: Dazed and confused, but trying to continue Would my Digium TDM410P cause an NMI, or is my computer failing? - Mike

Hi, Has anyone in the list tried Xen on Quad-Core Xeon E5300 series with Intel 5000X chipset? Thanks. Regards, Konstantin Skaburskas _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users

Hi all, I have a PowerEdge 1950 that was acting weird. Network connectivity was only performing at a quarter of what was expected (if that). Even if I scp'd something to localhost it would perform poorly. Rather than fight with it, I just decided to reload it. It was running 5.3, and it is now running 5.4. However, when I go to boot it gets stuck at starting udev. If I let it sit

> -----Original Message----- > From: Christopher [mailto:chris.robinson@voipsupply.com] > I see that there is a lot of discussion on the web about a > common error > after installing and modprobe'ing the zaptel driver. However I don't > see any resolution, anyone found a solution? > > Here's the output I get after modprobe: > > Uhhuh. NMI received.

Dear Zaptel and wcfxo devellopers, Hi, so far I have had no success moving this issue forward. Carl Andersson has been kind enough to help build various kernels to try, but with no success. So, I have tried to debug the problem directly. So far I have applied the patch below to wcfxo.c. (on the latest CVS head) This makes my system stable again (in that I dont have to keep pressing the big

http://bugs.freedesktop.org/show_bug.cgi?id=14391 Summary: nouveau lockup on NV44 / x86_64 Product: xorg Version: git Platform: Other OS/Version: All Status: NEW Severity: normal Priority: medium Component: Driver/nouveau AssignedTo: nouveau at lists.freedesktop.org ReportedBy: wwoods at

Hello everybody, After going through multiple posts on Internet and trying different things I can't seems get zaptel wcfxo loaded on the server correctly. I run dual P3 500 Mhz box. After reading README.udev I put a file 60-zaptel.rules /etc/udev/rules.d # Section for zaptel device KERNEL="zapctl", NAME="zap/ctl" KERNEL="zaptimer",

Hi all, I've struggled for several days trying to get a Digium TDM04B 4-port wxfco card working on a Dell 1U PowerEdge 750 machine running Fedora Core 1. I finally got a call back from Digium who indicated that there is a fundamental conflict between the card and the PowerEdge having to do with PCI interrupts. Asterisk version is stable v1-0 12/29/04. The symptoms of the problem were as

I have just noticed this message in my kernel logs, reporting the possibility of an error with my memory. This would go a long way towards explaining the problems i''ve been having. This particular error is occuring when i''m not running xen so is obviously not something brought on by xen itself. The strange thing is that the NMI error is always followed by the TLAN: eth0: Adaptor

Hi, I am struggling to get rid of a conflict on DELL 2800 : PCI Parity error (EB113 on the display) I am learning linux and asterisk as I go along, there might be obvious things I should know, but bear with me. >From demsg below my 2 digium cards installed are listed (no config or connections done to digium cards yet), the conflict is with the TDM400P card, without that card, in any slot, no

xen/arch/x86/crash.c | 116 ++++++++++++++++++++++++++++++++++----- xen/arch/x86/machine_kexec.c | 19 ++++++ xen/arch/x86/x86_64/entry.S | 34 +++++++++++ xen/include/asm-x86/desc.h | 45 +++++++++++++++ xen/include/asm-x86/processor.h | 4 + 5 files changed, 203 insertions(+), 15 deletions(-) Experimentally, certain crash kernels will triple fault very early

OK, I need to do something like this to io_apic.c - split the hardware specific parts out under mach-default, so we can override them for other subarchitectures. It's not finished, needs header file and makefile work. Would you be willing to take this if I do it? I'm not going to bother if you're not, such refactorings are a pig to maintain out of tree. Frankly, io_apic.c needs a

OK, I need to do something like this to io_apic.c - split the hardware specific parts out under mach-default, so we can override them for other subarchitectures. It's not finished, needs header file and makefile work. Would you be willing to take this if I do it? I'm not going to bother if you're not, such refactorings are a pig to maintain out of tree. Frankly, io_apic.c needs a

Hey all, Just wanting to add my 2 cents here. I have a X/OS 4 Dev box running on a P3 550 and 512MB. Started getting this error when I upgraded the kernel to 2.6.9-42.0.10.EL.XOS. added the nmi_watchdog=0 to the grub boot line and all is fine now. A strange side effect seems to be the system load has dropped by 0.5 - 1.0 since the change. may only be noticable on my box because of the older arch

https://bugs.freedesktop.org/show_bug.cgi?id=42672 Bug #: 42672 Summary: NMI SERR with 2 Geforce 310 cards Classification: Unclassified Product: xorg Version: 7.7 (2011) Platform: x86-64 (AMD64) OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium Component: Driver/nouveau

Isolate some of the non-VMI timer related changes in Linux. This patch moves the cyc_2_ns conversion code into a common location, eliminating redundant code in hpet and tsc timer implementations, and introduces some macros that may be redefined by the sub-architecture to avoid dependence on APIC routing, CMOS time sync, and testing for broken time hardware (which presumably, does not happen in a