Bug 175353 - [tmpfs] [panic] panic during building a nanobsd image + ports
Summary: [tmpfs] [panic] panic during building a nanobsd image + ports
Status: Closed FIXED
Alias: None
Product: Base System
Classification: Unclassified
Component: kern (show other bugs)
Version: 9.1-RELEASE
Hardware: Any Any
: Normal Affects Only Me
Assignee: Mateusz Guzik
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-01-16 14:20 UTC by olivier
Modified: 2013-01-17 23:06 UTC (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description olivier 2013-01-16 14:20:00 UTC 
Each time I'm trying to build my customized nanobsd image using tmpfs as a workdir, my system crash.
This problem is reproductible.

# First crash log
Here, I'm trying to cross-compile an i386 image from my amd64:

Jan 16 13:32:06 <kern.crit> orange kernel: Sleeping thread (tid 101584, pid 91068) owns a non-sleepable lock
Jan 16 13:32:06 <kern.crit> orange kernel: KDB: stack backtrace of thread 101584:
Jan 16 13:32:06 <kern.crit> orange kernel: #0 0xffffffff808f2d46 at mi_switch+0x186
Jan 16 13:32:06 <kern.crit> orange kernel: #1 0xffffffff8092b13c at sleepq_catch_signals+0x2cc
Jan 16 13:32:06 <kern.crit> orange kernel: #2 0xffffffff8092bac6 at sleepq_wait_sig+0x16
Jan 16 13:32:06 <kern.crit> orange kernel: #3 0xffffffff808f33fd at _sleep+0x29d
Jan 16 13:32:06 <kern.crit> orange kernel: #4 0xffffffff808b97c5 at kern_wait+0x6e5
Jan 16 13:32:06 <kern.crit> orange kernel: #5 0xffffffff80c45c95 at freebsd32_wait4+0x35

# second crash log
Here I only want to build an image:

Jan 16 14:56:26 <kern.crit> orange kernel: Sleeping thread (tid 100617, pid 54652) owns a non-sleepable lock
Jan 16 14:56:26 <kern.crit> orange kernel: KDB: stack backtrace of thread 100617:
Jan 16 14:56:26 <kern.crit> orange kernel: #0 0xffffffff808f2d46 at mi_switch+0x186
Jan 16 14:56:26 <kern.crit> orange kernel: #1 0xffffffff8092b13c at sleepq_catch_signals+0x2cc
Jan 16 14:56:26 <kern.crit> orange kernel: #2 0xffffffff8092bac6 at sleepq_wait_sig+0x16
Jan 16 14:56:26 <kern.crit> orange kernel: #3 0xffffffff808f33fd at _sleep+0x29d
Jan 16 14:56:26 <kern.crit> orange kernel: #4 0xffffffff808b97c5 at kern_wait+0x6e5
Jan 16 14:56:26 <kern.crit> orange kernel: #5 0xffffffff808b9995 at sys_wait4+0x35

# system info

My system have 56G of RAM, 8 cores and ZFS enabled.
Free RAM is quiet high:

[root@orange]~#vmstat
 procs      memory      page                    disks     faults         cpu
 r b w     avm    fre   flt  re  pi  po    fr  sr da0 da1   in   sy   cs us sy id
 0 0 0    576M    45G   545   0   3   0   546   0   0   0  880  779  415  0  1 99

How-To-Repeat: I can reproduce the problem each time I build a new BSDRP image using the TMPFS mode:

svn checkout https://svn.code.sf.net/p/bsdrp/code/trunk BSDRP
cd BSDRP
./make.sh  -r
Comment 1 Mark Linimon freebsd_committer freebsd_triage 2013-01-17 00:13:20 UTC 
Responsible Changed
From-To: freebsd-bugs->freebsd-fs

Over to maintainer(s).
Comment 2 olivier 2013-01-17 10:36:22 UTC 
Applying the mjg's patch of revision 245351 (kern_lock.c) solve this
problem on my 2 machines.

Regards,

Olivier
Comment 3 Mateusz Guzik freebsd_committer freebsd_triage 2013-01-17 23:05:48 UTC 
Responsible Changed
From-To: freebsd-fs->mjg

Take
Comment 4 Mateusz Guzik freebsd_committer freebsd_triage 2013-01-17 23:06:39 UTC 
State Changed
From-To: open->closed

Duplicate of kern/174969