Re: panic: random.ko
Roman Neuhauser writes: 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? Yes. M -- Mark Murray iumop ap!sdn w,I idlaH ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: panic: random.ko
# [EMAIL PROTECTED] / 2004-04-22 08:02:04 +0100: Roman Neuhauser writes: 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? Yes. Indeed, booting GENERIC with unload load kernel boot (or load /boot/kernel/kernel) works now, and would have worked then if I didn't screw up somehow. Sorry for the waste of time. -- 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 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: panic: random.ko
# [EMAIL PROTECTED] / 2004-04-04 19:02:07 -0700: On Mon, Apr 05, 2004 at 02:35:53AM +0200, Roman Neuhauser wrote: Booting a kernel with random compiled in, and load_random=YES in loader.conf causes a panic very similar to the one described here: http://lists.freebsd.org/pipermail/freebsd-alpha/2003-August/000656.html Hi Mark, please fix random.ko :-) Sounds like a generic module problem that is known to exist on FreeBSD. Don't do that is the solution. You can unload the preloaded kernel and/or modules from the loader to prevent it from panicking at boot, then modify loader.conf. The fun part (and reason I asked whether there was a way to tell loader to ignore loader.con) was that unload didn't help, it showed the kernel and modules were unloaded, but subsequent load kernel boot or boot kernel loaded the the modules again, and I had to disable-module for every individual module, about twelve times. Is that normal behavior, or was there a pilot error somewhere? -- 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 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: panic: random.ko
On Wed, Apr 21, 2004 at 10:20:14AM +0200, Roman Neuhauser wrote: # [EMAIL PROTECTED] / 2004-04-04 19:02:07 -0700: On Mon, Apr 05, 2004 at 02:35:53AM +0200, Roman Neuhauser wrote: Booting a kernel with random compiled in, and load_random=YES in loader.conf causes a panic very similar to the one described here: http://lists.freebsd.org/pipermail/freebsd-alpha/2003-August/000656.html Hi Mark, please fix random.ko :-) Sounds like a generic module problem that is known to exist on FreeBSD. Don't do that is the solution. You can unload the preloaded kernel and/or modules from the loader to prevent it from panicking at boot, then modify loader.conf. The fun part (and reason I asked whether there was a way to tell loader to ignore loader.con) was that unload didn't help, it showed the kernel and modules were unloaded, but subsequent load kernel boot or boot kernel loaded the the modules again, and I had to disable-module for every individual module, about twelve times. Is that normal behavior, or was there a pilot error somewhere? I think it's expected behaviour. My fingers know what to do to stop this, but my brain can't remember it right now :-) Kris pgp0.pgp Description: PGP signature
Re: panic: random.ko
Kris Kennaway writes: loader to ignore loader.con) was that unload didn't help, it showed the kernel and modules were unloaded, but subsequent load kernel boot or boot kernel loaded the the modules again, and I had to disable-module for every individual module, about twelve times. Is that normal behavior, or was there a pilot error somewhere? I think it's expected behaviour. My fingers know what to do to stop this, but my brain can't remember it right now :-) unload load /boot/kernel/kernel boot does it for me. M -- Mark Murray iumop ap!sdn w,I idlaH ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: panic: random.ko
# [EMAIL PROTECTED] / 2004-04-21 12:03:36 +0100: Kris Kennaway writes: loader to ignore loader.con) was that unload didn't help, it showed the kernel and modules were unloaded, but subsequent load kernel boot or boot kernel loaded the the modules again, and I had to disable-module for every individual module, about twelve times. Is that normal behavior, or was there a pilot error somewhere? I think it's expected behaviour. My fingers know what to do to stop this, but my brain can't remember it right now :-) 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. -- 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 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: panic: random.ko
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? M -- Mark Murray iumop ap!sdn w,I idlaH ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: panic: random.ko
# [EMAIL PROTECTED] / 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 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
panic: random.ko
Booting a kernel with random compiled in, and load_random=YES in loader.conf causes a panic very similar to the one described here: http://lists.freebsd.org/pipermail/freebsd-alpha/2003-August/000656.html Hi Mark, please fix random.ko :-) If a backtrace would be useful, I can retype it in an email. On a related note, how do I make loader(8) ignore loader.conf? -- 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 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: panic: random.ko
On Mon, Apr 05, 2004 at 02:35:53AM +0200, Roman Neuhauser wrote: Booting a kernel with random compiled in, and load_random=YES in loader.conf causes a panic very similar to the one described here: http://lists.freebsd.org/pipermail/freebsd-alpha/2003-August/000656.html Hi Mark, please fix random.ko :-) Sounds like a generic module problem that is known to exist on FreeBSD. Don't do that is the solution. You can unload the preloaded kernel and/or modules from the loader to prevent it from panicking at boot, then modify loader.conf. Kris pgp0.pgp Description: PGP signature
