similar to: Upgrading to Centos 4.7 on HP DL580G5 caused problems

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

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

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

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

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

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

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

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

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

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

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, 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, I had snv_111b running for a while on a HP DL160G5. With two 16GB USB sticks comprising the mirrored rpool for boot. And four 1TB drives comprising another pool, pool1, for data. So that''s been working just fine for a few months. Yesterday I get it into my mind to upgrade the OS to latest, then was snv_127. That worked, and all was well. Also did an upgrade to the

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

I am trying to compile lustre-1.6.6 against ofed-1.4 using following configure options : ./configure --disable-server --with-o2ib=/usr/src/ofa_kernel-1.4 --with-linux=/usr/src/kernels/2.6.18-92.el5-x86_64 I am getting following errors: configure: error: can''t compile with OpenIB gen2 headers under /usr/src/ofa_kernel-1.4 Is it that lustre-1.6.6 will only work with ofed-1.3. or I am

I have to say the CentOS machines I have used so far seem to work well, so I was surprised the other day when an HP DL580G5 I had running CentOS 6.4 x86_64 the other day for some VM's under KVM/QEMU went belly up. Sadly the sucker was a remote box, so I wasn't just sitting in front of the console, but it looks like it left some files in /var/spool/abrt/oops-2013-11-01-14:00:22-8047-1 on

Recently I started getting weird errors. All of a sudden I see the harddrive of my box glowing steadily and syslog is getting filled (and the cpu hogged) with these errors: It seems to start with this line: Jan 1 03:28:04 kernel: FXO PCI Master abort Jan 1 03:28:04 last message repeated 12 times Jan 1 03:28:06 kernel: CI Master abort Jan 1 03:28:06 kernel: FXO PCI Master abort and seems to

So, I just got back from Europe and is feeling all dazed and confused. Where really are we at with the early userspace development? -hpa

I am storing a shape object in a session, and somewhere I picked up that to make sure I can restore the full glory of Shape, I needed this line in ApplicationController model :Shape So, of course, I also have a file /app/models/shape.rb All was working well, but then I decided I''d rather name the model MyShape. So, I - edited the filename to "my_shape.rb" - edited