Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 36883 - nvidia-kernel-1.0.5328 seems to result in "sleeping function called from invalid context"
Summary: nvidia-kernel-1.0.5328 seems to result in "sleeping function called from inva...
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: New packages (show other bugs)
Hardware: x86 Linux
: High normal
Assignee: Gentoo X packagers
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-12-31 05:43 UTC by Vermyndax
Modified: 2009-08-20 12:02 UTC (History)
8 users (show)

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Vermyndax 2003-12-31 05:43:51 UTC
I'm getting this line every 10 seconds or so in my /var/log/current:

sleeping function called from invalid context at mm/slab.c:1856

After much reading and comparing, this appears to be coming from my NVidia drivers working on kernel 2.6.0.  I have updated to the latest nvidia-kernel ebuild.  The changelog mentions that the minions.de patch was included in 4368 (I think) but on the 5xxx driver I'm receiving this message.  Did the minions.de patch get included in the latest nvidia-kernel?  There is one available at http://www.minions.de if not.
Comment 1 Donnie Berkholz (RETIRED) gentoo-dev 2003-12-31 11:54:21 UTC
Yes, it's there and applied for 2.6 kernels. You can assume it's there unless the changelog says otherwise; if it weren't there, the ebuild wouldn't have compiled for a 2.6 kernel.
Comment 2 Donnie Berkholz (RETIRED) gentoo-dev 2003-12-31 11:56:40 UTC
Do you get this message from 2.4 kernels with the "nvidia" driver, or from 2.6 kernels using the "nv" driver?
Comment 3 Vermyndax 2003-12-31 15:05:56 UTC
I'm getting this from the 2.6.0 kernel using the "nvidia" driver... hence why I'm confused about the patch being applied.

Evidence:

asteria-linux root # uname -r
2.6.0-gentoo

From /var/log/everything/current:
Dec 31 07:05:01 [kernel] Debug: sleeping function called from invalid context at mm/slab.c:1856
                - Last output repeated 8 times -
Dec 31 07:05:21 [kernel]  [<e0d7f308>] _nv002465rm+0x98/0x420 [nvidia]

...and again later:

Dec 31 07:11:00 [CRON] (root) CMD (test -x /usr/sbin/run-crons && /usr/sbin/run-crons )_
Dec 31 07:11:00 [kernel] Debug: sleeping function called from invalid context at mm/slab.c:1856
Dec 31 07:11:00 [kernel] in_atomic():1, irqs_disabled():0
Dec 31 07:11:00 [kernel] Call Trace:
Dec 31 07:11:04 [kernel] Debug: sleeping function called from invalid context at mm/slab.c:1856
                - Last output repeated 10 times -

...

asteria-linux everything # genlop nvidia-kernel
 * media-video/nvidia-kernel

     Wed Dec 24 02:54:24 2003 --> media-video/nvidia-kernel-1.0.4496-r4
     Mon Dec 29 10:25:54 2003 --> media-video/nvidia-kernel-1.0.5328

 merged totally 2 ebuilds

...

asteria-linux everything # emerge -s nvidia-kernel
Searching...
[ Results for search key : nvidia-kernel ]
[ Applications found : 1 ]

*  media-video/nvidia-kernel
      Latest version available: 1.0.5328
      Latest version installed: 1.0.5328
      Size of downloaded files: 6,694 kB
      Homepage:    http://www.nvidia.com/
      Description: Linux kernel module for the NVIDIA's X driver

Comment 4 Donnie Berkholz (RETIRED) gentoo-dev 2003-12-31 21:44:22 UTC
Yes I'm aware of where you encounter the issue. I'm asking you to test other cases to try removing the issue.

Also, what basis do you have for suggesting the minion.de patch has anything to do with this? I'd like to see some links, etc.
Comment 5 Vermyndax 2003-12-31 22:24:21 UTC
The place I got my information was from this discussion:

http://www.ussg.iu.edu/hypermail/linux/kernel/0311.3/0372.html

Digging a little deeper, it looks like if I disable "sleep inside spinlock" or something to that effect, this error message will go away... I googled with the search of:

sleeping function called from invalid context at mm/slab.c:1856 nvidia

Someone mentioned that this didn't start happening until after applying the minion.de patch.  Whoa, I'm confused.  You kernel hackers will definitely know better than me.
Comment 6 Donnie Berkholz (RETIRED) gentoo-dev 2003-12-31 22:55:42 UTC
"Not really, it just shows the nvidia driver being buggy and using a
sleeping gfp allocation mask when it should not."

