Re: Revision 1.88 of kern_linker.c breaks module loading for diskless
On Fri, 26 Apr 2002, Brian Somers wrote: BSThe intent is to discover whether there's a filesystem yet (vn_open() BSwill die horribly otherwise). BS BSMy use of rootdev is (obviously) flawed. AFAICT, either rootvp BSor rootvnode should be used, but I can't tell the difference between BSthe two at a glance and am lacking development resources right now BS(my development box seems to enjoy dropping cores too frequently to BSbuild a kernel at the moment). BS BSIf somebody could test that rootvnode or rootvp are non-NULL after BSan NFS-mounted root is set up, I'd thankfully approve the quick BSfix... :*) dlc1# gdb -k /boot/kernel/kernel /dev/mem (no debugging symbols found)... IdlePTD at phsyical address 0x00392000 initial pcb at physical address 0x082bdda0 panic messages: --- --- #0 0xc017b968 in mi_switch () (kgdb) p rootdev $1 = -1 (kgdb) p rootvnode $2 = -843452416 (kgdb) p rootvp $3 = -843452416 (kgdb) They obviously point to the same thing and are non-NULL (root is NFS). harti -- harti brandt, http://www.fokus.gmd.de/research/cc/cats/employees/hartmut.brandt/private [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Revision 1.88 of kern_linker.c breaks module loading for diskless
Hello, the check for rootdev != NODEV introduced in rev 1.88 breaks loading of kernel modules from an NFS mounted root in diskless configurations. Dropping in gdb and printing rootdev shows -1 which is, I assume, NODEV. This worked before without problems. harti -- harti brandt, http://www.fokus.gmd.de/research/cc/cats/employees/hartmut.brandt/private [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Revision 1.88 of kern_linker.c breaks module loading for diskless
In message [EMAIL PROTECTED], Harti Brandt write s: the check for rootdev != NODEV introduced in rev 1.88 breaks loading of kernel modules from an NFS mounted root in diskless configurations. Dropping in gdb and printing rootdev shows -1 which is, I assume, NODEV. Ah, that would explain a problem I saw recently on a netbooted box where kldload only worked with full module paths. Could `rootvnode' be checked for NULL instead? Ian To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Revision 1.88 of kern_linker.c breaks module loading for diskless
In message [EMAIL PROTECTED], Harti Brandt write s: the check for rootdev != NODEV introduced in rev 1.88 breaks loading of kernel modules from an NFS mounted root in diskless configurations. Dropping in gdb and printing rootdev shows -1 which is, I assume, NODEV. Ah, that would explain a problem I saw recently on a netbooted box where kldload only worked with full module paths. Could `rootvnode' be checked for NULL instead? Hi, The intent is to discover whether there's a filesystem yet (vn_open() will die horribly otherwise). My use of rootdev is (obviously) flawed. AFAICT, either rootvp or rootvnode should be used, but I can't tell the difference between the two at a glance and am lacking development resources right now (my development box seems to enjoy dropping cores too frequently to build a kernel at the moment). If somebody could test that rootvnode or rootvp are non-NULL after an NFS-mounted root is set up, I'd thankfully approve the quick fix... :*) Cheers. Ian -- Brian [EMAIL PROTECTED][EMAIL PROTECTED] http://www.freebsd-services.com/brian@[uk.]FreeBSD.org Don't _EVER_ lose your sense of humour ! brian@[uk.]OpenBSD.org To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message