David Gwynne writes:
> On Wed, Apr 04, 2018 at 08:27:52PM +0200, Christian Barthel wrote:
>> Hello,
>>
>> After upgrading to 6.3, I've encountered a problem while using gif(4):
>>
>> Pre-Cond: fresh install of OpenBSD 6.3
>> # cat /etc/hostname.gif0
>> tunnel 10.0.0.1 10.0.0.2
>> 10.0.0.1 10.
On Wed, Apr 04, 2018 at 08:27:52PM +0200, Christian Barthel wrote:
> Hello,
>
> After upgrading to 6.3, I've encountered a problem while using gif(4):
>
> Pre-Cond: fresh install of OpenBSD 6.3
> # cat /etc/hostname.gif0
> tunnel 10.0.0.1 10.0.0.2
> 10.0.0.1 10.0.0.2
> # sh /etc/netstart.sh gif
On 2018/04/04 18:42, trondd wrote:
> On Wed, April 4, 2018 10:02 am, trondd wrote:
> > Bringing this back up from the depths. I kept rolling back to older
> httpd
> > code and forgetting about this :(
> > I still see this issue in 6.3 A new packet cap look the same.
>
> Ok, I was able to do some
On Wed, April 4, 2018 10:02 am, trondd wrote:
> Bringing this back up from the depths. I kept rolling back to older
httpd
> code and forgetting about this :(
> I still see this issue in 6.3 A new packet cap look the same.
Ok, I was able to do some more digging into this. httpd does not close
th
> Date: Thu, 5 Apr 2018 02:02:20 +1000
> From: Jonathan Gray
>
> On Mon, Apr 02, 2018 at 11:52:08AM +0200, Stefan Fritsch wrote:
> > Hi,
> >
> > We have seen problems with em on i219V and i219LM. For example, "Hardware
> > Initialization Failed" if no cable is plugged in during boot, or watchdo
Hello,
After upgrading to 6.3, I've encountered a problem while using gif(4):
Pre-Cond: fresh install of OpenBSD 6.3
# cat /etc/hostname.gif0
tunnel 10.0.0.1 10.0.0.2
10.0.0.1 10.0.0.2
# sh /etc/netstart.sh gif0
# ping 10.0.0.2
Result & Behavior: the kernel thread softnet starts running on th
On Mon, Apr 02, 2018 at 11:52:08AM +0200, Stefan Fritsch wrote:
> Hi,
>
> We have seen problems with em on i219V and i219LM. For example, "Hardware
> Initialization Failed" if no cable is plugged in during boot, or watchdog
> timeouts / hangs until next boot if the cable is removed while data is
Bringing this back up from the depths. I kept rolling back to older httpd
code and forgetting about this :(
I still see this issue in 6.3 A new packet cap look the same.
On Tue, April 18, 2017 4:23 pm, trondd wrote:
> On Tue, April 18, 2017 3:46 pm, Reyk Floeter wrote:
>>
>>> Am 18.04.2017 um 2
I'm not done with reviewing yet, but I'm running out of time for now.
Just a simple observation concerning this change:
> +/* convert uint64_t to base N string */
>
> char *
> -ulton(long unsigned int n, int base)
> +u64ton(uint64_t n, int base)
> {
> char *p;
> static char buf [20]
With the growing popularity of SoCs, external PHYs are making a bit of
a comeback. In quite a few cases I'm seeing rgephy(4) show up twice,
once on address 0 and once on some other address. But there is only
one PHY soldered onto the board. This is a little bit annoying but
mostly harmless. The
On 03/04/18(Tue) 16:59, Mark Kettenis wrote:
> > Date: Tue, 3 Apr 2018 16:48:09 +0200
> > From: Martin Pieuchot
> >
> > Similar to other diffs, this one move a FREF() right after
> > fd_getfile_mode(), ok?
> >
> > Index: kern/sys_generic.c
> >
On 2018-04-03 18:53:16, Bryan Linton wrote:
> On 2018-04-02 11:52:08, Stefan Fritsch wrote:
> > Hi,
> >
> > We have seen problems with em on i219V and i219LM. For example, "Hardware
> > Initialization Failed" if no cable is plugged in during boot, or watchdog
> > timeouts / hangs until next bo
On 2018/04/03 20:08, Tobias Stoeckmann wrote:
> Hi,
>
> this patch increases the number range on 32 bit architectures like
> i386 to 64 bit. These are already supported on 64 bit architectures
> due to using "long".
>
> The rational behind this patch is to unify test/expr/ksh in allowing
> 64 bit
13 matches
Mail list logo