http://www.ussg.iu.edu/hypermail/linux/kernel/0311.3/0485.html
Comment 7 Vermyndax 2004-01-03 10:38:26 UTC
More info...

Now I see this in my dmesg:

Debug: sleeping function called from invalid context at mm/slab.c:1856
in_atomic():1, irqs_disabled():0
Call Trace:
 [<c0121424>] __might_sleep+0xab/0xc9
 [<c0145d2d>] __kmalloc+0x8f/0x96
 [<e0cc7efa>] os_alloc_mem+0x5c/0x87 [nvidia]
 [<e0ce2380>] _nv001308rm+0x10/0x28 [nvidia]
 [<e0dfab1d>] _nv001518rm+0x7c9/0xb34 [nvidia]
 [<c02d645e>] ide_build_sglist+0x3d/0xa9
 [<e0d7f2f1>] _nv002465rm+0x81/0x420 [nvidia]
 [<e0d7f308>] _nv002465rm+0x98/0x420 [nvidia]
 [<e0cd7ef5>] _nv001338rm+0x1d/0x24 [nvidia]
 [<e0cc8ae5>] _nv005601rm+0xd/0x34 [nvidia]
 [<e0cd01c8>] _nv000858rm+0x300/0xe14 [nvidia]
 [<c0110d60>] timer_interrupt+0x7c/0x172
 [<c010c589>] handle_IRQ_event+0x39/0x62
 [<c010c96d>] do_IRQ+0xf0/0x197
 [<e0ccfec8>] _nv000858rm+0x0/0xe14 [nvidia]
 [<e0ccc47d>] _nv002962rm+0x2c5/0x3b8 [nvidia]
 [<e0ce6e39>] _nv000899rm+0x4c9/0xf70 [nvidia]
 [<e0ce6e4c>] _nv000899rm+0x4dc/0xf70 [nvidia]
 [<c01fe1f8>] search_for_position_by_key+0x1a4/0x3c8
 [<c01e8a4e>] _make_cpu_key+0x4e/0xb9
 [<c01e8b0d>] make_cpu_key+0x54/0x5e
 [<c01fceb2>] pathrelse+0x25/0x37
 [<c01e92a1>] _get_block_create_0+0x6ac/0x76a
 [<e0dadc2b>] _nv001532rm+0x1f/0x28 [nvidia]
 [<c011e11b>] wake_up_state+0x1a/0x1e
 [<e0dadc2b>] _nv001532rm+0x1f/0x28 [nvidia]
 [<e0dadd6b>] _nv001556rm+0x5b/0x6c [nvidia]
 [<e0dadc2b>] _nv001532rm+0x1f/0x28 [nvidia]
 [<e0dadd6b>] _nv001556rm+0x5b/0x6c [nvidia]
 [<e0dadd6b>] _nv001556rm+0x5b/0x6c [nvidia]
 [<e0dae46d>] _nv003622rm+0x15/0x1c [nvidia]
 [<e0df6ae0>] _nv001826rm+0xb0/0xbc [nvidia]
 [<e0dadd6b>] _nv001556rm+0x5b/0x6c [nvidia]
 [<e0dae46d>] _nv003622rm+0x15/0x1c [nvidia]
 [<e0df6ae0>] _nv001826rm+0xb0/0xbc [nvidia]
 [<e0dadd6b>] _nv001556rm+0x5b/0x6c [nvidia]
 [<e0dae46d>] _nv003622rm+0x15/0x1c [nvidia]
 [<e0d90cdd>] _nv003795rm+0xad9/0xaec [nvidia]
 [<e0dadc2b>] _nv001532rm+0x1f/0x28 [nvidia]
 [<e0cfa828>] _nv004240rm+0x180/0x18c [nvidia]
 [<e0dadbdc>] _nv001534rm+0x20/0x28 [nvidia]
 [<e0ce36d2>] _nv001223rm+0x12/0x18 [nvidia]
 [<e0cfabd7>] _nv004046rm+0x3a3/0x3b0 [nvidia]
 [<e0ce36d2>] _nv001223rm+0x12/0x18 [nvidia]
 [<c014200e>] buffered_rmqueue+0xed/0x194
 [<c014215c>] __alloc_pages+0xa7/0x332
 [<c01478d6>] __pagevec_lru_add_active+0x112/0x139
 [<c014d13c>] do_anonymous_page+0x164/0x27d
 [<c011e11b>] wake_up_state+0x1a/0x1e
 [<e0e436bf>] _nv000176rm+0x57/0x3ec [nvidia]
 [<c011dbfa>] recalc_task_prio+0x90/0x1aa
 [<c03937d1>] kfree_skbmem+0x25/0x2c
 [<c0393840>] __kfree_skb+0x68/0xd4
 [<c0111ce9>] convert_fxsr_to_user+0xbf/0x147
 [<c011dbfa>] recalc_task_prio+0x90/0x1aa
 [<c0111f1d>] save_i387_fxsave+0xc9/0xfb
 [<c0109b18>] setup_sigcontext+0xe3/0x129
 [<e0ce6541>] rm_ioctl+0x19/0x20 [nvidia]
 [<e0cc5b1b>] nv_kern_ioctl+0x4de/0x529 [nvidia]
 [<c010a0ac>] handle_signal+0xd9/0x154
 [<c012c760>] update_wall_time+0xf/0x3a
 [<c012cb9b>] do_timer+0xc1/0xc6
 [<c0110d60>] timer_interrupt+0x7c/0x172
 [<c010c589>] handle_IRQ_event+0x39/0x62
 [<c016eb66>] sys_ioctl+0x120/0x2c6
 [<c010a437>] syscall_call+0x7/0xb
