Go Back   nV News Forums > Linux Support Forums > NVIDIA Linux

Newegg Daily Deals

Reply
 
Thread Tools
Old 01-13-11, 02:51 PM   #1
Jakob
Registered User
 
Join Date: Jan 2011
Location: Stockholm, Sweden
Posts: 6
Default Nvidia NVS 3100M on Ubuntu 10.10 freeze - SOLVED!!!! .. I hope ;)

Background
=======
My Ubuntu 10.10 installation suddenly started to freeze X. The mouse would not move and the keyboard became unresponsive. Only option was to do a hard shutdown. Most of the time the crashes was triggered by mouse movements when surfing through a browser like Firefox or Chromium, but it occasionally also occurred at other times, even spontaneous without any user action

Log files contained messages like:
NVRM: os_pci_init_handle: invalid context!
NVRM: os_schedule: Attempted to yield the CPU while in atomic or interrupt context
NVRM: os_raise_smp_barrier(), invalid context!


It was possible to ssh into the machine when X was in frozen state, i.e. no real system crash.

The system crashed more frequently when it was running hot, which even affected the parallel Windows install and made it impossible to boot any OS installed on the machine. (Letting the computer rest for about 30 minutes or more made it possible to boot again)

System
=====
HP EliteBook 8440p
Nvidia NVS 3100M
Nvidia drivers (260.19.06 and 260.19.29)
Intel I7
Ubuntu 10.10 (both 32-bit and 64-bit)


The story
======
The computer came with 32-bit Win7 pre-installed. I also installed a 32-bit Ubuntu 10.04 in parallel and both systems ran flawless on this computer. I later upgraded Ubuntu to a 32-bit 10.10 and it ran fine for over a month. But sometime around 20 Dec it started to freeze. I frequently upgraded the system, but I haven't found any updates directly related to this problem.

I tried various solutions with different kernel options during boot up and different settings in the Nvidia X Server Settings application. Nothing worked. Then I did a completely fresh install of Ubuntu 10.10, but this time the 64-bit version to see if that made any difference. I added the x-swat repositories and upgraded to the latest driver (260.19.29) Still crashes.

I also tried the Nouveau driver, but the computer crashed even with that driver. And at the same time it also started to crash from within Windows and finally it became impossible to boot into any OS. This made me believe it was hardware failure and I gave up. Now I believe I was trying so much with a broken system that it was simply over heated. Letting the computer rest for 15-20 minutes didn't help.

One day later I really needed a document on the computer, so I made a last effort to boot into Windows. And it ran flawlessly! I realised that had cooled down, so I booted into Linux and immediately removed the Nvidia driver and installed Nouveau instead. It still ran without any crashes. So I made one last effort with the Nvidia drivers (260.19.29) from the x-swat repositories. Directly after the install I thought I had to make some kind of adjustment to make it work this time. So I went into the Nvidia X Server Settings one more time. This time I found an option that I had missed before...

The solution
========
In Nvidia X Server Settings there is an option to "Save to X Configuration File". Do you remember those nasty configuration files? We usually don't have to mess with them any more since a couple of years back, but it wasn't too long ago when I remember spending quite some time editing those files. Well... press the button, type your password and the application is creating a new Xorg.conf file in /etc/X11. Now reboot! When ubuntu starts it looks just normal, but a Nvidia splash is displayed for half a second before the login prompt. And the system finally seems to be stable!

My system has been running fine for a few days now and I'm actually starting to believe this works. I've got burned before, but now I'm actually starting to believe for real. I'm gradually loading it more and more. So far its responding fine to daily usage, which in my case involves some internet surfing through firefox (static pages, ajaxy pages, flash movies, etc) and Java development using Java IDEs and application servers. I haven't let it go into suspended mode yet and I haven't played any games. But I usually don't play any games anyway, so I don't know if I'm going to try it.

For reference: I reported some of the problems I had in this thread: http://www.nvnews.net/vbulletin/showthread.php?t=158172

I really hope this helps someone!
Jakob is offline   Reply With Quote
Old 01-13-11, 03:54 PM   #2
zoomy942
 
zoomy942's Avatar
 
