Red Hat Bugzilla – Bug 428772
Armacycles/Armagetron Advanced segmentation fault
Last modified: 2008-08-02 19:40:36 EDT
Description of problem:
While playing armacycles/armagetron advanced, the game occasionally crashes
without warning, because of a segmentation fault in the kernel (exists on
184.108.40.206-52.fc7 as well as past several kernel releases in F7 and has occurred
in F8 as well).
Version-Release number of selected component (if applicable):
Very. It happens after playing for a time, but the time does not seem to be a
consistent time. I haven't timed it, and it surprises me every time, but it
almost always crashes after playing 1-2 hours.
Steps to Reproduce:
1. Start game.
2. Play for 1-2 hours.
3. Act surprised when it quits.
Game quits unexpectedly.
Game continues playing.
content of /var/log/messages :
Jan 14 22:34:37 lappy kernel: armacyclesad: segfault at 0000000a eip 00b60
f46 esp b7d8dd04 error 4
hardware profile from /sbin/lspci :
00:00.0 Host bridge: Intel Corporation Mobile 945GM/PM/GMS, 943/940GML and 945GT
Express Memory Controller Hub (rev 03)
00:02.0 VGA compatible controller: Intel Corporation Mobile 945GM/GMS,
943/940GML Express Integrated Graphics Controller (rev 03)
00:02.1 Display controller: Intel Corporation Mobile 945GM/GMS, 943/940GML
Express Integrated Graphics Controller (rev 03)
00:1b.0 Audio device: Intel Corporation 82801G (ICH7 Family) High Definition
Audio Controller (rev 01)
00:1c.0 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 1
00:1c.1 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 2
00:1c.3 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 4
00:1d.0 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI
Controller #1 (rev 01)
00:1d.1 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI
Controller #2 (rev 01)
00:1d.2 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI
Controller #3 (rev 01)
00:1d.3 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI
Controller #4 (rev 01)
00:1d.7 USB Controller: Intel Corporation 82801G (ICH7 Family) USB2 EHCI
Controller (rev 01)
00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev e1)
00:1f.0 ISA bridge: Intel Corporation 82801GBM (ICH7-M) LPC Interface Bridge
00:1f.2 IDE interface: Intel Corporation 82801GBM/GHM (ICH7 Family) SATA IDE
Controller (rev 01)
00:1f.3 SMBus: Intel Corporation 82801G (ICH7 Family) SMBus Controller (rev 01)
02:00.0 Ethernet controller: Broadcom Corporation BCM4401-B0 100Base-TX (rev 02)
0c:00.0 Network controller: Intel Corporation PRO/Wireless 3945ABG Network
Connection (rev 02)
I tried to reproduce this with what I've got.
"Hardware": Virtual Box 1.5.4 non-gnu version running on Kubuntu Gutsy Gibbon,
with tools installed. That means, of course, the game will use software
Software: FC 8 with latest updates, that is
armacyclesad: 0.2.8.2.1-5.fc8.i386 and vanilla 0.2.8.2.1 compiled from source
The system defaults were only changed in one point, the screen saver was
disabled. Game settings, apart from player name, spectator mode and screen
resolution, were also at default.
The test: switch player 1 to spectator mode, set up a game between AIs only in
320x200 screen resolution, and leave it running overnight. Some network games
were spectated as well, but most servers are set to kick idle spectators. It
would have been a better test to actually play, but I'm not really willing
enduring software rendering and virtual machine typical timer glitches for
No crash was observed so far. This mostly rules out errors in the game, the
kernel and X11 as causes for the reported crashes, leaving the hardware itself
or the device drivers as the most probable cause. I'll repeat the tests over
the following nights, maybe extend them to remote GLX sessions, and report it
if anything new happens.
I can't reproduce this on my real hardware, either, on f8. Might want to see if
a memtest86+ run helps. In case youhadn't done this in Fedora before, just, as
yum install memtest86+
then reboot, and choose Memtest from your GRUB menu.
The information we've requested above is required in order
to review this problem report further and diagnose/fix the
issue if it is still present. Since there have not been any
updates to the report since thirty (30) days or more since we
requested additional information, we're assuming the problem
is either no longer present in the current Fedora release, or
that there is no longer any interest in tracking the problem.
Setting status to "CLOSED INSUFFICIENT_DATA". If you still
experience this problem after updating to our latest Fedora
release and can provide the information previously requested,
please feel free to reopen the bug report.
Thank you in advance.
Note that maintenance for Fedora 7 will end 30 days after the GA of Fedora 9.