https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=276294
Eugene Grosbein changed:
What|Removed |Added
See Also||https://bugs.freebsd.org/bu
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=276294
Eugene Grosbein changed:
What|Removed |Added
See Also||https://reviews.freebsd.org
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=276294
Tatsuki Makino changed:
What|Removed |Added
CC||tatsuki_mak...@hotmail.com
--- Co
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=276294
--- Comment #11 from Eugene Grosbein ---
(In reply to O. Hartmann from comment #10)
Please re-read comments above and provide requested debug information.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=276294
--- Comment #10 from O. Hartmann ---
(In reply to Eugene Grosbein from comment #9)
Yes, it is. The above described problem can be easily reproduced on any APU we
run with nanobsd and mpd5 running and configured using PPPoE. A simple "servi
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=276294
--- Comment #9 from Eugene Grosbein ---
Is this problem still relevant?
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=276294
--- Comment #8 from O. Hartmann ---
(In reply to Eugene Grosbein from comment #7)
I'll do so as soon as building a new image for the appliances in question.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=276294
--- Comment #7 from Eugene Grosbein ---
(In reply to O. Hartmann from comment #4)
You have to add "options KDB_TRACE" at very least.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=276294
Eugene Grosbein changed:
What|Removed |Added
Blocks|272319 |
--- Comment #6 from Eugene Gros
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=276294
--- Comment #5 from Gleb Smirnoff ---
On Wed May 8 20:54:10 2024 UTC, ohartm...@walstatt.org wrote:
> PR 272319 claims to have fixed the problem except for kernels with INVARIANTS
> option.
This is very unlikely related to 272319, which
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=276294
--- Comment #4 from O. Hartmann ---
(In reply to Eugene Grosbein from comment #2)
PR 272319 claims to have fixed the problem except for kernels with INVARIANTS
option.
My customized kernel has been stripped off almost every debugging and
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=276294
O. Hartmann changed:
What|Removed |Added
Blocks||272319
Referenced Bugs:
https://bu
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=276294
--- Comment #3 from O. Hartmann ---
As of today, the appliance has
FreeBSD 14.1-STABLE #2 stable/14-n267607-7e10c2d27a53: Sat May 4 08:33:15 CEST
2024 amd64
The router/FW was up a couple of days/weeks for now. We stopped triggering a
res
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=276294
Eugene Grosbein changed:
What|Removed |Added
Status|New |Open
CC|
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=276294
Eugene Grosbein changed:
What|Removed |Added
Keywords||crash, needs-qa
Versi
15 matches
Mail list logo