thr3ads.net - asterisk users - [Asterisk-Users] NMI issues... [Dec 2004]

If this information is useful, please help other people find it:
Share via:

I put the Who? in Mishehu

2004-Dec-20 23:42 UTC

[Asterisk-Users] NMI issues...

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 -->
http://www.3ware.com/kb/article.aspx?id=12435 ). The following is a list
of the configuration and the issues I have encountered. Any help would be
greatly appreciated.

System A:
Intel SE7525GP2 motherboard. Has BIOS revision 06, BMC 2.40 and FRUSDR
1.40 2x2.8GHz Xeon processors w/800Mhz FSB, actively cooled retail box set
1GB of ECC registered DDR333 RAM, 2 DIMMs
3ware 9500 SATA Raid, controlling a 3-disk raid5 array
550 Watt 24-pin ATX power supply

System B:
Asus A7N8X-E Deluxe
AMD Athlon XP 3200 (barton core)
512 MB RAM
ATI 9600SE OEM card
200GB SATA drive

Process is as follows:
1. On system A until further notice: The Intel SE7525GP2 conflicted with
the firmware on the 3ware 9500 SATA RAID controller until BIOS 06 was
released.
2. After having been flashed, Slackware 10.0 was then installed on it.
It currently runs stock kernel 2.6.9, udev 042, and the most recent
hotplug from 2004-09-23.
3. Installed a digium-supplied X101P into the machine into a 32bit PCI
slot. 4. Downloaded zaptel 1.0.3, compiled against kernel 2.6.9. Upon
modprobe wcfxo, NMI's are immediately reported (syslog to follow). The
instructions from README.udev were followed and parameters inserted into
the rules file for udev. Problem occurs regardless of whether or not
hotplug inserts the modules or the are manually inserted by me. Repeated
modprobe -r wcfxo; modprobe wcfxo produces no different result as well. 5.
Attempted all combinations of moving the card to other compatible slots,
CVS zaptel from 2004-12-17, and the TDM04b card. Snippet of syslog as
follows:

Dec 19 15:33:17 nisui kernel: Freshmaker version: 71
Dec 19 15:33:17 nisui kernel: Freshmaker passed register test
Dec 19 15:33:18 nisui kernel: Module 0: Installed -- AUTO FXO (FCC mode)
Dec 19 15:33:18 nisui kernel: Uhhuh. NMI received for unknown reason 31 on
CPU 0.
Dec 19 15:33:18 nisui kernel: Dazed and confused, but trying to continue
Dec 19 15:33:18 nisui kernel: Do you have a strange power saving mode
enabled?
Dec 19 15:33:18 nisui kernel: Module 1: Installed -- AUTO FXO (FCC mode)
Dec 19 15:33:18 nisui kernel: Module 2: Installed -- AUTO FXO (FCC mode)
Dec 19 15:33:19 nisui kernel: Module 3: Installed -- AUTO FXO (FCC mode)
Dec 19 15:33:19 nisui kernel: Found a Wildcard TDM: Wildcard TDM400P REV
E/F (4 modules)
Dec 19 15:33:19 nisui kernel: Uhhuh. NMI received for unknown reason 31 on
CPU 0.
Dec 19 15:33:19 nisui kernel: Dazed and confused, but trying to continue
Dec 19 15:33:19 nisui kernel: Do you have a strange power saving mode
enabled?
Dec 19 15:33:19 nisui kernel: Uhhuh. NMI received for unknown reason 21 on
CPU 0.

The NMI's will continue to report reasons 21 & 31 until the module is
removed from the kernel.

6. Attempted several kernel reconfigurations, including ones that
stripped out USB support and all SMP support. Even on this machine with a
uniprocessor kernel, NMI was still generated.
7. Took the X100P and installed it in System B. System B only reports:
Notice: Configuration file is /etc/zaptel.conf
line 143: Unable to open master device '/dev/zap/ctl'
Whenever I check, /dev/zap/ctl does exist. No NMI is generated on this
machine, though I do not know if it is capible of doing so. Otherwise, it
appears to operate normally.
8. Tried asterisklivecd that is maintained by somebody in Italy.
Actually got a freshmaker error on that trial, though it appeared to be
somewhat outdated.

Just to anticipate questions, whenever the TDM04b was tested, the power
connector was in fact connected. An Intel Etherexpress Pro 100 ethernet
card was tested on Machine A to verify that there was no problem with the
slots. The eepro100 initializes and operates perfectly. Attached to this
email is a copy of the kernel's configuration, and a list of currently
loaded modules is as follows:

Module Size Used by
md5 4992 1
ipv6 260352 16
hw_random 6548 0
pciehp 97540 0
shpchp 101124 0
pci_hotplug 13060 2 pciehp,shpchp
e1000 86788 0
evdev 10368 0

And output from /proc/interrupts immediately after loading the wctdm module:
CPU0 CPU1 CPU2 CPU3
0: 3791068 10 10 10 IO-APIC-edge timer 1:
7 1 0 0 IO-APIC-edge i8042 9:
0 0 0 0 IO-APIC-level acpi
12: 57 0 0 1 IO-APIC-edge i8042 14:
0 1 0 0 IO-APIC-edge ide0 169:
4222 0 1 0 IO-APIC-level eth0 185:
0 0 0 0 IO-APIC-level ehci_hcd 209:
22767 0 1 0 IO-APIC-level 3w-9xxx 217:
1063 0 0 1 IO-APIC-level wctdm NMI:
63 0 0 0
LOC: 3791179 3791182 3791180 3791179
ERR: 0
MIS: 0

Thanks in advance,

mishehu
-------------- next part --------------
A non-text attachment was scrubbed...
Name: nisui.config.bz2
Type: application/x-bzip
Size: 7354 bytes
Desc: not available
Url :
http://lists.digium.com/pipermail/asterisk-users/attachments/20041221/861d98c9/nisui.config.bin

Nestor A. Diaz L.

2005-Jan-20 14:50 UTC

head link

[Asterisk-Users] NMI issues...

Hello everybody, i have found a message on the list regarding this
problem, i experienced this too, my machine show this on the kernel log:

Jan 15 11:21:08 catwoman kernel: Uhhuh. NMI received for unknown reason 31.
Jan 15 11:21:08 catwoman kernel: Dazed and confused, but trying to continue
Jan 15 11:21:08 catwoman kernel: Do you have a strange power saving mode
enabled?
Jan 15 11:21:08 catwoman kernel: Uhhuh. NMI received for unknown reason 21.
Jan 15 11:21:08 catwoman kernel: Dazed and confused, but trying to continue
Jan 15 11:21:08 catwoman kernel: Do you have a strange power saving mode
enabled?

and loops forever, i see some posts on the list and the solution was to
start linux with the parameter nmi_watchdog=1:

so put in lilo.conf:

append="nmi_watchdog=1"

If i use the nmi_watchdog=0 the behavior was the normal, (a lot of output
on the console), with nmi_watchdog=1 the machine freeze, and with
nmi_watchdog=1 the asterisk is working, however there are still a lot of
nmi interrupts, but no log and it works anyway:

catwoman:~# cat /proc/interrupts
           CPU0
  0:    7938515    IO-APIC-edge  timer
  1:       1439    IO-APIC-edge  keyboard
  2:          0          XT-PIC  cascade
  4:         77    IO-APIC-edge  serial
  8:          1    IO-APIC-edge  rtc
 12:         19    IO-APIC-edge  PS/2 Mouse
 14:          2    IO-APIC-edge  libata
 15:     559174    IO-APIC-edge  libata
 18:    1978930   IO-APIC-level  eth0
 21:   79324605   IO-APIC-level  wcfxo
 22:   79325021   IO-APIC-level  wcfxo
 26:     238520   IO-APIC-level  eth1
NMI:   20571235
LOC:    7938676
ERR:          0
MIS:          0

The machine is a Dell Poweredge 700 with a sata disk.

Slds.

--
Nestor A. Diaz
Ingeniero de Sistemas y Comp.
Tel. +57 1 6005490 x 211
Cel. +57 315 8190760
nestor@tiendalinux.com
http://www.tiendalinux.com
Bogota, Colombia

Michael Loftis

2005-Jan-20 18:05 UTC

head link

[Asterisk-Users] NMI issues...

I dont' think it's the digium hardware fault.  Why?  I've got
probably 8-10
machines like this and they all get occasional NMIs with the 'uhhuh' 
message.  It's defiently kernel related...hell these boards don't work 
under anything older than 2.4.27.

--On Tuesday, December 21, 2004 00:42 -0600 "I put the Who? in
Mishehu"
<mishehu@shavedgoats.net> wrote:
> 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 -->
> http://www.3ware.com/kb/article.aspx?id=12435 ).  The following is a list
> of the configuration and the issues I have encountered.  Any help would be
> greatly appreciated.
>
> System A:
> Intel SE7525GP2 motherboard.  Has BIOS revision 06, BMC 2.40 and FRUSDR
> 1.40 2x2.8GHz Xeon processors w/800Mhz FSB, actively cooled retail box set
> 1GB of ECC registered DDR333 RAM, 2 DIMMs
> 3ware 9500 SATA Raid, controlling a 3-disk raid5 array
> 550 Watt 24-pin ATX power supply
>
> System B:
> Asus A7N8X-E Deluxe
> AMD Athlon XP 3200 (barton core)
> 512 MB RAM
> ATI 9600SE OEM card
> 200GB SATA drive
>
> Process is as follows:
> 1.  On system A until further notice: The Intel SE7525GP2 conflicted with
> the firmware on the 3ware 9500 SATA RAID controller until BIOS 06 was
> released.
> 2.  After having been flashed, Slackware 10.0 was then installed on it.
> It currently runs stock kernel 2.6.9, udev 042, and the most recent
> hotplug from 2004-09-23.
> 3.  Installed a digium-supplied X101P into the machine into a 32bit PCI
> slot. 4.  Downloaded zaptel 1.0.3, compiled against kernel 2.6.9.  Upon
> modprobe wcfxo, NMI's are immediately reported (syslog to follow).  The
> instructions from README.udev were followed and parameters inserted into
> the rules file for udev.  Problem occurs regardless of whether or not
> hotplug inserts the modules or the are manually inserted by me.  Repeated
> modprobe -r wcfxo; modprobe wcfxo produces no different result as well. 5.
>  Attempted all combinations of moving the card to other compatible slots,
> CVS zaptel from 2004-12-17, and the TDM04b card.  Snippet of syslog as
> follows:
>
> Dec 19 15:33:17 nisui kernel: Freshmaker version: 71
> Dec 19 15:33:17 nisui kernel: Freshmaker passed register test
> Dec 19 15:33:18 nisui kernel: Module 0: Installed -- AUTO FXO (FCC mode)
> Dec 19 15:33:18 nisui kernel: Uhhuh. NMI received for unknown reason 31 on
> CPU 0.
> Dec 19 15:33:18 nisui kernel: Dazed and confused, but trying to continue
> Dec 19 15:33:18 nisui kernel: Do you have a strange power saving mode
> enabled?
> Dec 19 15:33:18 nisui kernel: Module 1: Installed -- AUTO FXO (FCC mode)
> Dec 19 15:33:18 nisui kernel: Module 2: Installed -- AUTO FXO (FCC mode)
> Dec 19 15:33:19 nisui kernel: Module 3: Installed -- AUTO FXO (FCC mode)
> Dec 19 15:33:19 nisui kernel: Found a Wildcard TDM: Wildcard TDM400P REV
> E/F (4 modules)
> Dec 19 15:33:19 nisui kernel: Uhhuh. NMI received for unknown reason 31 on
> CPU 0.
> Dec 19 15:33:19 nisui kernel: Dazed and confused, but trying to continue
> Dec 19 15:33:19 nisui kernel: Do you have a strange power saving mode
> enabled?
> Dec 19 15:33:19 nisui kernel: Uhhuh. NMI received for unknown reason 21 on
> CPU 0.
>
> The NMI's will continue to report reasons 21 & 31 until the module
is
> removed from the kernel.
>
> 6.  Attempted several kernel reconfigurations, including ones that
> stripped out USB support and all SMP support.  Even on this machine with a
> uniprocessor kernel, NMI was still generated.
> 7.  Took the X100P and installed it in System B.  System B only reports:
> Notice: Configuration file is /etc/zaptel.conf
> line 143: Unable to open master device '/dev/zap/ctl'
> Whenever I check, /dev/zap/ctl does exist.  No NMI is generated on this
> machine, though I do not know if it is capible of doing so.  Otherwise, it
> appears to operate normally.
> 8.  Tried asterisklivecd that is maintained by somebody in Italy.
> Actually got a freshmaker error on that trial, though it appeared to be
> somewhat outdated.
>
> Just to anticipate questions, whenever the TDM04b was tested, the power
> connector was in fact connected.  An Intel Etherexpress Pro 100 ethernet
> card was tested on Machine A to verify that there was no problem with the
> slots.  The eepro100 initializes and operates perfectly.  Attached to this
> email is a copy of the kernel's configuration, and a list of currently
> loaded modules is as follows:
>
> Module                  Size  Used by
> md5                     4992  1
> ipv6                  260352  16
> hw_random               6548  0
> pciehp                 97540  0
> shpchp                101124  0
> pci_hotplug            13060  2 pciehp,shpchp
> e1000                  86788  0
> evdev                  10368  0
>
> And output from /proc/interrupts immediately after loading the wctdm
> module:           CPU0       CPU1       CPU2       CPU3
>  0:    3791068         10         10         10    IO-APIC-edge  timer 1:
>         7          1          0          0    IO-APIC-edge  i8042 9:
>     0          0          0          0   IO-APIC-level  acpi
> 12:         57          0          0          1    IO-APIC-edge  i8042 14:
>          0          1          0          0    IO-APIC-edge  ide0 169:
>   4222          0          1          0   IO-APIC-level  eth0 185:
>  0          0          0          0   IO-APIC-level  ehci_hcd 209:
> 22767          0          1          0   IO-APIC-level  3w-9xxx 217:
> 1063          0          0          1   IO-APIC-level  wctdm NMI:
> 63          0          0          0
> LOC:    3791179    3791182    3791180    3791179
> ERR:          0
> MIS:          0
>
> Thanks in advance,
>
> mishehu


