Re: Re: mode setting and console locking, nvidia failure

[Jon Smirl <jonsmirl@yahoo.com>]

I have a new clue.

From console:
modprobe radeonfb
rmmod radeonfb
works, there is a one line printk on rmmod displayed on console

From X:
modprobe radeonfb
rmmod radeonfb
works, there is a one line printk on rmmod logged

From X:
modprobe radeonfb
VT switch to console
rmmod radeonfb
system hangs, but is a little active Ctrl-Alt-Del prints a line.

Now remove the code that does the printk on exit
From X:
modprobe radeonfb
VT switch to console
rmmod radeonfb
works, line from printk is displayed.

One part of this has got to be a problem with the console semaphore.  That
semaphore should not be accessed from an fbdev driver. If you need to access if
from an fbdev driver then the fbdev design is broken. Think about the case with
multiple fbdev's loaded. Since we only have one console all of the fbdev can't
play with the semaphore. That semaphore needs to be controlled from fb/vgacon
and lock only the fbdev that is displaying the console, not the others.

Next experiment is to remove all reference to the console semaphore from my
fbdev driver.

=====
Jon Smirl
jonsmirl@yahoo.com


	
		
__________________________________
Do you Yahoo!?
SBC Yahoo! - Internet access at a great low price.
http://promo.yahoo.com/sbc/


-------------------------------------------------------
This SF.Net email is sponsored by: SourceForge.net Broadband
Sign-up now for SourceForge Broadband and get the fastest
6.0/768 connection for only $19.95/mo for the first 3 months!
http://ads.osdn.com/?ad_id=2562&alloc_id=6184&op=click