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

Newegg Daily Deals

Reply
 
Thread Tools
Old 11-17-10, 04:08 PM   #1
mjanusz
Registered User
 
Join Date: Nov 2010
Posts: 4
Default 260.19.*: NULL pointer dereference oops with GF330M (Sony VAIO F11)

The 260.19.* kernel drivers seem to be broken for my GF 330M. I get the following oops when X is started (excerpt below, full kernel log is attached in segfault.txt):

[ 116.736080] BUG: unable to handle kernel NULL pointer dereference at (null)
[ 116.736083] IP: [< (null)>] (null)
[ 116.736086] PGD 1a63ea067 PUD 1a547c067 PMD 0
[ 116.736088] Oops: 0010 [#1] SMP
[ 116.736089] last sysfs file: /sys/bus/acpi/drivers/NVIDIA ACPI Video Driver/uevent
[ 116.736091] CPU 4
[ 116.736091] Modules linked in: nvidia(P) button battery video ac
[ 116.736094]
[ 116.736096] Pid: 2978, comm: X Tainted: P 2.6.37-rc1-00609-g6800e4c #4 VAIO/VPCF11S1E
[ 116.736098] RIP: 0010:[<0000000000000000>] [< (null)>] (null)
[ 116.736099] RSP: 0018:ffff8801a62d3a60 EFLAGS: 00010292
[ 116.736101] RAX: 0000000000000121 RBX: ffff8801a4e82000 RCX: 0000000000000000
[ 116.736102] RDX: 0000000000000001 RSI: ffff8801a4e82000 RDI: ffff8801a54a6000
[ 116.736103] RBP: ffff8801a7a4def0 R08: 0000000000000000 R09: ffffffffa06ed221
[ 116.736104] R10: ffff8801a7d72c18 R11: ffff8801a62d39e8 R12: ffff8801a54a6000
[ 116.736106] R13: ffff8801a54a6000 R14: 0000000000000000 R15: 0000000000000000
[ 116.736107] FS: 00007fe56bb12700(0000) GS:ffff8800ced00000(0000) knlGS:0000000000000000
[ 116.736109] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[ 116.736110] CR2: 0000000000000000 CR3: 00000001a7aa7000 CR4: 00000000000006e0
[ 116.736111] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
[ 116.736113] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
[ 116.736114] Process X (pid: 2978, threadinfo ffff8801a62d2000, task ffff8801a628af00)
[ 116.736115] Stack:
[ 116.736116] ffffffffa01fb8a9 ffff8801a4e82000 ffff8801a4e82000 0000000000000000
[ 116.736118] ffffffffa020c1e7 0000000000000000 ffff8801a4e82000 ffff8801a54a6000
[ 116.736120] ffff8801a4e82000 0000000000000000 ffffffffa0209ff9 ffff8801a5584000
[ 116.736121] Call Trace:
[ 116.736268] [<ffffffffa01fb8a9>] ? _nv021443rm+0x13/0x26 [nvidia]
[ 116.736388] [<ffffffffa020c1e7>] ? _nv021342rm+0xf5/0x1b9 [nvidia]
[ 116.736640] [<ffffffffa0209ff9>] ? _nv021199rm+0x268/0x4c6 [nvidia]
[ 116.736768] [<ffffffffa024ef97>] ? _nv009132rm+0x86/0x1b3 [nvidia]
[ 116.736894] [<ffffffffa024748a>] ? _nv009647rm+0x1a0/0x237 [nvidia]
[ 116.737042] [<ffffffffa035d15f>] ? _nv014470rm+0x27b/0x4c9 [nvidia]
[ 116.737190] [<ffffffffa035c083>] ? _nv014752rm+0xea/0x167 [nvidia]
[ 116.737258] [<ffffffffa004e932>] ? _nv014931rm+0xd/0x12 [nvidia]
[ 116.737382] [<ffffffffa05240ce>] ? _nv002153rm+0x160/0x26f [nvidia]
[ 116.737599] [<ffffffffa0524ef2>] ? _nv002147rm+0x492/0x670 [nvidia]
[ 116.737722] [<ffffffffa052a929>] ? rm_init_adapter+0x89/0xfd [nvidia]
[ 116.737845] [<ffffffffa0547268>] ? nv_kern_open+0x5b8/0x720 [nvidia]
[ 116.737848] [<ffffffff81116835>] ? chrdev_open+0xe5/0x190
[ 116.737850] [<ffffffff81116750>] ? chrdev_open+0x0/0x190
[ 116.737852] [<ffffffff8111174a>] ? __dentry_open+0xca/0x2d0
[ 116.737854] [<ffffffff8111e9d0>] ? do_last+0x370/0x5e0
[ 116.737856] [<ffffffff811209db>] ? do_filp_open+0x1db/0x550
[ 116.737858] [<ffffffff81111578>] ? do_sys_open+0x68/0x120
[ 116.737861] [<ffffffff8102edeb>] ? system_call_fastpath+0x16/0x1b
[ 116.737862] Code: Bad RIP value.
[ 116.737865] RIP [< (null)>] (null)
[ 116.737867] RSP <ffff8801a62d3a60>
[ 116.737867] CR2: 0000000000000000
[ 116.737880] ---[ end trace fc16a4e23c73741f ]---

When X is started, the screen remains black and the console is unresponsive. The kernel log was captured over ssh. The nvidia-bug-report.log.gz file was generated after a reboot, as following the oops the system was unstable and writes to any file failed (resulting in an empty nvidia-bug-report.log.gz).

This has been happening for quite a while, with multiple kernel versions (2.6.35 and later) and multiple driver versions from the 260 line.

Please let me know if you need any additional info or if I can help with debugging this issue further.
Attached Files
File Type: gz nvidia-bug-report.log.gz (53.2 KB, 58 views)
File Type: txt segfault.txt (12.3 KB, 94 views)
mjanusz is offline   Reply With Quote
Old 12-01-10, 03:31 PM   #2
mjanusz
Registered User
 
Join Date: Nov 2010
Posts: 4
Default Re: 260.19.*: NULL pointer dereference oops with GF330M (Sony VAIO F11)

This problem is fixed in 260.19.26. Thanks!
mjanusz 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 09:47 AM.


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