Re: netpfil with if_output and ip(6)_output

2016-12-21 Thread Franco Fichtner
Hi all,

> On 14 Nov 2016, at 1:55 PM, Andrey V. Elsukov  wrote:
> 
> I have some thought related to your proposal.
> What you think if we will introduce new KPI to work with fwd_tags?
> With such KPI we can make fwd_tags opaque for PFIL consumers and handle
> tags identically in all *proto*_output() routines.

The proposed changes are now available at:

https://reviews.freebsd.org/D8877


Cheers,
Franco
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"


Re: Log spam: Limiting * response from 1 to 200 packets/sec

2016-12-21 Thread Eivind Nicolay Evensen

On Tue, Dec 13, 2016 at 09:48:59AM -0600, Eric van Gyzen wrote:
> On 12/13/2016 09:24, Michael Butler wrote:
> > Any hints as to why all of my -current equipment is complaining like below. 
> > Is
> > there a sysctl to moderate/turn this off?
> > 
> > Dec 13 10:00:01 archive kernel: Limiting icmp unreach response from 1 to 200
> > packets/sec
> > Dec 13 10:00:21 archive last message repeated 13 times
> > Dec 13 10:02:21 archive last message repeated 18 times
> > Dec 13 10:06:21 archive last message repeated 36 times
> > Dec 13 10:07:11 archive kernel: Limiting icmp ping response from 1 to 200
> > packets/sec


I repeated that on the nearest 10.0 here, because this looked strange, and
indeed I see:
Limiting icmp ping response from 294 to 200 packets/sec


However, the quoted line above that says it is limiting from 1 to 200
doesn't sound much of a limit?

-- 
Eivind N. Evensen
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"


Re: ACPI Error on HP ProBook 430 G2

2016-12-21 Thread Edward Tomasz Napierała
On 1220T1734, O. Hartmann wrote:
> Am Tue, 20 Dec 2016 18:09:20 +0300
> Vladimir Zakharov  schrieb:
> 
> > Hello!
> > 
> > Some time ago new ACPI messages appeared on console and in 
> > /var/log/messages. Like
> > these:
> > 
> > ACPI Error: Needed type [Reference], found [Processor] 0xf800043b8980
> > (20161117/exresop-111) ACPI Exception: AE_AML_OPERAND_TYPE, While resolving 
> > operands
> > for [OpcodeName unavailable] (20161117/dswexec-498) ACPI Error: Method 
> > parse/execution
> > failed [\134_SB.PCI0.LPCB.EC0.PPNT] (Node 0xf80004396640), 
> > AE_AML_OPERAND_TYPE
> > (20161117/psparse-560) ACPI Error: Method parse/execution failed
> > [\134_SB.PCI0.LPCB.EC0._Q04] (Node 0xf80004396c40), AE_AML_OPERAND_TYPE
> > (20161117/psparse-560) acpi_ec0: evaluation of query method _Q04 failed:
> > AE_AML_OPERAND_TYPE
> > 
> > I'm sure that there were no such messages earlier. Suspend/resume works
> > for me. But after disconnecting power line hw.acpi.acline still equals
> > to 1. And powerd/powerdxx do not adjust CPU frequency anymore.
> > 
> > System info:
> > $ uname -a
> > FreeBSD vzakharov 12.0-CURRENT FreeBSD 12.0-CURRENT #14 r310326M: Tue Dec 
> > 20 16:42:21
> > MSK 2016 root@vzakharov:/home/obj/usr/src/sys/GENERIC-NODEBUG  amd64
> > 
> > dmesg: http://pastebin.com/cYD8cR0b
> > hw.acpi: http://pastebin.com/Tht9B0FZ
> > acpidump: http://vzakharov.ru/z2v-HPProBook430G2.asl
> > 
> > 
> > PS. I'm not subscribed to freebsd-acpi. So keep me in CC, please.
> > 
> 
> I see lots of ACPI errors also shortly on a Lenovo E540 UEFI notebook running 
> most recent
> CURRENT ...

+1, I see the same on Thinkpad T420.

___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"


Re: Enabling NUMA in BIOS stop booting FreeBSD

2016-12-21 Thread Konstantin Belousov
On Tue, Dec 20, 2016 at 04:49:29PM -0500, Steve Wills wrote:
> Hi,
> 
> On 12/16/2016 16:20, John Baldwin wrote:
> > On Thursday, December 15, 2016 03:57:58 PM Adrian Chadd wrote:
> >> heh, an updated BIOS that solves the problem will solve the problem. :)
> >>
> >> I think you have enough information to provide to supermicro. Ie,
> >> "SMAP says X, when physical memory pages at addresses X are accessed,
> >> they don't behave like memory, maybe something is wrong".
> >>
> >> All I can think of is some hack to add a blacklist for that region so
> >> you can boot the unit. But it makes me wonder what else is going on.
> > 
> > We have the blacklist: it is the memory test.  That is the way to workaround
> > this type of BIOS breakage.  This is just the first time in over a decade 
> > that
> > test has been relevant.
> 
> I've got a SuperMicro X10SRA board that I bought back in March, I think.
> It was run CURRENT fine since then, until last month, when it started
> hanging during boot. I was about to update it to a new version of
> CURRENT when it started hanging at boot, but hadn't updated yet. The
> hang is after (verbose boot):
What is the exact version of the kernel you are running and which hangs ?
Try to bisect.