Comment 8 Mike Tangolics 2004-01-06 17:29:30 UTC
I'm having the exact same problems... Everytime so often (about 10-15 sec or when something graphical happens) the aforementioned error appears in my kernel log.  
I'll include as much information as I can.

main root # uname -r
2.6.1-rc2-gentoo

------------------- /var/log/kernel/current (excerpt)

Jan  6 20:11:48 [kernel] Debug: sleeping function called from invalid context at mm/slab.c:1856
                - Last output repeated 19 times -
Jan  6 20:14:34 [kernel]  [<e1d709ba>] _nv001344rm+0x22/0x6c [nvidia]
Jan  6 20:14:36 [kernel] Debug: sleeping function called from invalid context at mm/slab.c:1856
                - Last output repeated 10 times -
Jan  6 20:15:00 [kernel] in_atomic():1, irqs_disabled():0
Jan  6 20:15:00 [kernel] Call Trace:
Jan  6 20:15:08 [kernel] Debug: sleeping function called from invalid context at mm/slab.c:1856
                - Last output repeated 18 times -
Jan  6 20:18:44 [kernel] in_atomic():1, irqs_disabled():0
Jan  6 20:18:44 [kernel] Call Trace:
Jan  6 20:18:49 [kernel] Debug: sleeping function called from invalid context at mm/slab.c:1856

------------------- dmesg output (debugging from the error messages above)(also excerpt)