--
GPG/PGP --> 0xE736BD7E 5144 6A2D 977A 6651 DFBE 1462 E351 88B9 E736 BD7E

Matt Schulte

2005-Jan-21 06:22 UTC

head link

[Asterisk-Users] NMI issues...

I'm having the exact same issue on a brand new Dell Poweredge 700, using
FC2. It locks the machine totally.

-----Original Message-----
From: Michael Loftis [mailto:mloftis@wgops.com] 
Sent: Thursday, January 20, 2005 7:06 PM
To: Asterisk Users Mailing List - Non-Commercial Discussion
Subject: Re: [Asterisk-Users] NMI issues...


I dont' think it's the digium hardware fault.  Why?  I've got
probably
8-10 
machines like this and they all get occasional NMIs with the 'uhhuh' 
message.  It's defiently kernel related...hell these boards don't work 
under anything older than 2.4.27.

--On Tuesday, December 21, 2004 00:42 -0600 "I put the Who? in
Mishehu"
<mishehu@shavedgoats.net> wrote:
> 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 --> 
> http://www.3ware.com/kb/article.aspx?id=12435 ).  The following is a 
> list of the configuration and the issues I have encountered.  Any help
> would be greatly appreciated.
>
> System A:
> Intel SE7525GP2 motherboard.  Has BIOS revision 06, BMC 2.40 and 
> FRUSDR 1.40 2x2.8GHz Xeon processors w/800Mhz FSB, actively cooled 
> retail box set 1GB of ECC registered DDR333 RAM, 2 DIMMs 3ware 9500 
> SATA Raid, controlling a 3-disk raid5 array 550 Watt 24-pin ATX power 
> supply
>
> System B:
> Asus A7N8X-E Deluxe
> AMD Athlon XP 3200 (barton core)
> 512 MB RAM
> ATI 9600SE OEM card
> 200GB SATA drive
>
> Process is as follows:
> 1.  On system A until further notice: The Intel SE7525GP2 conflicted 
> with the firmware on the 3ware 9500 SATA RAID controller until BIOS 06
> was released. 2.  After having been flashed, Slackware 10.0 was then 
> installed on it. It currently runs stock kernel 2.6.9, udev 042, and 
> the most recent hotplug from 2004-09-23.
> 3.  Installed a digium-supplied X101P into the machine into a 32bit
PCI> slot. 4.  Downloaded zaptel 1.0.3, compiled against kernel 2.6.9.
Upon> modprobe wcfxo, NMI's are immediately reported (syslog to follow).
The> instructions from README.udev were followed and parameters inserted
into> the rules file for udev.  Problem occurs regardless of whether or not
> hotplug inserts the modules or the are manually inserted by me.
Repeated> modprobe -r wcfxo; modprobe wcfxo produces no different result as
well. 5.>  Attempted all combinations of moving the card to other compatible
slots,> CVS zaptel from 2004-12-17, and the TDM04b card.  Snippet of syslog as
> follows:
>
> Dec 19 15:33:17 nisui kernel: Freshmaker version: 71
> Dec 19 15:33:17 nisui kernel: Freshmaker passed register test Dec 19 
> 15:33:18 nisui kernel: Module 0: Installed -- AUTO FXO (FCC mode) Dec 
> 19 15:33:18 nisui kernel: Uhhuh. NMI received for unknown reason 31 on
> CPU 0. Dec 19 15:33:18 nisui kernel: Dazed and confused, but trying to
> continue Dec 19 15:33:18 nisui kernel: Do you have a strange power 
> saving mode enabled?
> Dec 19 15:33:18 nisui kernel: Module 1: Installed -- AUTO FXO (FCC
mode)> Dec 19 15:33:18 nisui kernel: Module 2: Installed -- AUTO FXO (FCC
mode)> Dec 19 15:33:19 nisui kernel: Module 3: Installed -- AUTO FXO (FCC
mode)> Dec 19 15:33:19 nisui kernel: Found a Wildcard TDM: Wildcard TDM400P
REV> E/F (4 modules)
> Dec 19 15:33:19 nisui kernel: Uhhuh. NMI received for unknown reason
31 on> CPU 0.
> Dec 19 15:33:19 nisui kernel: Dazed and confused, but trying to
continue> Dec 19 15:33:19 nisui kernel: Do you have a strange power saving mode
> enabled?
> Dec 19 15:33:19 nisui kernel: Uhhuh. NMI received for unknown reason
21 on> CPU 0.
>
> The NMI's will continue to report reasons 21 & 31 until the module
is
> removed from the kernel.
>
> 6.  Attempted several kernel reconfigurations, including ones that 
> stripped out USB support and all SMP support.  Even on this machine 
> with a uniprocessor kernel, NMI was still generated. 7.  Took the 
> X100P and installed it in System B.  System B only reports:
> Notice: Configuration file is /etc/zaptel.conf
> line 143: Unable to open master device '/dev/zap/ctl' Whenever I 
> check, /dev/zap/ctl does exist.  No NMI is generated on this machine, 
> though I do not know if it is capible of doing so.  Otherwise, it 
> appears to operate normally. 8.  Tried asterisklivecd that is 
> maintained by somebody in Italy. Actually got a freshmaker error on 
> that trial, though it appeared to be somewhat outdated.
>
> Just to anticipate questions, whenever the TDM04b was tested, the 
> power connector was in fact connected.  An Intel Etherexpress Pro 100 
> ethernet card was tested on Machine A to verify that there was no 
> problem with the slots.  The eepro100 initializes and operates 
> perfectly.  Attached to this email is a copy of the kernel's 
> configuration, and a list of currently loaded modules is as follows:
>
> Module                  Size  Used by
> md5                     4992  1
> ipv6                  260352  16
> hw_random               6548  0
> pciehp                 97540  0
> shpchp                101124  0
> pci_hotplug            13060  2 pciehp,shpchp
> e1000                  86788  0
> evdev                  10368  0
>
> And output from /proc/interrupts immediately after loading the wctdm
> module:           CPU0       CPU1       CPU2       CPU3
>  0:    3791068         10         10         10    IO-APIC-edge  timer
1:>         7          1          0          0    IO-APIC-edge  i8042 9:
>     0          0          0          0   IO-APIC-level  acpi
> 12:         57          0          0          1    IO-APIC-edge  i8042
14:>          0          1          0          0    IO-APIC-edge  ide0 169:
>   4222          0          1          0   IO-APIC-level  eth0 185:
>  0          0          0          0   IO-APIC-level  ehci_hcd 209:
> 22767          0          1          0   IO-APIC-level  3w-9xxx 217:
> 1063          0          0          1   IO-APIC-level  wctdm NMI:
> 63          0          0          0
> LOC:    3791179    3791182    3791180    3791179
> ERR:          0
> MIS:          0
>
> Thanks in advance,
>
> mishehu


