System crash (PCI Openvox A800p)

[bjorn]

Hi,

I have just set up a ubuntu based server for home use. I was intended to
serve for various tasks but I started with Asterisk. Based on recommendations
on the web I downloaded the asterisk application as src and built the service locally.
The system uses a Openvox A800p analog SLIC card to interface to the public telephony
provided by Telia in Sweden.

Building and running the modules and system worked with no issues but the system soon
started to crash and reboot. Sometimes already at boot, sometimes after a random amount of time
and sometimes when I shutdown the system. It has crashed ~50 times during the last 10 days.

I think the problem is related to the A800p PCI card since it stopped crashing after I disabled
the opvxa1200.ko driver. I have tried to change PCI slot but no change. First I had
xfce4 started for GUI access but stopped the gdm in case the graphical system was involved
but I could not see any change.

The system is an old but very robust HP Proliant DL380 G3 rack server
with 2 Intel(R) Xeon(TM) CPU 2.40GHz, 3 GB memory.

Asterisk software:

asterisk-1.4.26-rc1
asterisk-addons-1.4.8
dahdi-linux-2.2.0-rc5
dahdi-tools-2.2.0-rc3
opvxa1200.c
speex-1.2rc1

The opvxa1200.c is from Openvox: http://www.openvox.cn/download/drivers/dahdi/

I have search /var/log/messages and dmesg but not found anything strange

The HP LightsOut system captures:
hpasmcli> SHOW iml

Event: 99 Added: 06/18/2009 21:59
CRITICAL: PCI Bus - PCI Bus Error (Slot 0, Bus 6, Device 1, Function 0).

In my 15 years running Linux I have never seen a system this liable to break,
especially since the core system is higher grade than I am used to....

$ lsb_release -rd
Description: Ubuntu 9.04
Release: 9.04

Linux medium 2.6.28-11-server #42-Ubuntu SMP Fri Apr 17 02:48:10 UTC 2009 i686 GNU/Linux

[bjorn (b973)]

After some more unsuccessful testing I moved to an old HP Vectra (PIII 800 MHz) and the new system was
very stable. This means that the problem is related to the DL380 possibly in combination with the A800p board and possibly 9.04. I will try to test the DL380 with some other linux version to verify if 9.04 is involved in the problem.

/Björn

[Fabio Marconi (fabiomarconi)]

Thank you for taking the time to report this bug and helping to make Ubuntu better.
Is this bug reproducible with the latest Lucid packages ?
Tanks in advance.

[Fabio Marconi (fabiomarconi)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. This bug did not have a package associated with it, which is important for ensuring that it gets looked at by the proper developers. You can learn more about finding the right package at https://wiki.ubuntu.com/Bugs/FindRightPackage . I have classified this bug as a bug in linux.

When reporting bugs in the future please use apport by using 'ubuntu-bug' and the name of the package affected. You can learn more about this functionality at https://help.ubuntu.com/community/ReportingBugs.

[Fabio Marconi (fabiomarconi)]

hello
Can you please attach here these files:

[Fabio Marconi (fabiomarconi)]

Hello bjorn
Can you please attach here these files:
/var/log/syslog
/var/log/dmesg
/var/log/kern.log
Thanks
:)Fabio

[bjorn (b973)]

Hello,

Have been out for some time.

I had to give up and move the Openvox board
to another machine. The Proliant is still in the rack
so I could try to move the board back and create the files.

/Bjorn

2010-08-09 12:42, Fabio Marconi skrev:
> Hello bjorn
> Can you please attach here these files:
> /var/log/syslog
> /var/log/dmesg
> /var/log/kern.log
> Thanks
> :)Fabio
>
>

[Fabio Marconi (fabiomarconi)]

We'd like to figure out what's causing this bug for you, but we haven't heard back from you in a while. Could you please provide the requested information? Thanks!

[Fabio Marconi (fabiomarconi)]

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!