Debug: sleeping function called from invalid context at mm/slab.c:1856
in_atomic():1, irqs_disabled():0
Call Trace:
 [<c011f76a>] __might_sleep+0xab/0xc9
 [<c0140495>] __kmalloc+0x93/0x9a
 [<e1d60bba>] os_alloc_mem+0x5c/0x87 [nvidia]
 [<e1d7afd0>] _nv001308rm+0x10/0x28 [nvidia]
 [<e1e9376d>] _nv001518rm+0x7c9/0xb34 [nvidia]
 [<e1e17f41>] _nv002465rm+0x81/0x420 [nvidia]
 [<e1e17f58>] _nv002465rm+0x98/0x420 [nvidia]
 [<e1d70b45>] _nv001338rm+0x1d/0x24 [nvidia]
 [<e1d61735>] _nv005601rm+0xd/0x34 [nvidia]
 [<e1d68e18>] _nv000858rm+0x300/0xe14 [nvidia]
 [<c01561ff>] __getblk+0x2f/0x59
 [<c01ff4c8>] is_tree_node+0x66/0x68
 [<c01ffbd8>] search_by_key+0x70e/0xee1
 [<e1d6a1c8>] _nv000917rm+0x18c/0x1ac [nvidia]
 [<c010bbb2>] apic_timer_interrupt+0x1a/0x20
 [<e1d650cd>] _nv002962rm+0x2c5/0x3b8 [nvidia]
 [<e1d7fa89>] _nv000899rm+0x4c9/0xf70 [nvidia]
 [<e1d7fa9c>] _nv000899rm+0x4dc/0xf70 [nvidia]
 [<c01eb129>] make_cpu_key+0x54/0x5e
 [<c01ff209>] pathrelse+0x25/0x37
 [<c01eb8c0>] _get_block_create_0+0x6af/0x73c
 [<c0227908>] __delay+0x14/0x18
 [<c0383c8e>] dev_queue_xmit+0x216/0x2a8
 [<c0227908>] __delay+0x14/0x18
 [<c0227908>] __delay+0x14/0x18
 [<c0227908>] __delay+0x14/0x18
 [<e1edc30f>] _nv000176rm+0x57/0x3ec [nvidia]
 [<c03ab087>] tcp_send_delayed_ack+0xca/0xf3
 [<c03a6fd9>] tcp_rcv_established+0x229/0x6fc
 [<e1edc30f>] _nv000176rm+0x57/0x3ec [nvidia]
 [<c0227908>] __delay+0x14/0x18
 [<c0383c8e>] dev_queue_xmit+0x216/0x2a8
 [<c039ade1>] ip_finish_output2+0xc0/0x1b3
 [<c038df5d>] nf_hook_slow+0xee/0x139
 [<c039ad21>] ip_finish_output2+0x0/0x1b3
 [<c0398ae0>] ip_finish_output+0x206/0x20b
 [<c039ad21>] ip_finish_output2+0x0/0x1b3
 [<c039ad09>] dst_output+0x15/0x2d
 [<c038df5d>] nf_hook_slow+0xee/0x139
 [<c039acf4>] dst_output+0x0/0x2d
 [<c03991a2>] ip_queue_xmit+0x4ae/0x5b0
 [<c039acf4>] dst_output+0x0/0x2d
 [<e1d709ba>] _nv001344rm+0x22/0x6c [nvidia]
 [<e1e469bb>] _nv001556rm+0x5b/0x6c [nvidia]
 [<c010bbb2>] apic_timer_interrupt+0x1a/0x20
 [<c011d4fa>] recalc_task_prio+0x90/0x1aa
 [<c0109a48>] __switch_to+0x118/0x182
 [<c011e1e2>] schedule+0x329/0x57b
 [<c011e4ba>] __wake_up_common+0x31/0x50
 [<c0227d7e>] __copy_to_user_ll+0x64/0x68
 [<c03811b6>] memcpy_toiovec+0x6c/0x9a
 [<c01121a5>] convert_fxsr_to_user+0xbf/0x147
 [<c01123d9>] save_i387_fxsave+0xc9/0xfb
 [<c010a982>] setup_sigcontext+0xe3/0x129
 [<e1d7f191>] rm_ioctl+0x19/0x20 [nvidia]
 [<e1d5ea08>] nv_kern_ioctl+0x4de/0x529 [nvidia]
 [<c010af01>] handle_signal+0xc4/0x12a
 [<c0112252>] convert_fxsr_from_user+0x25/0xe3
 [<c0112598>] restore_i387_fxsave+0x84/0x8f
 [<c0112639>] restore_i387+0x96/0x98
 [<c010a6ac>] restore_sigcontext+0x116/0x130
 [<c0165011>] sys_ioctl+0x106/0x291
 [<c010b223>] syscall_call+0x7/0xb

Debug: sleeping function called from invalid context at mm/slab.c:1856
in_atomic():1, irqs_disabled():0
Call Trace:
 [<c011f76a>] __might_sleep+0xab/0xc9
 [<c0140495>] __kmalloc+0x93/0x9a
 [<e1d60bba>] os_alloc_mem+0x5c/0x87 [nvidia]
 [<e1d7afd0>] _nv001308rm+0x10/0x28 [nvidia]
 [<e1e9376d>] _nv001518rm+0x7c9/0xb34 [nvidia]
 [<e1e17f41>] _nv002465rm+0x81/0x420 [nvidia]
 [<e1e17f58>] _nv002465rm+0x98/0x420 [nvidia]
 [<e1d70b45>] _nv001338rm+0x1d/0x24 [nvidia]
 [<e1d61735>] _nv005601rm+0xd/0x34 [nvidia]
 [<e1d68e18>] _nv000858rm+0x300/0xe14 [nvidia]
 [<c01561ff>] __getblk+0x2f/0x59
 [<c01ff4c8>] is_tree_node+0x66/0x68
 [<c01ffbd8>] search_by_key+0x70e/0xee1
 [<e1d6a1c8>] _nv000917rm+0x18c/0x1ac [nvidia]
 [<c010bbb2>] apic_timer_interrupt+0x1a/0x20
 [<e1d650cd>] _nv002962rm+0x2c5/0x3b8 [nvidia]
 [<e1d7fa89>] _nv000899rm+0x4c9/0xf70 [nvidia]
 [<e1d7fa9c>] _nv000899rm+0x4dc/0xf70 [nvidia]
 [<c01eb129>] make_cpu_key+0x54/0x5e
 [<c01ff209>] pathrelse+0x25/0x37
 [<c01eb8c0>] _get_block_create_0+0x6af/0x73c
 [<c0227908>] __delay+0x14/0x18
 [<c0383c8e>] dev_queue_xmit+0x216/0x2a8
 [<c0227908>] __delay+0x14/0x18
 [<c0227908>] __delay+0x14/0x18
 [<c0227908>] __delay+0x14/0x18
 [<e1edc30f>] _nv000176rm+0x57/0x3ec [nvidia]
 [<c03ab087>] tcp_send_delayed_ack+0xca/0xf3
 [<c03a6fd9>] tcp_rcv_established+0x229/0x6fc
 [<e1edc30f>] _nv000176rm+0x57/0x3ec [nvidia]
 [<c0227908>] __delay+0x14/0x18
 [<c0227908>] __delay+0x14/0x18
 [<c0383c8e>] dev_queue_xmit+0x216/0x2a8
 [<c039ade1>] ip_finish_output2+0xc0/0x1b3
 [<c038df5d>] nf_hook_slow+0xee/0x139
 [<c039ad21>] ip_finish_output2+0x0/0x1b3
 [<c0398ae0>] ip_finish_output+0x206/0x20b
 [<c039ad21>] ip_finish_output2+0x0/0x1b3
 [<c039ad09>] dst_output+0x15/0x2d
 [<c038df5d>] nf_hook_slow+0xee/0x139
 [<c039acf4>] dst_output+0x0/0x2d
 [<c03991a2>] ip_queue_xmit+0x4ae/0x5b0
 [<c039acf4>] dst_output+0x0/0x2d
 [<c012994e>] update_process_times+0x46/0x50
 [<c01297cc>] update_wall_time+0xf/0x3a
 [<c0129c0a>] do_timer+0xdf/0xe4
 [<c0111276>] timer_interrupt+0x54/0x121
 [<c03ab087>] tcp_send_delayed_ack+0xca/0xf3
 [<c03af8e9>] tcp_v4_do_rcv+0x119/0x11e
 [<c03afeae>] tcp_v4_rcv+0x5c0/0x7a3
 [<c0396047>] ip_local_deliver_finish+0xae/0x156
 [<c0395f99>] ip_local_deliver_finish+0x0/0x156
 [<c038df5d>] nf_hook_slow+0xee/0x139
 [<c0395f99>] ip_local_deliver_finish+0x0/0x156
 [<c01121a5>] convert_fxsr_to_user+0xbf/0x147
 [<c01123d9>] save_i387_fxsave+0xc9/0xfb
 [<c010a982>] setup_sigcontext+0xe3/0x129
 [<e1d7f191>] rm_ioctl+0x19/0x20 [nvidia]
 [<e1d5ea08>] nv_kern_ioctl+0x4de/0x529 [nvidia]
 [<c010af01>] handle_signal+0xc4/0x12a
 [<c0112252>] convert_fxsr_from_user+0x25/0xe3
 [<c0112598>] restore_i387_fxsave+0x84/0x8f
 [<c0112639>] restore_i387+0x96/0x98
 [<c010a6ac>] restore_sigcontext+0x116/0x130
 [<c0165011>] sys_ioctl+0x106/0x291
 [<c010b223>] syscall_call+0x7/0xb