Join Date: Dec 2003
Location: Bellevue, ID
Posts: 5,338
Send a message via AIM to zoomy942 Send a message via MSN to zoomy942
Default Re: Nvidia NVS 3100M on Ubuntu 10.10 freeze - SOLVED!!!! .. I hope ;)

great post! thanks for the indepth info!
zoomy942 is offline   Reply With Quote
Old 01-16-11, 08:33 AM   #3
Jakob
Registered User
 
Join Date: Jan 2011
Location: Stockholm, Sweden
Posts: 6
Default Re: Nvidia NVS 3100M on Ubuntu 10.10 freeze - SOLVED!!!! .. I hope ;)

And now it crashed again

Same as before. It froze when I entered a web page through Firefox. No response from mouse or keyboard. Fan run at maximum speed after about 10 seconds. I don't know to think of this anymore? Is it the nVidia dirver, the Intel chipset or a kernel bug? I'm really out of ideas and I'll probably give up on this for now

This is what kern.log says:
Jan 16 12:15:24 hp8440p kernel: [ 5929.489723] wlan0: authenticate with 00:22:6b:86:78:d5 (try 1)
Jan 16 12:15:24 hp8440p kernel: [ 5929.503710] wlan0: authenticated
Jan 16 12:15:24 hp8440p kernel: [ 5929.512463] wlan0: associate with 00:22:6b:86:78:d5 (try 1)
Jan 16 12:15:24 hp8440p kernel: [ 5929.535452] wlan0: RX AssocResp from 00:22:6b:86:78:d5 (capab=0x411 status=0 aid=3)
Jan 16 12:15:24 hp8440p kernel: [ 5929.535460] wlan0: associated
Jan 16 14:13:50 hp8440p kernel: [13017.405506] hda-intel: spurious response 0x0:0x0, last cmd=0x470e00
Jan 16 14:13:50 hp8440p kernel: [13017.405510] hda-intel: spurious response 0x0:0x0, last cmd=0x470e00
Jan 16 14:13:50 hp8440p kernel: [13017.405511] hda-intel: spurious response 0x0:0x0, last cmd=0x470e00
Jan 16 14:13:50 hp8440p kernel: [13017.405513] hda-intel: spurious response 0x0:0x0, last cmd=0x470e00
Jan 16 14:13:50 hp8440p kernel: [13017.405514] hda-intel: spurious response 0x0:0x0, last cmd=0x470e00
Jan 16 14:13:50 hp8440p kernel: [13017.405515] hda-intel: spurious response 0x0:0x0, last cmd=0x470e00
Jan 16 14:13:50 hp8440p kernel: [13017.405517] hda-intel: spurious response 0x0:0x0, last cmd=0x470e00
Jan 16 14:13:50 hp8440p kernel: [13017.405518] hda-intel: spurious response 0x0:0x0, last cmd=0x470e00
Jan 16 14:13:50 hp8440p kernel: [13017.405519] hda-intel: spurious response 0x0:0x0, last cmd=0x470e00
Jan 16 14:13:50 hp8440p kernel: [13017.405521] hda-intel: spurious response 0x0:0x0, last cmd=0x470e00
Jan 16 14:13:50 hp8440p kernel: [13017.405522] hda-intel: spurious response 0x0:0x0, last cmd=0x470e00
Jan 16 14:13:50 hp8440p kernel: [13017.405523] hda-intel: spurious response 0x0:0x0, last cmd=0x470e00
Jan 16 14:13:50 hp8440p kernel: [13017.405525] hda-intel: spurious response 0x0:0x0, last cmd=0x470e00
Jan 16 14:13:50 hp8440p kernel: [13017.405526] hda-intel: spurious response 0x0:0x0, last cmd=0x470e00
Jan 16 14:13:50 hp8440p kernel: [13017.405527] hda-intel: spurious response 0x0:0x0, last cmd=0x470e00
Jan 16 14:13:50 hp8440p kernel: [13017.405529] hda-intel: spurious response 0x0:0x0, last cmd=0x470e00
Jan 16 14:13:50 hp8440p kernel: [13017.405530] hda-intel: spurious response 0x0:0x0, last cmd=0x470e00
Jan 16 14:13:50 hp8440p kernel: [13017.405531] hda-intel: spurious response 0x0:0x0, last cmd=0x470e00
Jan 16 14:13:50 hp8440p kernel: [13017.405533] hda-intel: spurious response 0x0:0x0, last cmd=0x470e00
Jan 16 14:13:50 hp8440p kernel: [13017.405534] hda-intel: spurious response 0x0:0x0, last cmd=0x470e00
Jan 16 14:13:50 hp8440p kernel: [13017.405535] hda-intel: spurious response 0x0:0x0, last cmd=0x470e00
Jan 16 14:13:50 hp8440p kernel: [13017.405537] hda-intel: spurious response 0x0:0x0, last cmd=0x470e00
Jan 16 14:13:50 hp8440p kernel: [13017.405538] hda-intel: spurious response 0x0:0x0, last cmd=0x470e00
Jan 16 14:13:50 hp8440p kernel: [13017.405539] hda-intel: spurious response 0x0:0x0, last cmd=0x470e00
Jan 16 14:13:50 hp8440p kernel: [13017.405541] hda-intel: spurious response 0x0:0x0, last cmd=0x470e00
Jan 16 14:13:50 hp8440p kernel: [13017.405542] hda-intel: spurious response 0x0:0x0, last cmd=0x470e00
Jan 16 14:13:50 hp8440p kernel: [13017.405543] hda-intel: spurious response 0x0:0x0, last cmd=0x470e00
Jan 16 14:13:50 hp8440p kernel: [13017.405545] hda-intel: spurious response 0x0:0x0, last cmd=0x470e00
Jan 16 14:13:50 hp8440p kernel: [13017.405546] hda-intel: spurious response 0x0:0x0, last cmd=0x470e00
Jan 16 14:13:50 hp8440p kernel: [13017.405547] hda-intel: spurious response 0x0:0x0, last cmd=0x470e00
Jan 16 14:13:50 hp8440p kernel: [13017.405549] hda-intel: spurious response 0x0:0x0, last cmd=0x470e00
Jan 16 14:13:50 hp8440p kernel: [13017.405550] hda-intel: spurious response 0x0:0x0, last cmd=0x470e00
Jan 16 14:13:50 hp8440p kernel: [13017.405551] hda-intel: spurious response 0x0:0x0, last cmd=0x470e00
Jan 16 14:13:50 hp8440p kernel: [13017.405553] hda-intel: spurious response 0x0:0x0, last cmd=0x470e00
Jan 16 14:13:50 hp8440p kernel: [13017.405554] hda-intel: spurious response 0x0:0x0, last cmd=0x470e00
Jan 16 14:13:50 hp8440p kernel: [13017.405555] hda-intel: spurious response 0x0:0x0, last cmd=0x470e00
Jan 16 14:13:50 hp8440p kernel: [13017.405557] hda-intel: spurious response 0x0:0x0, last cmd=0x470e00
Jan 16 14:13:50 hp8440p kernel: [13017.405558] hda-intel: spurious response 0x0:0x0, last cmd=0x470e00
Jan 16 14:13:50 hp8440p kernel: [13017.405559] hda-intel: spurious response 0x0:0x0, last cmd=0x470e00
Jan 16 14:13:50 hp8440p kernel: [13017.405561] hda-intel: spurious response 0x0:0x0, last cmd=0x470e00
Jan 16 14:13:50 hp8440p kernel: [13017.405562] hda-intel: spurious response 0x0:0x0, last cmd=0x470e00
Jan 16 14:13:50 hp8440p kernel: [13017.405563] hda-intel: spurious response 0x0:0x0, last cmd=0x470e00
Jan 16 14:13:50 hp8440p kernel: [13017.405565] hda-intel: spurious response 0x0:0x0, last cmd=0x470e00
Jan 16 14:13:50 hp8440p kernel: [13017.405566] hda-intel: spurious response 0x0:0x0, last cmd=0x470e00
Jan 16 14:13:50 hp8440p kernel: [13017.405567] hda-intel: spurious response 0x0:0x0, last cmd=0x470e00
Jan 16 14:13:50 hp8440p kernel: [13017.405569] hda-intel: spurious response 0x0:0x0, last cmd=0x470e00
Jan 16 14:13:50 hp8440p kernel: [13017.405570] hda-intel: spurious response 0x0:0x0, last cmd=0x470e00
Jan 16 14:13:50 hp8440p kernel: [13017.405571] hda-intel: spurious response 0x0:0x0, last cmd=0x470e00
Jan 16 14:13:50 hp8440p kernel: [13017.405573] hda-intel: spurious response 0x0:0x0, last cmd=0x470e00
Jan 16 14:13:50 hp8440p kernel: [13017.405574] hda-intel: spurious response 0x0:0x0, last cmd=0x470e00
Jan 16 14:13:50 hp8440p kernel: [13017.405575] hda-intel: spurious response 0x0:0x0, last cmd=0x470e00
Jan 16 14:13:50 hp8440p kernel: [13017.405577] hda-intel: spurious response 0x0:0x0, last cmd=0x470e00
Jan 16 14:13:50 hp8440p kernel: [13017.405578] hda-intel: spurious response 0x0:0x0, last cmd=0x470e00
Jan 16 14:13:50 hp8440p kernel: [13017.405579] hda-intel: spurious response 0x0:0x0, last cmd=0x470e00
Jan 16 14:13:50 hp8440p kernel: [13017.405581] hda-intel: spurious response 0x0:0x0, last cmd=0x470e00
Jan 16 14:13:50 hp8440p kernel: [13017.405582] hda-intel: spurious response 0x0:0x0, last cmd=0x470e00
Jan 16 14:13:50 hp8440p kernel: [13017.405583] hda-intel: spurious response 0x0:0x0, last cmd=0x470e00
Jan 16 14:13:50 hp8440p kernel: [13017.405584] hda-intel: spurious response 0x0:0x0, last cmd=0x470e00
Jan 16 14:13:50 hp8440p kernel: [13017.405586] hda-intel: spurious response 0x0:0x0, last cmd=0x470e00
Jan 16 14:13:50 hp8440p kernel: [13017.405587] hda-intel: spurious response 0x0:0x0, last cmd=0x470e00
Jan 16 14:13:50 hp8440p kernel: [13017.405588] hda-intel: spurious response 0x0:0x0, last cmd=0x470e00
Jan 16 14:13:50 hp8440p kernel: [13017.405590] hda-intel: spurious response 0x0:0x0, last cmd=0x470e00
Jan 16 14:13:50 hp8440p kernel: [13017.405591] hda-intel: spurious response 0x0:0x0, last cmd=0x470e00
Jan 16 14:13:50 hp8440p kernel: [13017.405592] hda-intel: spurious response 0x0:0x0, last cmd=0x470e00
Jan 16 14:13:50 hp8440p kernel: [13017.405594] hda-intel: spurious response 0x0:0x0, last cmd=0x470e00
Jan 16 14:13:50 hp8440p kernel: [13017.405595] hda-intel: spurious response 0x0:0x0, last cmd=0x470e00
Jan 16 14:13:50 hp8440p kernel: [13017.405596] hda-intel: spurious response 0x0:0x0, last cmd=0x470e00
Jan 16 14:13:50 hp8440p kernel: [13017.405598] hda-intel: spurious response 0x0:0x0, last cmd=0x470e00
Jan 16 14:13:50 hp8440p kernel: [13017.405599] hda-intel: spurious response 0x0:0x0, last cmd=0x470e00
Jan 16 14:13:50 hp8440p kernel: [13017.405600] hda-intel: spurious response 0x0:0x0, last cmd=0x470e00
Jan 16 14:13:50 hp8440p kernel: [13017.405602] hda-intel: spurious response 0x0:0x0, last cmd=0x470e00
Jan 16 14:13:50 hp8440p kernel: [13017.405603] hda-intel: spurious response 0x0:0x0, last cmd=0x470e00
Jan 16 14:13:50 hp8440p kernel: [13017.405604] hda-intel: spurious response 0x0:0x0, last cmd=0x470e00
Jan 16 14:13:50 hp8440p kernel: [13017.405606] hda-intel: spurious response 0x0:0x0, last cmd=0x470e00
Jan 16 14:13:50 hp8440p kernel: [13017.405607] hda-intel: spurious response 0x0:0x0, last cmd=0x470e00
Jan 16 14:13:50 hp8440p kernel: [13017.405608] hda-intel: spurious response 0x0:0x0, last cmd=0x470e00
Jan 16 14:13:50 hp8440p kernel: [13017.405610] hda-intel: spurious response 0x0:0x0, last cmd=0x470e00
Jan 16 14:13:50 hp8440p kernel: [13017.405611] hda-intel: spurious response 0x0:0x0, last cmd=0x470e00
Jan 16 14:13:50 hp8440p kernel: [13017.405612] hda-intel: spurious response 0x0:0x0, last cmd=0x470e00
Jan 16 14:13:50 hp8440p kernel: [13017.405614] hda-intel: spurious response 0x0:0x0, last cmd=0x470e00
Jan 16 14:13:50 hp8440p kernel: [13017.405615] hda-intel: spurious response 0x0:0x0, last cmd=0x470e00
Jan 16 14:13:50 hp8440p kernel: [13017.405616] hda-intel: spurious response 0x0:0x0, last cmd=0x470e00
Jan 16 14:13:50 hp8440p kernel: [13017.405618] hda-intel: spurious response 0x0:0x0, last cmd=0x470e00
Jan 16 14:13:50 hp8440p kernel: [13017.405619] hda-intel: spurious response 0x0:0x0, last cmd=0x470e00
Jan 16 14:13:50 hp8440p kernel: [13017.405620] hda-intel: spurious response 0x0:0x0, last cmd=0x470e00
Jan 16 14:13:50 hp8440p kernel: [13017.405622] hda-intel: spurious response 0x0:0x0, last cmd=0x470e00
Jan 16 14:13:50 hp8440p kernel: [13017.405623] hda-intel: spurious response 0x0:0x0, last cmd=0x470e00
Jan 16 14:13:50 hp8440p kernel: [13017.405624] hda-intel: spurious response 0x0:0x0, last cmd=0x470e00
Jan 16 14:13:50 hp8440p kernel: [13017.405626] hda-intel: spurious response 0x0:0x0, last cmd=0x470e00
Jan 16 14:13:50 hp8440p kernel: [13017.405627] hda-intel: spurious response 0x0:0x0, last cmd=0x470e00
Jan 16 14:13:50 hp8440p kernel: [13017.405628] hda-intel: spurious response 0x0:0x0, last cmd=0x470e00
Jan 16 14:13:50 hp8440p kernel: [13017.405630] hda-intel: spurious response 0x0:0x0, last cmd=0x470e00
Jan 16 14:13:50 hp8440p kernel: [13017.405631] hda-intel: spurious response 0x0:0x0, last cmd=0x470e00
Jan 16 14:13:50 hp8440p kernel: [13017.405632] hda-intel: spurious response 0x0:0x0, last cmd=0x470e00
Jan 16 14:13:50 hp8440p kernel: [13017.405634] hda-intel: spurious response 0x0:0x0, last cmd=0x470e00
Jan 16 14:13:50 hp8440p kernel: [13017.405635] hda-intel: spurious response 0x0:0x0, last cmd=0x470e00
Jan 16 14:13:50 hp8440p kernel: [13017.405636] hda-intel: spurious response 0x0:0x0, last cmd=0x470e00
Jan 16 14:13:50 hp8440p kernel: [13017.405638] hda-intel: spurious response 0x0:0x0, last cmd=0x470e00
Jan 16 14:13:50 hp8440p kernel: [13017.405639] hda-intel: spurious response 0x0:0x0, last cmd=0x470e00
Jan 16 14:13:50 hp8440p kernel: [13017.405640] hda-intel: spurious response 0x0:0x0, last cmd=0x470e00
Jan 16 14:13:50 hp8440p kernel: [13017.405642] hda-intel: spurious response 0x0:0x0, last cmd=0x470e00
Jan 16 14:13:50 hp8440p kernel: [13017.405643] hda-intel: spurious response 0x0:0x0, last cmd=0x470e00
Jan 16 14:13:50 hp8440p kernel: [13017.405644] hda-intel: spurious response 0x0:0x0, last cmd=0x470e00
Jan 16 14:13:50 hp8440p kernel: [13017.405646] hda-intel: spurious response 0x0:0x0, last cmd=0x470e00
Jan 16 14:13:50 hp8440p kernel: [13017.405647] hda-intel: spurious response 0x0:0x0, last cmd=0x470e00
Jan 16 14:13:50 hp8440p kernel: [13017.405648] hda-intel: spurious response 0x0:0x0, last cmd=0x470e00
Jan 16 14:13:50 hp8440p kernel: [13017.405650] hda-intel: spurious response 0x0:0x0, last cmd=0x470e00
Jan 16 14:14:10 hp8440p kernel: [13038.013302] NVRM: Xid (0001:00): 8, Channel 00000001
Jan 16 14:14:11 hp8440p kernel: [13038.168761] NVRM: os_pci_init_handle: invalid context!
Jan 16 14:14:11 hp8440p kernel: [13038.168763] NVRM: os_pci_init_handle: invalid context!
Jan 16 14:14:11 hp8440p kernel: [13038.168771] NVRM: os_pci_init_handle: invalid context!
Jan 16 14:14:11 hp8440p kernel: [13038.168772] NVRM: os_pci_init_handle: invalid context!
Jan 16 14:14:12 hp8440p kernel: [13039.939381] NVRM: os_schedule: Attempted to yield the CPU while in atomic or interrupt context
Jan 16 14:14:14 hp8440p kernel: [13041.934453] NVRM: os_schedule: Attempted to yield the CPU while in atomic or interrupt context
Jan 16 14:14:16 hp8440p kernel: [13043.929495] NVRM: os_schedule: Attempted to yield the CPU while in atomic or interrupt context
Jan 16 14:14:17 hp8440p kernel: [13044.487187] iwlagn 0000:44:00.0: Error sending REPLY_SCAN_ABORT_CMD: time out after 500ms.
Jan 16 14:14:18 hp8440p kernel: [13045.622449] iwlagn 0000:44:00.0: queue 4 stuck 3 time. Fw reload.
Jan 16 14:14:18 hp8440p kernel: [13045.622451] iwlagn 0000:44:00.0: On demand firmware reload
Jan 16 14:14:18 hp8440p kernel: [13045.924539] NVRM: os_schedule: Attempted to yield the CPU while in atomic or interrupt context
Jan 16 14:14:20 hp8440p kernel: [13047.919582] NVRM: os_schedule: Attempted to yield the CPU while in atomic or interrupt context
Jan 16 14:14:22 hp8440p kernel: [13049.914624] NVRM: os_schedule: Attempted to yield the CPU while in atomic or interrupt context
Jan 16 14:14:24 hp8440p kernel: [13051.909672] NVRM: os_schedule: Attempted to yield the CPU while in atomic or interrupt context
Jan 16 14:14:26 hp8440p kernel: [13053.904713] NVRM: os_schedule: Attempted to yield the CPU while in atomic or interrupt context
Jan 16 14:14:28 hp8440p kernel: [13055.899770] NVRM: os_schedule: Attempted to yield the CPU while in atomic or interrupt context
Jan 16 14:14:30 hp8440p kernel: [13057.894811] NVRM: os_schedule: Attempted to yield the CPU while in atomic or interrupt context
Jan 16 14:14:32 hp8440p kernel: [13059.889861] NVRM: os_schedule: Attempted to yield the CPU while in atomic or interrupt context
Jakob is offline   Reply With Quote
Old 07-21-11, 04:28 AM   #4
ppihus
Registered User
 
Join Date: Jul 2011
Posts: 1
Default Re: Nvidia NVS 3100M on Ubuntu 10.10 freeze - SOLVED!!!! .. I hope ;)

I know it's an really old topic but I've searched everywhere and tried everything I can think of. Did you eventually find a solution to the problem?
Google's results is full of this problem, but I haven't found a single one with a solution.
ppihus is offline   Reply With Quote
Reply


Thread Tools

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Forum Jump


All times are GMT -5. The time now is 08:57 AM.


Powered by vBulletin® Version 3.7.1
Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Copyright 1998 - 2014, nV News.