> On Thu, 8 Oct 1998, Mike wrote:
>
> > Date: Thu, 8 Oct 1998 10:35:24 +0100 (GMT)
> > From: Mike <mike@oakley.keble.ox.ac.uk>
> > Reply-To: Mike Ricketts <rickettm@ox.compsoc.net>
> > To: Jakob Borg <jborg@df.lth.se>
> > Subject: Re: 2.1.124: oops when rmmodding ne.o
> >
> > On Thu, 8 Oct 1998, Chris Wedgwood wrote:
> >
> > > lsmod after error:
> > >
> > > # lsmod
> > > Module Size Used by
> > > lsmod: QM_INFO: No such file or directory
> > >
> > What version of modultils are you using?
>
> 2.1.121. But I'm not particularly surprised lsmod doesn't work after
> the oops, I was rather hoping people would be surprised the the ne
> module oopsed. It has never done that before to me.
>
The reason I asked is that I saw an Ooops on somebody else's box a couple
of days ago, with pretty much the same results, when they were rmmoding
ne. The problem turned out to be that they were using an old modutils.
-- Mike <rickettm@ox.compsoc.net>"You know, we've won awards for this crap." -- David Letterman
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/