I recompiled nvidia-kernel-1.0.5328 when i installed 2.6, and that's when the error messages began.  I assume removing that spinlock option in the kernel would get rid of the errors, but there is SERIOUS performance degradation associated with this.  i.e. glxgears gives me 17 fps average on my GeForce4
Comment 9 Mike Tangolics 2004-01-15 11:44:17 UTC
I don't know whether it was fixed in 2.6.1 or not, but I turned off spinlock checking in my config, and from what I can tell, the majority of speed has been restored.
Comment 10 peteru 2004-01-23 04:43:11 UTC
I've also seen this bug and the symptoms that I am seeing appear to be more serious than others are reporting.

I have a system that I use for capturing and playback of DVB-T material. Typical scenario is for one process to record an MPEG2 DVB stream to a file. Another process will be reading a different file from the disk, decoding the MPEG2 stream and displaying it using xv on an nVidia NV17 MX440 card.

In gentoo-dev-sources-2.6.1-r1 with nvidia-kernel-1.0.5328-r1 I get the following:

Debug: sleeping function called from invalid context at mm/slab.c:1856
APIC error on CPU0: 60(60)
APIC error on CPU0: 60(60)
Debug: sleeping function called from invalid context at mm/slab.c:1856

This can go for about 10-30 minutes until the system becomes unstable and starts having issues with IDE drive access, eventually resulting in a system corrupted so badly it requires a cold boot. The push of a reset button does not fix up the corrupted state that the hard disk is left in, only a powercycle brings the machine back.

Exact dmesg:

Debug: sleeping function called from invalid context at mm/slab.c:1856
in_atomic():1, irqs_disabled():0
Call Trace:
 [<c012172b>] __might_sleep+0xab/0xc9
 [<c014651e>] __kmalloc+0x8f/0x96
 [<f8c13efa>] os_alloc_mem+0x5c/0x87 [nvidia]
 [<f8c2e380>] _nv001308rm+0x10/0x28 [nvidia]
 [<f8d46b1d>] _nv001518rm+0x7c9/0xb34 [nvidia]
 [<f8c14ae5>] _nv005601rm+0xd/0x34 [nvidia]
 [<f8c152ab>] _nv005593rm+0x13/0x34 [nvidia]
 [<f8c23ef5>] _nv001338rm+0x1d/0x24 [nvidia]
 [<f8c14ae5>] _nv005601rm+0xd/0x34 [nvidia]
 [<f8c1c1c8>] _nv000858rm+0x300/0xe14 [nvidia]
 [<c012887a>] tasklet_action+0x68/0xb1
 [<c010ba6c>] do_IRQ+0x145/0x197
 [<c0109e1c>] common_interrupt+0x18/0x20
 [<f8c1847d>] _nv002962rm+0x2c5/0x3b8 [nvidia]
 [<f8c32e39>] _nv000899rm+0x4c9/0xf70 [nvidia]
 [<f8c32e4c>] _nv000899rm+0x4dc/0xf70 [nvidia]
 [<f8cfa46d>] _nv003622rm+0x15/0x1c [nvidia]
 [<f8d429f8>] _nv001823rm+0x0/0x38 [nvidia]
 [<f8d10766>] _nv002127rm+0x11a/0x14c [nvidia]
 [<f8d429f8>] _nv001823rm+0x0/0x38 [nvidia]
 [<f8d429f8>] _nv001823rm+0x0/0x38 [nvidia]
 [<f8d1284c>] _nv002088rm+0x1404/0x16d4 [nvidia]
 [<f8d7d624>] _nv001803rm+0x14/0x18 [nvidia]
 [<f8cf9d6b>] _nv001556rm+0x5b/0x6c [nvidia]
 [<f8cfa46d>] _nv003622rm+0x15/0x1c [nvidia]
 [<f8d42ae0>] _nv001826rm+0xb0/0xbc [nvidia]
 [<f8d429f8>] _nv001823rm+0x0/0x38 [nvidia]
 [<f8d10766>] _nv002127rm+0x11a/0x14c [nvidia]
 [<f8cf9c2b>] _nv001532rm+0x1f/0x28 [nvidia]
 [<f8cf9c2b>] _nv001532rm+0x1f/0x28 [nvidia]
 [<f8cfa411>] _nv003619rm+0x19/0x20 [nvidia]
 [<f8d42a24>] _nv001823rm+0x2c/0x38 [nvidia]
 [<f8c23d6a>] _nv001344rm+0x22/0x6c [nvidia]
 [<f8c23d6a>] _nv001344rm+0x22/0x6c [nvidia]
 [<f8cf9c2b>] _nv001532rm+0x1f/0x28 [nvidia]
 [<f8cfa411>] _nv003619rm+0x19/0x20 [nvidia]
 [<f8d42a24>] _nv001823rm+0x2c/0x38 [nvidia]
 [<f8c23d6a>] _nv001344rm+0x22/0x6c [nvidia]
 [<f8c23d6a>] _nv001344rm+0x22/0x6c [nvidia]
 [<f8cf9d6b>] _nv001556rm+0x5b/0x6c [nvidia]
 [<f8d7d624>] _nv001803rm+0x14/0x18 [nvidia]
 [<f8cf9d6b>] _nv001556rm+0x5b/0x6c [nvidia]
 [<f8cfa46d>] _nv003622rm+0x15/0x1c [nvidia]
 [<f8d42ae0>] _nv001826rm+0xb0/0xbc [nvidia]
 [<f8d10766>] _nv002127rm+0x11a/0x14c [nvidia]
 [<f8d12b0e>] _nv002088rm+0x16c6/0x16d4 [nvidia]
 [<f8d8f6bf>] _nv000176rm+0x57/0x3ec [nvidia]
 [<c030849c>] atkbd_interrupt+0x1a7/0x392
 [<f8d8f6bf>] _nv000176rm+0x57/0x3ec [nvidia]
 [<f8cf9c2b>] _nv001532rm+0x1f/0x28 [nvidia]
 [<f8cf9bdc>] _nv001534rm+0x20/0x28 [nvidia]
 [<f8d8f6bf>] _nv000176rm+0x57/0x3ec [nvidia]
 [<f8d8f6bf>] _nv000176rm+0x57/0x3ec [nvidia]
 [<c011defa>] recalc_task_prio+0x90/0x1aa
 [<c0107a7a>] __switch_to+0x136/0x19e
 [<c011f65c>] schedule+0x36e/0x695
 [<c011defa>] recalc_task_prio+0x90/0x1aa
 [<c012cc59>] update_wall_time+0xf/0x3a
 [<c01427a8>] buffered_rmqueue+0xed/0x194
 [<c0110d15>] convert_fxsr_to_user+0xbf/0x147
 [<c0110f49>] save_i387_fxsave+0xc9/0xfb
 [<c0108b18>] setup_sigcontext+0xe3/0x129
 [<f8c32541>] rm_ioctl+0x19/0x20 [nvidia]
 [<f8c11b30>] nv_kern_ioctl+0x4de/0x529 [nvidia]
 [<c01090ac>] handle_signal+0xd9/0x154
 [<c0110dc2>] convert_fxsr_from_user+0x25/0xe3
 [<c0111108>] restore_i387_fxsave+0x84/0x8f
 [<c01111a9>] restore_i387+0x96/0x98
 [<c01277ce>] it_real_fn+0x0/0x61
 [<c01087f3>] restore_sigcontext+0x116/0x130
 [<c016eaca>] sys_ioctl+0x120/0x2c6
 [<c0109437>] syscall_call+0x7/0xb

