On Wed, October 16, 2013 10:23 am, Jan Stary wrote: > Just installed Patrick's fresh snapshot. > > OpenBSD 5.4-current (GENERIC-OMAP) #11: Tue Oct 8 08:49:25 CEST 2013 > r...@imx.fritz.box:/usr/src/sys/arch/armv7/compile/GENERIC-OMAP > real mem = 536870912 (512MB) > avail mem = 519208960 (495MB) > mainbus0 at root > cpu0 at mainbus0: ARM Cortex A8 R3 rev 2 (ARMv7 core) > cpu0: DC enabled IC enabled WB disabled EABT branch prediction enabled > cpu0: 32KB(64b/l,4way) I-cache, 32KB(64b/l,4way) wr-back D-cache > omap0 at mainbus0: BeagleBone > prcm0 at omap0 rev 0.2 > sitaracm0 at omap0: control module, rev 1.0 > intc0 at omap0 rev 5.0 > omap0: device edma unit 0 not configured > dmtimer0 at omap0 rev 3.1 > dmtimer1 at omap0 rev 3.1 > omdog0 at omap0 rev 0.1 > ommmc0 at omap0 > sdmmc0 at ommmc0 > ommmc1 at omap0 > sdmmc1 at ommmc1 > com0 at omap0: ti16750, 64 byte fifo > com0: console > cpsw0 at omap0: version 1.12 (0), address 90:59:af:5f:1e:3d > ukphy0 at cpsw0 phy 0: Generic IEEE 802.3u media interface, rev. 1: OUI > 0x0001f0, model 0x000f > /dev/ksyms: Symbol table not valid. > scsibus0 at sdmmc0: 2 targets, initiator 0 > sd0 at scsibus0 targ 1 lun 0: <SD/MMC, Drive #01, > SCSI2 0/direct fixed > sd0: 16000MB, 512 bytes/sector, 32768000 sectors > scsibus1 at sdmmc1: 2 targets, initiator 0 > sd1 at scsibus1 targ 1 lun 0: <SD/MMC, Drive #01, > SCSI2 0/direct fixed > sd1: 1832MB, 512 bytes/sector, 3751936 sectors > vscsi0 at root > scsibus2 at vscsi0: 256 targets > softraid0 at root > scsibus3 at softraid0: 256 targets > boot device: sd0 > root on sd0a (2fd113e40920709f.a) swap on sd0b dump on sd0b > WARNING: CHECK AND RESET THE DATE! > > Mostly seems to work, but this is how my boot sequence ends: > > DHCPREQUEST on cpsw0 to 255.255.255.255 port 67 > DHCPACK from 192.168.111.1 (00:0d:b9:12:9f:2d) > bound to 192.168.111.11 -- renewal in 21600 seconds. > dmtimer_intr: negative duration! > Segmentation fault > Segmentation fault > Segmentation fault > Segmentation fault > Segmentation fault
Strangely, I can't reproduce this, not even the 'negative duration'. tmux is crashing here too. > > Also, tmux keeps segfaulting on me. > Is anyone else seeing this? > > > Jan
