panic: random.ko

Roman Neuhauser neuhauser at chello.cz
Wed Apr 21 16:45:02 PDT 2004


# markm at FreeBSD.ORG / 2004-04-21 23:54:43 +0100:
> Roman Neuhauser writes:
> > > unload
> > > load /boot/kernel/kernel
> > > boot
> > > 
> > > does it for me.
> > 
> >     Of course I run unload as the first step. It wrote it unloaded the
> >     modules, and the started loading them again booting the new kernel.
> 
> Did you type the exact THREE commands as shown above?

    Of course, it's been three weeks since I had that problem so I
    would be insane to claim I have exact recollection. I might have
    been typing
    
    unload
    boot /boot/kernel/kernel

    over and over again in an attempt to convince myself that I had made
    a typo, but I doubt that. Nevertheless, would that make a difference?
    
    It's more likely (= I'm quite sure) I tried both versions more than
    once; I *really* wanted to avoid typing "disable-module <foo>"
    twelve or so times, which I ended up doing.

    Also note that we're talking about CURRENT in case that could mean
    a difference.

    Hm, I still have the exact same kernel/world on the machine. I'll
    try it out in the morning, and will let you know.

-- 
If you cc me or remove the list(s) completely I'll most likely ignore
your message.    see http://www.eyrie.org./~eagle/faqs/questions.html


More information about the freebsd-hackers mailing list