Do you have EARLY_AP_STARTUP option in the kernel config ?

> 
> ACPI APIC Table: 
> Package ID shift: 4
> L3 cache ID shift: 4
> L2 cache ID shift: 1
> L1 cache ID shift: 1
> Core ID shift: 1
Send NMI with 'ipmi power diag' and show the machine state from ddb.

> 
> Recently I've tried booting 9.3 and 10.3 on it without success. Other
> operating systems boot fine. Thinking the hang was similar to the one in
> this thread (or at least the board is), I tried many different BIOS
> changes and also tried enabling the memory test, but none of that
> changes anything. This is a single socket board so there are no NUMA or
> memory interleaving options in the BIOS. The BIOS is up to date (2.0a).
> It will boot if SMP is disabled. That's obviously sub-optimal, but is
> useful for building updated kernels, which I've tried. If anyone has any
> suggestions or ideas, I'd appreciate it.
> 
> Thanks,
> Steve
> 



___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"


Re: Enabling NUMA in BIOS stop booting FreeBSD

2016-12-21 Thread Steve Wills
Hi,

On 12/21/2016 06:58, Konstantin Belousov wrote:
> What is the exact version of the kernel you are running and which hangs ?

Right now I'm running r310303, booted with SMP disabled.

> Try to bisect.
> 

The issue appeared without updating the OS, but I have since updated.
That said, I have tried booting 10.3 and 9.3 from USB memstick without
success.

> Do you have EARLY_AP_STARTUP option in the kernel config ?
> 

