public inbox for speakup@linux-speakup.org
 help / color / mirror / Atom feed
From: Hynek Hanke <hanke@brailcom.org>
To: Speakup <speakup@braille.uwo.ca>
Subject: modprobe speakupmain hangs
Date: Wed, 01 Nov 2006 15:47:14 +0100	[thread overview]
Message-ID: <1162392434.3281.50.camel@chopin> (raw)


Hello,

we are experiencing a problem with the speakupmain module (the latest
CVS versions with 2.6.18 kernel) on at least one machine here in
Brailcom. I can't say much about it except for this:

1) Our target configuration is Speakup with the sftsyn module. We tried
to load the modules separately and we are sure the hang happens because
of the speakupmain module.

2) The modprobe hangs every time we try to do
	modprobe speakupmain
and when it hangs, the /dev/sftsyn device is still not intialized.

3) After we killall modprobe, the /dev/sftsyn device appears and there
comes a notice about it in syslog. The module stays loaded. It is then
possible to load speakup_sftsyn and Speakup works just fine. I'm not
sure if something is not missing in /proc/speakup or somewhere, but we
didn't notice anything strange.

4) Trying to increase modprobe verbosity or kernel logging level reveals
no additional information. gdb shows that the hang happens inside the
module_init() function in modprobe.

Our workaround is (which also illustrates the issue):
	modprobe speakupmain &
	sleep 1
	killall modprobe
	sleep 1
	modprobe speakup_sftsyn

We would appreciate some help with this or some guidance about how could
we get more information about it. Also, does someone else experience
this issue?

Thanks a lot,
Hynek Hanke



             reply	other threads:[~ UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 Hynek Hanke [this message]
 ` luke
   ` Gregory Nowak
     ` luke
   ` Hynek Hanke
     ` luke

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=1162392434.3281.50.camel@chopin \
    --to=hanke@brailcom.org \
    --cc=speakup@braille.uwo.ca \
    /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 read-only IMAP folder(s) and NNTP newsgroup(s).