Re: panic: unveil_nipledge_lookup: unexpected pledge bits: 8589934592 after update to recent -current

2018-08-02 Thread Sebastien Marie
On Fri, Aug 03, 2018 at 12:02:17AM +0200, Felix Maschek wrote:
> Hi,
> 
> I've updated to the recent -current on my Lenovo T450 and get a kernel panic

> panic: unveil_nipledge_lookup: unexpected pledge bits: 8589934592

this panic is from my diff I recently sent to tech@. it seems it has
been put in snapshots. it also means I was wrong in some place, and that
I didn't check enough it before sending the diff. I am really sorry
about that.

The bit I missed is: 8589934592 => 0x2 which is PLEDGE_CHOWN. It
means all syscalls using this pledge annotation could generate the
panic if the program is used with unveil(2)... bad.

> Any idea how to bring up my system again?

wait for a new snapshot or rebuild a kernel from source (possibly from
another system, as using chown(2) with unveil(2) will generate the
panic).

Sorry.
-- 
Sebastien Marie



panic: unveil_nipledge_lookup: unexpected pledge bits: 8589934592 after update to recent -current

2018-08-02 Thread Felix Maschek

Hi,

I've updated to the recent -current on my Lenovo T450 and get a kernel 
panic at the following point:


starting local daemons: apmd cron xenodm.
Thu Aug  2 23:44:13 CEST 2018

-> at this point it is starting X but fall back to panic.

This is the output directly after the panic message:

Stopped at db_enter+0x12: popq %r11
TIDPIDUIDPRFLAGSPFLAGSCPU   COMMAND
52492   30180   0   0x2   0   0   getty
50658   51951   0   0x2   0   2   getty
*273210   59371   0   0x2   0   3K   getty
213631   9301   0   0x2   0   1   getty
db_enter() at db_enter+0x12
panic() at panic+0x120
unveil_check_component(717dcd5addc519e1,ff025bf0de10,800043c4fc88) 
at unveil_check_component+0x18e

vfs_lookup(27dc50307a7045d2) at vfs_lookup+0x296
namei(c6110ecd0e5b1a65) at namei+0x297
dofchownat(5195e973b86aec18,100,800043b25058,10,800043c4fef0,7f7dee28) 
at dofchownat0x91

syscall(717dcd5add7470f3) at syscall+0x32a
Xsyscall(6,10,bf8189078f0,10,3,7f7deee8) at Xsyscall+0x128
end of kernel

One more observation: the needed iwm0 firmware is missing on my system.

Any idea how to bring up my system again?

Kind regards
Felix