> On 09-Jun-98 Tim Waugh wrote:
> >
> > The oops isn't useful without running ksymoops on it (you can find it in
> > the scripts directory). Can you reproduce the oops at all?
>
> Oops, forgot about that. The oops and ksymoops is in this mesg.
> Briefly, here's what I was doing. I was in the /proc/parport/0 dir and
> poking around in there. the parport modules were loaded. Then I
> unloaded the modules, and typed 'ls' in /proc/parport/0 (which is now
> nonexistant). Voila! "Segmentation fault" is printed to console, and
> kernel Oops.
Right. I think Alan's latest 2.1.105 patch ("ac2") fixes that.
> > With regard to printing not working, does typing "dmesg" reveal any
> > messages from parport?
>
> Yes, most notably:
> lp: driver loaded but no devices found
And when you do a "modprobe parport; modprobe parport_pc"?
Tim.
*/
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu