Ubuntu
linux-restricted-modules-2.6.20 package

[nvidia-glx-legacy] Running bzflag results in xorg lockup/Xid

Bug #63427 reported by Sitsofe Wheeler
4
Affects Status Importance Assigned to Milestone
linux-restricted-modules-2.6.20 (Ubuntu)
Invalid
Undecided
Unassigned
linux-restricted-modules-2.6.22 (Ubuntu)
Won't Fix
Undecided
Unassigned

Bug Description

Binary package hint: nvidia-glx-legacy

Description of the problem:
The act of running BZflag seems to be able to trigger a bug in the nvidia-glx-legacy driver for me. This problem seems to have gotten worse over the years and is something that only nvidia can fix. This is just a place holder for other people to find.

Steps to reproduce:
1. Install nvidia-glx-legacy and ensure that composite is turned off so 3D acceleration works.
2. Install bzflag .
3. Run bzflag then go to: Join Game -> Start Server -> Start .

Expected result:
Server to fail to start because bzflag-server is not installed. "Failed (exit = 2)." to be displayed.

Actual result:
Server fails to start because bzflag-server is not installed. "Failed (exit = 2)." is displayed. Keyboard stops responding and bzflag will chew up 98% of the CPU until killed off at a virtual terminal. The following is printed in syslog:
NVRM: Xid: 6, PE0002 0404 00120000 00000000 80000000 00120000
(or)
NVRM: Xid: 6, PE0002 0404 00120000 00210000 80000000 00120000

How reproducible is this problem?
It is reproducible every time.

Version information:
nvidia-glx-legacy 1.0.7184+2.6.17.5-5
linux-image-2.6.17-10-386 2.6.17-10.24
linux-restricted-modules-2.6.17-10-386 2.6.17.5-5
nVidia Corporation NV10DDR [GeForce 256 DDR] (rev 10)

See original description
Revision history for this message
Sitsofe Wheeler (sitsofe) wrote :

This hang is still here in Feisty.

Version information:
nvidia-glx-legacy 1.0.7184+2.6.20.2-9.8
linux-image-2.6.20-9-generic 2.6.20-9.16
linux-restricted-modules-2.6.20-9-generic 2.6.20.2-9.8

After triggering the problem and then attempting to initiate a shutdown I eventually found that the machine was actually just alive (but almost entirely unresponsive). Here's what was logged to syslog:

