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

Newegg Daily Deals

Reply
 
Thread Tools
Old 12-28-05, 10:49 AM   #1
psv619
Registered User
 
Join Date: Nov 2005
Posts: 2
Default Problem: sleeping function called from invalid context at include/linux/rwsem.h?

This message was found in dmesg on all 7 machines that we had running with the NV 7676 drivers and the NF net 1.0-12 & audio 1.0-6 drivers. We noticed that there were updated drivers on nVidia's website so we downloaded them and installed on all machines. After reboot with the newest drivers we still get the same error in dmesg - and the machines don't run OGL programs smoothly, there is noticeable chop.

dmesg error:

Code:
Debug: sleeping function called from invalid context at include/linux/rwsem.h:66
in_atomic():1, irqs_disabled():0

Call Trace:<ffffffff8012ea2f>{__might_sleep+191} <ffffffff80122940>{change_page_attr_addr+48}
       <ffffffff80101c28>{init_level4_pgt+3112} <ffffffff80121db9>{ioremap_change_attr+73}
       <ffffffff8012247c>{iounmap+140} <ffffffff88366e34>{:nvidia:os_unmap_kernel_space+9}
       <ffffffff88142de7>{:nvidia:_nv001759rm+101} <ffffffff881237d5>{:nvidia:_nv008259rm+347}
       <ffffffff8822f0a1>{:nvidia:_nv005184rm+257} <ffffffff8812ab06>{:nvidia:_nv008258rm+406}
       <ffffffff8812a903>{:nvidia:_nv008261rm+73} <ffffffff8812a6c2>{:nvidia:_nv008266rm+60}
       <ffffffff88282e76>{:nvidia:_nv003947rm+124} <ffffffff8814a4d2>{:nvidia:rm_set_interrupts+274}
       <ffffffff881493ba>{:nvidia:_nv008246rm+74} <ffffffff8814ab09>{:nvidia:rm_free_unused_clients+125}
       <ffffffff883610e6>{:nvidia:nv_kern_ctl_close+167} <ffffffff883630cf>{:nvidia:nv_kern_close+82}
       <ffffffff8017bca2>{__fput+210} <ffffffff8017a2ae>{filp_close+110}
       <ffffffff801355eb>{put_files_struct+107} <ffffffff80135fcb>{do_exit+539}
       <ffffffff8013e2c5>{__dequeue_signal+501} <ffffffff80136afd>{do_group_exit+237}
       <ffffffff8014044d>{get_signal_to_deliver+1405} <ffffffff8010deaf>{do_signal+159}
       <ffffffff80359803>{_spin_unlock+19} <ffffffff80353c4b>{unix_ioctl+235}
       <ffffffff802e640c>{sock_ioctl+636} <ffffffff8010d496>{__switch_to+534}
       <ffffffff803598c4>{_spin_unlock_irq+20} <ffffffff80357f6f>{thread_return+187}
       <ffffffff8018f722>{vfs_ioctl+690} <ffffffff8010f12a>{retint_signal+61}
System specs:

Asus A8N-SLI
AMD 64bit 4000+
nVidia 6800 Ultra 256mb PCI-E (EVGA)
2gb DDR400
Redhat Enterprise Linux 64bit 4.0
2.6.14.2 #3 PREEMPT Tue Nov 15 11:26:50 CST 2005 x86_64 x86_64 x86_64 GNU/Linux

Any idea where to start looking?
Attached Files
File Type: zip nvidia-bug-report.zip (24.4 KB, 125 views)
psv619 is offline   Reply With Quote
Old 12-28-05, 01:34 PM   #2
zander
NVIDIA Corporation
 
zander's Avatar
 
Join Date: Aug 2002
Posts: 3,740
Default Re: Problem: sleeping function called from invalid context at include/linux/rwsem.h?

This is actually a kernel bug, iounmap() acquires and holds the lock in question; it's unclear if the warnings are related to the OpenGL problem(s) you're seeing. You can avoid the warnings and possibly improve reliability by rebuilding your kernel without CONFIG_PREEMPT.
zander is offline   Reply With Quote
Old 12-29-05, 07:17 AM   #3
dmetz99
Registered User
 
Join Date: Mar 2005
Posts: 84
Default Re: Problem: sleeping function called from invalid context at include/linux/rwsem.h?

I've seen similar problems and using a non-preempt kernel does help. Does nvidia have any plans to make the Linux drivers work well with preempt (and/or preempt_rt) kernels? Many desktop-type users run preempt kernels to get better overall system interactivity. In particular, audio apps suffer greatly under non-preempt kernels.
dmetz99 is offline   Reply With Quote
Old 12-29-05, 07:23 AM   #4
zander
NVIDIA Corporation
 
zander's Avatar
 
Join Date: Aug 2002
Posts: 3,740
Default Re: Problem: sleeping function called from invalid context at include/linux/rwsem.h?

There are no known interaction problems between the NVIDIA Linux graphics driver and kernels built with CONFIG_PREEMPT as such, but my experience, at least, has been that preemptible kernels generally are less reliable.
zander is offline   Reply With Quote
Old 12-29-05, 07:37 AM   #5
dmetz99
Registered User
 
Join Date: Mar 2005
Posts: 84
Default Re: Problem: sleeping function called from invalid context at include/linux/rwsem.h?

Actually, I've had few problems with vanilla kernels compiled with preempt enabled. Going to a RT kernel (preempt_rt enabled) causes this message:

Dec 29 08:23:13 dmetzlerv kernel: NVRM: Trying to sleep during raised irql!!
Dec 29 08:23:13 dmetzlerv kernel: NVRM: are we holding a lock?
Dec 29 08:23:13 dmetzlerv kernel: NVRM: skipping os_delay

to appear multiple times in the syslog, but the system seems to run OK. Not really a complaint, just an observation. (Yes, I know the RT kernels are highly experimental!)

JaXXon - If you're lurking out there, any comments?
dmetz99 is offline   Reply With Quote
Old 12-29-05, 08:38 AM   #6
zander
NVIDIA Corporation
 
zander's Avatar
 
Join Date: Aug 2002
Posts: 3,740
Default Re: Problem: sleeping function called from invalid context at include/linux/rwsem.h?

We're aware of the reports of problems with Ingo's realtime kernels on this forum and hope to investigate them at some point in the future, but due to their experimental nature and other projects, I don't have a time frame for when that will happen. I expect most, if not all, of them can be addressed with changes to the open source interface code.
zander is offline   Reply With Quote
Old 12-29-05, 09:18 AM   #7
dmetz99
Registered User
 
Join Date: Mar 2005
Posts: 84
Default Re: Problem: sleeping function called from invalid context at include/linux/rwsem.h?

That seems like a reasonable approach, considering that mainline kernel issues need to be addressed first. At least the pace of RT development as slowed down considerably (at least for the short term). I'll keep my ear to ground, so to speak.
dmetz99 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 03:34 AM.


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