--
GPG/PGP --> 0xE736BD7E 5144 6A2D 977A 6651 DFBE 1462 E351 88B9 E736 BD7E

_______________________________________________
Asterisk-Users mailing list
Asterisk-Users@lists.digium.com
http://lists.digium.com/mailman/listinfo/asterisk-users
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-users

Matt Schulte

2005-Jan-31 14:18 UTC

head link

[Asterisk-Users] NMI issues...

Ok, so we went out and bought a 2650 per the lists advice, putting it
plainly
...
SSDD

DD = different dell, I won't even bother with "SS" :)

	Matt

-----Original Message-----
From: Matt Schulte 
Sent: Friday, January 21, 2005 7:23 AM
To: Asterisk Users Mailing List - Non-Commercial Discussion
Subject: RE: [Asterisk-Users] NMI issues...


I'm having the exact same issue on a brand new Dell Poweredge 700, using
FC2. It locks the machine totally.

-----Original Message-----
From: Michael Loftis [mailto:mloftis@wgops.com] 
Sent: Thursday, January 20, 2005 7:06 PM
To: Asterisk Users Mailing List - Non-Commercial Discussion
Subject: Re: [Asterisk-Users] NMI issues...


I dont' think it's the digium hardware fault.  Why?  I've got
probably
8-10 
machines like this and they all get occasional NMIs with the 'uhhuh' 
message.  It's defiently kernel related...hell these boards don't work 
under anything older than 2.4.27.

--On Tuesday, December 21, 2004 00:42 -0600 "I put the Who? in
Mishehu"
<mishehu@shavedgoats.net> wrote:
> 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 --> 
> http://www.3ware.com/kb/article.aspx?id=12435 ).  The following is a 
> list of the configuration and the issues I have encountered.  Any help
> would be greatly appreciated.
>
> System A:
> Intel SE7525GP2 motherboard.  Has BIOS revision 06, BMC 2.40 and
> FRUSDR 1.40 2x2.8GHz Xeon processors w/800Mhz FSB, actively cooled 
> retail box set 1GB of ECC registered DDR333 RAM, 2 DIMMs 3ware 9500 
> SATA Raid, controlling a 3-disk raid5 array 550 Watt 24-pin ATX power 
> supply
>
> System B:
> Asus A7N8X-E Deluxe
> AMD Athlon XP 3200 (barton core)
> 512 MB RAM
> ATI 9600SE OEM card
> 200GB SATA drive
>
> Process is as follows:
> 1.  On system A until further notice: The Intel SE7525GP2 conflicted
> with the firmware on the 3ware 9500 SATA RAID controller until BIOS 06
> was released. 2.  After having been flashed, Slackware 10.0 was then
> installed on it. It currently runs stock kernel 2.6.9, udev 042, and 
> the most recent hotplug from 2004-09-23.
> 3.  Installed a digium-supplied X101P into the machine into a 32bit
PCI> slot. 4.  Downloaded zaptel 1.0.3, compiled against kernel 2.6.9.
Upon> modprobe wcfxo, NMI's are immediately reported (syslog to follow).
The> instructions from README.udev were followed and parameters inserted
into> the rules file for udev.  Problem occurs regardless of whether or not 
> hotplug inserts the modules or the are manually inserted by me.
Repeated> modprobe -r wcfxo; modprobe wcfxo produces no different result as
well. 5.>  Attempted all combinations of moving the card to other compatible
slots,> CVS zaptel from 2004-12-17, and the TDM04b card.  Snippet of syslog as
> follows:
>
> Dec 19 15:33:17 nisui kernel: Freshmaker version: 71
> Dec 19 15:33:17 nisui kernel: Freshmaker passed register test Dec 19
> 15:33:18 nisui kernel: Module 0: Installed -- AUTO FXO (FCC mode) Dec 
> 19 15:33:18 nisui kernel: Uhhuh. NMI received for unknown reason 31 on
> CPU 0. Dec 19 15:33:18 nisui kernel: Dazed and confused, but trying to
> continue Dec 19 15:33:18 nisui kernel: Do you have a strange power
> saving mode enabled?
> Dec 19 15:33:18 nisui kernel: Module 1: Installed -- AUTO FXO (FCC
mode)> Dec 19 15:33:18 nisui kernel: Module 2: Installed -- AUTO FXO (FCC
mode)> Dec 19 15:33:19 nisui kernel: Module 3: Installed -- AUTO FXO (FCC
mode)> Dec 19 15:33:19 nisui kernel: Found a Wildcard TDM: Wildcard TDM400P
REV> E/F (4 modules)
> Dec 19 15:33:19 nisui kernel: Uhhuh. NMI received for unknown reason
31 on> CPU 0.
> Dec 19 15:33:19 nisui kernel: Dazed and confused, but trying to
continue> Dec 19 15:33:19 nisui kernel: Do you have a strange power saving mode 
> enabled? Dec 19 15:33:19 nisui kernel: Uhhuh. NMI received for unknown
> reason
21 on> CPU 0.
>
> The NMI's will continue to report reasons 21 & 31 until the module
is
> removed from the kernel.
>
> 6.  Attempted several kernel reconfigurations, including ones that
> stripped out USB support and all SMP support.  Even on this machine 
> with a uniprocessor kernel, NMI was still generated. 7.  Took the 
> X100P and installed it in System B.  System B only reports:
> Notice: Configuration file is /etc/zaptel.conf
> line 143: Unable to open master device '/dev/zap/ctl' Whenever I 
> check, /dev/zap/ctl does exist.  No NMI is generated on this machine, 
> though I do not know if it is capible of doing so.  Otherwise, it 
> appears to operate normally. 8.  Tried asterisklivecd that is 
> maintained by somebody in Italy. Actually got a freshmaker error on 
> that trial, though it appeared to be somewhat outdated.
>
> Just to anticipate questions, whenever the TDM04b was tested, the
> power connector was in fact connected.  An Intel Etherexpress Pro 100 
> ethernet card was tested on Machine A to verify that there was no 
> problem with the slots.  The eepro100 initializes and operates 
> perfectly.  Attached to this email is a copy of the kernel's 
> configuration, and a list of currently loaded modules is as follows:
>
> Module                  Size  Used by
> md5                     4992  1
> ipv6                  260352  16
> hw_random               6548  0
> pciehp                 97540  0
> shpchp                101124  0
> pci_hotplug            13060  2 pciehp,shpchp
> e1000                  86788  0
> evdev                  10368  0
>
> And output from /proc/interrupts immediately after loading the wctdm
> module:           CPU0       CPU1       CPU2       CPU3
>  0:    3791068         10         10         10    IO-APIC-edge  timer
1:>         7          1          0          0    IO-APIC-edge  i8042 9:
>     0          0          0          0   IO-APIC-level  acpi
> 12:         57          0          0          1    IO-APIC-edge  i8042
14:>          0          1          0          0    IO-APIC-edge  ide0 169:
>   4222          0          1          0   IO-APIC-level  eth0 185:
>  0          0          0          0   IO-APIC-level  ehci_hcd 209:
> 22767          0          1          0   IO-APIC-level  3w-9xxx 217:
> 1063          0          0          1   IO-APIC-level  wctdm NMI:
> 63          0          0          0
> LOC:    3791179    3791182    3791180    3791179
> ERR:          0
> MIS:          0
>
> Thanks in advance,
>
> mishehu