I did, but I have since tried adding nooptions EARLY_AP_STARTUP to my
kernel config (my config include's GENERIC), which didn't affect the issue.

> Send NMI with 'ipmi power diag' and show the machine state from ddb.
> 

This board is the version without ipmi support, so I unfortunately can't
do that.

Steve



signature.asc
Description: OpenPGP digital signature


Re: ACPI Error on HP ProBook 430 G2

2016-12-21 Thread Alexandr Krivulya

21.12.2016 13:14, Edward Tomasz Napierała пишет:

On 1220T1734, O. Hartmann wrote:

Am Tue, 20 Dec 2016 18:09:20 +0300
Vladimir Zakharov  schrieb:


Hello!

Some time ago new ACPI messages appeared on console and in /var/log/messages. 
Like
these:

ACPI Error: Needed type [Reference], found [Processor] 0xf800043b8980
(20161117/exresop-111) ACPI Exception: AE_AML_OPERAND_TYPE, While resolving 
operands
for [OpcodeName unavailable] (20161117/dswexec-498) ACPI Error: Method 
parse/execution
failed [\134_SB.PCI0.LPCB.EC0.PPNT] (Node 0xf80004396640), 
AE_AML_OPERAND_TYPE
(20161117/psparse-560) ACPI Error: Method parse/execution failed
[\134_SB.PCI0.LPCB.EC0._Q04] (Node 0xf80004396c40), AE_AML_OPERAND_TYPE
(20161117/psparse-560) acpi_ec0: evaluation of query method _Q04 failed:
AE_AML_OPERAND_TYPE

I'm sure that there were no such messages earlier. Suspend/resume works
for me. But after disconnecting power line hw.acpi.acline still equals
to 1. And powerd/powerdxx do not adjust CPU frequency anymore.

System info:
$ uname -a
FreeBSD vzakharov 12.0-CURRENT FreeBSD 12.0-CURRENT #14 r310326M: Tue Dec 20 
16:42:21
MSK 2016 root@vzakharov:/home/obj/usr/src/sys/GENERIC-NODEBUG  amd64

dmesg: http://pastebin.com/cYD8cR0b
hw.acpi: http://pastebin.com/Tht9B0FZ
acpidump: http://vzakharov.ru/z2v-HPProBook430G2.asl


PS. I'm not subscribed to freebsd-acpi. So keep me in CC, please.


I see lots of ACPI errors also shortly on a Lenovo E540 UEFI notebook running 
most recent
CURRENT ...

+1, I see the same on Thinkpad T420.
Same on Thinkpad E530, but hw.acpi.acline changes on ac lost and powerd 
works.


--
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: Log spam: Limiting * response from 1 to 200 packets/sec

2016-12-21 Thread Gleb Smirnoff
On Wed, Dec 21, 2016 at 11:03:14AM +0100, Eivind Nicolay Evensen wrote:
E> 
E> On Tue, Dec 13, 2016 at 09:48:59AM -0600, Eric van Gyzen wrote:
E> > On 12/13/2016 09:24, Michael Butler wrote:
E> > > Any hints as to why all of my -current equipment is complaining like 
below. Is
E> > > there a sysctl to moderate/turn this off?
E> > > 
E> > > Dec 13 10:00:01 archive kernel: Limiting icmp unreach response from 1 to 
200
E> > > packets/sec
E> > > Dec 13 10:00:21 archive last message repeated 13 times
E> > > Dec 13 10:02:21 archive last message repeated 18 times
E> > > Dec 13 10:06:21 archive last message repeated 36 times
E> > > Dec 13 10:07:11 archive kernel: Limiting icmp ping response from 1 to 200
E> > > packets/sec
E> 
E> 
E> I repeated that on the nearest 10.0 here, because this looked strange, and
E> indeed I see:
E> Limiting icmp ping response from 294 to 200 packets/sec

This is what should happen.

E> However, the quoted line above that says it is limiting from 1 to 200
E> doesn't sound much of a limit?

That was my failure and already fixed.

-- 
Totus tuus, Glebius.
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"


RE: ACPI Error on HP ProBook 430 G2

2016-12-21 Thread Moore, Robert
We have fixed this issue for the latest version of ACPICA that will happen this 
week, probably 22 december.


> -Original Message-
> From: owner-freebsd-a...@freebsd.org [mailto:owner-freebsd-
> a...@freebsd.org] On Behalf Of Edward Tomasz Napierala
> Sent: Wednesday, December 21, 2016 3:15 AM
> To: O. Hartmann 
> Cc: freebsd-a...@freebsd.org; freebsd-current@freebsd.org; Vladimir
> Zakharov 
> Subject: Re: ACPI Error on HP ProBook 430 G2
> 
> On 1220T1734, O. Hartmann wrote:
> > Am Tue, 20 Dec 2016 18:09:20 +0300
> > Vladimir Zakharov  schrieb:
> >
> > > Hello!
> > >
> > > Some time ago new ACPI messages appeared on console and in
> > > /var/log/messages. Like
> > > these:
> > >
> > > ACPI Error: Needed type [Reference], found [Processor]
> > > 0xf800043b8980
> > > (20161117/exresop-111) ACPI Exception: AE_AML_OPERAND_TYPE, While
> > > resolving operands for [OpcodeName unavailable]
> > > (20161117/dswexec-498) ACPI Error: Method parse/execution failed
> > > [\134_SB.PCI0.LPCB.EC0.PPNT] (Node 0xf80004396640),
> > > AE_AML_OPERAND_TYPE
> > > (20161117/psparse-560) ACPI Error: Method parse/execution failed
> > > [\134_SB.PCI0.LPCB.EC0._Q04] (Node 0xf80004396c40),
> > > AE_AML_OPERAND_TYPE
> > > (20161117/psparse-560) acpi_ec0: evaluation of query method _Q04
> failed:
> > > AE_AML_OPERAND_TYPE
> > >
> > > I'm sure that there were no such messages earlier. Suspend/resume
> > > works for me. But after disconnecting power line hw.acpi.acline
> > > still equals to 1. And powerd/powerdxx do not adjust CPU frequency
> anymore.
> > >
> > > System info:
> > > $ uname -a
> > > FreeBSD vzakharov 12.0-CURRENT FreeBSD 12.0-CURRENT #14 r310326M:
> > > Tue Dec 20 16:42:21 MSK 2016
> > > root@vzakharov:/home/obj/usr/src/sys/GENERIC-NODEBUG  amd64
> > >
> > > dmesg: http://pastebin.com/cYD8cR0b
> > > hw.acpi: http://pastebin.com/Tht9B0FZ
> > > acpidump: http://vzakharov.ru/z2v-HPProBook430G2.asl
> > >
> > >
> > > PS. I'm not subscribed to freebsd-acpi. So keep me in CC, please.
> > >
> >
> > I see lots of ACPI errors also shortly on a Lenovo E540 UEFI notebook
> > running most recent CURRENT ...
> 
> +1, I see the same on Thinkpad T420.
> 
> ___
> freebsd-a...@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-acpi
> To unsubscribe, send any mail to "freebsd-acpi-unsubscr...@freebsd.org"
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"


Re: Log spam: Limiting * response from 1 to 200 packets/sec

2016-12-21 Thread Ben Woods
On Thu., 22 Dec. 2016 at 12:45 am, Gleb Smirnoff 
wrote:

> That was my failure and already fixed.
>
Thanks for the fix!

For those of us playing along at home, I believe the fix can in r310032.










https://svnweb.freebsd.org/base?view=revision&revision=310032




Regards,
Ben
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"