search

tvogel / vaio-f11-linux

Automatically exported from code.google.com/p/vaio-f11-linux
7 stars 2 forks source link

NVidia 260 drivers unusable (crashing Xorg) #34

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
Probably this should be organized as a separate issue...

What steps will reproduce the problem?
1. Install NVidia drivers version 260.xx (either via ppa or manually).

What is the expected output? What do you see instead?
Xorg doesn't load (crashes).

What version of the product are you using? On what operating system?
VPCF1190, Ubuntu 10.04 / 10.10, kernels 2.6.32 / 2.6.35.

Please provide any additional information below.
Well, Xorg's stack trace is below:

Oct 13 22:38:54 sbx kernel: [   16.833215] NVRM: loading NVIDIA UNIX x86_64 
Kernel Module  260.19.12  Fri Oct  8 11:17:08 PDT 2010                          

Oct 13 22:38:54 sbx kernel: [   17.038310] ppdev: user-space parallel port 
driver                                                                          

Oct 13 22:38:56 sbx kernel: [   18.622442] PGD 11a65e067 PUD 11a65f067 PMD 0    

Oct 13 22:38:56 sbx kernel: [   18.622451] CPU 3                                

Oct 13 22:38:56 sbx kernel: [   18.622452] Modules linked in: parport_pc ppdev 
snd_hda_codec_nvhdmi rfcomm binfmt_misc sco bnep l2cap vboxnetadp vboxnetflt 
vboxdrv nvidia(P) snd_hda_codec_realtek arc4 nouveau snd_hda_intel ath9k 
snd_hda_codec snd_hwdep snd_pcm snd_se
q_midi snd_rawmidi i7core_edac ath9k_common edac_core snd_seq_midi_event 
ath9k_hw ath mac80211 ttm uvcvideo videodev drm_kms_helper btusb drm snd_seq 
snd_timer i2c_algo_bit snd_seq_device v4l1_compat v4l2_compat_ioctl32 bluetooth 
joydev psmouse snd sony_laptop serio_
raw cfg80211 soundcore snd_page_alloc lp parport uvesafb usbhid hid 
firewire_ohci sky2 ahci firewire_core libahci sdhci_pci sdhci led_class 
crc_itu_t video output                                                          

Oct 13 22:38:56 sbx kernel: [   18.622486]                                      

Oct 13 22:38:56 sbx kernel: [   18.622489] Pid: 1663, comm: Xorg Tainted: P     
       2.6.35-22-generic #33-Ubuntu VAIO/VPCF119FX                              

Oct 13 22:38:56 sbx kernel: [   18.622491] RIP: 0010:[<0000000000000000>]  
[<(null)>] (null)                                                               

Oct 13 22:38:56 sbx kernel: [   18.622494] RSP: 0018:ffff88012ab21990  EFLAGS: 
00010292                                                                        

Oct 13 22:38:56 sbx kernel: [   18.622496] RAX: 0000000000000161 RBX: 
ffff88012ae6c000 RCX: 0000000000000000                                          

Oct 13 22:38:56 sbx kernel: [   18.622498] RDX: 0000000000000001 RSI: 
ffff88012ae6c000 RDI: ffff88011a2c2000                                          

Oct 13 22:38:56 sbx kernel: [   18.622500] RBP: ffff88012b04def0 R08: 
0000000000000000 R09: 0000000000000000                                          

Oct 13 22:38:56 sbx kernel: [   18.622503] R10: 0000000000000098 R11: 
0000000000000000 R12: ffff88011a2c2000                                          

Oct 13 22:38:56 sbx kernel: [   18.622505] R13: ffff88011a2c2000 R14: 
0000000000000000 R15: 0000000000000000                                          

Oct 13 22:38:56 sbx kernel: [   18.622508] FS:  00007fe9d2218840(0000) 
GS:ffff880001ec0000(0000) knlGS:0000000000000000                                

Oct 13 22:38:56 sbx kernel: [   18.622510] CS:  0010 DS: 0000 ES: 0000 CR0: 
000000008005003b                                                                

Oct 13 22:38:56 sbx kernel: [   18.622512] CR2: 0000000000000000 CR3: 
000000011a661000 CR4: 00000000000006e0                                          

Oct 13 22:38:56 sbx kernel: [   18.622515] DR0: 0000000000000000 DR1: 
0000000000000000 DR2: 0000000000000000                                          

Oct 13 22:38:56 sbx kernel: [   18.622517] DR3: 0000000000000000 DR6: 
00000000ffff0ff0 DR7: 0000000000000400                                          

