Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#6693 - X "soft" crashes

Attached to Project: Arch Linux
Opened by Skottish (skottish) - Friday, 23 March 2007, 23:18 GMT
Last edited by Roman Kyrylych (Romashka) - Saturday, 24 March 2007, 18:11 GMT
Task Type Bug Report
Category System
Status Closed
Assigned To Tom Killian (tomk)
Architecture x86_64
Severity High
Priority Normal
Reported Version 0.7.2 Gimmick
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

I've had "soft" X crashed in the last few days. So far it's only happening when I launch KMPlayer. I start a video, it looks likes X is trying to change something, then both monitors go blank. Sometimes I can CTRL-ALT-DELETE and KDE will refresh both screens; sometimes one screen; sometimes neither. And, sometimes I can switch to another terminal session, sometimes not.

This message is reported from my 'everything.log' file repeatedly:

Mar 23 13:14:16 localhost Losing some ticks... checking if CPU frequency changed.
Mar 23 13:15:36 localhost BUG: soft lockup detected on CPU#0!
Mar 23 13:15:36 localhost
Mar 23 13:15:36 localhost Call Trace:
Mar 23 13:15:36 localhost <IRQ> [<ffffffff802b50aa>] softlockup_tick+0xfa/0x140
Mar 23 13:15:36 localhost [<ffffffff80299bf7>] update_process_times+0x57/0x90
Mar 23 13:15:36 localhost [<ffffffff80279ec4>] smp_local_timer_interrupt+0x34/0x60
Mar 23 13:15:36 localhost [<ffffffff8027a639>] smp_apic_timer_interrupt+0x59/0x80
Mar 23 13:15:36 localhost [<ffffffff80262d16>] apic_timer_interrupt+0x66/0x70
Mar 23 13:15:36 localhost [<ffffffff88459d63>] :nvidia:_nv000819rm+0x13/0x18
Mar 23 13:15:36 localhost [<ffffffff883bef44>] :nvidia:_nv010726rm+0x40/0x82
Mar 23 13:15:36 localhost [<ffffffff883bf0a0>] :nvidia:_nv010725rm+0x11a/0x12a
Mar 23 13:15:36 localhost [<ffffffff883c2d71>] :nvidia:_nv010113rm+0x2719/0x4a0c
Mar 23 13:15:36 localhost [<ffffffff80262d16>] apic_timer_interrupt+0x66/0x70
Mar 23 13:15:36 localhost [<ffffffff883b1503>] :nvidia:_nv010836rm+0x67/0x86
Mar 23 13:15:36 localhost [<ffffffff885a4d83>] :nvidia:_nv012278rm+0xdf7/0x100a
Mar 23 13:15:36 localhost [<ffffffff8835bf9a>] :nvidia:_nv012144rm+0x5e/0xbc
Mar 23 13:15:36 localhost [<ffffffff88312ab1>] :nvidia:_nv003589rm+0x27/0x36
Mar 23 13:15:36 localhost [<ffffffff884daa30>] :nvidia:_nv007834rm+0x416/0x9f0
Mar 23 13:15:36 localhost [<ffffffff8850c6c2>] :nvidia:_nv007240rm+0x30/0x54
Mar 23 13:15:36 localhost [<ffffffff8850c3da>] :nvidia:_nv006972rm+0xc8/0xd8
Mar 23 13:15:36 localhost [<ffffffff8028bd3d>] slice+0xd/0x30
Mar 23 13:15:36 localhost [<ffffffff80405f08>] pci_mmcfg_read+0x68/0x120
Mar 23 13:15:36 localhost [<ffffffff80379944>] pci_bus_read_config_word+0x84/0xb0
Mar 23 13:15:36 localhost [<ffffffff8850c76c>] :nvidia:_nv007238rm+0x26/0x2c
Mar 23 13:15:36 localhost [<ffffffff885876b6>] :nvidia:_nv004932rm+0x2c6/0x4fa
Mar 23 13:15:36 localhost [<ffffffff8857d97f>] :nvidia:_nv004943rm+0x8b/0xd2
Mar 23 13:15:36 localhost [<ffffffff88327faf>] :nvidia:_nv002554rm+0x99/0xbe
Mar 23 13:15:36 localhost [<ffffffff8832cde1>] :nvidia:rm_isr_bh+0x53/0x56
Mar 23 13:15:36 localhost [<ffffffff88630387>] :nvidia:nv_kern_isr_bh+0x16/0x18
Mar 23 13:15:36 localhost [<ffffffff802952a9>] tasklet_action+0x59/0xa0
Mar 23 13:15:36 localhost [<ffffffff8021192f>] __do_softirq+0x5f/0xd0
Mar 23 13:15:36 localhost [<ffffffff8026326c>] call_softirq+0x1c/0x28
Mar 23 13:15:36 localhost [<ffffffff8026f8ec>] do_softirq+0x2c/0x90
Mar 23 13:15:36 localhost [<ffffffff8029522f>] irq_exit+0x3f/0x60
Mar 23 13:15:36 localhost [<ffffffff8026fa16>] do_IRQ+0xc6/0xf0
Mar 23 13:15:36 localhost [<ffffffff80262631>] ret_from_intr+0x0/0xa
Mar 23 13:15:36 localhost <EOI>
Mar 23 13:15:37 localhost BUG: soft lockup detected on CPU#0!


This is the only thing that I've noticed in the logs that seems out of place.

The kernel that this was happening with is kernel26ck-2.6.20.1.ck1. It was upgraded today to kernel26ck 2.6.20.3.ck1.

nvidia-ck 1.0.9755
kmplayer 0.9.4

This task depends upon

Closed by  Tom Killian (tomk)
Monday, 02 April 2007, 11:15 GMT
Reason for closing:  Fixed
Additional comments about closing:  Reported fixed by original poster after kernel26ck package upgrade.
Comment by Jan de Groot (JGC) - Saturday, 24 March 2007, 14:17 GMT
Assigning to Tom, it's either a bug in the CK kernel, or something in the closed nvidia drivers. Try using a normal stock kernel if you want this fixed the easy way.
Comment by Skottish (skottish) - Saturday, 24 March 2007, 16:57 GMT
Thanks for looking into this.

Since I just upgraded my kernel, I'm not sure if it's going to happen again. If it does, what all do you need from me?
Comment by Skottish (skottish) - Saturday, 24 March 2007, 16:59 GMT
Egads! I forgot to mark this for x64_86. Sorry.
Comment by Tom Killian (tomk) - Sunday, 25 March 2007, 20:28 GMT
Did it start with 2.6.20.1.ck1, or was it there with previous versions? Has it occurred yet with 2.6.20.3.ck1?
Comment by Skottish (skottish) - Sunday, 25 March 2007, 21:46 GMT
This particular problem started with 2.6.20.1.ck1. It hasn't happened since the last kernel update. I think that this bug report should be closed as fixed.

Loading...