You are not logged in.

#1 2008-09-18 15:28:59

Crimsonknave
Member
Registered: 2008-09-18
Posts: 23

Total system lockup

I'm somewhat new to arch, but not to linux and recently my system has been locking up and freezing.  It takes a hard restart to get it back, Ctrl+Alt+Delete does nothing, Caps Lock does nothing.  I can't seem to find a pattern between when it crashes, it has crashed once while I was using it, but usually seems to be when I am away.  I'm using 64 bit linux and my system is up to date.  I've got an nVidia card and using their drivers, I am also using compiz-fusion.  I've seen this happen when using KDE and Gnome.  The only clue I've got atm is a bit from the everything.log that seems to happen each time it crashes.  Also, I have opera, azureus running more or less constantly I don't think any other programs have been running each time.

Sep 18 07:51:06 shiny Xorg[3729]: segfault at 100000008 ip 7f802eda4f46 sp 7fff36fb04e0 error 4 in ld-2.8.so[7f802ed98000+1c000]
Sep 18 07:51:06 shiny NVRM: Xid (0001:00): 6, PE0001
Sep 18 07:51:12 shiny opera[4176] general protection ip:7f2d6beb622e sp:7fff7454e1d0 error:0 in libqt-mt.so.3.3.8 (deleted)[7f2d6b8b9000+7fc000]
Sep 18 07:51:13 shiny gdm-binary[3725]: WARNING: gdm_slave_xioerror_handler: Fatal X error - Restarting :0
Sep 18 07:51:15 shiny NVRM: Xid (0001:00): 43, CMDre 00000000 00000000 00000000 00000001 00000001
 Sep 16 16:49:41 shiny Xorg[3773]: segfault at 6003008b8 ip 7f05eea4cf46 sp 7ffff6c5a710 error 4 in ld-2.8.so[7f05eea40000+1c000]
Sep 16 16:49:41 shiny NVRM: Xid (0001:00): 6, PE0001
Sep 16 16:49:45 shiny NVRM: Xid (0001:00): 6, PE0003
Sep 16 16:49:47 shiny opera[4356] general protection ip:7fa4717b622e sp:7fff79e50a90 error:0 in libqt-mt.so.3.3.8[7fa4711b9000+7fc000]
Sep 16 16:49:48 shiny gdm-binary[3769]: WARNING: gdm_slave_xioerror_handler: Fatal X error - Restarting :0
Sep 16 16:49:52 shiny NVRM: Xid (0001:00): 43, CMDre 00000000 00000000 00000000 00000001 00000001
Sep 16 16:49:55 shiny NVRM: Xid (0001:00): 6, PE0001
Sep 16 16:49:55 shiny NVRM: Xid (0001:00): 43, CMDre 00000000 00000000 00000000 00000001 00000001

Everything else in the log is 10 or more minutes before or from when I rebooted.  The opera error seems to be in all of them so perhaps it is related to that?

Let me know what other information I should post.

Offline

#2 2008-09-19 01:15:05

dav7
Member
From: Australia
Registered: 2008-02-08
Posts: 674

Re: Total system lockup

It looks like X is crashing. And based on the times from the logs, it seems like your system continues to do stuff for 9-10 seconds, suggesting something other than a complete crash.

