Hello Kevin, * kevin <kevinxlinuz_at_163.com> wrote: > Hi, > I update to the newest source tree and rebuild kernel(with zfs > patch).kernel panic on system startup.Should I rebuild world? > ...... > Starting gdm. > Sleeping thread (tid 100068,pid 1145) owns a non-sleepable lock ^^^^^^^^^^^^^^^^^^^ > sched_switch() at sched_switch+0x184 > mi_switch() at mi_switch+0x21b > sleepq_switch() at sleepq_switch+0xfa > sleepq_wait() at sleepq_wait+0x46 > _sx_slock_hard() at _sx_slock_hard+0x169 > _sx_slock() at _sx_slock+0x6b > acct_process() at acct_process+0x24b > exit1() at exit1+0x3e8 > sys_exit() at sys_exit+0xe > syscall() at syscall+0x1dd > Xfast_syscall() at Xfast_syscall+0xab > --- syscall (1, FreeBSD ELF64, sys_exit), rip = 0x80094dd0c, rsp = > 0x7fffffffcdf8, rbp = 0x62d548 --- > panic: sleeping thread > cpuid = 0 > KDB: enter: panic > [thread pid 1143 tid 100127 ] ^^^^^^^^^^^^^^^^^^^ It seems like the actual problem lies within a different thread. Can you reproduce this? If so, can you get a list of locks that was held by the offending thread? -- Ed Schouten <ed_at_80386.nl> WWW: http://80386.nl/
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:39:34 UTC