Re: panic during boot of 5.7 in de(4) running in Hyper-V

2015-06-25 Thread Reyk Floeter
On Tue, Jun 23, 2015 at 09:08:25PM -0600, Theo de Raadt wrote: I looked into this last year but lost interest. It seems like the DMA buffer is being placed past the UVM constraint for DMA ( eg 4GB). A configuration buffer is in the softc. It should be allocated to be dma-reachable.

Re: panic during boot of 5.7 in de(4) running in Hyper-V

2015-06-24 Thread pizdelect
On Tue, Jun 23, 2015 at 09:08:25PM -0600, Theo de Raadt wrote: -bcopy(sc-tulip_setupdata, sc-tulip_setupbuf, - sizeof(sc-tulip_setupbuf)); +bcopy(sc-tulip_setupdata, sc-tulip_setupbuf, TULIP_SETUP); +sc-tulip_setupbuf = dma_alloc(TULIP_SETUP, PR_WAITOK); +

panic during boot of 5.7 in de(4) running in Hyper-V

2015-06-23 Thread Tom Schutter
I installed 5.7 from http://ftp3.usa.openbsd.org/pub/OpenBSD/5.7/amd64/install57.iso in a Windows Server 2012 R2 Hyper-V VM using the Legacy Network Adapter. I always get a kernel panic in the de(4) driver during boot. If I remove the legacy NIC from the VM config, then I successfully boot, but

Re: panic during boot of 5.7 in de(4) running in Hyper-V

2015-06-23 Thread Theo de Raadt
I looked into this last year but lost interest. It seems like the DMA buffer is being placed past the UVM constraint for DMA ( eg 4GB). A configuration buffer is in the softc. It should be allocated to be dma-reachable. This driver is quite ugly. Maybe the following diff works? Index:

Re: panic during boot of 5.7 in de(4) running in Hyper-V

2015-06-23 Thread Mike Larkin
On Tue, Jun 23, 2015 at 02:57:51PM -0600, Tom Schutter wrote: I installed 5.7 from http://ftp3.usa.openbsd.org/pub/OpenBSD/5.7/amd64/install57.iso in a Windows Server 2012 R2 Hyper-V VM using the Legacy Network Adapter. I always get a kernel panic in the de(4) driver during boot. If I