I suspect there may be an interaction between the nvidia drivers and the rest of the system - in particular memory and disk management.

Please let me know if there is any further information I can supply to narrow this problem down.
Comment 11 Daniel Milne 2004-01-24 06:16:06 UTC
I'm having very similar problems. I've been documenting in the forums here.

http://forums.gentoo.org/viewtopic.php?t=127884

I seem to get the messages on focus changes, but not consistently.
Comment 12 Colin Tinker 2004-01-24 11:28:37 UTC
I am getting this too after installing the nvidia drivers.
Comment 13 Vermyndax 2004-01-27 05:11:47 UTC
There are new NVidia drivers on NVidia's website that claims to natively support 2.6 kernels:

http://www.nvidia.com/object/linux_display_ia32_1.0-5336.html
Comment 14 Alex Walker 2004-01-31 06:26:40 UTC
Have installed the new drivers from Nvidia (no ebuild yet) and they fix this problem...
Comment 15 Andrew Bevitt 2004-04-13 07:44:55 UTC
Marking as LATER so we can resolve when 533* is marked stable
Comment 16 Rémi Cardona (RETIRED) gentoo-dev 2009-08-20 12:01:26 UTC
reopening
Comment 17 Rémi Cardona (RETIRED) gentoo-dev 2009-08-20 12:02:02 UTC
Much newer versions of nvidia-drivers are now stable. Closing with the proper resolution.