- From: Amy Baum <amy_baum_at_lynceantech.com>
- Date: Tue, 02 Sep 2003 18:45:26 -0700
I was only trying to help the guy who was having trouble running comedi_config by sharing my experience running it for the first time. Maybe he only needed to load another module. I didn't think he'd be interested in a stack trace. Amy David Schleef wrote: > On Tue, Sep 02, 2003 at 05:51:33PM -0700, Amy Baum wrote: > >>I got a kernel OOPs when ! ran comedi_config when I didn't >>have the kcomedilib module loaded. I don't know if this helps, >>but I thought I'd throw it out there. > > > As a general comment, if you get an Oops when running comedi_config, > comedi_calibrate, or some other program that uses Comedi, you need > to file a bug, and attach a kernel log that was decoded with > ksymoops. Typically, this is as simple as running > > dmesg | ksymoops >log > > and attaching the file "log" to the bug. As with all bugs, you need > to say what device you're using. > > Just saying that you get an oops is not really interesting, nor are > undecoded Oops messages (i.e., raw kernel logs). > > > > dave... > > > > _______________________________________________ > comedi mailing list > comedi_at_comedi.org > https://cvs.comedi.org/cgi-bin/mailman/listinfo/comedi >
Received on 2003-09-03Z00:45:26