--
GPG/PGP --> 0xE736BD7E 5144 6A2D 977A 6651 DFBE 1462 E351 88B9 E736 BD7E

_______________________________________________
Asterisk-Users mailing list
Asterisk-Users@lists.digium.com
http://lists.digium.com/mailman/listinfo/asterisk-users
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-users
_______________________________________________
Asterisk-Users mailing list
Asterisk-Users@lists.digium.com
http://lists.digium.com/mailman/listinfo/asterisk-users
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-users

Christopher Slaght

2005-Feb-01 06:52 UTC

head link

[Asterisk-Users] NMI issues...

I tried to get the TDM card to work in an IBM xSeries 350 700Mhz Zeon.
What I found was that the WCTDM card does not like the 64 bit slots.  If
you put the card in the 32-bit 33Mhz slot it works all day.  If you move
it into a 33Mhz/64-bit slot or 66 MHz/64-bit slot, as soon as you
modprobe wctdm, the NMI lights on the server light up and you have about
a minute before the server reboots itself.
 

-----Original Message-----
From: asterisk-users-bounces@lists.digium.com
[mailto:asterisk-users-bounces@lists.digium.com] On Behalf Of Matt
Schulte
Sent: Monday, January 31, 2005 4:19 PM
To: Asterisk Users Mailing List - Non-Commercial Discussion
Subject: RE: [Asterisk-Users] NMI issues...

Ok, so we went out and bought a 2650 per the lists advice, putting it
plainly ...
SSDD

DD = different dell, I won't even bother with "SS" :)

	Matt

-----Original Message-----
From: Matt Schulte
Sent: Friday, January 21, 2005 7:23 AM
To: Asterisk Users Mailing List - Non-Commercial Discussion
Subject: RE: [Asterisk-Users] NMI issues...


I'm having the exact same issue on a brand new Dell Poweredge 700, using
FC2. It locks the machine totally.

-----Original Message-----
From: Michael Loftis [mailto:mloftis@wgops.com] 
Sent: Thursday, January 20, 2005 7:06 PM
To: Asterisk Users Mailing List - Non-Commercial Discussion
Subject: Re: [Asterisk-Users] NMI issues...


I dont' think it's the digium hardware fault.  Why?  I've got
probably
8-10 
machines like this and they all get occasional NMIs with the 'uhhuh' 
message.  It's defiently kernel related...hell these boards don't work 
under anything older than 2.4.27.

--On Tuesday, December 21, 2004 00:42 -0600 "I put the Who? in
Mishehu"
<mishehu@shavedgoats.net> wrote:
> 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 --> 
> http://www.3ware.com/kb/article.aspx?id=12435 ).  The following is a 
> list of the configuration and the issues I have encountered.  Any help
> would be greatly appreciated.
>
> System A:
> Intel SE7525GP2 motherboard.  Has BIOS revision 06, BMC 2.40 and
> FRUSDR 1.40 2x2.8GHz Xeon processors w/800Mhz FSB, actively cooled 
> retail box set 1GB of ECC registered DDR333 RAM, 2 DIMMs 3ware 9500 
> SATA Raid, controlling a 3-disk raid5 array 550 Watt 24-pin ATX power 
> supply
>
> System B:
> Asus A7N8X-E Deluxe
> AMD Athlon XP 3200 (barton core)
> 512 MB RAM
> ATI 9600SE OEM card
> 200GB SATA drive
>
> Process is as follows:
> 1.  On system A until further notice: The Intel SE7525GP2 conflicted
> with the firmware on the 3ware 9500 SATA RAID controller until BIOS 06
> was released. 2.  After having been flashed, Slackware 10.0 was then
> installed on it. It currently runs stock kernel 2.6.9, udev 042, and 
> the most recent hotplug from 2004-09-23.
> 3.  Installed a digium-supplied X101P into the machine into a 32bit
PCI> slot. 4.  Downloaded zaptel 1.0.3, compiled against kernel 2.6.9.
Upon> modprobe wcfxo, NMI's are immediately reported (syslog to follow).
The> instructions from README.udev were followed and parameters inserted
into> the rules file for udev.  Problem occurs regardless of whether or not 
> hotplug inserts the modules or the are manually inserted by me.
Repeated> modprobe -r wcfxo; modprobe wcfxo produces no different result as
well. 5.>  Attempted all combinations of moving the card to other compatible
slots,> CVS zaptel from 2004-12-17, and the TDM04b card.  Snippet of syslog as
> follows:
>
> Dec 19 15:33:17 nisui kernel: Freshmaker version: 71
> Dec 19 15:33:17 nisui kernel: Freshmaker passed register test Dec 19
> 15:33:18 nisui kernel: Module 0: Installed -- AUTO FXO (FCC mode) Dec 
> 19 15:33:18 nisui kernel: Uhhuh. NMI received for unknown reason 31 on
> CPU 0. Dec 19 15:33:18 nisui kernel: Dazed and confused, but trying to
> continue Dec 19 15:33:18 nisui kernel: Do you have a strange power
> saving mode enabled?
> Dec 19 15:33:18 nisui kernel: Module 1: Installed -- AUTO FXO (FCC
mode)> Dec 19 15:33:18 nisui kernel: Module 2: Installed -- AUTO FXO (FCC
mode)> Dec 19 15:33:19 nisui kernel: Module 3: Installed -- AUTO FXO (FCC
mode)> Dec 19 15:33:19 nisui kernel: Found a Wildcard TDM: Wildcard TDM400P
REV> E/F (4 modules)
> Dec 19 15:33:19 nisui kernel: Uhhuh. NMI received for unknown reason
31 on> CPU 0.
> Dec 19 15:33:19 nisui kernel: Dazed and confused, but trying to
continue> Dec 19 15:33:19 nisui kernel: Do you have a strange power saving mode 
> enabled? Dec 19 15:33:19 nisui kernel: Uhhuh. NMI received for unknown
> reason
21 on> CPU 0.
>
> The NMI's will continue to report reasons 21 & 31 until the module
is
> removed from the kernel.
>
> 6.  Attempted several kernel reconfigurations, including ones that
> stripped out USB support and all SMP support.  Even on this machine 
> with a uniprocessor kernel, NMI was still generated. 7.  Took the 
> X100P and installed it in System B.  System B only reports:
> Notice: Configuration file is /etc/zaptel.conf
> line 143: Unable to open master device '/dev/zap/ctl' Whenever I 
> check, /dev/zap/ctl does exist.  No NMI is generated on this machine, 
> though I do not know if it is capible of doing so.  Otherwise, it 
> appears to operate normally. 8.  Tried asterisklivecd that is 
> maintained by somebody in Italy. Actually got a freshmaker error on 
> that trial, though it appeared to be somewhat outdated.
>
> Just to anticipate questions, whenever the TDM04b was tested, the
> power connector was in fact connected.  An Intel Etherexpress Pro 100 
> ethernet card was tested on Machine A to verify that there was no 
> problem with the slots.  The eepro100 initializes and operates 
> perfectly.  Attached to this email is a copy of the kernel's 
> configuration, and a list of currently loaded modules is as follows:
>
> Module                  Size  Used by
> md5                     4992  1
> ipv6                  260352  16
> hw_random               6548  0
> pciehp                 97540  0
> shpchp                101124  0
> pci_hotplug            13060  2 pciehp,shpchp
> e1000                  86788  0
> evdev                  10368  0
>
> And output from /proc/interrupts immediately after loading the wctdm
> module:           CPU0       CPU1       CPU2       CPU3
>  0:    3791068         10         10         10    IO-APIC-edge  timer
1:>         7          1          0          0    IO-APIC-edge  i8042 9:
>     0          0          0          0   IO-APIC-level  acpi
> 12:         57          0          0          1    IO-APIC-edge  i8042
14:>          0          1          0          0    IO-APIC-edge  ide0 169:
>   4222          0          1          0   IO-APIC-level  eth0 185:
>  0          0          0          0   IO-APIC-level  ehci_hcd 209:
> 22767          0          1          0   IO-APIC-level  3w-9xxx 217:
> 1063          0          0          1   IO-APIC-level  wctdm NMI:
> 63          0          0          0
> LOC:    3791179    3791182    3791180    3791179
> ERR:          0
> MIS:          0
>
> Thanks in advance,
>
> mishehu


--
GPG/PGP --> 0xE736BD7E 5144 6A2D 977A 6651 DFBE 1462 E351 88B9 E736 BD7E

_______________________________________________
Asterisk-Users mailing list
Asterisk-Users@lists.digium.com
http://lists.digium.com/mailman/listinfo/asterisk-users
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-users
_______________________________________________
Asterisk-Users mailing list
Asterisk-Users@lists.digium.com
http://lists.digium.com/mailman/listinfo/asterisk-users
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-users
_______________________________________________
Asterisk-Users mailing list
Asterisk-Users@lists.digium.com
http://lists.digium.com/mailman/listinfo/asterisk-users
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-users

Matt Schulte

2005-Feb-01 06:57 UTC

head link

[Asterisk-Users] NMI issues...

Really... I *think* I tried this already, I'll try on our "old"
Dell 700
and see if this helps. Thanks.

-----Original Message-----
From: Christopher Slaght [mailto:cmslaght@issohio.com] 
Sent: Tuesday, February 01, 2005 7:52 AM
To: Asterisk Users Mailing List - Non-Commercial Discussion
Subject: RE: [Asterisk-Users] NMI issues...


I tried to get the TDM card to work in an IBM xSeries 350 700Mhz Zeon.
What I found was that the WCTDM card does not like the 64 bit slots.  If
you put the card in the 32-bit 33Mhz slot it works all day.  If you move
it into a 33Mhz/64-bit slot or 66 MHz/64-bit slot, as soon as you
modprobe wctdm, the NMI lights on the server light up and you have about
a minute before the server reboots itself.
 

-----Original Message-----
From: asterisk-users-bounces@lists.digium.com
[mailto:asterisk-users-bounces@lists.digium.com] On Behalf Of Matt
Schulte
Sent: Monday, January 31, 2005 4:19 PM
To: Asterisk Users Mailing List - Non-Commercial Discussion
Subject: RE: [Asterisk-Users] NMI issues...

Ok, so we went out and bought a 2650 per the lists advice, putting it
plainly ... SSDD

DD = different dell, I won't even bother with "SS" :)

	Matt

-----Original Message-----
From: Matt Schulte
Sent: Friday, January 21, 2005 7:23 AM
To: Asterisk Users Mailing List - Non-Commercial Discussion
Subject: RE: [Asterisk-Users] NMI issues...


I'm having the exact same issue on a brand new Dell Poweredge 700, using
FC2. It locks the machine totally.

-----Original Message-----
From: Michael Loftis [mailto:mloftis@wgops.com] 
Sent: Thursday, January 20, 2005 7:06 PM
To: Asterisk Users Mailing List - Non-Commercial Discussion
Subject: Re: [Asterisk-Users] NMI issues...


I dont' think it's the digium hardware fault.  Why?  I've got
probably
8-10 
machines like this and they all get occasional NMIs with the 'uhhuh' 
message.  It's defiently kernel related...hell these boards don't work 
under anything older than 2.4.27.

--On Tuesday, December 21, 2004 00:42 -0600 "I put the Who? in
Mishehu"
<mishehu@shavedgoats.net> wrote:
> 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 --> 
> http://www.3ware.com/kb/article.aspx?id=12435 ).  The following is a 
> list of the configuration and the issues I have encountered.  Any help
> would be greatly appreciated.
>
> System A:
> Intel SE7525GP2 motherboard.  Has BIOS revision 06, BMC 2.40 and 
> FRUSDR 1.40 2x2.8GHz Xeon processors w/800Mhz FSB, actively cooled 
> retail box set 1GB of ECC registered DDR333 RAM, 2 DIMMs 3ware 9500 
> SATA Raid, controlling a 3-disk raid5 array 550 Watt 24-pin ATX power 
> supply
>
> System B:
> Asus A7N8X-E Deluxe
> AMD Athlon XP 3200 (barton core)
> 512 MB RAM
> ATI 9600SE OEM card
> 200GB SATA drive
>
> Process is as follows:
> 1.  On system A until further notice: The Intel SE7525GP2 conflicted 
> with the firmware on the 3ware 9500 SATA RAID controller until BIOS 06
> was released. 2.  After having been flashed, Slackware 10.0 was then 
> installed on it. It currently runs stock kernel 2.6.9, udev 042, and 
> the most recent hotplug from 2004-09-23. 3.  Installed a 
> digium-supplied X101P into the machine into a 32bit
PCI> slot. 4.  Downloaded zaptel 1.0.3, compiled against kernel 2.6.9.
Upon> modprobe wcfxo, NMI's are immediately reported (syslog to follow).
The> instructions from README.udev were followed and parameters inserted
into> the rules file for udev.  Problem occurs regardless of whether or not
> hotplug inserts the modules or the are manually inserted by me.
Repeated> modprobe -r wcfxo; modprobe wcfxo produces no different result as
well. 5.>  Attempted all combinations of moving the card to other compatible
slots,> CVS zaptel from 2004-12-17, and the TDM04b card.  Snippet of syslog as
> follows:
>
> Dec 19 15:33:17 nisui kernel: Freshmaker version: 71
> Dec 19 15:33:17 nisui kernel: Freshmaker passed register test Dec 19 
> 15:33:18 nisui kernel: Module 0: Installed -- AUTO FXO (FCC mode) Dec 
> 19 15:33:18 nisui kernel: Uhhuh. NMI received for unknown reason 31 on
> CPU 0. Dec 19 15:33:18 nisui kernel: Dazed and confused, but trying to
> continue Dec 19 15:33:18 nisui kernel: Do you have a strange power 
> saving mode enabled? Dec 19 15:33:18 nisui kernel: Module 1: Installed
> -- AUTO FXO (FCC
mode)> Dec 19 15:33:18 nisui kernel: Module 2: Installed -- AUTO FXO (FCC
mode)> Dec 19 15:33:19 nisui kernel: Module 3: Installed -- AUTO FXO (FCC
mode)> Dec 19 15:33:19 nisui kernel: Found a Wildcard TDM: Wildcard TDM400P
REV> E/F (4 modules)
> Dec 19 15:33:19 nisui kernel: Uhhuh. NMI received for unknown reason
31 on> CPU 0.
> Dec 19 15:33:19 nisui kernel: Dazed and confused, but trying to
continue> Dec 19 15:33:19 nisui kernel: Do you have a strange power saving mode
> enabled? Dec 19 15:33:19 nisui kernel: Uhhuh. NMI received for unknown
> reason
21 on> CPU 0.
>
> The NMI's will continue to report reasons 21 & 31 until the module
is
> removed from the kernel.
>
> 6.  Attempted several kernel reconfigurations, including ones that 
> stripped out USB support and all SMP support.  Even on this machine 
> with a uniprocessor kernel, NMI was still generated. 7.  Took the 
> X100P and installed it in System B.  System B only reports:
> Notice: Configuration file is /etc/zaptel.conf
> line 143: Unable to open master device '/dev/zap/ctl' Whenever I
> check, /dev/zap/ctl does exist.  No NMI is generated on this machine, 
> though I do not know if it is capible of doing so.  Otherwise, it 
> appears to operate normally. 8.  Tried asterisklivecd that is 
> maintained by somebody in Italy. Actually got a freshmaker error on 
> that trial, though it appeared to be somewhat outdated.
>
> Just to anticipate questions, whenever the TDM04b was tested, the 
> power connector was in fact connected.  An Intel Etherexpress Pro 100 
> ethernet card was tested on Machine A to verify that there was no 
> problem with the slots.  The eepro100 initializes and operates 
> perfectly.  Attached to this email is a copy of the kernel's 
> configuration, and a list of currently loaded modules is as follows:
>
> Module                  Size  Used by
> md5                     4992  1
> ipv6                  260352  16
> hw_random               6548  0
> pciehp                 97540  0
> shpchp                101124  0
> pci_hotplug            13060  2 pciehp,shpchp
> e1000                  86788  0
> evdev                  10368  0
>
> And output from /proc/interrupts immediately after loading the wctdm
> module:           CPU0       CPU1       CPU2       CPU3
>  0:    3791068         10         10         10    IO-APIC-edge  timer
1:>         7          1          0          0    IO-APIC-edge  i8042 9:
>     0          0          0          0   IO-APIC-level  acpi
> 12:         57          0          0          1    IO-APIC-edge  i8042
14:>          0          1          0          0    IO-APIC-edge  ide0 169:
>   4222          0          1          0   IO-APIC-level  eth0 185:
>  0          0          0          0   IO-APIC-level  ehci_hcd 209:
> 22767          0          1          0   IO-APIC-level  3w-9xxx 217:
> 1063          0          0          1   IO-APIC-level  wctdm NMI:
> 63          0          0          0
> LOC:    3791179    3791182    3791180    3791179
> ERR:          0
> MIS:          0
>
> Thanks in advance,
>
> mishehu


--
GPG/PGP --> 0xE736BD7E 5144 6A2D 977A 6651 DFBE 1462 E351 88B9 E736 BD7E

_______________________________________________
Asterisk-Users mailing list
Asterisk-Users@lists.digium.com
http://lists.digium.com/mailman/listinfo/asterisk-users
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-users
_______________________________________________
Asterisk-Users mailing list
Asterisk-Users@lists.digium.com
http://lists.digium.com/mailman/listinfo/asterisk-users
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-users
_______________________________________________
Asterisk-Users mailing list
Asterisk-Users@lists.digium.com
http://lists.digium.com/mailman/listinfo/asterisk-users
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-users
_______________________________________________
Asterisk-Users mailing list
Asterisk-Users@lists.digium.com
http://lists.digium.com/mailman/listinfo/asterisk-users
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-users

Matt Schulte

2005-Feb-01 08:18 UTC

head link

[Asterisk-Users] NMI issues...

Just tried this, same deal. A bunch of NMI errors and eventually locks
up.



-----Original Message-----
From: Matt Schulte 
Sent: Tuesday, February 01, 2005 7:58 AM
To: Asterisk Users Mailing List - Non-Commercial Discussion
Subject: RE: [Asterisk-Users] NMI issues...


Really... I *think* I tried this already, I'll try on our "old"
Dell 700
and see if this helps. Thanks.

-----Original Message-----
From: Christopher Slaght [mailto:cmslaght@issohio.com] 
Sent: Tuesday, February 01, 2005 7:52 AM
To: Asterisk Users Mailing List - Non-Commercial Discussion
Subject: RE: [Asterisk-Users] NMI issues...


I tried to get the TDM card to work in an IBM xSeries 350 700Mhz Zeon.
What I found was that the WCTDM card does not like the 64 bit slots.  If
you put the card in the 32-bit 33Mhz slot it works all day.  If you move
it into a 33Mhz/64-bit slot or 66 MHz/64-bit slot, as soon as you
modprobe wctdm, the NMI lights on the server light up and you have about
a minute before the server reboots itself.
 

-----Original Message-----
From: asterisk-users-bounces@lists.digium.com
[mailto:asterisk-users-bounces@lists.digium.com] On Behalf Of Matt
Schulte
Sent: Monday, January 31, 2005 4:19 PM
To: Asterisk Users Mailing List - Non-Commercial Discussion
Subject: RE: [Asterisk-Users] NMI issues...

Ok, so we went out and bought a 2650 per the lists advice, putting it
plainly ... SSDD

DD = different dell, I won't even bother with "SS" :)

	Matt

-----Original Message-----
From: Matt Schulte
Sent: Friday, January 21, 2005 7:23 AM
To: Asterisk Users Mailing List - Non-Commercial Discussion
Subject: RE: [Asterisk-Users] NMI issues...


I'm having the exact same issue on a brand new Dell Poweredge 700, using
FC2. It locks the machine totally.

-----Original Message-----
From: Michael Loftis [mailto:mloftis@wgops.com] 
Sent: Thursday, January 20, 2005 7:06 PM
To: Asterisk Users Mailing List - Non-Commercial Discussion
Subject: Re: [Asterisk-Users] NMI issues...


I dont' think it's the digium hardware fault.  Why?  I've got
probably
8-10 
machines like this and they all get occasional NMIs with the 'uhhuh' 
message.  It's defiently kernel related...hell these boards don't work 
under anything older than 2.4.27.

--On Tuesday, December 21, 2004 00:42 -0600 "I put the Who? in
Mishehu"
<mishehu@shavedgoats.net> wrote:
> 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 --> 
> http://www.3ware.com/kb/article.aspx?id=12435 ).  The following is a 
> list of the configuration and the issues I have encountered.  Any help
> would be greatly appreciated.
>
> System A:
> Intel SE7525GP2 motherboard.  Has BIOS revision 06, BMC 2.40 and
> FRUSDR 1.40 2x2.8GHz Xeon processors w/800Mhz FSB, actively cooled 
> retail box set 1GB of ECC registered DDR333 RAM, 2 DIMMs 3ware 9500 
> SATA Raid, controlling a 3-disk raid5 array 550 Watt 24-pin ATX power 
> supply
>
> System B:
> Asus A7N8X-E Deluxe
> AMD Athlon XP 3200 (barton core)
> 512 MB RAM
> ATI 9600SE OEM card
> 200GB SATA drive
>
> Process is as follows:
> 1.  On system A until further notice: The Intel SE7525GP2 conflicted
> with the firmware on the 3ware 9500 SATA RAID controller until BIOS 06
> was released. 2.  After having been flashed, Slackware 10.0 was then
> installed on it. It currently runs stock kernel 2.6.9, udev 042, and 
> the most recent hotplug from 2004-09-23. 3.  Installed a 
> digium-supplied X101P into the machine into a 32bit
PCI> slot. 4.  Downloaded zaptel 1.0.3, compiled against kernel 2.6.9.
Upon> modprobe wcfxo, NMI's are immediately reported (syslog to follow).
The> instructions from README.udev were followed and parameters inserted
into> the rules file for udev.  Problem occurs regardless of whether or not 
> hotplug inserts the modules or the are manually inserted by me.
Repeated> modprobe -r wcfxo; modprobe wcfxo produces no different result as
well. 5.>  Attempted all combinations of moving the card to other compatible
slots,> CVS zaptel from 2004-12-17, and the TDM04b card.  Snippet of syslog as
> follows:
>
> Dec 19 15:33:17 nisui kernel: Freshmaker version: 71
> Dec 19 15:33:17 nisui kernel: Freshmaker passed register test Dec 19
> 15:33:18 nisui kernel: Module 0: Installed -- AUTO FXO (FCC mode) Dec 
> 19 15:33:18 nisui kernel: Uhhuh. NMI received for unknown reason 31 on
> CPU 0. Dec 19 15:33:18 nisui kernel: Dazed and confused, but trying to
> continue Dec 19 15:33:18 nisui kernel: Do you have a strange power
> saving mode enabled? Dec 19 15:33:18 nisui kernel: Module 1: Installed
> -- AUTO FXO (FCC
mode)> Dec 19 15:33:18 nisui kernel: Module 2: Installed -- AUTO FXO (FCC
mode)> Dec 19 15:33:19 nisui kernel: Module 3: Installed -- AUTO FXO (FCC
mode)> Dec 19 15:33:19 nisui kernel: Found a Wildcard TDM: Wildcard TDM400P
REV> E/F (4 modules)
> Dec 19 15:33:19 nisui kernel: Uhhuh. NMI received for unknown reason
31 on> CPU 0.
> Dec 19 15:33:19 nisui kernel: Dazed and confused, but trying to
continue> Dec 19 15:33:19 nisui kernel: Do you have a strange power saving mode 
> enabled? Dec 19 15:33:19 nisui kernel: Uhhuh. NMI received for unknown
> reason
21 on> CPU 0.
>
> The NMI's will continue to report reasons 21 & 31 until the module
is
> removed from the kernel.
>
> 6.  Attempted several kernel reconfigurations, including ones that
> stripped out USB support and all SMP support.  Even on this machine 
> with a uniprocessor kernel, NMI was still generated. 7.  Took the 
> X100P and installed it in System B.  System B only reports:
> Notice: Configuration file is /etc/zaptel.conf
> line 143: Unable to open master device '/dev/zap/ctl' Whenever I
> check, /dev/zap/ctl does exist.  No NMI is generated on this machine, 
> though I do not know if it is capible of doing so.  Otherwise, it 
> appears to operate normally. 8.  Tried asterisklivecd that is 
> maintained by somebody in Italy. Actually got a freshmaker error on 
> that trial, though it appeared to be somewhat outdated.
>
> Just to anticipate questions, whenever the TDM04b was tested, the
> power connector was in fact connected.  An Intel Etherexpress Pro 100 
> ethernet card was tested on Machine A to verify that there was no 
> problem with the slots.  The eepro100 initializes and operates 
> perfectly.  Attached to this email is a copy of the kernel's 
> configuration, and a list of currently loaded modules is as follows:
>
> Module                  Size  Used by
> md5                     4992  1
> ipv6                  260352  16
> hw_random               6548  0
> pciehp                 97540  0
> shpchp                101124  0
> pci_hotplug            13060  2 pciehp,shpchp
> e1000                  86788  0
> evdev                  10368  0
>
> And output from /proc/interrupts immediately after loading the wctdm
> module:           CPU0       CPU1       CPU2       CPU3
>  0:    3791068         10         10         10    IO-APIC-edge  timer
1:>         7          1          0          0    IO-APIC-edge  i8042 9:
>     0          0          0          0   IO-APIC-level  acpi
> 12:         57          0          0          1    IO-APIC-edge  i8042
14:>          0          1          0          0    IO-APIC-edge  ide0 169:
>   4222          0          1          0   IO-APIC-level  eth0 185:
>  0          0          0          0   IO-APIC-level  ehci_hcd 209:
> 22767          0          1          0   IO-APIC-level  3w-9xxx 217:
> 1063          0          0          1   IO-APIC-level  wctdm NMI:
> 63          0          0          0
> LOC:    3791179    3791182    3791180    3791179
> ERR:          0
> MIS:          0
>
> Thanks in advance,
>
> mishehu


--
GPG/PGP --> 0xE736BD7E 5144 6A2D 977A 6651 DFBE 1462 E351 88B9 E736 BD7E

_______________________________________________
Asterisk-Users mailing list
Asterisk-Users@lists.digium.com
http://lists.digium.com/mailman/listinfo/asterisk-users
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-users
_______________________________________________
Asterisk-Users mailing list
Asterisk-Users@lists.digium.com
http://lists.digium.com/mailman/listinfo/asterisk-users
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-users
_______________________________________________
Asterisk-Users mailing list
Asterisk-Users@lists.digium.com
http://lists.digium.com/mailman/listinfo/asterisk-users
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-users
_______________________________________________
Asterisk-Users mailing list
Asterisk-Users@lists.digium.com
http://lists.digium.com/mailman/listinfo/asterisk-users
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-users
_______________________________________________
Asterisk-Users mailing list
Asterisk-Users@lists.digium.com
http://lists.digium.com/mailman/listinfo/asterisk-users
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-users

Seemingly Similar Threads

Search for more apparently analagous threads

asterisk users - Dec 2004 - NMI issues...

[Asterisk-Users] NMI issues...

[Asterisk-Users] NMI issues...

[Asterisk-Users] NMI issues...

[Asterisk-Users] NMI issues...

[Asterisk-Users] NMI issues...

[Asterisk-Users] NMI issues...

[Asterisk-Users] NMI issues...

[Asterisk-Users] NMI issues...

Seemingly Similar Threads