From: Jon Smirl <jonsmirl@yahoo.com>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: James Simmons <jsimmons@infradead.org>,
fb-devel <linux-fbdev-devel@lists.sourceforge.net>
Subject: Re: Re: mode setting and console locking, nvidia failure
Date: Mon, 17 May 2004 20:53:57 -0700 (PDT) [thread overview]
Message-ID: <20040518035357.72794.qmail@web14927.mail.yahoo.com> (raw)
In-Reply-To: <1084851433.15183.20.camel@gaston>
It's your fbdev driver but taking out all console semaphore references didn't
make a difference. It was the ones in fbmem.c I though were the problem, not the
ones in the pm code.
I have this case, rmmod with printk in module remove routine causes hang. Get
rid of the printk and rmmod will succeed.
How do you debug this?
=====
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
prev parent reply other threads:[~2004-05-18 3:53 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-16 15:57 mode setting and console locking Jon Smirl
2004-05-16 22:03 ` Benjamin Herrenschmidt
2004-05-17 2:29 ` Jon Smirl
2004-05-17 3:51 ` Jon Smirl
2004-05-17 3:51 ` Benjamin Herrenschmidt
2004-05-17 4:12 ` Jon Smirl
2004-05-17 4:15 ` Benjamin Herrenschmidt
2004-05-17 4:51 ` Re: mode setting and console locking, nvidia failure Jon Smirl
2004-05-17 5:03 ` Jon Smirl
2004-05-17 22:56 ` James Simmons
2004-05-17 23:26 ` Jon Smirl
2004-05-18 3:00 ` Jon Smirl
2004-05-18 3:38 ` Jon Smirl
2004-05-18 3:37 ` Benjamin Herrenschmidt
2004-05-18 3:53 ` Jon Smirl [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20040518035357.72794.qmail@web14927.mail.yahoo.com \
--to=jonsmirl@yahoo.com \
--cc=benh@kernel.crashing.org \
--cc=jsimmons@infradead.org \
--cc=linux-fbdev-devel@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).