DragonFly bugs List (threaded) for 2003-09
Re: slaballocation panic on boot
:Content-Type: text/plain; charset=us-ascii
:I would like to bring good news but unfortunately that is not the case. I have
:updated to sources with todays (9/25) fixes. The machine running 4.8-p10 is
:rebooted into the dragonfly kernel so make installworld can be performed.
:'make installworld 2>&1 | tee /devel/dragonfly/buildlog/installworld.log' does
:not get written, but on the console only the first shell script 'for _x in [
:cp....' is printed. The system always fails here. Sometimes with ddb,
:sometimes without. The panics I have seen have been double faults. The core
:dumps I have collected yield useless information (see attached).
:kernel config is attacted (no slaballoc, no memap)
:useless crashdump attached
Well, at least we know it isn't the slab allocator.
The 4.x gdb will not be able to debug a dragonfly crash dump, but a
dragonfly gdb should.
I am somewhat at a loss for the moment. I suggest putting the crash
dump and the dragonfly kernel.debug up on a web or ftp server where
I can fetch them. I'll see if I can garner any information from it.