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

Newegg Daily Deals

Reply
 
Thread Tools
Old 04-16-11, 05:52 PM   #13
Licaon
Registered User
 
Licaon's Avatar
 
Join Date: Nov 2004
Location: Between the keyboard and the chair.
Posts: 490
Default Re: BUG in _nv026629rm while starting X on kernel 2.6.35

can you read http://www.nvnews.net/vbulletin/showthread.php?t=46678 and generate a good report with the debug ( -logverbose 6 ) info as instructed after the issue appears ?

tried any newer drivers too? 270.xx ?
Licaon is offline   Reply With Quote
Old 04-17-11, 12:01 PM   #14
zander
NVIDIA Corporation
 
zander's Avatar
 
Join Date: Aug 2002
Posts: 3,740
Default Re: BUG in _nv026629rm while starting X on kernel 2.6.35

I briefly looked at a reproduction of what likely is the same (or a very similar) problem a few weeks ago. In my case, at least, the problem appeared to be that the kernel hadn't relocated one of the module's read-only data sections correctly, which caused a crash when the NVIDIA driver accessed a string located in that section.

I didn't get a chance for an in-depth investigation at the time. I did try to determine if the problem lay with the kernel, the toolchain, or something else entirely, but had trouble building a working kernel on the system. There's a bug filed internally, and I plan on revisiting it. Unfortunately, given the problem's nature and the low number of reports, this likely won't happen soon.
zander is offline   Reply With Quote
Old 04-17-11, 12:19 PM   #15
TTimo
Registered User
 
Join Date: Dec 2002
Posts: 5
Default Re: BUG in _nv026629rm while starting X on kernel 2.6.35

A bug report against the 270.x drivers is attached.

I have seen this module crash for several weeks now, on several kernels, debian's official releases and my own compiles. Also happening across multiple driver generations, 270.x, 260.x and I'm pretty sure I tried the 195.x too.

I have a fairly solid repro case here, and I'm reasonably knowledgeable with kernel compiling and tweaking, I can iterate on this if you need me to check on some stuff.
Attached Files
File Type: gz nvidia-bug-report.log.gz (38.5 KB, 49 views)
TTimo is offline   Reply With Quote
Old 04-18-11, 10:35 AM   #16
zander
NVIDIA Corporation
 
zander's Avatar
 
Join Date: Aug 2002
Posts: 3,740
Default Re: BUG in _nv026629rm while starting X on kernel 2.6.35

Thanks, TTimo. Judging from the backtrace, the driver crashed in the same place, accessing a built-in string for the first time. If this happens with both Debian's and vanilla kernels, then I think the problem needs to be debugged head-on.

If you're comfortable instrumenting one of your kernel's module loaders to print relocation related information, the output might help. If not, I can try to find some time this week to put together the instrumentation.

What was the most recent vanilla kernel version you tried?
zander is offline   Reply With Quote
Old 04-23-11, 04:01 PM   #17
TTimo
Registered User
 
Join Date: Dec 2002
Posts: 5
Default Re: BUG in _nv026629rm while starting X on kernel 2.6.35

Hey Zander,

I confirmed that vanilla 2.6.38-2-amd64 has the problem. Turns out I get very little time to look at this, just a few hours here and there, going to learn up on module loading and symbol relocation in the kernel, but that's probably at the far edge of my kernel knowledge
TTimo is offline   Reply With Quote
Old 04-23-11, 10:45 PM   #18
TTimo
Registered User
 
Join Date: Dec 2002
Posts: 5
Default Re: BUG in _nv026629rm while starting X on kernel 2.6.35

Another report is attached. This is with a debug kernel build, and debug print enabled in the module loading code of the kernel. It looks like the bug reporting tool is looking for /var/log/kernel.log, on my system it's /var/log/kern.log for some reason.

So I dug around since the report doesn't include much useful stuff, this is the module loading part. Let me know if this is the right direction

