From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by befuddled.reisers.ca (Postfix, from userid 65534) id BBECE1EF826; Thu, 9 Oct 2014 16:34:14 -0400 (EDT) Received: from opera.rednote.net (opera.rednote.net [IPv6:2600:3c03::f03c:91ff:fe70:e783]) by befuddled.reisers.ca (Postfix) with ESMTPS id 4F66E1EF73A for ; Thu, 9 Oct 2014 16:34:13 -0400 (EDT) Received: from opera.rednote.net (localhost [IPv6:::1]) by opera.rednote.net (8.14.8/8.14.7) with ESMTP id s99KYCLt013027 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO) for ; Thu, 9 Oct 2014 20:34:12 GMT Received: (from janina@localhost) by opera.rednote.net (8.14.8/8.14.6/Submit) id s99KYC64013026 for speakup@linux-speakup.org; Thu, 9 Oct 2014 16:34:12 -0400 X-Authentication-Warning: opera.rednote.net: janina set sender to janina@rednote.net using -f Date: Thu, 9 Oct 2014 16:34:12 -0400 From: Janina Sajka To: "Speakup is a screen review system for Linux." Subject: Re: a little sysadmin story Message-ID: <20141009203412.GP1044@opera.rednote.net> References: <86a956i23h.fsf@vibrator.pk5001z> <20141009125200.GI1044@opera.rednote.net> <86ppe1gyed.fsf@vibrator.pk5001z> <5436B2E4.5060306@math.wisc.edu> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline In-Reply-To: <5436B2E4.5060306@math.wisc.edu> X-Operating-System: Linux opera.rednote.net 3.16.3-200.fc20.x86_64 X-PGP-Key: http://rednote.net/JaninaSajka_gpg_key.html User-Agent: Mutt/1.5.23 (2014-03-12) X-Bogosity: Ham, tests=bogofilter, spamicity=0.000000, version=1.2.4 X-BeenThere: speakup@linux-speakup.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: "Speakup is a screen review system for Linux." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 09 Oct 2014 20:34:14 -0000 I should probably add I haven't seen Speakup hangs recently. I do believe you can easily create one, though, by calling Speakup to talk to one of the four ttyS? devices and then not hooking something up at that address. I believe this would hang the boot still, but this si much NOT a big deal. John G. Heim writes: > Hmmm... I don't know. I have to say that I remain unconvinced. I've never > seen speakup cause a kernel panic. On the other hand, I have witnessed the > false cause effect. Something happens that causes a kernel panic and since > speakup is part of the kernel, it naturally has problems. You were on a > development server, right? Isn't it more likely that one of the developers > crashed the server amd that, in turn, caused problems for speakup? I run > some development servers here at the UW math department and it happens all > the time. Somebody causes an OOM (out of memory) event and, yes, that > crashes speakup. > > I once asked on the kernel developers list for comments on what's wrong with > the speakup code. There is that one biggie, of course, speakup writes > directly to the serial port. But all the other criticisms were things like > not following naming conventions, poor indentation, etc. Maybe the people > who mattered didn't bother to answer my question. But there wasn't anything > in there that would tend to indicate that speakup is prone to causing kernel > panics. Now, any software package can have a bug. But I have no reason to > believe that speakup is particularly unstable. Quite the contrary in fact. > > And even if there is a bug in speakup that can cause a kernel panic, that's > an argument for finding the bug and fixing it. Not for abandoning it > entirely. > > > > On 10/09/14 08:34, Deedra Waters wrote: > >Janina, > > > >speakup was the cause because when bossman came down to hook up a > >monitor and look, the panick messages had something to do with speakup. > > > >As for backing up their work, they were trying to fix their fuck-up to > >begin with. The initial problem wasn't with speakup. However when i was > >helping them debug it, speakup made the kernel panick and crash. > > > >Debian i dont think likes people with root access on their box to begin > >with, but i think they kind of didn't like speakup in their kernel to > >begin with. > > > >I suspect on the other hand that if speakup was a user-space app, it > >wouldn't have mattered to them so much. If a userspace program crashes > >it doesn't take down the whole box. When speakup does though, it takes > >down the whole box. > > > > > _______________________________________________ > Speakup mailing list > Speakup@linux-speakup.org > http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup -- Janina Sajka, Phone: +1.443.300.2200 sip:janina@asterisk.rednote.net Email: janina@rednote.net Linux Foundation Fellow Executive Chair, Accessibility Workgroup: http://a11y.org The World Wide Web Consortium (W3C), Web Accessibility Initiative (WAI) Chair, Protocols & Formats http://www.w3.org/wai/pf Indie UI http://www.w3.org/WAI/IndieUI/