https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=200319
--- Comment #19 from Kristof Provost ---
(In reply to Gyver Def from comment #18)
The problem is being worked on.
In the mean time the following sysctl tweaks should make the problem less
likely to trigger:
net.isr.bindthreads=1
net.isr.m
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=243319
Kyle Evans changed:
What|Removed |Added
CC||c...@freebsd.org,
|
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=243319
--- Comment #2 from Mark Johnston ---
(In reply to Kyle Evans from comment #1)
What happens after the panic? Does the system attempt to dump core? Do you
perhaps have a DDB script that attempts to trigger a netdump?
--
You are receiving
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=243319
--- Comment #3 from Kyle Evans ---
(In reply to Mark Johnston from comment #2)
Yeah, so from the system's viewpoint it looks like an absolutely normal panic
and I'm at ddb prompt and able to dump (and did, because I needed to examine
later
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=243319
--- Comment #4 from Mark Johnston ---
You could try repro'ing the problem with net.debugnet.debug=1 or =2 to verify
that the debugnet code isn't actually running somehow.
--
You are receiving this mail because:
You are on the CC list for
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=200319
--- Comment #20 from Kristof Provost ---
(In reply to Kristof Provost from comment #19)
I may have been conflating two different issues.
To clarify: if the system fully freezes then these sysctls won't help. If the
system keeps running, bu
Karl Denninger wrote:
[dd]
>
> Strongswan works fine with Win10 HOWEVER note that Windows 10 until
> somewhat recently (last summer, I believe) and ALL PREVIOUS VERSIONS
> (e.g. Win7, 8, etc.) had a SEVERE problem with IkeV2 connections, which
Karl,
Thanks a lot for the detailed info. I may ne
On 1/13/2020 10:26, Victor Sudakov wrote:
> Karl Denninger wrote:
>
> [dd]
>
>> Strongswan works fine with Win10 HOWEVER note that Windows 10 until
>> somewhat recently (last summer, I believe) and ALL PREVIOUS VERSIONS
>> (e.g. Win7, 8, etc.) had a SEVERE problem with IkeV2 connections, which
> Ka
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=243319
--- Comment #5 from Kyle Evans ---
(In reply to Mark Johnston from comment #4)
Doing this resulted in no activity from debugnet, at least.
It might be worth noting that it does take a while after the initial panic for
this misbehavior to
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=243319
--- Comment #6 from Conrad Meyer ---
These are different requesters? It would help to spell out which IP(s) are the
panic'd laptop.
07:55:53.025959 ARP, Request who-has 10.6.112.1 tell 10.6.112.16, length 46
07:55:53.025980 ARP, Request w
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=243319
--- Comment #7 from Kyle Evans ---
(In reply to Conrad Meyer from comment #6)
Hmm... yeah, good point- I misread '18' as '16', and those are actually the two
Windows boxen on the local segment; 10.6.112.1 being the gateway for this vlan.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=243319
--- Comment #8 from Kyle Evans ---
I've uploaded a fairly noisy pcap file:
https://people.freebsd.org/~kevans/re0.pcap
The panicked laptop was plugged back in within a minute of starting this dump.
Around 7 minutes in at *:45/*:46 is whe
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=242070
Brendan Shanks changed:
What|Removed |Added
CC||mrpi...@gmail.com
--- Comment #6
13 matches
Mail list logo