Code:
Apr 23 21:54:12 plageis kernel: [  124.897295] NVRM: loading NVIDIA UNIX x86_64 Kernel Module  270.41.06  Mon Apr 18 14:53:56 PDT 2011
Apr 23 21:54:12 plageis kernel: [  124.900808] nvidia 0000:01:00.0: PCI INT A disabled
Apr 23 21:54:12 plageis kernel: [  124.901095] nvidia unusing i2c_core
Apr 23 21:56:09 plageis kernel: [  241.909331] load_module: umod=00007fd070c3e000, len=15923728, uargs=00000000013eab90
Apr 23 21:56:09 plageis kernel: [  241.924693] Core section allocation order:
Apr 23 21:56:09 plageis kernel: [  241.924800]  .text
Apr 23 21:56:09 plageis kernel: [  241.924890]  .exit.text
Apr 23 21:56:09 plageis kernel: [  241.924981]  .altinstr_replacement
Apr 23 21:56:09 plageis kernel: [  241.925099]  .rodata
Apr 23 21:56:09 plageis kernel: [  241.925195]  .rodata.str1.1
Apr 23 21:56:09 plageis kernel: [  241.925290]  .rodata.str1.8
Apr 23 21:56:09 plageis kernel: [  241.925384]  .rodata.cst1
Apr 23 21:56:09 plageis kernel: [  241.925477]  .smp_locks
Apr 23 21:56:09 plageis kernel: [  241.925569]  .parainstructions
Apr 23 21:56:09 plageis kernel: [  241.925664]  .altinstructions
Apr 23 21:56:09 plageis kernel: [  241.925759]  __param
Apr 23 21:56:09 plageis kernel: [  241.925849]  .note.gnu.build-id
Apr 23 21:56:09 plageis kernel: [  241.925945]  .data
Apr 23 21:56:09 plageis kernel: [  241.926038]  .bss
Apr 23 21:56:09 plageis kernel: [  241.926128]  .gnu.linkonce.this_module
Apr 23 21:56:09 plageis kernel: [  241.926229] Init section allocation order:
Apr 23 21:56:09 plageis kernel: [  241.926331]  .init.text
Apr 23 21:56:09 plageis kernel: [  241.926440]  .symtab
Apr 23 21:56:09 plageis kernel: [  241.928021]  .strtab
Apr 23 21:56:09 plageis kernel: [  241.931947] final section addresses:
Apr 23 21:56:09 plageis kernel: [  241.935213]  0xffffffffa1244000 .text
Apr 23 21:56:09 plageis kernel: [  241.936183]  0xffffffffa178c920 .rodata
Apr 23 21:56:09 plageis kernel: [  241.936315]  0xffffffffa192e950 .rodata.str1.1
Apr 23 21:56:09 plageis kernel: [  241.936451]  0xffffffffa193d848 .rodata.str1.8
Apr 23 21:56:09 plageis kernel: [  241.936555]  0xffffffffa194cab0 .rodata.cst1
Apr 23 21:56:09 plageis kernel: [  241.937749]  0xffffffffa194d220 .data
Apr 23 21:56:09 plageis kernel: [  241.937853]  0xffffffffa1b50fe0 .bss
Apr 23 21:56:09 plageis kernel: [  241.937953]  0xffffffffa194cab4 .smp_locks
Apr 23 21:56:09 plageis kernel: [  241.938067]  0xffffffffa194cb08 .parainstructions
Apr 23 21:56:09 plageis kernel: [  241.938177]  0xffffffffa1c46000 .init.text
Apr 23 21:56:09 plageis kernel: [  241.938279]  0xffffffffa178c550 .exit.text
Apr 23 21:56:09 plageis kernel: [  241.938381]  0xffffffffa194ced8 .altinstructions
Apr 23 21:56:09 plageis kernel: [  241.938486]  0xffffffffa178c915 .altinstr_replacement
Apr 23 21:56:09 plageis kernel: [  241.938594]  0xffffffffa194cef0 __param
Apr 23 21:56:09 plageis kernel: [  241.938696]  0xffffffffa1b5b780 .gnu.linkonce.this_module
Apr 23 21:56:09 plageis kernel: [  241.940482]  0xffffffffa194d1f0 .note.gnu.build-id
Apr 23 21:56:09 plageis kernel: [  241.940993]  0xffffffffa1c466b8 .symtab
Apr 23 21:56:09 plageis kernel: [  241.941318]  0xffffffffa1d0ac78 .strtab
Apr 23 21:56:09 plageis kernel: [  241.941648] Absolute symbol: 0x00000000
Apr 23 21:56:09 plageis kernel: [  241.941749] Absolute symbol: 0x00000000
Apr 23 21:56:09 plageis kernel: [  241.941849] Absolute symbol: 0x00000000
Apr 23 21:56:09 plageis kernel: [  241.941948] Absolute symbol: 0x00000000
Apr 23 21:56:09 plageis kernel: [  241.942056] Absolute symbol: 0x00000000
Apr 23 21:56:09 plageis kernel: [  241.942157] Absolute symbol: 0x00000000
Apr 23 21:56:09 plageis kernel: [  241.942257] Absolute symbol: 0x00000000
Apr 23 21:56:09 plageis kernel: [  241.942357] Absolute symbol: 0x00000000
Apr 23 21:56:09 plageis kernel: [  241.942457] Absolute symbol: 0x00000000
Apr 23 21:56:09 plageis kernel: [  241.942557] Absolute symbol: 0x00000000
Apr 23 21:56:09 plageis kernel: [  241.942658] Absolute symbol: 0x00000000
Apr 23 21:56:09 plageis kernel: [  241.942757] Absolute symbol: 0x00000000
Apr 23 21:56:09 plageis kernel: [  241.942858] Absolute symbol: 0x00000000
Apr 23 21:56:09 plageis kernel: [  241.942958] Absolute symbol: 0x00000000
Apr 23 21:56:09 plageis kernel: [  241.944895] nvidia does not use i2c_core!
Apr 23 21:56:09 plageis kernel: [  241.944997] Allocating new usage for nvidia.
Apr 23 21:56:09 plageis kernel: [  241.945184] nvidia uses i2c_core!
Apr 23 21:56:09 plageis kernel: [  241.945565] Applying relocate section 30 to 1
Apr 23 21:56:09 plageis kernel: [  241.945670] type 2 st_value ffffffffa12493af r_addend fffffffffffffffc loc ffffffffa12442d4
[..]
Attached Files
File Type: gz nvidia-bug-report.log.gz (48.9 KB, 47 views)
TTimo is offline   Reply With Quote
Old 09-03-11, 04:53 AM   #19
corentin1234
Registered User
 
Join Date: Aug 2011
Posts: 1
Default Re: BUG in _nv026629rm while starting X on kernel 2.6.35

It seem to be linker gold problem.
http://sourceware.org/bugzilla/show_bug.cgi?id=11172
https://bugs.launchpad.net/ubuntu/+s...rs/+bug/607399
http://sourceware.org/bugzilla/show_bug.cgi?id=13127
corentin1234 is offline   Reply With Quote
Old 09-03-11, 11:10 AM   #20
TTimo
Registered User
 
Join Date: Dec 2002
Posts: 5
Default Re: BUG in _nv026629rm while starting X on kernel 2.6.35

Confirmed. Latest stuff no longer has this problem. Now to figure why glxinfo is still failing..
TTimo 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 11:35 AM.


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