From: Gregory Nowak <greg@romuald.net.eu.org>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Re: Kernel Oops with Linux-2.6.18.2, Speech-dispatcher-0.6.1, and Speechd-up-0.4
Date: Sat, 11 Nov 2006 10:55:13 -0700 [thread overview]
Message-ID: <20061111175513.GA30278@localhost.localdomain> (raw)
In-Reply-To: <20061111164107.GB24056@lava-net.com>
-----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-----
prev parent reply other threads:[~ UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
Igor Gueths
` Gregory Nowak
` Igor Gueths
` Gregory Nowak [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=20061111175513.GA30278@localhost.localdomain \
--to=greg@romuald.net.eu.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).