X could simply be hanging up and you might still have a functional system. Try CTRL+ALT+Backspace next crash, although I doubt that will work. For a true test, try sshing to your machine when it crashes (if you can). There's a high possibility (IMHO) that you'll be able to ssh. In which case it's X's (and in turn almost certainly a driver's) fault.

-dav7


Windows was made for looking at success from a distance through a wall of oversimplicity. Linux removes the wall, so you can just walk up to success and make it your own.
--
Reinventing the wheel is fun. You get to redefine pi.

Offline

#3 2008-09-19 05:53:19

Dheart
Member
From: Sofia, Bulgaria
Registered: 2006-10-26
Posts: 956

Re: Total system lockup

You could post us your hardware for starters...
Anyway X crashes are annoying and you can't get a away with ctrl + alt + backspace.


My victim you are meant to be
No, you cannot hide nor flee
You know what I'm looking for
Pleasure your torture, I will endure...

Offline

#4 2008-09-19 14:38:24

Crimsonknave
Member
Registered: 2008-09-18
Posts: 23

Re: Total system lockup

Sorry, when I said Ctrl+Alt+Delete I meant Backspace, it does nothing and I can't get into a virtual terminal either.  I will try to ssh in the next time it happens, though I usually find when the capslock button won't even light up the light on my keyboard things are pretty dead.

I've got a Intel Core 2 Duo E8400 processor, Nvidia GeForce 9500GT video card, also have a hauppauge HVR-1800 card I haven't got to work yet (College doesn't have digital cable and the drivers only support digital cable atm).

Also the freezes seem to have been increasing in frequency, and the one last night had some different errors with it.

Sep 18 23:53:37 shiny NVRM: Xid (0001:00): 26, Ch 00000000 M 00000860 D ffffffff intr 04400000
Sep 18 23:53:37 shiny NVRM: Xid (0001:00): 26, Ch 00000000 M 00000860 D ffffffff intr 00400000
Sep 18 23:53:37 shiny NVRM: Xid (0001:00): 26, Ch 00000000 M 00000860 D ffffffff intr 04400000
Sep 18 23:53:37 shiny NVRM: Xid (0001:00): 26, Ch 00000000 M 00000860 D 00ffffff intr 00400000
Sep 18 23:53:37 shiny NVRM: Xid (0001:00): 26, Ch 00000000 M 00000860 D ffffffff intr 04400000
Sep 18 23:53:37 shiny NVRM: Xid (0001:00): 26, Ch 00000000 M 00000860 D 00ffffff intr 00400000
Sep 18 23:53:37 shiny NVRM: Xid (0001:00): 26, Ch 00000000 M 00000860 D ffffffff intr 04400000
Sep 18 23:53:37 shiny irq 16: nobody cared (try booting with the "irqpoll" option)
Sep 18 23:53:37 shiny Pid: 3730, comm: Xorg Tainted: P          2.6.26-ARCH #1
Sep 18 23:53:37 shiny
Sep 18 23:53:37 shiny Call Trace:
Sep 18 23:53:37 shiny <IRQ>  [<ffffffff802707de>] __report_bad_irq+0x1e/0x80
Sep 18 23:53:37 shiny [<ffffffff80270af0>] note_interrupt+0x2b0/0x2e0
Sep 18 23:53:37 shiny [<ffffffff802713ed>] handle_fasteoi_irq+0xdd/0x100
Sep 18 23:53:37 shiny [<ffffffff8020ff1c>] do_IRQ+0x7c/0x100
Sep 18 23:53:37 shiny [<ffffffff8020cb3d>] ret_from_intr+0x0/0x19
Sep 18 23:53:37 shiny <EOI>  [<ffffffff803c8040>] pci_conf1_read+0x0/0x100
Sep 18 23:53:37 shiny [<ffffffff802143a8>] native_read_tsc+0x8/0x20
Sep 18 23:53:37 shiny [<ffffffff8033ad5e>] __delay+0x7e/0xe0
Sep 18 23:53:37 shiny [<ffffffffa068ae63>] :nvidia:os_delay+0x173/0x2a0
Sep 18 23:53:37 shiny [<ffffffffa05c4297>] :nvidia:_nv004032rm+0x9/0xe
Sep 18 23:53:37 shiny [<ffffffffa060e974>] :nvidia:_nv002729rm+0x27c/0x296
Sep 18 23:53:37 shiny [<ffffffffa02e5b52>] :nvidia:_nv013994rm+0x100/0x158
Sep 18 23:53:37 shiny [<ffffffffa053e6fb>] :nvidia:_nv005871rm+0x2ac/0x42f
Sep 18 23:53:37 shiny [<ffffffffa046b951>] :nvidia:_nv009691rm+0x153/0x28b
Sep 18 23:53:37 shiny [<ffffffffa05fa139>] :nvidia:_nv003318rm+0x194/0x29b
Sep 18 23:53:37 shiny [<ffffffffa05f9e98>] :nvidia:_nv003317rm+0x576/0x683
Sep 18 23:53:37 shiny [<ffffffffa046ecb2>] :nvidia:_nv009374rm+0xbe5/0x10f0
Sep 18 23:53:37 shiny [<ffffffffa046ec7a>] :nvidia:_nv009374rm+0xbad/0x10f0
Sep 18 23:53:37 shiny [<ffffffffa044f66c>] :nvidia:_nv009380rm+0x44/0x4e
Sep 18 23:53:37 shiny [<ffffffffa046f281>] :nvidia:_nv009368rm+0xc4/0x99f
Sep 18 23:53:37 shiny [<ffffffffa0536e93>] :nvidia:_nv005860rm+0x49f/0x557
Sep 18 23:53:37 shiny [<ffffffffa0475bb9>] :nvidia:_nv009304rm+0x177/0x1de
Sep 18 23:53:37 shiny [<ffffffffa055bd2c>] :nvidia:_nv003038rm+0x1c5/0x4ee
Sep 18 23:53:37 shiny [<ffffffffa055b49c>] :nvidia:_nv003033rm+0xa9/0x2fc
Sep 18 23:53:37 shiny [<ffffffffa055b321>] :nvidia:_nv003036rm+0xda/0x1ac
Sep 18 23:53:37 shiny [<ffffffffa055af70>] :nvidia:_nv003039rm+0x33/0x30a
Sep 18 23:53:37 shiny [<ffffffffa05ca5e0>] :nvidia:_nv003011rm+0x50/0x85
Sep 18 23:53:37 shiny [<ffffffffa05cc3fc>] :nvidia:rm_free_unused_clients+0x90/0xe1
Sep 18 23:53:37 shiny [<ffffffffa068681c>] :nvidia:nv_kern_ctl_close+0x6c/0x100
Sep 18 23:53:37 shiny [<ffffffff802a6825>] __fput+0xb5/0x1c0
Sep 18 23:53:37 shiny [<ffffffff802a2cab>] filp_close+0x5b/0x90
Sep 18 23:53:37 shiny [<ffffffff8023cb36>] put_files_struct+0x76/0xe0
Sep 18 23:53:37 shiny [<ffffffff8023e54d>] do_exit+0x1dd/0x7a0
Sep 18 23:53:37 shiny [<ffffffff8023eb43>] do_group_exit+0x33/0xa0
Sep 18 23:53:37 shiny [<ffffffff802499e6>] get_signal_to_deliver+0x286/0x3c0
Sep 18 23:53:37 shiny [<ffffffff8020b7cf>] do_notify_resume+0x10f/0x990
Sep 18 23:53:37 shiny [<ffffffff8022f55c>] task_rq_lock+0x5c/0xa0
Sep 18 23:53:37 shiny [<ffffffff8022f8ae>] try_to_wake_up+0x8e/0x1a0
Sep 18 23:53:37 shiny [<ffffffff80466b62>] thread_return+0x61/0x53f
Sep 18 23:53:37 shiny [<ffffffff80247675>] signal_wake_up+0x25/0x40
Sep 18 23:53:37 shiny [<ffffffff80247a13>] send_signal+0x133/0x350
Sep 18 23:53:37 shiny [<ffffffff8020cc84>] retint_signal+0x50/0x9c
Sep 18 23:53:37 shiny
Sep 18 23:53:37 shiny handlers:
Sep 18 23:53:37 shiny [<ffffffffa0033d80>] (ata_sff_interrupt+0x0/0x2e0 [libata])
Sep 18 23:53:37 shiny [<ffffffffa0061a70>] (usb_hcd_irq+0x0/0xa0 [usbcore])
Sep 18 23:53:37 shiny [<ffffffffa0b5dea0>] (cx23885_irq+0x0/0x510 [cx23885])
Sep 18 23:53:37 shiny [<ffffffffa0686e80>] (nv_kern_isr+0x0/0xa0 [nvidia])
Sep 18 23:53:37 shiny Disabling IRQ #16
Sep 18 23:53:44 shiny gdm-binary[3724]: WARNING: gdm_slave_xioerror_handler: Fatal X error - Restarting :0

So, yeah I'm thinking it would be nvidia drivers.  My Xorg.conf is here if it helps, it got copied from my old computer which had the same monitor setup but a different card:

Section "ServerLayout"
    Identifier     "Layout0"
    Screen      0  "Screen0"
    InputDevice    "Keyboard0" "CoreKeyboard"
    InputDevice    "Mouse0" "CorePointer"
EndSection

Section "Files"
    RgbPath         "/usr/lib/X11/rgb"
EndSection

Section "Module"
    Load           "dbe"
    Load           "extmod"
    Load           "type1"
    Load           "freetype"
    Load           "glx"
EndSection
Section "ServerFlags"
        Option          "Xinerama" "0"
EndSection

Section "InputDevice"
    # generated from default
    Identifier     "Mouse0"
    Driver         "mouse"
    Option         "Protocol" "auto"
    Option         "Device" "/dev/psaux"
    Option         "Emulate3Buttons" "no"
    Option         "ZAxisMapping" "4 5"
EndSection

Section "InputDevice"
    # generated from default
    Identifier     "Keyboard0"
    Driver         "keyboard"
EndSection

Section "Monitor"
    Identifier     "Monitor0"
    VendorName     "Unknown"
    ModelName      "Unknown"
    HorizSync       30.0 - 110.0
    VertRefresh     50.0 - 150.0
    Option         "DPMS"
EndSection

Section "Device"
    Identifier     "Device0"
    Driver         "nvidia"
    VendorName     "NVIDIA Corporation"
EndSection

Section "Screen"
    Identifier     "Screen0"
    Device         "Device0"
    Monitor        "Monitor0"
    DefaultDepth    24
    Option         "TwinView" "1"
    Option         "MetaModes" "1280x1024,1280x1024;1280x1024,0x0;1024x768,1024x768;1024x768,0x0;800x600,800x600;800x600_75,0x0;640x480,0x0"
    Option         "NoLogo" "true"
    Option         "RenderAccel" "true"
    SubSection     "Display"
        Depth       24
    EndSubSection
EndSection

Offline

#5 2008-09-20 06:13:52

Dheart
Member
From: Sofia, Bulgaria
Registered: 2006-10-26
Posts: 956

Re: Total system lockup

Back up your xorg.conf, than delete the current one and generate new (for example hwd -x or xorgconfig/cfg or nvidia xconfing tool) and see whether there are crashes again or not. If there are crashes again replace nvidia with nv (or vesa, I don't know whether nv supports your card) and see if there are crashes. If there aren't any more crashes it means an nvidia issue - try the beta driver...


My victim you are meant to be
No, you cannot hide nor flee
You know what I'm looking for
Pleasure your torture, I will endure...

Offline

#6 2008-09-20 07:18:49

dav7
Member
From: Australia
Registered: 2008-02-08
Posts: 674

Re: Total system lockup

Not so on-topic but has a bit of relation anyway:

...I usually find when the capslock button won't even light up the light on my keyboard things are pretty dead.

That is very true, I use numlock here myself. However, since X has "direct" hardware drivers for the mouse and keyboard, it fully intercepts and interprets their I/O when X is the current (active) terminal (yes, terminal, since X is, more or less, a terminal system).

Therefore, the num/caps lock LEDs locking up could simply be the result of a hang inside X itself caused by rogue drivers that has fallen through to the mouse and/or keyboard. It's happened to me a few times, so yeah. tongue

-dav7


Windows was made for looking at success from a distance through a wall of oversimplicity. Linux removes the wall, so you can just walk up to success and make it your own.
--
Reinventing the wheel is fun. You get to redefine pi.

Offline

#7 2008-09-20 15:13:29

Crimsonknave
Member
Registered: 2008-09-18
Posts: 23

Re: Total system lockup

Good to know about X and caps-lock.

I shall get me a new Xorg.conf file and see if that fixes it.  I thought that I had fixed it by just using fluxbox and not compiz inside gnome or KDE, but it crashed last night while I was playing Warhammer Online via wine.  The screen froze and stayed frozen for 4-5 seconds then it started flashing black until it finally turned off.  I'm also going to try adding the irqpoll boot option as the 'irq nobody cared' message told me to.

Offline

#8 2008-09-21 21:55:19

Crimsonknave
Member
Registered: 2008-09-18
Posts: 23

Re: Total system lockup

Well, I made myself a new Xorg.conf file, but that didn't not fix the issue, adding the 'irqpoll' option at boot up only removed some of the errors, which left only gdm-binary errors.  So I removed gdm from startup and replaced it with kdm, so far I haven't gotten any errors, but it has only been about half a day.

Offline

#9 2008-09-26 12:34:54

Crimsonknave
Member
Registered: 2008-09-18
Posts: 23

Re: Total system lockup

Well, just posting an update.  It started to happen more and more often, so I reinstalled.  The problem is more or less gone, it does't crash when I'm not there and so far has only crashed while playing Warhammer Online via wine and doesn't do that often (Once every 6ish hours). 

I'm open to any suggestions of other things I can try, I never did try removing the nvidia drivers or using the beta ones.  I can't really test using the nv or vesa driver now as it only crashes when I'm playing a game and I'd need 3d acceleration.  Would I look for the beta drivers on their site?

Offline

#10 2008-09-26 13:01:29

krigun
Member
From: Norway
Registered: 2005-06-06
Posts: 122
Website

Re: Total system lockup

Crimsonknave wrote:

Well, just posting an update.  It started to happen more and more often, so I reinstalled.  The problem is more or less gone, it does't crash when I'm not there and so far has only crashed while playing Warhammer Online via wine and doesn't do that often (Once every 6ish hours). 

I'm open to any suggestions of other things I can try, I never did try removing the nvidia drivers or using the beta ones.  I can't really test using the nv or vesa driver now as it only crashes when I'm playing a game and I'd need 3d acceleration.  Would I look for the beta drivers on their site?

Hi,

Ill post here just out of sympathy. A while back (a year or so) I had the display freeze stuff happening myself on my nvidia 7900 GS hardware. It seemed as the system was locked but the keyboard worked, so I was able to run CTRL-ALT-DEL which would reboot the computer, while my frozen desktop image followed all the way down. Bet if you try another graphics card that it doesnt happen. I think faulty nvidia drivers are to blame here. Try the 'nv' or 'vesa' driver in xorg for fun, at least you won't be "freezing" anymore.

OR: Try an ATI card next time. You might not be able to squeeze as much juice out of them as you would on windows (they have been focussing their powers on DirectToHell related technologies), but the Linux drivers that Nvidia poops out are of very varying quality. My ATI machine has not had that freezing problem yet.

Offline

Board footer

Powered by FluxBB