Re: Several minor questions (12.0-amd64)

2017-04-24 Thread Beeblebrox 
/boot/loader.conf allows for an earlier time frame
for having dumpdev.


Thanks a lot, that's a very nice suggestion.
Did not work though surprisingly, which suggests panic is ocuring in a way
that interferes with loader. No matter, I noted down the output of trace
and had alredy moved relevant modules to rc.conf. The capture attempt was
so I could send it to a drm-next developer.

Regards.
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: Several minor questions (12.0-amd64)

2017-04-22 Thread Mark Millard 
Beeblebrox zaphod at berentweb.com wrote on Sat Apr 22 06:04:01 UTC 2017 :

> 3. Under one scenario, I'm getting a kernel panic but I cannot dump because
> busybox states "no dumpdev specified" which means rc.conf (where I have
> dumpdev set) has not been read yet. How can I pass dumpdev wile in busybox
> command line so that ">dump" does its job?

/boot/loader.conf allows for an earlier time frame
for having dumpdev. For example I have:

# more /boot/loader.conf
geom_label_load="YES"   # File system labels (see glabel(8))
kern.cam.boot_delay="1"
dumpdev="/dev/label/BPIM3swap"

Supporting documentation is from:

https://www.freebsd.org/cgi/man.cgi?query=loader=8=0=FreeBSD+11.0-RELEASE+and+Ports

and includes the following about dumpdev:

LOADER(8)   FreeBSD System Manager's Manual  LOADER(8)


NAME

 
loader
 -- kernel bootstrapping final stage

. . .

   BUILTIN ENVIRONMENT VARIABLES

 The loader has actually two different kinds of `environment' variables.
 There are ANS Forth's environmental queries, and a separate space of
 environment variables used by builtins, which are not directly available
 to Forth words.  It is the latter type that this section covers.
. . .
 dumpdev   Sets the device for kernel dumps.  This can be used to ensure
   that a device is configured before the corresponding dumpdev
   directive from rc.conf(5) has been processed, allowing kernel
   panics that happen during the early stages of boot to be cap-
   tured.




===
Mark Millard
markmi at dsl-only.net

___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Several minor questions (12.0-amd64)

2017-04-22 Thread Beeblebrox 
Hello, I have several brief questions on issues I'm slightly stuck on:

1. For buildworld, my /etc/src.conf uses default CROSS_COMPILER,
CLANG_BOOTSTRAP, CLANG_FULL  for amd64, but I would like clang to xbuild
only for target i386 as I do not need the others (like Target/arm). Is
there a knob for this?

2. Is there a way to read a list of modules inside an unloaded kernel? Sort
of "kldstat -v" for a non-loaded kernel? Reading the kernel manifest
(INCLUDE_CONFIG_FILE setting) is not what I need.

3. Under one scenario, I'm getting a kernel panic but I cannot dump because
busybox states "no dumpdev specified" which means rc.conf (where I have
dumpdev set) has not been read yet. How can I pass dumpdev wile in busybox
command line so that ">dump" does its job?

4. Getting several of these lock order reversals. Kernel is drm-next but
Generic from Head gives the same messages. Not urgent, just FYI.

lock order reversal:
 1st 0xf80064915040 filedesc structure (filedesc structure) @
/asp/git/srcdrm/sys/kern/kern_descrip.c:1234
 2nd 0xf8002e9f0d50 ufs (ufs) @
/asp/git/srcdrm/sys/kern/vfs_subr.c:5022
 stack backtrace:
 #0 0x804d3180 at witness_debugger+0x70
 #1 0x804d3073 at witness_checkorder+0xe23
 #2 0x8044aa35 at __lockmgr_args+0x875
 #3 0x814d09e5 at ffs_lock+0xa5
 #4 0x80717840 at VOP_LOCK1_APV+0xe0
 #5 0x8054847a at _vn_lock+0x6a
 #6 0x8042c9c8 at knlist_remove_kq+0x88
 #7 0x8053f358 at filt_vfsdetach+0x28
 #8 0x8042d4f1 at knote_fdclose+0x171
 #9 0x804206b5 at closefp+0x65
 #10 0x806afe9a at amd64_syscall+0x57a
 #11 0x80692dcb at Xfast_syscall+0xfb

 lock order reversal:
 1st 0xf80064915040 filedesc structure (filedesc structure) @
/asp/git/srcdrm/sys/kern/kern_descrip.c:1234
 2nd 0xf8004b4d3d50 zfs (zfs) @
/asp/git/srcdrm/sys/kern/vfs_subr.c:5022
 stack backtrace:
 #0 0x804d3180 at witness_debugger+0x70
 #1 0x804d3073 at witness_checkorder+0xe23
 #2 0x8044a0fe at lockmgr_lock_fast_path+0x1ce
 #3 0x80717840 at VOP_LOCK1_APV+0xe0
 #4 0x8054847a at _vn_lock+0x6a
 #5 0x8042c9c8 at knlist_remove_kq+0x88
 #6 0x8053f358 at filt_vfsdetach+0x28
 #7 0x8042d4f1 at knote_fdclose+0x171
 #8 0x804206b5 at closefp+0x65
 #9 0x806afe9a at amd64_syscall+0x57a
 #10 0x80692dcb at Xfast_syscall+0xfb

 lock order reversal:
 1st 0xf801aec715f0 syncer (syncer) @
/asp/git/srcdrm/sys/kern/vfs_subr.c:2152
 2nd 0xf8004bc3e068 zfs (zfs) @
/asp/git/srcdrm/sys/kern/vfs_subr.c:2602
 stack backtrace:
 #0 0x804d3180 at witness_debugger+0x70
 #1 0x804d3073 at witness_checkorder+0xe23
 #2 0x8044a0fe at lockmgr_lock_fast_path+0x1ce
 #3 0x80717840 at VOP_LOCK1_APV+0xe0
 #4 0x8054847a at _vn_lock+0x6a
 #5 0x80538892 at vget+0x82
 #6 0x8053a936 at vfs_msync+0xa6
 #7 0x8053ef96 at sync_fsync+0xc6
 #8 0x80716890 at VOP_FSYNC_APV+0xe0
 #9 0x8053d2fc at sched_sync+0x36c
 #10 0x80436f44 at fork_exit+0x84
 #11 0x8069301e at fork_trampoline+0xe

 lock order reversal:
 1st 0xf80039590d50 zfs (zfs) @
/asp/git/srcdrm/sys/kern/vfs_mount.c:855
 2nd 0xf8001a4489a0 devfs (devfs) @
/asp/git/srcdrm/sys/kern/vfs_subr.c:2602
 stack backtrace:
 #0 0x804d3180 at witness_debugger+0x70
 #1 0x804d3073 at witness_checkorder+0xe23
 #2 0x8044a0fe at lo
 ckmgr_lock_fast_path+0x1ce
 #3 0x80717840 at VOP_LOCK1_APV+0xe0
 #4 0x8054847a at _vn_lock+0x6a
 #5 0x80538892 at vget+0x82
 #6 0x80395b2d at devfs_allocv+0xcd
 #7 0x80395643 at devfs_root+0x43
 #8 0x8052f66f at vfs_donmount+0x118f
 #9 0x8052e4b2 at sys_nmount+0x72
 #10 0x806afe9a at amd64_syscall+0x57a
 #11 0x80692dcb at Xfast_syscall+0xfb
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"