I rearranged my network and ended up getting these in messages:
cannot forward src fe80:9::a691:b1ff:fe1f:d2a0, dst
2001:44b8:3110:fb00:200:5eff:fe00:10a, nxt 58, rcvif 9, outif 1
I guess I could run ifconfig and count interfaces, but I'm lazy and the
kernel knows what they are.
cannot forward
On 02/01/18(Tue) 20:44, Darren Tucker wrote:
> I rearranged my network and ended up getting these in messages:
>
> cannot forward src fe80:9::a691:b1ff:fe1f:d2a0, dst
> 2001:44b8:3110:fb00:200:5eff:fe00:10a, nxt 58, rcvif 9, outif 1
>
> I guess I could run ifconfig and count interfaces, but I'm
On Mon, Jan 01, 2018 at 09:07:25PM -0700, Todd C. Miller wrote:
> On Mon, 01 Jan 2018 19:54:07 -0600, Scott Cheloha wrote:
>
> > Hey,
> >
> > In the mg(1) *compile* buffer, currently you get incorrect
> > output like:
> >
> > Command exited abnormally with code 256 at [...]
> >
> > Using the
On Tue, Jan 2, 2018 at 3:06 PM, Ingo Schwarze wrote:
...
> OK for the patch at the end?
>
> Testing - before:
>
...
> --- args.c 16 Aug 2016 16:44:55 - 1.28
> +++ args.c 2 Jan 2018 22:47:19 -
> @@ -406,8 +406,9 @@ get_off(char *val)
> off_t num,
On Sat, 30 Dec 2017 11:50:53 +, Otto Moerbeek wrote:
> Slightly different diff: instead of initing all chunk_info structs in
> page, do it on demand at first use. Measurements show that a lot of
> programs only use a few chunk_info structs, so it is a bit wasteful to
> always initialize all of
on -current amd64, simply doing "$ ktrace -p $pid_of_firefox" is enough
to freeze my box:
OpenBSD 6.2-current (GENERIC.MP) #313: Mon Jan 1 17:51:21 MST 2018
dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
real mem = 8238301184 (7856MB)
avail mem = 7981707264 (7611MB)
On Tue, Jan 02, 2018 at 12:40:33AM +0100, Aron Diehl wrote:
> Hi,
>
>
> I'm working on measuring OpenBSD code coverage.
>
>
> Code coverage of what? The regression-tests make target?
>
> Cheers
> Aron
Obviously.
On 02/01/18(Tue) 17:35, Mark Kettenis wrote:
> > Date: Tue, 2 Jan 2018 16:02:16 +0100
> > From: Martin Pieuchot
> >
> > We're no longer using the 'mtx_lock' field, so remove it.
> >
> > While here remove the 'volatile' keyword from amd64's 'struct mutex'.
>
> You mean the
> Date: Tue, 2 Jan 2018 16:02:16 +0100
> From: Martin Pieuchot
>
> We're no longer using the 'mtx_lock' field, so remove it.
>
> While here remove the 'volatile' keyword from amd64's 'struct mutex'.
You mean the mtx_owner member.
> ok?
I think that is wrong. Unless we
On 19/12/17(Tue) 18:06, Marco Pfatschbacher wrote:
> On Tue, Dec 19, 2017 at 12:43:48PM +0100, Martin Pieuchot wrote:
> > I'd like to see some information about my tunnels in my NMS.
>
> Nice. I would find that very useful :)
>
> > The problem is that there's not standard MIB for this and most
In 2007 I changed this code to use table 3 by default, falling back
on table 2 (the previous default) or 1. This was done just to make
the keyboard on the OQO model 01 work, and these devices are long
gone.
10 years later, some newer Lenovo machines seem to have trouble
trying this mode
New year, new diff. Assuming we can live with the kqueue(2) races,
here's a diff to remove the KERNEL_LOCK() from all pr_input() routines.
I'd appreciate tests.
Index: net/if.c
===
RCS file: /cvs/src/sys/net/if.c,v
retrieving
We're no longer using the 'mtx_lock' field, so remove it.
While here remove the 'volatile' keyword from amd64's 'struct mutex'.
ok?
Index: i386/i386/genassym.cf
===
RCS file: /cvs/src/sys/arch/i386/i386/genassym.cf,v
retrieving
/bin/dd/args.c r1.28
get_off(char *val)
Code:
num = strtoll(val, , 0);
if (num == LLONG_MAX) /* Overflow. */
err(1, "%s", oper);
if (expr == val)/* No digits. */
errx(1, "%s: illegal numeric value",
Hello,
In bwfm_pci_dmamem_alloc() and bwfm_pci_dmamem_free(), bdm points
to a single struct not an array. When freeing it we can just use
the struct size. Does this look correct?
- Michael
Index: if_bwfm_pci.c
===
RCS file:
> On 3 Jan 2018, at 08:25, Mark Kettenis wrote:
>
> This cip advertises itself as a PCI IDE controller, but actually
> implements an AHCI interface. Adding it to the ahci_devices lists,
> without any quirks makes ahci(4) work. It doesn't actually work with
> our
On Tue, Jan 02, 2018 at 11:25:55PM +0100, Mark Kettenis wrote:
> This cip advertises itself as a PCI IDE controller, but actually
> implements an AHCI interface. Adding it to the ahci_devices lists,
> without any quirks makes ahci(4) work. It doesn't actually work with
> our pciide(4) driver!
>
> On Jan 2, 2018, at 13:37, Job Snijders wrote:
>
> I often observed on my Thinkpad x270 that after an upgrade via bsd.rd,
> the first reboot resulted in keystrokes being garbage (and at second
> reboot everything was fine again).
You just explained why I saw what I saw this
Hi all,
I often observed on my Thinkpad x270 that after an upgrade via bsd.rd,
the first reboot resulted in keystrokes being garbage (and at second
reboot everything was fine again).
The below patch seems to be an improvement.
Kind regards,
Job
On Tue, Jan 02, 2018 at 09:36:49AM -0600, joshua
This cip advertises itself as a PCI IDE controller, but actually
implements an AHCI interface. Adding it to the ahci_devices lists,
without any quirks makes ahci(4) work. It doesn't actually work with
our pciide(4) driver!
ok?
Index: dev/pci/ahci_pci.c
Hi,
Bulat Musin wrote on Tue, Jan 02, 2018 at 09:47:39PM +0300:
> /bin/dd/args.c r1.28
> get_off(char *val)
>
> num = strtoll(val, , 0);
> if (num == LLONG_MAX) /* Overflow. */
> err(1, "%s", oper);
>
> Incorrect checking of overflow.
> Firstly, set
21 matches
Mail list logo