[ 5687.507118] NVRM: Xid: 8, Channel 00000002
[ 5737.566323] BUG: soft lockup detected on CPU#0!
[ 5737.566381] [softlockup_tick+156/240] softlockup_tick+0x9c/0xf0
[ 5737.566413] [update_process_times+51/128] update_process_times+0x33/0x80
[ 5737.566431] [timer_interrupt+133/176] timer_interrupt+0x85/0xb0
[ 5737.566449] [handle_IRQ_event+48/96] handle_IRQ_event+0x30/0x60
[ 5737.566462] [handle_level_irq+141/288] handle_level_irq+0x8d/0x120
[ 5737.566478] [do_IRQ+64/128] do_IRQ+0x40/0x80
[ 5737.566488] [<e8ff7916>] _nv001787rm+0x26/0x2c [nvidia]
[ 5737.567173] [common_interrupt+35/48] common_interrupt+0x23/0x30
[ 5737.567197] [<e9006071>] _nv001708rm+0x15/0x1c [nvidia]
[ 5737.567437] [<e91253b7>] _nv004209rm+0xa7/0xe8 [nvidia]
[ 5737.567758] [<e8ff781f>] _nv001791rm+0x47/0x5c [nvidia]
[ 5737.567985] [<e8ff79d5>] _nv001790rm+0x15/0x1c [nvidia]
[ 5737.568217] [<e91e86c6>] _nv000648rm+0x4e/0x64 [nvidia]
[ 5737.568532] [<e9198aa1>] _nv003133rm+0x201/0x300 [nvidia]
[ 5737.568834] [<e91e752c>] _nv000673rm+0x28/0x1f0 [nvidia]
[ 5737.569126] [<e91e7556>] _nv000673rm+0x52/0x1f0 [nvidia]
[ 5737.569434] [<e910cf1a>] _nv004684rm+0xce/0x4b4 [nvidia]
[ 5737.569735] [<e910cf01>] _nv004684rm+0xb5/0x4b4 [nvidia]
[ 5737.570041] [<e8ff6eaa>] _nv001893rm+0x36/0xe0 [nvidia]
[ 5737.570274] [<e8ff790d>] _nv001787rm+0x1d/0x2c [nvidia]
[ 5737.570499] [<e8ff7916>] _nv001787rm+0x26/0x2c [nvidia]
[ 5737.570726] [<e8ff790d>] _nv001787rm+0x1d/0x2c [nvidia]
[ 5737.570951] [<e8ff7916>] _nv001787rm+0x26/0x2c [nvidia]
[ 5737.571178] [<e8ff790d>] _nv001787rm+0x1d/0x2c [nvidia]
[ 5737.571404] [<e9125a24>] _nv004325rm+0x18/0x48 [nvidia]
[ 5737.571706] [<e8ff7916>] _nv001787rm+0x26/0x2c [nvidia]
[ 5737.571932] [<e8fee887>] _nv001222rm+0x1a3/0x1c8 [nvidia]
[ 5737.572173] [<e9125178>] _nv004173rm+0x88/0x94 [nvidia]
[ 5737.572480] [<e8feeb1b>] _nv001221rm+0x26f/0x2a0 [nvidia]
[ 5737.572707] [__activate_task+33/64] __activate_task+0x21/0x40
[ 5737.572731] [try_to_wake_up+70/1152] try_to_wake_up+0x46/0x480
[ 5737.572751] [<e8fe7b7f>] _nv002873rm+0x7f/0xa4 [nvidia]
[ 5737.572988] [<e900c10d>] _nv001204rm+0x3d/0x618 [nvidia]
[ 5737.573227] [<e900c45b>] _nv001204rm+0x38b/0x618 [nvidia]
[ 5737.573481] [<e900b080>] rm_ioctl+0x1c/0x24 [nvidia]
[ 5737.573725] [copy_from_user+39/96] copy_from_user+0x27/0x60
[ 5737.573744] [<e92156ba>] nv_kern_ioctl+0x2f9/0x382 [nvidia]
[ 5737.574045] [do_ioctl+120/144] do_ioctl+0x78/0x90
[ 5737.574060] [vfs_ioctl+92/672] vfs_ioctl+0x5c/0x2a0
[ 5737.574076] [sys_ioctl+114/144] sys_ioctl+0x72/0x90
[ 5737.574090] [sysenter_past_esp+105/169] sysenter_past_esp+0x69/0xa9
[ 5737.574121] =======================

Sitsofe Wheeler (sitsofe)
description: updated
Revision history for this message
Sitsofe Wheeler (sitsofe) wrote :

This bug is still here in Gutsy:

[ 845.803462] NVRM: Xid: 6, PE0002 0404 000e0000 00210000 80000000 000e0000
[ 930.274870] NVRM: Xid: 8, Channel 00000002

Version information:
nvidia-glx-legacy 1.0.7185+2.6.22.4-14.10
linux-image-generic 2.6.22.14.21
linux-restricted-modules-2.6.22-14-generic 2.6.22.4-14.10

Revision history for this message
Timo Aaltonen (tjaalton) wrote :

I doubt that NVIDIA will update the legacy driver to fix this. Marking as won't fix, people will still find the bug if reporting the same issue.

Changed in linux-restricted-modules-2.6.20:
status: New → Invalid
Changed in linux-restricted-modules-2.6.22:
status: New → Won't Fix
Revision history for this message
LEGOManiac (bzflaglegomaniac) wrote :

For what it's worth, I'm getting the same error, minus the CPU lock-up in Ubuntu 8.10. I am NOT using a nvidia graphics card. I have a VIA chipset with on-board video:

VGA compatible controller [0300]: VIA Technologies, Inc. CN700/P4M800 Pro/P4M800 CE/VN800 [S3 UniChrome Pro] [1106:3344] (rev 01)

Revision history for this message
Sitsofe Wheeler (sitsofe) wrote :

LEGOManiac:
Your bug is almost certainly different - even your symptom is different (you don't get a CPU lockup) as your hardware is different and the driver for that hardware is different. Please check to see if here is an appropriate bug report in launchpad already and if not please file a new bug report (otherwise your issue could remain lost here).

Good luck!

(PS: Make sure you subscribe yourself to bugs otherwise you won't see people replying to you)

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

Other bug subscribers

Remote bug watches

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