Kernel Oops with Linux-2.6.18.2, Speech-dispatcher-0.6.1, and Speechd-up-0.4

Kernel Oops with Linux-2.6.18.2, Speech-dispatcher-0.6.1, and Speechd-up-0.4

[Igor Gueths]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Hi all. I just completed installing LFS on my laptop; this includes Gcc-4.1.1, and Glibc-2.5. I restored a known good configuration from backup that was working perfectly on my previous 
Slackware system, which was running Linux-2.6.17.1. I have noticed two things so far; for one thing, I can't hear anything when I start Speech-dispatcher and Speechd-up with Espeak-1.16. Also, 
for some reason when I go to stop Dispatcher and Speechd-up, Speechd-up doesn't terminate properly. When I killall speechd-up, I get the following:
Message from syslogd@lappie at Sat Nov 11 00:17:30 2006 ...
lappie kernel: Oops: 0000 [#4]

Message from syslogd@lappie at Sat Nov 11 00:17:30 2006 ...
lappie kernel: CPU:    0

Message from syslogd@lappie at Sat Nov 11 00:17:30 2006 ...
lappie kernel: EIP is at filp_close+0x25/0x80

Message from syslogd@lappie at Sat Nov 11 00:17:30 2006 ...
lappie kernel: eax: e083de80   ebx: dee6c780   ecx: 00000257   edx: dee6c780

Message from syslogd@lappie at Sat Nov 11 00:17:30 2006 ...
lappie kernel: esi: c17a59c8   edi: c17a59c0   ebp: 00000000   esp: d873fe38

Message from syslogd@lappie at Sat Nov 11 00:17:30 2006 ...
lappie kernel: ds: 007b   es: 007b   ss: 0068

Message from syslogd@lappie at Sat Nov 11 00:17:30 2006 ...
lappie kernel: Process speechd-up (pid: 830, ti=d873e000 task=df885a70 task.ti=d873e000)

Message from syslogd@lappie at Sat Nov 11 00:17:30 2006 ...
lappie kernel: Stack: dee6c540 c17a59c0 00000003 c17a59c8 00000000 c011efbc dee6c780 c17a59c0

Message from syslogd@lappie at Sat Nov 11 00:17:30 2006 ...
lappie kernel:        c17a59c0 00000018 00000000 df885a70 00000001 0000000f c0120002 df885a70

Message from syslogd@lappie at Sat Nov 11 00:17:30 2006 ...
lappie kernel:        df885edc 00000009 d873ff14 c0127615 00000246 00000008 00000009 fffffe00

Message from syslogd@lappie at Sat Nov 11 00:17:30 2006 ...
lappie kernel: Call Trace:

Message from syslogd@lappie at Sat Nov 11 00:17:30 2006 ...
lappie kernel: Code: c3 90 8d 74 26 00 83 ec 14 89 5c 24 08 8b 5c 24 18 89 7c 24 10 8b 7c 24 1c 89 74 24 0c 8b 43 14 85 c0 74 52 8b 43 10 85 c0 74 43 <8b> 40 34 85 c0 74 3c 89 7c 24 04 89 1c 
24 ff d0
89 c6 89 7c 24

Message from syslogd@lappie at Sat Nov 11 00:17:30 2006 ...
lappie kernel: EIP: [filp_close+37/128] filp_close+0x25/0x80 SS:ESP 0068:d873fe38

And the script I use to stop speech when I'm done:
#!/bin/bash
echo none >/proc/speakup/synth_name
sleep 1
killall speechd_up
killall speech-dispatcher
modprobe -r speakup_sftsyn

Does anyone know if there is a fix and or workaround for the above kernel Oops? Might this have anything to do with why I can't hear Espeak say anything, despite the fact that I can use Espeak 
by itself with no problems? Thanks!
- -- 
For an IRC experience without all the clutter, check out BOFHNet at irc.bofhnet.us.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.2 (GNU/Linux)

iQIVAwUBRVVeW6e2pgKIdGq4AQpZcxAAgKc0gSUpR0Q7HegopWrig6tpKX6IeZlc
RoUkn+CX+I9T5CznvxGMPRkzvxiwtDmQSSgOg6oGizuavAA0GO2odOKhxnNl2rRa
jCXjpUoAoWCWLj70OofvPXxFfjtBrQKzr3tijxdsO0/8Dpt0JWowR6TEx4Dqriut
jzXA4xJ87dxAXjq5cjPHOenQA5/WB+QBYi76m2Ua/GbX/DmykzCt//P/PQOooG38
KcrYrdLDSxz/O/1jBDjTM//pgxMuMYpIyKMydofWM9wLuLXLFC+NaxOs8oS2cBrH
RwYDt7Ey5fOm9V9W85gAZiwbI6pedUTp8A+qUXLqF+Ue8YZvC80VZg+dAefMWUH+
Y2Xdy6spBDxbKVI6QzV2ocqBhT/y9jGcQRFh1i+7X4XVI5hpbGQIs8A/8cipbiBU
AV1/2XqvOvmfVS/apZfD39VdTGMWyzQihjilGKYgl2U1E4IRk9JFQtHjacRw+IaT
49QTVD5uJmBtFhZ8ZyLiNNP0Rz7J2Qt51X/d5wGhaVQPOqapjmKthe0iFouh6a0p
rUltRh1edoYhyuhStJOOACl1r2ByvH8nk5ztuV1G+UIktpChEgAJnj7QA5Gz2cEK
q2Su7Fpby4RNqUp0QcxS41sUJS9enbSKAJZNfC0MlTd+WzQirUCwJehDQMKHwX99
IEZabe1DnBw=
=uSoV
-----END PGP SIGNATURE-----

-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

Re: Kernel Oops with Linux-2.6.18.2, Speech-dispatcher-0.6.1, and Speechd-up-0.4

[Gregory Nowak]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

I'd guess your problem is either with echo none
>/proc/speakup/synth_name, with modprobe -r, or with both. I know I've
reported problems here in the past about the kernel going bye-bye when
echoing none to synth_name, and when modprobing speakup
modules. Others have reported modprobe issues here as well, so your
report isn't the first, it just serves to confirm that a problem does
in fact exist in certain configurations, but not in others, as I've
also mentioned in the past.

As for why you don't get speech, I would have to guess you don't have
software speech configured properly, or are again loading speakup
modules before starting speech-dispatcher/speechd-up, causing things
to act strange.

Greg


On Sat, Nov 11, 2006 at 12:23:39AM -0500, Igor Gueths wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA512
> 
> Hi all. I just completed installing LFS on my laptop; this includes Gcc-4.1.1, and Glibc-2.5. I restored a known good configuration from backup that was working perfectly on my previous 
> Slackware system, which was running Linux-2.6.17.1. I have noticed two things so far; for one thing, I can't hear anything when I start Speech-dispatcher and Speechd-up with Espeak-1.16. Also, 
> for some reason when I go to stop Dispatcher and Speechd-up, Speechd-up doesn't terminate properly. When I killall speechd-up, I get the following:

- -- 
web site: http://www.romuald.net.eu.org
gpg public key: http://www.romuald.net.eu.org/pubkey.asc
skype: gregn1
(authorization required, add me to your contacts list first)

- --
Free domains: http://www.eu.org/ or mail dns-manager@EU.org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)

iD8DBQFFVWjs7s9z/XlyUyARAoLRAKDablOmniJbkxXr7ioQl2ccw57rxwCgnHIW
BJnAi8w/1rosmMT0+9bv7Z8=
=RTKs
-----END PGP SIGNATURE-----

Re: Kernel Oops with Linux-2.6.18.2, Speech-dispatcher-0.6.1, and Speechd-up-0.4

[Igor Gueths]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Hi. I guess I'll try building speakup_sftsyn into the kernel and see what happens. The interesting thing is that when the kernel Oops occurs, it never actually crashes; I just get all those 
messages printed to STDOUT. Consequently, I have found I can replicate the problem as many times as I want, and not lose any other system functionality in doing so.
On Fri, Nov 10, 2006 at 11:08:44PM -0700, Gregory Nowak wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> I'd guess your problem is either with echo none
> >/proc/speakup/synth_name, with modprobe -r, or with both. I know I've
> reported problems here in the past about the kernel going bye-bye when
> echoing none to synth_name, and when modprobing speakup
> modules. Others have reported modprobe issues here as well, so your
> report isn't the first, it just serves to confirm that a problem does
> in fact exist in certain configurations, but not in others, as I've
> also mentioned in the past.
> 
> As for why you don't get speech, I would have to guess you don't have
> software speech configured properly, or are again loading speakup
> modules before starting speech-dispatcher/speechd-up, causing things
> to act strange.
> 
> Greg
> 
> 
> On Sat, Nov 11, 2006 at 12:23:39AM -0500, Igor Gueths wrote:
> > -----BEGIN PGP SIGNED MESSAGE-----
> > Hash: SHA512
> > 
> > Hi all. I just completed installing LFS on my laptop; this includes Gcc-4.1.1, and Glibc-2.5. I restored a known good configuration from backup that was working perfectly on my previous 
> > Slackware system, which was running Linux-2.6.17.1. I have noticed two things so far; for one thing, I can't hear anything when I start Speech-dispatcher and Speechd-up with Espeak-1.16. Also, 
> > for some reason when I go to stop Dispatcher and Speechd-up, Speechd-up doesn't terminate properly. When I killall speechd-up, I get the following:
> 
> - -- 
> web site: http://www.romuald.net.eu.org
> gpg public key: http://www.romuald.net.eu.org/pubkey.asc
> skype: gregn1
> (authorization required, add me to your contacts list first)
> 
> - --
> Free domains: http://www.eu.org/ or mail dns-manager@EU.org
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.5 (GNU/Linux)
> 
> iD8DBQFFVWjs7s9z/XlyUyARAoLRAKDablOmniJbkxXr7ioQl2ccw57rxwCgnHIW
> BJnAi8w/1rosmMT0+9bv7Z8=
> =RTKs
> -----END PGP SIGNATURE-----
> 
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
> 
> -- 
> This message has been scanned for viruses and
> dangerous content by MailScanner, and is
> believed to be clean.
> 

- -- 
For an IRC experience without all the clutter, check out BOFHNet at irc.bofhnet.us.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.2 (GNU/Linux)

iQIVAwUBRVX9I6e2pgKIdGq4AQphfw//Rk+Y0qRALbWhk3QMk7G0V/VneYzUaArw
E7Ew0Cg3iRsBsIZQiTgqYcw6BpGTWpIMYBWMm3rnc1ouXpxWE29N5PAZQHxrNiPr
gdrxBzKzssoTffXLvohyHa/snBme4PQgb/XJgjevbNaniyMXZgwrw+g/vh9WY+u9
wR6/iQ9o+sXAf3RV0EwdaHyRFDS8kucIKcdz5aVYFG4NfSmWE9yBET/D3623iArw
K5/OaXc7h3kGafJKUkFuu/xWq/dWHGJkZsP7beCJho7l3tviiAKtR7E9CmViS7KT
jxzI/eFJN0fYR1q/1j/7hvPKMsvySMo0QtF5oh9liMHl/gZNrNqvknSmYZaBbS3s
mN2d7VEOQIU2STAcdc75rdCjEzT51rcvAZLG70SGfj1TPEFK9sWAAlaKhi9ebtt1
ZuDn6yvTWD01LCCjLRq/oxVt6srMKmQ8Fc67bYowkkzOaqHGYOpedibUYyJ/6lms
g5OmaiIy9oT/keiL8TLcLJO8ZkCMK8Y0QrxtR59qgnO17gJaCe9Y1PCdiOGkhLcI
Judc7fx/66HRu0wsObnCJyfM4IhEZUuX7F3sTkku1mrGYk83J6Tct/jALeeU6FXr
PdAJIa2B4XfQIGLwy+CfYpKWSFBwEDkfnH6tlLGcu7+RM4c/CCc1nw7j56IOSar+
hRh+koezIJs=
=1TAX
-----END PGP SIGNATURE-----

-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

Re: Kernel Oops with Linux-2.6.18.2, Speech-dispatcher-0.6.1, and Speechd-up-0.4

[Gregory Nowak]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Ok, maybe saying that the kernel goes bye-bye wasn't the best way to
describe it. Yes, in my case, and I believe in the other reports, the
rest of the system is still very useable.

Greg


On Sat, Nov 11, 2006 at 11:41:07AM -0500, Igor Gueths wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA512
> 
> Hi. I guess I'll try building speakup_sftsyn into the kernel and see what happens. The interesting thing is that when the kernel Oops occurs, it never actually crashes; I just get all those 
> messages printed to STDOUT. Consequently, I have found I can replicate the problem as many times as I want, and not lose any other system functionality in doing so.

- -- 
web site: http://www.romuald.net.eu.org
gpg public key: http://www.romuald.net.eu.org/pubkey.asc
skype: gregn1
(authorization required, add me to your contacts list first)

- --
Free domains: http://www.eu.org/ or mail dns-manager@EU.org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)

iD8DBQFFVg6B7s9z/XlyUyARAih9AJ98xUKwm/A+iCdFP0746LqCiIuwEwCdFNH7
Cju6dQifqoX5e0Srj2aQv/U=
=Sb7A
-----END PGP SIGNATURE-----