https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=282535
--- Comment #2 from Alexander Ziaee ---
Yes, thought you might find it interesting; sorry for the disruption.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=282535
--- Comment #1 from Lexi Winter ---
Alexander: did you mean to cc me on this? i have never touched this code and
know nothing about it.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=282535
Alexander Ziaee changed:
What|Removed |Added
Assignee|b...@freebsd.org|n...@freebsd.org
--
You are rec
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=278220
Dirk Meyer changed:
What|Removed |Added
Status|New |Closed
Resolution|---
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=255309
Mitchell Horne changed:
What|Removed |Added
CC||mho...@freebsd.org
St
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=255309
--- Comment #4 from commit-h...@freebsd.org ---
A commit in branch main references this bug:
URL:
https://cgit.FreeBSD.org/src/commit/?id=6e5650896fe47398e49e3d81af60cc60dbb09e6e
commit 6e5650896fe47398e49e3d81af60cc60dbb09e6e
Author:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=277125
Jose Luis Duran changed:
What|Removed |Added
CC||jldu...@freebsd.org
--- Comment
To view an individual PR, use:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id).
The following is a listing of current problems submitted by FreeBSD users,
which need special attention. These represent problem reports covering
all versions including experimental development code and ob
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254341
--- Comment #22 from Kevin Bowling ---
(In reply to Kevin Bowling from comment #21)
I think suggestion 1 above also requires 14.2beta1+ as well due to a bug I
found and fixed.
--
You are receiving this mail because:
You are the assignee f
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254341
Kevin Bowling changed:
What|Removed |Added
Status|New |In Progress
--- Comment #21 from K
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254341
--- Comment #20 from Vladislav Shabanov ---
Created attachment 254907
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=254907&action=edit
watchdog dump on 14.1, after network hungs, before ifconfig down + up
--
You are receiving
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254341
--- Comment #19 from Vladislav Shabanov ---
Created attachment 254906
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=254906&action=edit
watchdog dump on 14.1, before network hungs
pfctl -si
netstat -m
sysctl dev.igb.0.reg_dump
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=282434
--- Comment #2 from Lexi Winter ---
Created attachment 254891
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=254891&action=edit
'sysctl debug.witness' output
--
You are receiving this mail because:
You are the assignee for the
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254341
--- Comment #18 from Vladislav Shabanov ---
(In reply to Kevin Bowling from comment #17)
The problem persistis. The server still works, now on FreeBSD 14.1. BIOS
upgrade does not solve the issue. The network hungs every day, from 1 to 10
ti
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254341
--- Comment #17 from Kevin Bowling ---
Were you able to do any of the above? A dump from a recent version where I
have added the nvm prints would be helpful to me.
I would like to make some progress or close this out. I don't doubt you'v
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=282478
Jose Luis Duran changed:
What|Removed |Added
Assignee|n...@freebsd.org |jldu...@freebsd.org
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=282478
Mark Johnston changed:
What|Removed |Added
Status|New |Open
CC|
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=282434
Mark Johnston changed:
What|Removed |Added
CC||ma...@freebsd.org
Stat
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=256393
--- Comment #33 from Eugene Grosbein ---
(In reply to Alexander V. Chernikov from comment #11)
It seems the problem is same as in my old PR:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=223129
The problem was fixed back in 2017 with
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=282478
Mark Linimon changed:
What|Removed |Added
Assignee|b...@freebsd.org|n...@freebsd.org
--
You are receiv
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254514
--- Comment #5 from Mark Johnston ---
I believe the underlying problem was fixed by commit
f1c5a2e3a625053e2b70d5b1777d849a4d9328f2, which is in 14.1. Can anyone confirm
this?
--
You are receiving this mail because:
You are the assignee
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=277849
Franco Fichtner changed:
What|Removed |Added
CC||fra...@opnsense.org
--- Comment
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=277849
--- Comment #5 from Zhenlei Huang ---
(In reply to Martin Matuska from comment #2)
> with unpopulated ifm:
> ifm->ifm_mask = 0
> ifm->ifm_media = 0
> ifm->ifm_cur = 0x0
> ifm->ifm_change = 0x0
> ifm->ifm_status = 0x0
That looks weird.
>Fr
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=282431
Mark Linimon changed:
What|Removed |Added
Assignee|b...@freebsd.org|n...@freebsd.org
--
You are receiv
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=282434
Mark Linimon changed:
What|Removed |Added
Assignee|b...@freebsd.org|n...@freebsd.org
--
You are receiv
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=263982
David T changed:
What|Removed |Added
CC||d...@dev.snart.me
--- Comment #4 from Da
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=282378
Mateusz Guzik changed:
What|Removed |Added
Status|New |In Progress
Assignee|n..
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=282378
--- Comment #11 from Mateusz Guzik ---
Thanks. I'm going to ship you with either a fix or some more debug later today,
hopefully the former :)
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=282378
--- Comment #10 from Lexi Winter ---
Unread portion of the kernel message buffer:
panic: lle 0xf8015f8e8000 not locked @
/data/build/src/freebsd/lf/main/sys/netinet6/nd6.c:2368!
cpuid = 1
time = 1730156941
KDB: stack backtrace:
#0 0xfff
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=280648
--- Comment #27 from Zhenlei Huang ---
(In reply to Egor from comment #0)
> Hello everyone. I met a problem with my Freebsd configuration. I used two
> fibs fib0
> for management and fib1 for traffic routing. When i tried to connect to my
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=173002
Zhenlei Huang changed:
What|Removed |Added
URL||https://reviews.freebsd.org
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=282378
--- Comment #9 from Mateusz Guzik ---
Thanks.
How is the testing going so far?
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=171228
Dan Lukes changed:
What|Removed |Added
Resolution|--- |FIXED
Status|Open
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=281560
Mark Johnston changed:
What|Removed |Added
Resolution|--- |FIXED
Status|Open
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=173002
Zhenlei Huang changed:
What|Removed |Added
CC||z...@freebsd.org
--- Comment #5 fr
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=38554
Alexander Vereeken changed:
What|Removed |Added
Keywords|patch |
Summary|[patch] ch
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=183407
Alexander Vereeken changed:
What|Removed |Added
Keywords|patch |
Summary|[rc.d] [p
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=61744
Alexander Vereeken changed:
What|Removed |Added
CC||Alexander88207@protonmail.c
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=266735
Mark Johnston changed:
What|Removed |Added
Status|New |Closed
Resolution|---
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=278100
Mark Johnston changed:
What|Removed |Added
CC||ma...@freebsd.org
Assign
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=171228
Alexander Vereeken changed:
What|Removed |Added
CC||Alexander88207@protonmail.c
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192558
Alexander Vereeken changed:
What|Removed |Added
Keywords|patch |
CC|
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=281938
Alexander Vereeken changed:
What|Removed |Added
Summary|[PATCH] Make sure max_len |Make sure max_len is not 0
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=173002
Alexander Vereeken changed:
What|Removed |Added
Keywords|patch |
CC|
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=218687
Alexander Vereeken changed:
What|Removed |Added
Summary|[patch] use uninitialized |use uninitialized fields of
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=218687
Mark Johnston changed:
What|Removed |Added
Resolution|--- |Overcome By Events
Sta
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=236219
Mark Johnston changed:
What|Removed |Added
Status|New |Closed
Resolution|---
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230807
Mark Johnston changed:
What|Removed |Added
CC||ma...@freebsd.org
Stat
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230807
--- Comment #30 from commit-h...@freebsd.org ---
A commit in branch stable/13 references this bug:
URL:
https://cgit.FreeBSD.org/src/commit/?id=b1c2fc54f32c2e670bb419230de917901d1dff6b
commit b1c2fc54f32c2e670bb419230de917901d1dff6b
Author
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=282378
--- Comment #8 from Lexi Winter ---
okay, i replaced that patch with your patch and will reboot later tonight.
CPU: Intel(R) Atom(TM) CPU C3758R @ 2.40GHz (2400.22-MHz K8-class CPU)
Origin="GenuineIntel" Id=0x506f1 Family=0x6 Model=0x
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=282378
--- Comment #7 from Mateusz Guzik ---
That patch does NOT fix the problem, whatever it may happen to be.
Instead of that, can you please apply the following:
https://people.freebsd.org/~mjg/nd6_debug.diff
It should still crash, but provid
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=282378
--- Comment #6 from Lexi Winter ---
i've built a new release with https://reviews.freebsd.org/D45913 applied and
will deploy this to test tonight.
this might not be a (recent) regression; i think the issue here might be that
we recently ma
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=282378
--- Comment #5 from Lexi Winter ---
"Routes with IPv6 Address as Next Hop for IPv4 Destination Causes Kernel Panic"
i do have one of these:
Internet:
DestinationGatewayFlags Netif Expire
10.254.3.1 fe80
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=278100
Osama Abboud changed:
What|Removed |Added
CC||osama...@amazon.com
--- Comment #3
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=282378
Kevin Bowling changed:
What|Removed |Added
CC||kbowl...@freebsd.org,
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=282378
Mark Linimon changed:
What|Removed |Added
Keywords||crash, regression
Assigne
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=282374
Mark Linimon changed:
What|Removed |Added
Keywords||crash
Assignee|b...@freeb
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=282374
Navdeep Parhar changed:
What|Removed |Added
Assignee|n...@freebsd.org |n...@freebsd.org
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=241106
Mark Linimon changed:
What|Removed |Added
Keywords|needs-patch |
--
You are receiving this mail be
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=282373
Mark Linimon changed:
What|Removed |Added
Resolution|--- |DUPLICATE
Status|New
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=282373
Mark Linimon changed:
What|Removed |Added
Assignee|b...@freebsd.org|n...@freebsd.org
Keywords
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=166724
--- Comment #122 from Jan Przybylak ---
I was using the patched driver for a several of years without issue, but it
stopped working earlier this year due to a different bug. I switched back to
the regular driver and it was fine until a few
To view an individual PR, use:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id).
The following is a listing of current problems submitted by FreeBSD users,
which need special attention. These represent problem reports covering
all versions including experimental development code and ob
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=261129
Patrick M. Hausen changed:
What|Removed |Added
CC||p...@hausen.com
--- Comment #2
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=262024
Kevin Bowling changed:
What|Removed |Added
Status|Open|In Progress
--- Comment #6 from Ke
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=261129
--- Comment #19 from Tatsuki Makino ---
If something like the one shown below was about to be built, /etc/rc.conf
needed to define a value like:
ipv6_cpe_wanif="em0"
Also, it is mandatory to send RA from the bridge interface.
If it is sent
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=271205
Kevin Bowling changed:
What|Removed |Added
Status|New |Open
CC|
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=268092
--- Comment #1 from commit-h...@freebsd.org ---
A commit in branch main references this bug:
URL:
https://cgit.FreeBSD.org/src/commit/?id=cdbe3de5383706da0f6d3c29f1ec2dcfed366bf1
commit cdbe3de5383706da0f6d3c29f1ec2dcfed366bf1
Author:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=268092
Kevin Bowling changed:
What|Removed |Added
Status|New |In Progress
CC|
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=277038
Mark Johnston changed:
What|Removed |Added
Status|New |Open
CC|
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=280386
Andrew Gallatin changed:
What|Removed |Added
CC||galla...@freebsd.org
--- Comment
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=280386
Cheng Cui changed:
What|Removed |Added
CC||c...@freebsd.org
--- Comment #25 from
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=280386
--- Comment #24 from Kevin Bowling ---
(In reply to pascal.guitierrez from comment #23)
Thanks for reporting back. That is very interesting.
There are two possibilities that come to mind 1) the RACK stack is correctly
identifying the loss
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=280386
--- Comment #23 from pascal.guitier...@gmail.com ---
(In reply to Kevin Bowling from comment #21)
(In reply to Kevin Bowling from comment #22)
Interesting, thanks for that.
I tried changing dev.igb.0.iflib.override_ntxqs=4096 but to no eff
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=280386
--- Comment #22 from Kevin Bowling ---
(In reply to Kevin Bowling from comment #21)
Thinking back a bit harder one thing that might help workaround this is to
increase the number of transmit descriptors.. try something like this in
/boot/lo
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=280386
--- Comment #21 from Kevin Bowling ---
(In reply to pascal.guitierrez from comment #20)
> Do you know if this is expected behaviour or is it a problem?
Caveat it has been a long time since I have been line-rating large numbers of
FreeBSD sy
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=280386
--- Comment #20 from pascal.guitier...@gmail.com ---
(In reply to Kevin Bowling from comment #19)
Thanks Kevin, yes you are right, repeating the test gets to a state where
interrupts are processed on a single core and packet drops occur:
To view an individual PR, use:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id).
The following is a listing of current problems submitted by FreeBSD users,
which need special attention. These represent problem reports covering
all versions including experimental development code and ob
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=279850
--- Comment #8 from Kyle Evans ---
(In reply to Zhenlei Huang from comment #7)
We have a patch, but pending a better patch. See
https://reviews.freebsd.org/D46670 and commentary
--
You are receiving this mail because:
You are on the CC l
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=279850
--- Comment #7 from Zhenlei Huang ---
(In reply to Lexi Winter from comment #5)
Hi Lexi, this should be easy to spot which line of source code is to be blamed
if you have kernel debug options enabled. Or you can provide a simple / minimum
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=279653
--- Comment #17 from tom+fbsdbugzi...@nuegia.net ---
What about upstreaming PFSense's workaround until a proper solution can be
found?
https://github.com/pfsense/FreeBSD-src/commit/9834d8bb0d3344cd82552c3cd16e5b2d84543d8f
--
You are receiv
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=282168
Mark Johnston changed:
What|Removed |Added
Assignee|n...@freebsd.org |ma...@freebsd.org
Sta
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=282168
--- Comment #11 from commit-h...@freebsd.org ---
A commit in branch main references this bug:
URL:
https://cgit.FreeBSD.org/src/commit/?id=f4e35c044c8988b7452cefbdcc417f5fd723e021
commit f4e35c044c8988b7452cefbdcc417f5fd723e021
Author:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=282168
Mark Johnston changed:
What|Removed |Added
CC||z...@freebsd.org
--- Comment #10 f
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=255678
Mark Linimon changed:
What|Removed |Added
Resolution|--- |FIXED
Status|In Progres
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=282168
--- Comment #9 from Mark Johnston ---
(In reply to Lexi Winter from comment #8)
Oops. Fixed by the latest revision.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=271270
Mark Johnston changed:
What|Removed |Added
Status|Open|Closed
Resolution|---
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=282168
--- Comment #8 from Lexi Winter ---
i can't build world with the patch from D47174 on top of
fa573868f187956b384722a90392866769f4965a.
--- subr_bus.o ---
/data/build/src/freebsd/lf/main/sys/kern/subr_bus.c:2577:26: error: incomplete
defini
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=271270
--- Comment #5 from Alan Somers ---
That said, I don't currently have any systems available to test with.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=271270
--- Comment #4 from Alan Somers ---
(In reply to Mark Johnston from comment #3)
Oh you're right. I should really read my own posts more carefully.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=271270
--- Comment #3 from Mark Johnston ---
(In reply to Alan Somers from comment #2)
Are you sure it was observed in 14.0-RELEASE? The first comment says
14.0-CURRENT. This bug report predates 14.0-RELEASE by about 6 months, and it
predates th
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=271270
--- Comment #2 from Alan Somers ---
(In reply to Mark Johnston from comment #1)
I can't be, because that commit was already present in 14.0-RELEASE, where the
bug was originally observed.
--
You are receiving this mail because:
You are th
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=282168
--- Comment #7 from Lexi Winter ---
thanks, i'm in the process of doing a src+ports build now but once that's done
i'll test this patch and see if it fixes the panic for me.
--
You are receiving this mail because:
You are the assignee for
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=271270
Mark Johnston changed:
What|Removed |Added
CC||e...@freebsd.org,
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=282168
--- Comment #6 from Mark Johnston ---
This is due to a VNET bug. When a network driver attaches, it needs to have
the current VNET set, e.g., because if_attach_internal()->if_addgroup()
accesses the VNET-global variable V_ifg_head. Normal
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=282168
Mark Linimon changed:
What|Removed |Added
Assignee|b...@freebsd.org|n...@freebsd.org
Keywords
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=282140
Kevin Bowling changed:
What|Removed |Added
CC||kbowl...@freebsd.org
--- Comment #
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=282140
Mark Linimon changed:
What|Removed |Added
Assignee|b...@freebsd.org|n...@freebsd.org
Keywords
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=278100
Zhenlei Huang changed:
What|Removed |Added
CC||z...@freebsd.org
--- Comment #2 fr
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=282095
--- Comment #6 from Scott Aitken ---
So the MTU was already set in CIMC to 9K. I installed Fedora and the Linux
driver must read the value since it picked up 9K:
enp19s0: flags=4163 mtu 9000
ether 70:70:8b:77:7e:76 txqueuelen 100
1 - 100 of 3043 matches
Mail list logo