First Last Prev Next    No search results available      Search page      Enter new bug
Bug#: 120103
Alias:
Product:
Component:
Status: RESOLVED
Resolution: FIXED
Assigned To: X11 External Driver Maintainers <x11-drivers@gentoo.org>
Hardware:
OS:
Version:
Priority:
Severity:
Reporter: Dennis Hildebrandt <madman001@gmx.de>
Add CC:
CC:
Remove selected CCs
URL:
Summary:
Status Whiteboard:
Keywords:

Filename Description Type Creator Created Size Actions
configs.tbz2 My configs && messages application/octet-stream Alex B. Bychko 2006-01-26 23:13 0000 4.38 KB Details
Create a New Attachment (proposed patch, testcase, etc.) View All

Bug 120103 depends on: Show dependency tree
Bug 120103 blocks:
Votes: 0    Show votes for this bug    Vote for this bug

Additional Comments: (this is where you put emerge --info)


Not eligible to see or edit group visibility for this bug.






View Bug Activity   |   Format For Printing   |   XML   |   Clone This Bug

Description:   Opened: 2006-01-23 14:34 0000 
Today I installed this new kernel. After rebooting X11 doesn't start anymore.
Everything I get is a blank Screen. After emerging nvidia drivers version
1.0.8178-r3 everything works fine.

Here is the failure output in /var/log/messages when starting X with the old
nvidia drivers:

Jan 23 23:01:14 bloody xfs[10860]: ignoring font path element
/usr/share/fonts/ttf/western (unreadable)
Jan 23 23:01:15 bloody init: Activating demand-procedures for 'A'
Jan 23 23:01:16 bloody kdm_config[10932]: Unrecognized key 'UseLilo' in section
[Shutdown] at /usr/kde/3.4/share/config/kdm/kdmrc:12
Jan 23 23:01:18 bloody ------------[ cut here ]------------
Jan 23 23:01:18 bloody kernel BUG at arch/i386/mm/pageattr.c:137!
Jan 23 23:01:18 bloody invalid operand: 0000 [#1]
Jan 23 23:01:18 bloody Modules linked in: lp snd_seq_midi snd_pcm_oss
snd_mixer_oss snd_seq_oss snd_seq_midi_event snd_seq parport_pc parport pcspkr
snd_via82xx snd_mpu401_uart snd_ens1371 gameport snd_r$
Jan 23 23:01:18 bloody CPU:    0
Jan 23 23:01:18 bloody EIP:    0060:[<c01160ae>]    Tainted: P      VLI
Jan 23 23:01:18 bloody EFLAGS: 00013082   (2.6.15-gentoo-r1)
Jan 23 23:01:18 bloody EIP is at __change_page_attr+0xdf/0x174
Jan 23 23:01:18 bloody eax: 000000e3   ebx: c16d2800   ecx: c1008480   edx:
c1000000
Jan 23 23:01:18 bloody esi: c0424f68   edi: f6940000   ebp: 00000163   esp:
f68a3d74
Jan 23 23:01:18 bloody ds: 007b   es: 007b   ss: 0068
Jan 23 23:01:18 bloody Process X (pid: 10934, threadinfo=f68a2000
task=f782ea90)
Jan 23 23:01:18 bloody Stack: c16d2800 00000010 00003246 00000011 c0116164
c16d2800 00000163 f69be760
Jan 23 23:01:18 bloody f9240000 f784c400 f68a3dec c0115e58 c16d2600 00000011
00000163 00010000
Jan 23 23:01:18 bloody f9240000 f95d5f01 f9240000 f93ea180 f9240000 00010000
f784c400 f93ea173
Jan 23 23:01:18 bloody Call Trace:
Jan 23 23:01:18 bloody [<c0116164>] change_page_attr+0x21/0x36
Jan 23 23:01:18 bloody [<c0115e58>] iounmap+0x94/0xc4
Jan 23 23:01:18 bloody [<f95d5f01>] os_unmap_kernel_space+0xf/0x13 [nvidia]
Jan 23 23:01:18 bloody [<f93ea180>] _nv001706rm+0x20/0x2c [nvidia]
Jan 23 23:01:18 bloody [<f93ea173>] _nv001706rm+0x13/0x2c [nvidia]
Jan 23 23:01:18 bloody [<f93e6731>] _nv002359rm+0xe9/0x184 [nvidia]
Jan 23 23:01:18 bloody [<f93dda7a>] _nv001955rm+0x36/0xe0 [nvidia]
Jan 23 23:01:18 bloody [<f93f098c>] rm_teardown_agp+0x48/0x50 [nvidia]
Jan 23 23:01:18 bloody [<f93ef3e6>] _nv001296rm+0x1ce/0x1e4 [nvidia]
Jan 23 23:01:18 bloody [<f95d3e75>] nv_agp_teardown+0x53/0x71 [nvidia]
Jan 23 23:01:18 bloody [<f93ec5cb>] _nv001708rm+0x73/0xa0 [nvidia]
Jan 23 23:01:18 bloody [<f93de4a6>] _nv001847rm+0x26/0x2c [nvidia]
Jan 23 23:01:18 bloody [<f93ecf7c>] _nv000650rm+0x58/0xcc [nvidia]
Jan 23 23:01:18 bloody [<f93ecfd7>] _nv000650rm+0xb3/0xcc [nvidia]
Jan 23 23:01:18 bloody [<f93ed671>] _nv001362rm+0x71/0xb0 [nvidia]
Jan 23 23:01:18 bloody [<f93ed67e>] _nv001362rm+0x7e/0xb0 [nvidia]
Jan 23 23:01:18 bloody [<f93ea4be>] _nv001820rm+0x12/0x18 [nvidia]
Jan 23 23:01:18 bloody [<f93f00e7>] rm_disable_adapter+0x2f/0x8c [nvidia]
Jan 23 23:01:18 bloody [<f93f0117>] rm_disable_adapter+0x5f/0x8c [nvidia]
Jan 23 23:01:18 bloody [<f93f010b>] rm_disable_adapter+0x53/0x8c [nvidia]
Jan 23 23:01:18 bloody [<f95d1b78>] nv_kern_close+0x16f/0x1e0 [nvidia]
Jan 23 23:01:18 bloody [<c014a049>] __fput+0x95/0x120
Jan 23 23:01:18 bloody [<c0148caf>] filp_close+0x4c/0x55
Jan 23 23:01:18 bloody [<c0148d06>] sys_close+0x4e/0x5a
Jan 23 23:01:18 bloody [<c0102a9d>] syscall_call+0x7/0xb
Jan 23 23:01:18 bloody Code: 83 c4 0c 89 d9 8b 01 89 ca f6 c4 40 74 03 8b 51 0c
ff 42 04 eb 1d 84 c0 78 11 29 d3 c1 fb 05 c1 e3 0c 09 eb 89 1e ff 49 04 eb 08
<0f> 0b 89 00 54 68 35 c0 8b 01 f6 c4 04 75 7$
Jan 23 23:01:18 bloody kdm: :0[10935]: IO Error in XOpenDisplay
Jan 23 23:01:18 bloody kdm[10931]: Display :0 cannot be opened
Jan 23 23:01:18 bloody kdm[10931]: Unable to fire up local display :0;
disabling.

------- Comment #1 From Benjamin Greiner 2006-01-26 09:09:41 0000 ------- 
Same here

------- Comment #2 From Alex B. Bychko 2006-01-26 23:03:44 0000 ------- 
I get the same after kernel upgrade.
My configs in attachment.

------- Comment #3 From Alex B. Bychko 2006-01-26 23:13:29 0000 ------- 
Created an attachment (id=78265) [details]
My configs && messages

After upgrade to nvidia-kernel-1.0.6629-r5 games (Quake3, Quake4, Doom3)
produces delay after start (about 10-40 seconds). Strace shows only
gettimeofday() in the cycle while such delay occurs. After delay games work
fine.

------- Comment #4 From MAL 2006-02-03 03:12:19 0000 ------- 
I confirm the same as reporter.  Upgraded to 8178 and X now starts.

Out of interest, why is stable nvidia-kernel so old?

------- Comment #5 From David W Noon 2006-02-08 04:44:46 0000 ------- 
I also get the same as the original reporter. My only concern about upgrading
the nvidia-kernel package is that my video card is a GeForce MX-440, which is
not the newest chipset Nvidia makes, so it might not be supported by newer
versions of the video driver.

------- Comment #6 From David W Noon 2006-02-08 05:46:47 0000 ------- 
Well, I tried the newer drivers and they did not like my elderly GeForce2 card.
So, an immediate upgrade is not an option for me.

------- Comment #7 From Jakub Moc (RETIRED) 2006-02-12 04:42:34 0000 ------- 
*** Bug 122545 has been marked as a duplicate of this bug. ***

------- Comment #8 From Peter Kasting 2006-02-13 14:16:37 0000 ------- 
Using vanilla-sources-2.6.15.1, I saw this same problem, but an upgrade to
nvidia-kernel-1.0.8178-r3 did NOT fix my problem.  I have to use the "nv" X
driver instead of the "nvidia" driver, or my machine completely hangs trying to
start X.

------- Comment #9 From Rob David 2006-02-15 14:58:53 0000 ------- 
I've also been having very similar problems, but with slightly different
symptoms.

My system has (or rather had) an old GeForce 2 MX 400. Everything was working
fine with gentoo-sources-2.6.14-r5 and the latest stable nvidia drivers
1.0.6629-r5.

Upgrading to kernel 2.6.15-r1 with the same drivers resulted in an unstable
system. X would start OK, but when attempting to run something graphics
intensive, such as playing a DVD, I would get kernel  panics like this one:

Feb  7 23:48:35 delos kernel: Bad page state at free_hot_cold_page (in process
'xine', page c13ab620)
Feb  7 23:48:35 delos kernel: flags:0x80000400 mapping:00000000 mapcount:0
count:0
Feb  7 23:48:35 delos kernel: Backtrace:
Feb  7 23:48:35 delos kernel:  [bad_page+128/192] bad_page+0x80/0xc0
Feb  7 23:48:35 delos kernel:  [<c013c280>] bad_page+0x80/0xc0
Feb  7 23:48:35 delos kernel:  [free_hot_cold_page+97/272]
free_hot_cold_page+0x61/0x110
Feb  7 23:48:35 delos kernel:  [<c013cac1>] free_hot_cold_page+0x61/0x110
Feb  7 23:48:35 delos kernel:  [pg0+547209579/1067906048] _nv007274rm+0x13/0x34
[nvidia]
Feb  7 23:48:35 delos kernel:  [<e0f6b16b>] _nv007274rm+0x13/0x34 [nvidia]
Feb  7 23:48:35 delos kernel:  [pg0+549349562/1067906048]
nv_vm_free_pages+0x9b/0xdd [nvidia]
Feb  7 23:48:35 delos kernel:  [<e11758ba>] nv_vm_free_pages+0x9b/0xdd [nvidia]
Feb  7 23:48:35 delos kernel:  [pg0+549345198/1067906048]
nv_free_pages+0x1da/0x1f5 [nvidia]
Feb  7 23:48:35 delos kernel:  [<e11747ae>] nv_free_pages+0x1da/0x1f5 [nvidia]
Feb  7 23:48:35 delos kernel:  [pg0+547341938/1067906048] _nv001794rm+0x56/0x60
[nvidia]
Feb  7 23:48:35 delos kernel:  [<e0f8b672>] _nv001794rm+0x56/0x60 [nvidia]
Feb  7 23:48:35 delos kernel:  [pg0+547292326/1067906048] _nv001847rm+0x26/0x2c
[nvidia]
Feb  7 23:48:35 delos kernel:  [<e0f7f4a6>] _nv001847rm+0x26/0x2c [nvidia]
Feb  7 23:48:35 delos kernel:  [pg0+547211834/1067906048] _nv007231rm+0x9a/0xd4
[nvidia]
Feb  7 23:48:35 delos kernel:  [<e0f6ba3a>] _nv007231rm+0x9a/0xd4 [nvidia]
Feb  7 23:48:35 delos kernel:  [pg0+547249395/1067906048] _nv001334rm+0x87/0x98
[nvidia]
Feb  7 23:48:35 delos kernel:  [<e0f74cf3>] _nv001334rm+0x87/0x98 [nvidia]
Feb  7 23:48:35 delos kernel:  [pg0+547209579/1067906048] _nv007274rm+0x13/0x34
[nvidia]
Feb  7 23:48:35 delos kernel:  [<e0f6b16b>] _nv007274rm+0x13/0x34 [nvidia]
Feb  7 23:48:35 delos kernel:  [pg0+547248946/1067906048]
_nv001338rm+0x7e/0x140 [nvidia]
Feb  7 23:48:35 delos kernel:  [<e0f74b32>] _nv001338rm+0x7e/0x140 [nvidia]
Feb  7 23:48:35 delos kernel:  [pg0+547249009/1067906048]
_nv001338rm+0xbd/0x140 [nvidia]
Feb  7 23:48:35 delos kernel:  [<e0f74b71>] _nv001338rm+0xbd/0x140 [nvidia]
Feb  7 23:48:35 delos kernel:  [pg0+547245915/1067906048]
_nv001350rm+0x137/0x1f4 [nvidia]
Feb  7 23:48:35 delos kernel:  [<e0f73f5b>] _nv001350rm+0x137/0x1f4 [nvidia]
Feb  7 23:48:35 delos kernel:  [shrink_slab+132/496] shrink_slab+0x84/0x1f0
Feb  7 23:48:35 delos kernel:  [<c0143944>] shrink_slab+0x84/0x1f0
Feb  7 23:48:35 delos kernel:  [pg0+547341502/1067906048] _nv001820rm+0x12/0x18
[nvidia]
Feb  7 23:48:35 delos kernel:  [<e0f8b4be>] _nv001820rm+0x12/0x18 [nvidia]
Feb  7 23:48:35 delos kernel:  [pg0+547227951/1067906048] _nv004022rm+0x33/0xa0
[nvidia]
Feb  7 23:48:35 delos fetchmail[11020]: sleeping at Tue Feb  7 23:48:35 2006 
Feb  7 23:48:35 delos kernel:  [<e0f6f92f>] _nv004022rm+0x33/0xa0 [nvidia]
Feb  7 23:48:35 delos kernel:  [pg0+547228006/1067906048] _nv004022rm+0x6a/0xa0
[nvidia]
Feb  7 23:48:35 delos kernel:  [<e0f6f966>] _nv004022rm+0x6a/0xa0 [nvidia]
Feb  7 23:48:35 delos kernel:  [pg0+547369389/1067906048]
_nv001308rm+0x3d/0x53c [nvidia]
Feb  7 23:48:35 delos kernel:  [<e0f921ad>] _nv001308rm+0x3d/0x53c [nvidia]
Feb  7 23:48:35 delos kernel:  [pg0+547369875/1067906048]
_nv001308rm+0x223/0x53c [nvidia]
Feb  7 23:48:35 delos kernel:  [<e0f92393>] _nv001308rm+0x223/0x53c [nvidia]
Feb  7 23:48:35 delos kernel:  [pg0+547366167/1067906048] rm_ioctl+0x23/0x38
[nvidia]
Feb  7 23:48:35 delos kernel:  [<e0f91517>] rm_ioctl+0x23/0x38 [nvidia]
Feb  7 23:48:35 delos kernel:  [unset_nmi_callback+9/16]
unset_nmi_callback+0x9/0x10
Feb  7 23:48:35 delos kernel:  [<c0104629>] unset_nmi_callback+0x9/0x10
Feb  7 23:48:35 delos kernel:  [pg0+549340181/1067906048]
nv_kern_ioctl+0x33a/0x38d [nvidia]
Feb  7 23:48:35 delos kernel:  [<e1173415>] nv_kern_ioctl+0x33a/0x38d [nvidia]
Feb  7 23:48:35 delos kernel:  [unset_nmi_callback+9/16]
unset_nmi_callback+0x9/0x10
Feb  7 23:48:35 delos kernel:  [<c0104629>] unset_nmi_callback+0x9/0x10
Feb  7 23:48:35 delos kernel:  [do_ioctl+111/160] do_ioctl+0x6f/0xa0
Feb  7 23:48:35 delos kernel:  [<c016a86f>] do_ioctl+0x6f/0xa0
Feb  7 23:48:35 delos kernel:  [unset_nmi_callback+9/16]
unset_nmi_callback+0x9/0x10
Feb  7 23:48:35 delos kernel:  [<c0104629>] unset_nmi_callback+0x9/0x10
Feb  7 23:48:35 delos kernel:  [vfs_ioctl+101/464] vfs_ioctl+0x65/0x1d0
Feb  7 23:48:35 delos kernel:  [<c016aa55>] vfs_ioctl+0x65/0x1d0
Feb  7 23:48:35 delos kernel:  [unset_nmi_callback+9/16]
unset_nmi_callback+0x9/0x10
Feb  7 23:48:35 delos kernel:  [<c0104629>] unset_nmi_callback+0x9/0x10
Feb  7 23:48:35 delos kernel:  [sys_ioctl+69/128] sys_ioctl+0x45/0x80
Feb  7 23:48:35 delos kernel:  [<c016ac05>] sys_ioctl+0x45/0x80
Feb  7 23:48:35 delos kernel:  [unset_nmi_callback+9/16]
unset_nmi_callback+0x9/0x10
Feb  7 23:48:35 delos kernel:  [<c0104629>] unset_nmi_callback+0x9/0x10
Feb  7 23:48:35 delos kernel:  [sysenter_past_esp+84/117]
sysenter_past_esp+0x54/0x75
Feb  7 23:48:35 delos kernel:  [<c0102e27>] sysenter_past_esp+0x54/0x75
Feb  7 23:48:35 delos kernel:  [unset_nmi_callback+9/16]
unset_nmi_callback+0x9/0x10
Feb  7 23:48:35 delos kernel:  [<c0104629>] unset_nmi_callback+0x9/0x10
Feb  7 23:48:35 delos kernel: Trying to fix it up, but a reboot is needed

Often this would lead to a complete lockup. I then tried the 1.0.8178 nvidia
drivers with the above kernel. These were better

------- Comment #10 From Rob David 2006-02-15 14:58:53 0000 ------- 
I've also been having very similar problems, but with slightly different
symptoms.

My system has (or rather had) an old GeForce 2 MX 400. Everything was working
fine with gentoo-sources-2.6.14-r5 and the latest stable nvidia drivers
1.0.6629-r5.

Upgrading to kernel 2.6.15-r1 with the same drivers resulted in an unstable
system. X would start OK, but when attempting to run something graphics
intensive, such as playing a DVD, I would get kernel  panics like this one:

Feb  7 23:48:35 delos kernel: Bad page state at free_hot_cold_page (in process
'xine', page c13ab620)
Feb  7 23:48:35 delos kernel: flags:0x80000400 mapping:00000000 mapcount:0
count:0
Feb  7 23:48:35 delos kernel: Backtrace:
Feb  7 23:48:35 delos kernel:  [bad_page+128/192] bad_page+0x80/0xc0
Feb  7 23:48:35 delos kernel:  [<c013c280>] bad_page+0x80/0xc0
Feb  7 23:48:35 delos kernel:  [free_hot_cold_page+97/272]
free_hot_cold_page+0x61/0x110
Feb  7 23:48:35 delos kernel:  [<c013cac1>] free_hot_cold_page+0x61/0x110
Feb  7 23:48:35 delos kernel:  [pg0+547209579/1067906048] _nv007274rm+0x13/0x34
[nvidia]
Feb  7 23:48:35 delos kernel:  [<e0f6b16b>] _nv007274rm+0x13/0x34 [nvidia]
Feb  7 23:48:35 delos kernel:  [pg0+549349562/1067906048]
nv_vm_free_pages+0x9b/0xdd [nvidia]
Feb  7 23:48:35 delos kernel:  [<e11758ba>] nv_vm_free_pages+0x9b/0xdd [nvidia]
Feb  7 23:48:35 delos kernel:  [pg0+549345198/1067906048]
nv_free_pages+0x1da/0x1f5 [nvidia]
Feb  7 23:48:35 delos kernel:  [<e11747ae>] nv_free_pages+0x1da/0x1f5 [nvidia]
Feb  7 23:48:35 delos kernel:  [pg0+547341938/1067906048] _nv001794rm+0x56/0x60
[nvidia]
Feb  7 23:48:35 delos kernel:  [<e0f8b672>] _nv001794rm+0x56/0x60 [nvidia]
Feb  7 23:48:35 delos kernel:  [pg0+547292326/1067906048] _nv001847rm+0x26/0x2c
[nvidia]
Feb  7 23:48:35 delos kernel:  [<e0f7f4a6>] _nv001847rm+0x26/0x2c [nvidia]
Feb  7 23:48:35 delos kernel:  [pg0+547211834/1067906048] _nv007231rm+0x9a/0xd4
[nvidia]
Feb  7 23:48:35 delos kernel:  [<e0f6ba3a>] _nv007231rm+0x9a/0xd4 [nvidia]
Feb  7 23:48:35 delos kernel:  [pg0+547249395/1067906048] _nv001334rm+0x87/0x98
[nvidia]
Feb  7 23:48:35 delos kernel:  [<e0f74cf3>] _nv001334rm+0x87/0x98 [nvidia]
Feb  7 23:48:35 delos kernel:  [pg0+547209579/1067906048] _nv007274rm+0x13/0x34
[nvidia]
Feb  7 23:48:35 delos kernel:  [<e0f6b16b>] _nv007274rm+0x13/0x34 [nvidia]
Feb  7 23:48:35 delos kernel:  [pg0+547248946/1067906048]
_nv001338rm+0x7e/0x140 [nvidia]
Feb  7 23:48:35 delos kernel:  [<e0f74b32>] _nv001338rm+0x7e/0x140 [nvidia]
Feb  7 23:48:35 delos kernel:  [pg0+547249009/1067906048]
_nv001338rm+0xbd/0x140 [nvidia]
Feb  7 23:48:35 delos kernel:  [<e0f74b71>] _nv001338rm+0xbd/0x140 [nvidia]
Feb  7 23:48:35 delos kernel:  [pg0+547245915/1067906048]
_nv001350rm+0x137/0x1f4 [nvidia]
Feb  7 23:48:35 delos kernel:  [<e0f73f5b>] _nv001350rm+0x137/0x1f4 [nvidia]
Feb  7 23:48:35 delos kernel:  [shrink_slab+132/496] shrink_slab+0x84/0x1f0
Feb  7 23:48:35 delos kernel:  [<c0143944>] shrink_slab+0x84/0x1f0
Feb  7 23:48:35 delos kernel:  [pg0+547341502/1067906048] _nv001820rm+0x12/0x18
[nvidia]
Feb  7 23:48:35 delos kernel:  [<e0f8b4be>] _nv001820rm+0x12/0x18 [nvidia]
Feb  7 23:48:35 delos kernel:  [pg0+547227951/1067906048] _nv004022rm+0x33/0xa0
[nvidia]
Feb  7 23:48:35 delos fetchmail[11020]: sleeping at Tue Feb  7 23:48:35 2006 
Feb  7 23:48:35 delos kernel:  [<e0f6f92f>] _nv004022rm+0x33/0xa0 [nvidia]
Feb  7 23:48:35 delos kernel:  [pg0+547228006/1067906048] _nv004022rm+0x6a/0xa0
[nvidia]
Feb  7 23:48:35 delos kernel:  [<e0f6f966>] _nv004022rm+0x6a/0xa0 [nvidia]
Feb  7 23:48:35 delos kernel:  [pg0+547369389/1067906048]
_nv001308rm+0x3d/0x53c [nvidia]
Feb  7 23:48:35 delos kernel:  [<e0f921ad>] _nv001308rm+0x3d/0x53c [nvidia]
Feb  7 23:48:35 delos kernel:  [pg0+547369875/1067906048]
_nv001308rm+0x223/0x53c [nvidia]
Feb  7 23:48:35 delos kernel:  [<e0f92393>] _nv001308rm+0x223/0x53c [nvidia]
Feb  7 23:48:35 delos kernel:  [pg0+547366167/1067906048] rm_ioctl+0x23/0x38
[nvidia]
Feb  7 23:48:35 delos kernel:  [<e0f91517>] rm_ioctl+0x23/0x38 [nvidia]
Feb  7 23:48:35 delos kernel:  [unset_nmi_callback+9/16]
unset_nmi_callback+0x9/0x10
Feb  7 23:48:35 delos kernel:  [<c0104629>] unset_nmi_callback+0x9/0x10
Feb  7 23:48:35 delos kernel:  [pg0+549340181/1067906048]
nv_kern_ioctl+0x33a/0x38d [nvidia]
Feb  7 23:48:35 delos kernel:  [<e1173415>] nv_kern_ioctl+0x33a/0x38d [nvidia]
Feb  7 23:48:35 delos kernel:  [unset_nmi_callback+9/16]
unset_nmi_callback+0x9/0x10
Feb  7 23:48:35 delos kernel:  [<c0104629>] unset_nmi_callback+0x9/0x10
Feb  7 23:48:35 delos kernel:  [do_ioctl+111/160] do_ioctl+0x6f/0xa0
Feb  7 23:48:35 delos kernel:  [<c016a86f>] do_ioctl+0x6f/0xa0
Feb  7 23:48:35 delos kernel:  [unset_nmi_callback+9/16]
unset_nmi_callback+0x9/0x10
Feb  7 23:48:35 delos kernel:  [<c0104629>] unset_nmi_callback+0x9/0x10
Feb  7 23:48:35 delos kernel:  [vfs_ioctl+101/464] vfs_ioctl+0x65/0x1d0
Feb  7 23:48:35 delos kernel:  [<c016aa55>] vfs_ioctl+0x65/0x1d0
Feb  7 23:48:35 delos kernel:  [unset_nmi_callback+9/16]
unset_nmi_callback+0x9/0x10
Feb  7 23:48:35 delos kernel:  [<c0104629>] unset_nmi_callback+0x9/0x10
Feb  7 23:48:35 delos kernel:  [sys_ioctl+69/128] sys_ioctl+0x45/0x80
Feb  7 23:48:35 delos kernel:  [<c016ac05>] sys_ioctl+0x45/0x80
Feb  7 23:48:35 delos kernel:  [unset_nmi_callback+9/16]
unset_nmi_callback+0x9/0x10
Feb  7 23:48:35 delos kernel:  [<c0104629>] unset_nmi_callback+0x9/0x10
Feb  7 23:48:35 delos kernel:  [sysenter_past_esp+84/117]
sysenter_past_esp+0x54/0x75
Feb  7 23:48:35 delos kernel:  [<c0102e27>] sysenter_past_esp+0x54/0x75
Feb  7 23:48:35 delos kernel:  [unset_nmi_callback+9/16]
unset_nmi_callback+0x9/0x10
Feb  7 23:48:35 delos kernel:  [<c0104629>] unset_nmi_callback+0x9/0x10
Feb  7 23:48:35 delos kernel: Trying to fix it up, but a reboot is needed

Often this would lead to a complete lockup. I then tried the 1.0.8178 nvidia
drivers with the above kernel. These were better – a DVD would play, but
certain programs using graphics (tuxracer, xmame, sdlquake2) would lock up the
system at the point when they tried put the display into a different
resolution. I tried the 1.0.7676 driver but it produced the same kind of
aforementioned kernel panics. 

I've since upgraded my graphics card to a GeForce 6200, and I still get the
same lockups with the 2.6.15-r1 kernel and 1.0.8178 driver combination.

All these problems go away if I downgrade to gentoo-sources-2.6.14-r5 and
nvidia drivers 1.0.7676.

So basically, the 2.6.15 kernel is unstable for me with every nvidia driver
I've tried.

Result of emerge –info below.

Gentoo Base System version 1.6.14
Portage 2.0.54 (default-linux/x86/2005.1, gcc-3.3.6, glibc-2.3.5-r2,
2.6.14-gentoo-r5 i686)
=================================================================
System uname: 2.6.14-gentoo-r5 i686 AMD Athlon(tm) XP 2400+
dev-lang/python:     2.3.5-r2, 2.4.2
sys-apps/sandbox:    1.2.12
sys-devel/autoconf:  2.13, 2.59-r6
sys-devel/automake:  1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.6-r1
sys-devel/binutils:  2.16.1
sys-devel/libtool:   1.5.22
virtual/os-headers:  2.6.11-r2
ACCEPT_KEYWORDS="x86"
AUTOCLEAN="yes"
CBUILD="i686-pc-linux-gnu"
CFLAGS="-O3 -mcpu=athlon-xp -pipe"
CHOST="i686-pc-linux-gnu"
CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3.3/env
/usr/kde/3.3/share/config /usr/kde/3.3/shutdown /usr/kde/3.4/env
/usr/kde/3.4/share/config /usr/kde/3.4/shutdown /usr/kde/3/share/config
/usr/lib/X11/xkb /usr/lib/fax /usr/lib/mozilla/defaults/pref /usr/share/config
/usr/share/texmf/dvipdfm/config/ /usr/share/texmf/dvips/config/
/usr/share/texmf/tex/generic/config/ /usr/share/texmf/tex/platex/config/
/usr/share/texmf/xdvi/ /var/qmail/control /var/spool/fax/etc"
CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d"
CXXFLAGS="-O3 -mcpu=athlon-xp -pipe"
DISTDIR="/usr/portage/distfiles"
FEATURES="autoconfig distlocks sandbox sfperms strict"
GENTOO_MIRRORS="ftp://mirrors.blueyonder.co.uk/mirrors/gentoo
ftp://ftp6.uni-erlangen.de/pub/mirrors/gentoo
ftp://ftp.ipv6.uni-muenster.de/pub/linux/distributions/gentoo
http://vlaai.snt.ipv6.utwente.nl/pub/os/linux/gentoo/
http://ftp6.uni-erlangen.de/pub/mirrors/gentoo ftp://ftp.demon.co.uk/pub/CPAN"
LANG="en_GB.UTF-8"
MAKEOPTS="-j2"
PKGDIR="/usr/portage/packages"
PORTAGE_TMPDIR="/var/tmp"
PORTDIR="/usr/portage"
PORTDIR_OVERLAY="/usr/local/portage"
SYNC="rsync://rsync.gentoo.org/gentoo-portage"
USE="x86 X alsa apm audiofile avi berkdb bitmap-fonts bonobo bzip2 cdb
cdparanoia cdr crypt cups curl dvd dvdr dvdread eds emacs emboss encode esd
ethereal exif expat fam ffmpeg flac foomaticdb fortran ftp gcj gd gdbm gif glut
gmp gnome gphoto2 gpm gstreamer gtk gtk2 gtkhtml hal idn imagemagick imap imlib
ipv6 java joystick jpeg junit lcms ldap libg++ libwww lm_sensors lua mad mbox
mhash mikmod mime mmx mng motif mozilla mp3 mpeg mysql ncurses nls nptl nvidia
ogg oggvorbis openal opengl oss pam pcre pda pdflib perl php png posix postgres
ppds python quicktime readline recode ruby samba sdl sox speex spell ssl svga
tcltk tcpd tetex threads tiff truetype truetype-fonts type1-fonts udev usb vcd
videos vorbis wxwindows xine xml xml2 xmms xpm xv xvid zlib userland_GNU
kernel_linux elibc_glibc"
Unset:  ASFLAGS, CTARGET, LC_ALL, LDFLAGS, LINGUAS

------- Comment #11 From David W Noon 2006-02-15 17:11:16 0000 ------- 
(In reply to comment #9)
[snip]
> Upgrading to kernel 2.6.15-r1 with the same drivers resulted in an unstable
> system. X would start OK, but when attempting to run something graphics
> intensive, such as playing a DVD, I would get kernel  panics like this one:
[snip]

Did you upgrade nvidia-glx too?

------- Comment #12 From Rob David 2006-02-16 04:06:05 0000 ------- 
Yes. It's been my experience that X will refuse the start if the kernel module
and the glx libraries don't match up.

------- Comment #13 From Martin von Gagern 2006-02-19 04:09:05 0000 ------- 
I have the same problem with nvidia-1.0.6629-r5 and linux-2.6.15-gentoo-r1.
Once I had a text mode curser on this blank screen. When updating to
1.0.8178-r3, I get a "no screens found" error instead. This might be related to
bug #81343 which already caused trouble on my system several times. I'm now
using the nv driver.

------- Comment #14 From Kim Pedersen 2006-03-03 07:31:50 0000 ------- 
I am using gentoo-sources-2.6.15-r1 and nvidia-kernel-1.0.6629-r5 and I am able
to use X with NVidia.
However it does write the following:
NVIDIA: Failed to set MTRR 0x80000000, 128M (write-combining)

Regarding the no screens found (#12), have you tried  running NVmakedevices.sh?

------- Comment #15 From David W Noon 2006-03-07 03:38:30 0000 ------- 
I had problems (X start-up world hang) when I installed 1.0.8178, but I tried
nvidia-kernel-1.0.8178-r3/nvidia-glx-1.0.8178 and they work -- even with my old
GeForce2 card!

I needed to add the following lines to /etc/portage/package.keywords:
=media-video/nvidia-kernel-1.0.8178-r3 ~x86
=media-video/nvidia-glx-1.0.8178 ~x86
=app-admin/eselect-1.0 ~x86
=app-admin/eselect-opengl-1.0.3 ~x86

One thing I have noticed is that the NVidia logo during X start-up now stays on
the screen much longer than it did before. It used to be there for about 1/4
second, but now it stays for almost a second. Perhaps the revised driver probes
for more models of GeForce chipsets.

Anyhow, I can now run the 2.6.15 kernel.

------- Comment #16 From Rob David 2006-03-07 17:26:31 0000 ------- 
> 
> Anyhow, I can now run the 2.6.15 kernel.
> 

Have you tried any graphics intensive stuff with your configuration? I've tried
the same combination of packages, and X starts OK for me too, but some programs
will still crash my system, which work fine with older kernel/nvidia. Good
candidates are anything that tries switch to a different resolution (eg.
TuxRacer). I'd be interested if you experience anything similar.

------- Comment #17 From David W Noon 2006-03-07 17:38:49 0000 ------- 
(In reply to comment #15)
> > 
> > Anyhow, I can now run the 2.6.15 kernel.
> > 
> 
> Have you tried any graphics intensive stuff with your configuration?

I have just tried Critical Mass (an OpenGL game), Celestia and Stellarium (both
planetarium programs). I also use an OpenGL screensaver. All work well.

The new drivers also solve the "no screens found" problem that was introduced a
couple of kernels ago.

------- Comment #18 From Rob David 2006-05-04 17:19:17 0000 ------- 
Futher update:

I've now upgraded to the latest nvidia drivers (1.0.8756) and to kernel
2.6.16-gentoo-r3. I've been running this for a week or so now, and I have had
no re-occurence of any of my previous problems. Since these have been very easy
to re-create in the past, it would appear the problem has been cured for me.

------- Comment #19 From Doug Goldstein 2007-07-14 11:12:21 0000 ------- 
Based on user feedback, this appears fixed.
First Last Prev Next    No search results available      Search page      Enter new bug