Re: RELENG_8 kernel as of Apr 14 does not boot
On Monday, April 16, 2012 3:59:09 am Eugene Grosbein wrote: Just update my 8.x kernel sources last weekend, and newly built kernel did not boot for me: link_elf: symbol mem_range_softc undefined KLD file acpi.ko - could not finalize loading kernel trap 12 with interrupts disabled Try to add 'device mem' to your kernel configuration. :-) I explicitly have nodevice mem and nodevice io in my config. They are being loaded from /boot/loader.conf. This worked fine for quite a while. I will try to have it compiled-in, but would still prefer it fixed, or in case it cannot be fixed and mem.ko cannot be loaded separately from now on, appropriate entry in UPDATING. It seems John Baldwin brought dependency of acpi.ko on device mem 4 days ago to RELENG_8 with MFC: http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/i386/acpica/acpi_wakeup.c#rev1.50.2.3 I believe the patch at www.freebsd.org/~jhb/patches/device_mem.patch should fix this. It reverts part of 217515 and 217539 to move the mem_range_softc back into the base kernel so it is always present. -- John Baldwin ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: RELENG_8 kernel as of Apr 14 does not boot
On Monday, April 16, 2012 3:59:09 am Eugene Grosbein wrote: Just update my 8.x kernel sources last weekend, and newly built kernel did not boot for me: link_elf: symbol mem_range_softc undefined KLD file acpi.ko - could not finalize loading kernel trap 12 with interrupts disabled Try to add 'device mem' to your kernel configuration. :-) I explicitly have nodevice mem and nodevice io in my config. They are being loaded from /boot/loader.conf. This worked fine for quite a while. I will try to have it compiled-in, but would still prefer it fixed, or in case it cannot be fixed and mem.ko cannot be loaded separately from now on, appropriate entry in UPDATING. It seems John Baldwin brought dependency of acpi.ko on device mem 4 days ago to RELENG_8 with MFC: http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/i386/acpica/acpi_wakeup.c#rev1.50.2.3 Eugene Grosbein Hmm, this has been broken for a long time on HEAD and 9 it seems. However, there you get compile breakage (as acpi is no longer supported as a module in 9+) if you try to build a kernel with 'nodevice mem'. Hmm, mp_machdep.c also breaks. That is probably true on i386 as well, and has been true even on 7.x. (That is, you can't use 'nodevice mem' and 'SMP' in the same kernel.) The simplest fix is to just move mem_range_softc out of mem.ko into the base kernel. OTOH, what are you trying to gain by putting mem.ko into a module rather than part of the base kernel? Do you just want no /dev/mem file or are you trying to disable all of the MTRR support as well? It may be that we need to rethink what goes into mem.ko and have it only exclude /dev/mem but always leave MTRR support enabled. -- John Baldwin ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: RELENG_8 kernel as of Apr 14 does not boot
On Monday, April 16, 2012 3:59:09 am Eugene Grosbein wrote: Just update my 8.x kernel sources last weekend, and newly built kernel did not boot for me: link_elf: symbol mem_range_softc undefined KLD file acpi.ko - could not finalize loading kernel trap 12 with interrupts disabled Try to add 'device mem' to your kernel configuration. :-) I explicitly have nodevice mem and nodevice io in my config. They are being loaded from /boot/loader.conf. This worked fine for quite a while. I will try to have it compiled-in, but would still prefer it fixed, or in case it cannot be fixed and mem.ko cannot be loaded separately from now on, appropriate entry in UPDATING. It seems John Baldwin brought dependency of acpi.ko on device mem 4 days ago to RELENG_8 with MFC: http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/i386/acpica/acpi_wakeup.c#rev1.50.2.3 Hmm, this has been broken for a long time on HEAD and 9 it seems. However, there you get compile breakage (as acpi is no longer supported as a module in 9+) if you try to build a kernel with 'nodevice mem'. Hmm, mp_machdep.c also breaks. That is probably true on i386 as well, and has been true even on 7.x. (That is, you can't use 'nodevice mem' and 'SMP' in the same kernel.) The simplest fix is to just move mem_range_softc out of mem.ko into the base kernel. OTOH, what are you trying to gain by putting mem.ko into a module rather than part of the base kernel? Do you just want no /dev/mem file or are you trying to disable all of the MTRR support as well? It may be that we need to rethink what goes into mem.ko and have it only exclude /dev/mem but always leave MTRR support enabled. I guess, Alexey just tries to make smallest possible kernel just for fun :-) Or, for PicoBSD case where kernel should be booted from very small media and modules from another one. Eugene Grosbein ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: RELENG_8 kernel as of Apr 14 does not boot
I am working on the Jerome's computer. What you want is still on the server in Moscow. Yes, there is a copy on the Jerome's computer but it is password protected. What is the password? I don't know but it is the same one that is used to access the Exchange server in Moscow. So, we come back to the same bottleneck: Access to the Exchange Server in Moscow. The best thing to do is to get access to Jerome's current email on the server in Moscow. The alternative is to get this password and I setup TeamViewer on the Jerome's computer and you access his computer from London (via TeamViewer). In either case, we need Jerome's Outlook Password and that can only be reset in Moscow. On Tue, Apr 17, 2012 at 3:08 PM, Eugene Grosbein egrosb...@rdtc.ru wrote: On Monday, April 16, 2012 3:59:09 am Eugene Grosbein wrote: Just update my 8.x kernel sources last weekend, and newly built kernel did not boot for me: link_elf: symbol mem_range_softc undefined KLD file acpi.ko - could not finalize loading kernel trap 12 with interrupts disabled Try to add 'device mem' to your kernel configuration. :-) I explicitly have nodevice mem and nodevice io in my config. They are being loaded from /boot/loader.conf. This worked fine for quite a while. I will try to have it compiled-in, but would still prefer it fixed, or in case it cannot be fixed and mem.ko cannot be loaded separately from now on, appropriate entry in UPDATING. It seems John Baldwin brought dependency of acpi.ko on device mem 4 days ago to RELENG_8 with MFC: http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/i386/acpica/acpi_wakeup.c#rev1.50.2.3 Hmm, this has been broken for a long time on HEAD and 9 it seems. However, there you get compile breakage (as acpi is no longer supported as a module in 9+) if you try to build a kernel with 'nodevice mem'. Hmm, mp_machdep.c also breaks. That is probably true on i386 as well, and has been true even on 7.x. (That is, you can't use 'nodevice mem' and 'SMP' in the same kernel.) The simplest fix is to just move mem_range_softc out of mem.ko into the base kernel. OTOH, what are you trying to gain by putting mem.ko into a module rather than part of the base kernel? Do you just want no /dev/mem file or are you trying to disable all of the MTRR support as well? It may be that we need to rethink what goes into mem.ko and have it only exclude /dev/mem but always leave MTRR support enabled. I guess, Alexey just tries to make smallest possible kernel just for fun :-) Or, for PicoBSD case where kernel should be booted from very small media and modules from another one. Eugene Grosbein ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: RELENG_8 kernel as of Apr 14 does not boot
My bad. Please accept my apologies. Working on too many things at one time. On Tue, Apr 17, 2012 at 3:48 PM, Garrett Anderson g...@amerlok.com wrote: I am working on the Jerome's computer. What you want is still on the server in Moscow. Yes, there is a copy on the Jerome's computer but it is password protected. What is the password? I don't know but it is the same one that is used to access the Exchange server in Moscow. So, we come back to the same bottleneck: Access to the Exchange Server in Moscow. The best thing to do is to get access to Jerome's current email on the server in Moscow. The alternative is to get this password and I setup TeamViewer on the Jerome's computer and you access his computer from London (via TeamViewer). In either case, we need Jerome's Outlook Password and that can only be reset in Moscow. On Tue, Apr 17, 2012 at 3:08 PM, Eugene Grosbein egrosb...@rdtc.ru wrote: On Monday, April 16, 2012 3:59:09 am Eugene Grosbein wrote: Just update my 8.x kernel sources last weekend, and newly built kernel did not boot for me: link_elf: symbol mem_range_softc undefined KLD file acpi.ko - could not finalize loading kernel trap 12 with interrupts disabled Try to add 'device mem' to your kernel configuration. :-) I explicitly have nodevice mem and nodevice io in my config. They are being loaded from /boot/loader.conf. This worked fine for quite a while. I will try to have it compiled-in, but would still prefer it fixed, or in case it cannot be fixed and mem.ko cannot be loaded separately from now on, appropriate entry in UPDATING. It seems John Baldwin brought dependency of acpi.ko on device mem 4 days ago to RELENG_8 with MFC: http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/i386/acpica/acpi_wakeup.c#rev1.50.2.3 Hmm, this has been broken for a long time on HEAD and 9 it seems. However, there you get compile breakage (as acpi is no longer supported as a module in 9+) if you try to build a kernel with 'nodevice mem'. Hmm, mp_machdep.c also breaks. That is probably true on i386 as well, and has been true even on 7.x. (That is, you can't use 'nodevice mem' and 'SMP' in the same kernel.) The simplest fix is to just move mem_range_softc out of mem.ko into the base kernel. OTOH, what are you trying to gain by putting mem.ko into a module rather than part of the base kernel? Do you just want no /dev/mem file or are you trying to disable all of the MTRR support as well? It may be that we need to rethink what goes into mem.ko and have it only exclude /dev/mem but always leave MTRR support enabled. I guess, Alexey just tries to make smallest possible kernel just for fun :-) Or, for PicoBSD case where kernel should be booted from very small media and modules from another one. Eugene Grosbein ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: RELENG_8 kernel as of Apr 14 does not boot
On Tue, Apr 17, 2012 at 08:08:40PM +0700, Eugene Grosbein wrote: I guess, Alexey just tries to make smallest possible kernel just for fun :-) You are correct. Not for the size reasons though, but I want to be able to change as much as possible on the fly, without a reboot, and I cannot kldunload kernel yet. ;-) Another thing is that, while this is kinda unsupported configuration, it should work, even being an edge case. So it's a good test if our kernel has no hidden dependencies which would inhibit use of a module when it exists. Personally I do not see much benefits in having mem/io as modules, but if they are provided, I should be able to load them from the loader. If they must be compiled in, I suggest we stop shipping them as modules so not to confuse people (even that one must specially use nodevice to exclude them). ./danfe ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: RELENG_8 kernel as of Apr 14 does not boot
On Tue, Apr 17, 2012 at 08:40:37AM -0400, John Baldwin wrote: Hmm, this has been broken for a long time on HEAD and 9 it seems. However, there you get compile breakage (as acpi is no longer supported as a module in 9+) if you try to build a kernel with 'nodevice mem'. Yes, I am aware. Unfortunately, I am frightened to upgrade to 9.x as I have no confidence that it behaves well on my laptop. I still do not know how to fix 8.x after January which broke suspend/resume for me (EDIT: see below!). Hmm, mp_machdep.c also breaks. That is probably true on i386 as well, and has been true even on 7.x. (That is, you can't use 'nodevice mem' and 'SMP' in the same kernel.) Right, I have appropriate comment about it in my kernel config file. :-) OTOH, what are you trying to gain by putting mem.ko into a module rather than part of the base kernel? Do you just want no /dev/mem file or are you trying to disable all of the MTRR support as well? No, no, nothing other than checking how far can I go in putting everything possible into modules and loading them from /boot/loader.conf. I was not aware it affects MTRR support... It may be that we need to rethink what goes into mem.ko and have it only exclude /dev/mem but always leave MTRR support enabled. Hmm, this is interesting. I've been waiting for you to MFC r232742 to RELENG_8 as jkim@ mentioned that these are features that could be responsible for broken suspend/resume on i386. Are you saying that having loading mem.ko as module could affect certain registers restoration, and thus preventing correct resume? I've just tried to zzz/resume several times in a row with latest 8.x kernel with io/mem compiled in. Maybe I am speaking too fast, but guess what: keyboard works now, network service are accessible, bluetooth mouse works, etc. Unbelievable. My stupid nodevice gimmick prevented me from having working resume, LOL. I think that if we continue to install mem.ko as module, it should be clearly documented that results of such setup might be quite different from defaults. Thanks for pieces of valuable wisdom John. ./danfe ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: RELENG_8 kernel as of Apr 14 does not boot
On Tue, Apr 17, 2012 at 09:46:43PM +0700, Alexey Dokuchaev wrote: I've just tried to zzz/resume several times in a row with latest 8.x kernel with io/mem compiled in. Maybe I am speaking too fast, but guess what: keyboard works now, network service are accessible, bluetooth mouse works, etc. Unbelievable. My stupid nodevice gimmick prevented me from having working resume, LOL. Alas, fresh reboot -- and it all as bad as before. Need to debug more... ./danfe ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: RELENG_8 kernel as of Apr 14 does not boot
16.04.2012 11:26, Alexey Dokuchaev пишет: Hi, Just update my 8.x kernel sources last weekend, and newly built kernel did not boot for me: link_elf: symbol mem_range_softc undefined KLD file acpi.ko - could not finalize loading kernel trap 12 with interrupts disabled This is stripped down kernel with everything possible loaded from modules. Any ideas? Did not see any warnings in UPDATING... Try to add 'device mem' to your kernel configuration. Eugene Grosbein ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: RELENG_8 kernel as of Apr 14 does not boot
On Mon, Apr 16, 2012 at 01:37:29PM +0700, Eugene Grosbein wrote: 16.04.2012 11:26, Alexey Dokuchaev пишет: Just update my 8.x kernel sources last weekend, and newly built kernel did not boot for me: link_elf: symbol mem_range_softc undefined KLD file acpi.ko - could not finalize loading kernel trap 12 with interrupts disabled Try to add 'device mem' to your kernel configuration. :-) I explicitly have nodevice mem and nodevice io in my config. They are being loaded from /boot/loader.conf. This worked fine for quite a while. I will try to have it compiled-in, but would still prefer it fixed, or in case it cannot be fixed and mem.ko cannot be loaded separately from now on, appropriate entry in UPDATING. ./danfe ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: RELENG_8 kernel as of Apr 14 does not boot
Just update my 8.x kernel sources last weekend, and newly built kernel did not boot for me: link_elf: symbol mem_range_softc undefined KLD file acpi.ko - could not finalize loading kernel trap 12 with interrupts disabled Try to add 'device mem' to your kernel configuration. :-) I explicitly have nodevice mem and nodevice io in my config. They are being loaded from /boot/loader.conf. This worked fine for quite a while. I will try to have it compiled-in, but would still prefer it fixed, or in case it cannot be fixed and mem.ko cannot be loaded separately from now on, appropriate entry in UPDATING. It seems John Baldwin brought dependency of acpi.ko on device mem 4 days ago to RELENG_8 with MFC: http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/i386/acpica/acpi_wakeup.c#rev1.50.2.3 Eugene Grosbein ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
RELENG_8 kernel as of Apr 14 does not boot
Hi, Just update my 8.x kernel sources last weekend, and newly built kernel did not boot for me: link_elf: symbol mem_range_softc undefined KLD file acpi.ko - could not finalize loading kernel trap 12 with interrupts disabled This is stripped down kernel with everything possible loaded from modules. Any ideas? Did not see any warnings in UPDATING... ./danfe ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
