System freeze with Intel Atom D510MO

Bug #676467 reported by Mario B.
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
capi4hylafax (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

Binary package hint: capi4hylafax

I just installed a fresh Ubuntu Server 10.10 i386 with hylafax. "/etc/init.d/capi4hylafax start" freezes the system. This does not happen with e.g. an old ABit KT7A mainboard (Athlon 1.2 GHz). It only happens with an Intel Atom D510MO and it did before with Ubuntu Server 10.04

Steps to reproduce:
- Get a modern Intel Atom mainboard
- Install Ubuntu Server i386, version 10.04 or 10.10
- I used ext4 without LVM and checked "SSH Server" and "Mail Server" but that should not be necessary to run into problems

- Login and do a "sudo su"
- apt-get update
- apt-get upgrade
- wget ftp://ftp.in-berlin.de/pub/capi4linux/firmware/b1/3-11-03/b1.t4
- mkdir /lib/isdn
- mv b1.t4 /lib/isdn
- apt-get install capiutils
- Delete comment in /etc/isdn/capi.conf for "b1pci"
- apt-get install capi4hylafax
- Delete comment in /etc/default/capi4hylafax for "run_capi4hylafax=1"
 - /etc/init.d/capi4hylafax start
-> system freezes

A restart ends in a freeze as well because capi4hylafax will be started automatically.

Revision history for this message
Thomas Broda (spam-magnet) wrote :

I've got exactly the same issue on my Athlon D510 system.

I'm using Ubuntu 12.04.01, 64Bit with an AVM B1 card. The capi4hylafax version is 1:01.03.00.99.svn.300-16. The system will freeze right after starting capi4hylafax.

This should really be investigated.

Revision history for this message
Martin Gmeindl (martin-gmeindl) wrote :

Same problem with Ubuntu 12.04 LTS, capi4hylafax and B1 Card on a new asus mainboard with AMD FX-4170 Quad-Core Processor.
After some testing i will send more details.

Revision history for this message
Martin Gmeindl (martin-gmeindl) wrote :

It is not looking ood for this fine B1 card.
It seemed to work fine on Ubuntu 12.10 but after some time even without a aplication running we get a
"BUG: soft lockup - CPU#1 stuck for 22s! []
Stack:"
after the driver is loaded.
This happens on a ASUS M5A97 with quadcore AMD CPU and on a AS Rock with Intel dual core CPU
Sometimes the driver can start and the issue occurs when i start c2faxrecv.
Then we have:
"BUG: soft lockup - CPU#1 stuck for 22s! [c2faxrecv:5619]
Stack:
Call Trace:
Code:"(some Hex-Nubers)
The message comes every few seconds somtimes with a
<IRQ>
<EOI>

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in capi4hylafax (Ubuntu):
status: New → Confirmed
Revision history for this message
Martin Gmeindl (martin-gmeindl) wrote :

there is a relation to the config file /etc/hylafax/config.faxCAPI
very simple configfiles are working.
More complex configuration with e.g. DDIOffset set are not working.
I tried it now on a 8.04 hardy server i386 and everything is working there even with a lot of nonsense in the configfile.
Since it is not only related to Intel Atom boards the thread should possibly get another name

Revision history for this message
vbargsten (vbargsten) wrote :

When migrating an old server, capi4hylafax was triggering kernel panics on the new system (opensuse though). So, if anyone ever reads this thread, here is what I found:
1) do not use the "newest" firmware for your b1 pci card but version 3.10-02
2) there are some corruptions happening due to simultaneous write access to the same object from different threads within capi4hylafax. This garbles the settings used for the card. I fixed one, when starting a receive thread; however, multiple receive threads per device still have this problem and should be avoided (just use one full config section for each channel). I have put the development code here (all patches from debian/suse have been integrated) https://github.com/vbargsten/capi4hylafax

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.