Oct 13 22:38:56 sbx kernel: [   18.622520] Process Xorg (pid: 1663, threadinfo 
ffff88012ab20000, task ffff88011a592dc0)                                        

Oct 13 22:38:56 sbx kernel: [   18.622523]  ffffffffa06d67b9 ffff88012ae6c000 
ffff88012ae6c000 0000000000000000                                               

Oct 13 22:38:56 sbx kernel: [   18.622526] <0> ffffffffa06e7050 
0000000000000000 ffff88012ae6c000 ffff88011a2c2000                              

Oct 13 22:38:56 sbx kernel: [   18.622528] <0> ffff88012ae6c000 
0000000000000000 ffffffffa06e4f09 ffff88012aa0c000                              

Oct 13 22:38:56 sbx kernel: [   18.622740]  [<ffffffffa06d67b9>] ? 
_nv021430rm+0x13/0x26 [nvidia]                                                  

Oct 13 22:38:56 sbx kernel: [   18.622934]  [<ffffffffa06e7050>] ? 
_nv021329rm+0xf5/0x1b9 [nvidia]                                                 

Oct 13 22:38:56 sbx kernel: [   18.623127]  [<ffffffffa06e4f09>] ? 
_nv021186rm+0x268/0x4c6 [nvidia]                                                

Oct 13 22:38:56 sbx kernel: [   18.623334]  [<ffffffffa0729e07>] ? 
_nv009131rm+0x86/0x1b3 [nvidia]                                                 

Oct 13 22:38:56 sbx kernel: [   18.623540]  [<ffffffffa07222fa>] ? 
_nv009646rm+0x1a0/0x237 [nvidia]                                                

Oct 13 22:38:56 sbx kernel: [   18.623780]  [<ffffffffa083811f>] ? 
_nv014469rm+0x27b/0x4c9 [nvidia]                                                

Oct 13 22:38:56 sbx kernel: [   18.624020]  [<ffffffffa0837043>] ? 
_nv014749rm+0xea/0x167 [nvidia]                                                 

Oct 13 22:38:56 sbx kernel: [   18.624131]  [<ffffffffa0529912>] ? 
_nv014928rm+0xd/0x12 [nvidia]                                                   

Oct 13 22:38:56 sbx kernel: [   18.624332]  [<ffffffffa09fea3e>] ? 
_nv002152rm+0x160/0x26f [nvidia]                                                

Oct 13 22:38:56 sbx kernel: [   18.624532]  [<ffffffffa09ff862>] ? 
_nv002146rm+0x492/0x65a [nvidia]                                                

Oct 13 22:38:56 sbx kernel: [   18.624732]  [<ffffffffa0a05279>] ? 
rm_init_adapter+0x89/0xfd [nvidia]                                              

Oct 13 22:38:56 sbx kernel: [   18.624932]  [<ffffffffa0a2297e>] ? 
nv_kern_open+0x5ae/0x760 [nvidia]                                               

Oct 13 22:38:56 sbx kernel: [   18.624938]  [<ffffffff8115688a>] ? 
chrdev_open+0x10a/0x200                                                         

Oct 13 22:38:56 sbx kernel: [   18.624941]  [<ffffffff81156780>] ? 
chrdev_open+0x0/0x200                                                           

Oct 13 22:38:56 sbx kernel: [   18.624945]  [<ffffffff81150ce5>] ? 
__dentry_open+0xe5/0x330                                                        

Oct 13 22:38:56 sbx kernel: [   18.624949]  [<ffffffff8126060f>] ? 
security_inode_permission+0x1f/0x30                                             

Oct 13 22:38:56 sbx kernel: [   18.624953]  [<ffffffff81151044>] ? 
nameidata_to_filp+0x54/0x70                                                     

Oct 13 22:38:56 sbx kernel: [   18.624956]  [<ffffffff8115dbf8>] ? 
finish_open+0xe8/0x1d0                                                          

Oct 13 22:38:56 sbx kernel: [   18.624960]  [<ffffffff8116687f>] ? 
dput+0xdf/0x1b0                                                                 

Oct 13 22:38:56 sbx kernel: [   18.624962]  [<ffffffff8115f056>] ? 
do_last+0x86/0x460                                                              

Oct 13 22:38:56 sbx kernel: [   18.624965]  [<ffffffff8116138b>] ? 
do_filp_open+0x21b/0x660                                                        

Oct 13 22:38:56 sbx kernel: [   18.624970]  [<ffffffff8116cb9a>] ? 
alloc_fd+0x10a/0x150                                                            

Oct 13 22:38:56 sbx kernel: [   18.624973]  [<ffffffff81150a89>] ? 
do_sys_open+0x69/0x170                                                          

