This whole story sounds like it needs another couple of bears to make it
all interesting. So speakup crashed the kernel. I've had issues, but
apart from known bugs I've never seen speakup panic the kernel all the
time. Speakup caused a system to crash? Perhaps. People should also
backup their work.
On 10/9/2014 9:34 AM, 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.
--
Take care,
Ty
http://tds-solutions.net
He that will not reason is a bigot; he that cannot reason is a fool; he that dares not reason is a slave.
_______________________________________________
Speakup mailing list
Speakup@xxxxxxxxxxxxxxxxx
http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup
