similar to: re ceiving NMI while using a PCI card.

G'day, I am testing a new server with a Supermicro X7SBA motherboard and TE405 cards. When I load Dahdi and run dahdi_cfg I get the following errors: kernel: Uhhuh, NMI received for unknown reason b1 on CPU 0 You probably have a hardware problem with your RAM chips Dazed and confused, but trying to continue The reason codes I have seen are a0, a1, and

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.

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 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: [

Hi, With the pcibackend feature of Xen 3.0.2, I pass a S-ATA card to a domU. This card is recognized with the sata_uli module but not the disk. # lspci 0000:02:09.0 Mass storage controller: ALi Corporation ALi M5281 Serial ATA / RAID Host Controller (rev a1) # modprobe sata_uli sata_uli 0000:02:09.0: version 0.5 ata3: SATA max UDMA/133 cmd 0xC800 ctl 0xC402 bmdma 0xB400 irq 16 ata4: SATA max

Hi Folks: I am oot able to add HP Intel 4Port PCIe to a linux hvm domain. HW is a HP DC7900. ErrorMessage: VmError: pci: to avoid potential security issue, 0000:22:00.0 is not allowed to be assigned to guest since it is behind PCIe switch that does not support or enable ACS. I also added in /etc/xen/xend-config.sxp: pci-passthrough-strict-check no pci-dev-assign-strict-check no but no

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

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

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",

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

Hello, Similar to others I have freezeups on the system, it is consistent with high IO load. If the system runs (even with multiple) XenU it does not happen. But I can consistently force the situation to occur. Running 4 dd processes dumping 20GB each on a LVM/mdadm soft RAID5 volume it consistenly crashes in a DomU. Running without XEN I do not see the problem at all - (e.g. after about 3TB of

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

Hi, I am having some problems mentioned below, the box is in production live environment with traffic around 30 - 100 calls. I am running T/E410P in a Dual P4 xeon with HT disabled. I am using zaptel 0.9.0 and asterisk stable 1 release. There is no gui, just mysql, perl (small script) and asterisk. System runs very smoothly if the calls are around 40-50 and comes one by one , however sometimes

The old CPU_CLK_UNHALTED performance counter no longer runs on Core or Core2 CPUs. Use the new CPU_CLK_UNHALTED.CORE_P one. Signed-off-by: Tim Deegan <Tim.Deegan@citrix.com> _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

On Tue, Feb 11, 2020 at 5:53 AM Joerg Roedel <joro at 8bytes.org> wrote: > > From: Joerg Roedel <jroedel at suse.de> > > Keep NMI state in SEV-ES code so the kernel can re-enable NMIs for the > vCPU when it reaches IRET. This patch is overcomplicated IMO. Just do the magic incantation in C from do_nmi or from here: /* * For ease of testing, unmask