Oct 13 22:38:56 sbx kernel: [   18.624976]  [<ffffffff81150bd0>] ? 
sys_open+0x20/0x30                                                              

Oct 13 22:38:56 sbx kernel: [   18.624981]  [<ffffffff8100a0f2>] ? 
system_call_fastpath+0x16/0x1b                                                  

Oct 13 22:38:56 sbx kernel: [   18.624989]  RSP <ffff88012ab21990>              

Oct 13 22:38:56 sbx kernel: [   18.624997] ---[ end trace c2a79762d89a15d3 ]---

Original issue reported on code.google.com by shand...@gmail.com on 13 Oct 2010 at 8:05

GoogleCodeExporter commented 9 years ago 
Has anyone tried 260.19.12?  I know that 260.19.06 does not work.  260.19.12 
just showed up on nvidia's website, and I am downloading it now.  I will try it 
as soon as the download is done.

Original comment by britr...@gmail.com on 13 Oct 2010 at 8:27

GoogleCodeExporter commented 9 years ago 
Sure, I did.
It doesn't work the same way as 19.04 does not.

Original comment by shand...@gmail.com on 13 Oct 2010 at 8:43

GoogleCodeExporter commented 9 years ago 
Ok I won't try then.  Thanks.

Original comment by britr...@gmail.com on 13 Oct 2010 at 8:59

GoogleCodeExporter commented 9 years ago 
I'm having the same problem, my model is VPCF11S1E.

Both Kubuntu's bundled nvidia drivers and nvidia drivers from nvidia.com 
doens't work.
Newest version tried: 260.19.12

Original comment by Anders.J...@gmail.com on 15 Oct 2010 at 8:21

GoogleCodeExporter commented 9 years ago 
My nVidia card is GeForce GT 330M...

Original comment by Anders.J...@gmail.com on 15 Oct 2010 at 8:24

GoogleCodeExporter commented 9 years ago 
I have the same problem with a Vaio VPCF11M1E, GeForce GT 330M, kernel 
2.6.35-22, nvidia 260.19.12.

I hope they will fix it..

Original comment by kenjiru...@gmail.com on 15 Oct 2010 at 6:28

GoogleCodeExporter commented 9 years ago 
It's great how the Sony laptops and Linux hate each other so much :-/. Here I 
thought I was getting myself a nice, quality laptop.

For now, I'm just sticking with what works and using 19.36.24

Original comment by xxBartonxx@gmail.com on 16 Oct 2010 at 12:10

GoogleCodeExporter commented 9 years ago 
19.36.24 is exactly what?
I thought the exact same thought xxBartonxx

Quality laptop my a**

Original comment by Anders.J...@gmail.com on 16 Oct 2010 at 12:16

GoogleCodeExporter commented 9 years ago 
@Anders.Jacob.Hansen 195.36.24 are good old nvidia drivers ;-)

Original comment by xjc...@gmail.com on 16 Oct 2010 at 3:24

GoogleCodeExporter commented 9 years ago 
[deleted comment]
GoogleCodeExporter commented 9 years ago 
[deleted comment]
GoogleCodeExporter commented 9 years ago 
[deleted comment]
GoogleCodeExporter commented 9 years ago 
[deleted comment]
GoogleCodeExporter commented 9 years ago 
I removed the off topic comments. Stay on topic please.

256.44 is the last known working version in my experience. Anyone make any 
headway with the 260 series?

Original comment by Jason.Donenfeld on 9 Nov 2010 at 5:42

GoogleCodeExporter commented 9 years ago 
@Jason.Donenfeld: I am running 256.53 with success, although a bit jumpy and 
too much CPU consuming (for Xorg) in my opinion

Original comment by stephv...@gmail.com on 9 Nov 2010 at 8:29

GoogleCodeExporter commented 9 years ago 
@Stephvast -- aaa yes; that's right. .53 works, but it's extremely CPU 
intensive ; full screen flash stutters. That's why I went back to .44.

Original comment by Jason.Donenfeld on 9 Nov 2010 at 6:39

GoogleCodeExporter commented 9 years ago 
@Jason.Donenfeld: so you would recommend me install 256.44 in place of 256.53?

Original comment by stephv...@gmail.com on 9 Nov 2010 at 8:51

GoogleCodeExporter commented 9 years ago 
With out a doubt yes, but let's stay on topic here:

How can we get 260.* working?

Original comment by Jason.Donenfeld on 9 Nov 2010 at 8:52

GoogleCodeExporter commented 9 years ago 
New drivers was released - 260.19.21. In the evening I will try it :)
http://www.nvnews.net/vbulletin/showthread.php?p=2345016

