Hi all
On a recount 11-STABLE I see that the interaction with netisr and rss has
changed. Forgive me if this is clumsy but I don’t quite get what changes were.
On 10-Stable when I have a solarflare or intel Ixgbe card I would get a kernel
thread per rss queue per card and a netirs queue:bucket
Vincent
I used the scfb driver in openbsd land for a work project . Currently I am
using 11-STABLE with the Radeon driver but at one point I had a different card
under 11.0 that didn’t work unless I used the scfb driver .
---
Mark Saad | nones...@longcount.org
> On Jun 21, 2018, at 11:41
Chris H wrote on 2018/06/22 23:46:
On Fri, 22 Jun 2018 23:13:17 +0200 "Miroslav Lachman" <000.f...@quip.cz>
said
I don't know if it is better to discuss it in jail@ or stable@ list so
a do cross-post.
FreeBSD has many jail aware utilities but they are inconsistent in
taking JID as
On Fri, 22 Jun 2018 23:13:17 +0200 "Miroslav Lachman" <000.f...@quip.cz> said
I don't know if it is better to discuss it in jail@ or stable@ list so a
do cross-post.
FreeBSD has many jail aware utilities but they are inconsistent in
taking JID as parameter.
For example "sockstat" takes -j
I don't know if it is better to discuss it in jail@ or stable@ list so a
do cross-post.
FreeBSD has many jail aware utilities but they are inconsistent in
taking JID as parameter.
For example "sockstat" takes -j JID "Show only sockets belonging to the
specified jail ID" and it means numeric
Hi Michael, Marek,
2018-06-22 22:48 GMT+02:00 Marek Zarychta :
> Patch compiles fine and I can confirm, that it resolves the issue.
Thanks for testing to both of you. Really appreciated.
I've just committed this patch as r335565. As it is a bit more
intrusive than the previous patch I wrote,
Chris H wrote:
[stuff snipped]
>>
>> Thank you for information. I added above lines to /boot/loader.conf
>> and rebooted system. Then all boot messages are displayed and console
>> works fine!
>
>WooHoo! :-)
>
>I could make further observations based on *why* that worked. But several
>are likely,
On Fri, Jun 22, 2018 at 09:11:06PM +0200, Ed Schouten wrote:
> Hi Marek,
>
> [ +glebius ]
>
> Thanks for reporting this!
>
> 2018-06-22 18:54 GMT+02:00 Michael Grimm :
> >> Failed to parse TIMESTAMP from x.x.x.x: 12403: Jun 22 17:31:38 CEST:
> >> %LINEPROTO-5-UPDOWN: Line protocol on Interface
On 22. Jun 2018, at 22:28, Ed Schouten wrote:
> 2018-06-22 22:06 GMT+02:00 Michael Grimm :
>> After applying your patch:
>>Jun 22 21:22:01 HOSTNAME [31033]: NOTICE [JAILNAME]
>> Unban x.x.x.x
>>
>> Watch: 'fail2ban.actions' -the service- is missing.
>
> That's likely due to the fact
Hi Michael,
2018-06-22 22:06 GMT+02:00 Michael Grimm :
> After applying your patch:
> Jun 22 21:22:01 HOSTNAME [31033]: NOTICE [JAILNAME]
> Unban x.x.x.x
>
> Watch: 'fail2ban.actions' -the service- is missing.
That's likely due to the fact that it now interprets the first word in
the
Hi Ed,
On Fri, Jun 22, 2018 at 09:11:06PM +0200, Ed Schouten wrote:
E> > Ah, yes! Haven't thought about running syslogd in debugging mode:
E> >
E> > Failed to parse TIMESTAMP from x.x.x.x: fail2ban.filter [79598]:
INFO […]
E>
E> This is interesting. As fail2ban uses Python's logging
On 22. Jun 2018, at 21:26, Michael Grimm wrote:
> On 22. Jun 2018, at 21:11, Ed Schouten wrote:
>> Michael, Marek, could you please give this patch a try? Thanks!
>
> Recompiled world (FreeBSD 11.2-STABLE r335532), substituted syslogd with the
> re-compiled one, and:
>
> Thank you! Your
On 22. Jun 2018, at 21:11, Ed Schouten wrote:
> Gleb, what are your thoughts on the attached patch? It alters syslogd
> to let the 'legacy' RFC 3164 parser also accept messages without a
> timestamp. The time on the syslogd server will be used instead.
>
> Michael, Marek, could you please give
Hi Marek,
[ +glebius ]
Thanks for reporting this!
2018-06-22 18:54 GMT+02:00 Michael Grimm :
>> Failed to parse TIMESTAMP from x.x.x.x: 12403: Jun 22 17:31:38 CEST:
>> %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/17,
>> changed state to down
>
> Ah, yes! Haven't thought about
On Fri, Jun 22, 2018 at 08:13:59PM +0200, Kurt Jaeger wrote:
> > I have rolled back to r334835. The issue has gone. Should a PR be
> > created about this regression ?
>
> Yes, please.
>
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=229236
--
Marek Zarychta
signature.asc
Description: PGP
I submitted this problem as following bug report.
Bug 229235 - vt(4) of 11.2-RELEASE is broken with hardware dependent problem.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=229235
Just FYI.
---
Yasuhiro KIMURA
___
freebsd-stable@freebsd.org
Hi!
> >> Could you please give any advice or workaround for this issue?
> > I switched to a workaround for the time being which you might use as well
> > in a similar way:
> >
> > #) configure fail2ban to use /var/log/faillog
> > #) run something like that in the background:
> >
> > nohup
W dniu 2018.06.22 o 19:14, Michael Grimm pisze:
> On 22. Jun 2018, at 17:59, Marek Zarychta
> wrote:
>
>> Could you please give any advice or workaround for this issue?
> I switched to a workaround for the time being which you might use as well in
> a similar way:
>
> #) configure fail2ban to
From: "Chris H"
Subject: Re: Console is broken after updating to 11.2-RELEASE
Date: Fri, 22 Jun 2018 06:13:39 -0700
> Try adding the following to your loader.conf(5) file
> (/boot/loader.conf):
>
> # Load SysCons driver
> kern.vty=sc
> # noisy boot
> boot_verbose="YES"
>
> Hope this helps!
On 22. Jun 2018, at 17:59, Marek Zarychta wrote:
> Could you please give any advice or workaround for this issue?
I switched to a workaround for the time being which you might use as well in a
similar way:
#) configure fail2ban to use /var/log/faillog
#) run something like that in the
Marek Zarychta wrote:
> On Fri, Jun 22, 2018 at 03:12:05PM +0200, Michael Grimm wrote:
>> Hi,
>>
>> this is 11.2-STABLE (r335532), and I am referring to the recent MFC of
>> syslogd modifications [1].
>>
>> Because I cannot judge whether fail2ban lacks support for the renewed
>> syslogd or
On Fri, Jun 22, 2018 at 03:12:05PM +0200, Michael Grimm wrote:
> Hi,
>
> this is 11.2-STABLE (r335532), and I am referring to the recent MFC of
> syslogd modifications [1].
>
> Because I cannot judge whether fail2ban lacks support for the renewed syslogd
> or syslogd has an issue in receiving
On Wed, Jun 20, 2018 at 07:37:20PM +0200, Miroslav Lachman wrote:
> > %busy comes from the devstat layer. It's defined as the percent of the
> > time over the polling interval in which at least one transaction was
> > awaiting completion by the lower layers. It's an imperfect measure of
> >
On Fri, 22 Jun 2018 20:42:18 +0900 (JST) "Yasuhiro KIMURA"
said
From: Warner Losh
Subject: Re: Console is broken after updating to 11.2-RELEASE
Date: Fri, 22 Jun 2018 05:03:43 -0600
> UEFI or legacy boot? Is a BMC involved?
Legacy boot. And BMC is not involved.
Try adding the following to
Hi,
this is 11.2-STABLE (r335532), and I am referring to the recent MFC of syslogd
modifications [1].
Because I cannot judge whether fail2ban lacks support for the renewed syslogd
or syslogd has an issue in receiving fail2ban messages I do crosspost this mail
to ports and stable.
I do have
From: Warner Losh
Subject: Re: Console is broken after updating to 11.2-RELEASE
Date: Fri, 22 Jun 2018 05:03:43 -0600
> UEFI or legacy boot? Is a BMC involved?
Legacy boot. And BMC is not involved.
---
Yasuhiro KIMURA
___
freebsd-stable@freebsd.org
From: tech-lists
Subject: Re: Console is broken after updating to 11.2-RELEASE
Date: Fri, 22 Jun 2018 11:44:29 +0100
> I've seen this effect elsewhere. Not exactly the same, but it's been
> happening with me on some systems since 11.1. The context I see it is
> when spinning up a bhyve instance
UEFI or legacy boot? Is a BMC involved?
Warner
On Fri, Jun 22, 2018, 2:09 AM Yasuhiro KIMURA wrote:
> Hello.
>
> With the commit of r335510 releng/11.2 switched to -RELEASE. So I
> updated one of my home server from 11.1-RELEASE-p11 to 11.2-RELEASE.
>
> But when I rebooted I found OS boot
Hi,
On 22/06/2018 09:07, Yasuhiro KIMURA wrote:
1. BIOS message are displayed.
2. Boot menu of FreeBSD is displayed.
3. Kernel boot starts but after 'Booting...' no following messages
are displayed.
4. After OS has booted console stays unusable.
I've seen this effect elsewhere. Not
From: Yasuhiro KIMURA
Subject: Console is broken after updating to 11.2-RELEASE
Date: Fri, 22 Jun 2018 17:07:20 +0900 (JST)
> With the commit of r335510 releng/11.2 switched to -RELEASE. So I
> updated one of my home server from 11.1-RELEASE-p11 to 11.2-RELEASE.
>
> But when I rebooted I found
From: "Andrey V. Elsukov"
Subject: Re: Console is broken after updating to 11.2-RELEASE,Re: Console is
broken after updating to 11.2-RELEASE
Date: Fri, 22 Jun 2018 11:47:24 +0300
> Do you have some tweaks for serial console in your loader.conf?
No. I don't use serial console at all. Folloging
On 22.06.2018 11:07, Yasuhiro KIMURA wrote:
> Hello.
>
> With the commit of r335510 releng/11.2 switched to -RELEASE. So I
> updated one of my home server from 11.1-RELEASE-p11 to 11.2-RELEASE.
>
> But when I rebooted I found OS boot messages are not displayed on
> console while OS itself has
Hello.
With the commit of r335510 releng/11.2 switched to -RELEASE. So I
updated one of my home server from 11.1-RELEASE-p11 to 11.2-RELEASE.
But when I rebooted I found OS boot messages are not displayed on
console while OS itself has booted successfully. To be exact,
1. BIOS message are
33 matches
Mail list logo