Original comment by xjc...@gmail.com on 10 Nov 2010 at 9:37

GoogleCodeExporter commented 9 years ago 
@xjcook I wouldn't bother.... I just tried 260.19.21,... no change

Original comment by britr...@gmail.com on 10 Nov 2010 at 2:07

GoogleCodeExporter commented 9 years ago 
@britrock http://nvnews.net/vbulletin/showpost.php?p=2345359&postcount=21

Next release will fixed the bug :-)))

Original comment by xjc...@gmail.com on 10 Nov 2010 at 8:32

GoogleCodeExporter commented 9 years ago 
Wonderful. Thanks a lot, xjcook, for reporting this to the proper folks.

Original comment by Jason.Donenfeld on 10 Nov 2010 at 10:15

GoogleCodeExporter commented 9 years ago 
@xjcook Awesome!  I can't wait to get my hands on that.

Original comment by britr...@gmail.com on 10 Nov 2010 at 10:35

GoogleCodeExporter commented 9 years ago 
Having the same issue on Gentoo with 260.19.21 on a Sony VPCF12MOE, system 
completely crashes.  Having to use 256.53.  Would also be nice to get the VTs 
working again :)

I've attached my nvidia-bugreport (32kb) if that might help.. it's incomplete 
due to the crash.

Original comment by Moye...@gmail.com on 23 Nov 2010 at 8:44

Attachments:

GoogleCodeExporter commented 9 years ago 
Yes. As said earlier, the fix will be in the release after .21.

Original comment by Jason.Donenfeld on 23 Nov 2010 at 8:46

GoogleCodeExporter commented 9 years ago 
Do you know if there is any date for the new driver version? I expected it was 
going to be released the last week, but there is no new yet, sorry for my bad 
english

Original comment by Josemsa...@gmail.com on 24 Nov 2010 at 9:43

GoogleCodeExporter commented 9 years ago 
@Josemsar92 We don't know a date.  If you want to know more you can read the 
threads on nvnews.net (see the link above).  Thats all we know.

Original comment by britr...@gmail.com on 24 Nov 2010 at 10:15

GoogleCodeExporter commented 9 years ago 
Phoronix says it released a new beta driver. I can't get to the site atm tho..

Original comment by Ian.Corn...@gmail.com on 1 Dec 2010 at 1:24

GoogleCodeExporter commented 9 years ago 
http://www.phoronix.com/forums/showthread.php?t=27450

They uploaded it on their ftp servers

Original comment by Ian.Corn...@gmail.com on 1 Dec 2010 at 1:27

GoogleCodeExporter commented 9 years ago 
Using the new driver on 330m Works pretty much fine for desktop, 

however I cannot switch to a (working) TTY (ubuntu 11.04)

Vaio VPCF12C5E

Original comment by NashBan...@gmail.com on 1 Dec 2010 at 1:30

GoogleCodeExporter commented 9 years ago 
I confirm the new drivers work for my 425m.
VPCF13M1E

Original comment by Ian.Corn...@gmail.com on 1 Dec 2010 at 1:41

GoogleCodeExporter commented 9 years ago 
I confirm that 260.19.26 doesn't make xorg crash. Switching to TTYs works in 
the same awful way as it used to be all the time with this great laptop :)

VPCF1190X, Ubuntu 10.10, latest official 2.6.35-23 kernel.

Original comment by shand...@gmail.com on 1 Dec 2010 at 9:03

GoogleCodeExporter commented 9 years ago 
Works on Gentoo.. I now have X.. still no VTs.. maybe in the next update :)

Thanks for the hard work :)

Original comment by Moye...@gmail.com on 1 Dec 2010 at 9:03

GoogleCodeExporter commented 9 years ago 
@cdstealer

Enable uvesafb and you will have working vts

Original comment by gpanta...@gmail.com on 1 Dec 2010 at 11:03

GoogleCodeExporter commented 9 years ago 
@gpantalos - Thanks.. worked like a charm :D  very happy

Original comment by Moye...@gmail.com on 2 Dec 2010 at 8:04

GoogleCodeExporter commented 9 years ago 
Yeah that's working...awesome :)

Original comment by xjc...@gmail.com on 2 Dec 2010 at 8:08

GoogleCodeExporter commented 9 years ago 
Well, "working" may not be the right word.  For me (and may others from what I 
understand) the VTs will work with uveasafb installed, but are nearly unusable 
because they are "shaky"... Oh well.

Original comment by britr...@gmail.com on 2 Dec 2010 at 4:24

GoogleCodeExporter commented 9 years ago 
.26

Original comment by Jason.Donenfeld on 2 Dec 2010 at 5:36