https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=249500
Bug ID: 249500
Summary: Pager change (r365488) makes vboxdrv panic
Product: Base System
Version: 12.1-STABLE
Hardware: Any
OS: Any
Status: New
Sever
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=249500
--- Comment #1 from Kubilay Kocak ---
(In reply to Adriaan de Groot from comment #0)
Any reason we cant re-classify bug 249326 ?
--
You are receiving this mail because:
You are the assignee for the bug.
__
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=249500
--- Comment #2 from Adriaan de Groot ---
(In reply to Kubilay Kocak from comment #1)
No, there isn't. I'm not used to kernel-crash reporting though, and am not sure
what to do with a "here is a 100% reproducible, user-facing, kernel panic
Invoice prompt statement #223848
Sincerely,
Kinder Murphy
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
Repayment expected #94963
Sincerely,
Somerville Jones
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=246886
Alan Somers changed:
What|Removed |Added
CC||c...@freebsd.org,
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=228019
Poul-Henning Kamp changed:
What|Removed |Added
Resolution|--- |FIXED
Status|New
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=245908
Poul-Henning Kamp changed:
What|Removed |Added
Resolution|--- |FIXED
Status|New
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=246886
--- Comment #45 from Gleb Smirnoff ---
I had faced this problem with 12.1-RELEASE and NFS. I contacted rmacklem@ but
he wasn't able to provide help.
I am absolutely sure this isn't a general sendfile problem, but specific to
NFS. It is pos
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=246886
--- Comment #46 from Alan Somers ---
(In reply to Gleb Smirnoff from comment #45)
Based on your understanding of the problem, could you suggest a better way to
reproduce it? The reason there's been no progress so far is because nobody has
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=246886
--- Comment #47 from Gleb Smirnoff ---
No idea, sorry. I faced it on a production server that serves mostly from UFS,
but there are a few NFS mounts also available via HTTP, with small traffic. The
problem happens once in a few months on th
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=246886
--- Comment #48 from Gleb Smirnoff ---
One more thought. The problem could live outside of NFS or FUSE but in general
VM page code and is exposed only by those filesystems that run sendfile
synchronously (UFS doesn't). However, ZFS also run
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=246886
--- Comment #49 from Alan Somers ---
(In reply to Gleb Smirnoff from comment #48)
But ZFS also doesn't use the page cache. Maybe the problem is specific to file
systems that use the page cache and also run sendfile synchronously?
Do you u
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=209842
--- Comment #1 from commit-h...@freebsd.org ---
A commit references this bug:
Author: phk
Date: Mon Sep 21 16:43:39 UTC 2020
New revision: 365952
URL: https://svnweb.freebsd.org/changeset/base/365952
Log:
Pull in fix from upstream NetBSD
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=246886
--- Comment #50 from Gleb Smirnoff ---
There is number of torture tests for sendfile in pho@ suite. Other way to test
is just wrk against nginx.
--
You are receiving this mail because:
You are the assignee for the bug.
___
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=209842
Poul-Henning Kamp changed:
What|Removed |Added
Status|New |Closed
Resolution|---
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=246886
--- Comment #51 from jsml4thwwbid6...@protonmail.com ---
(In reply to Alan Somers from comment #41)
Sendfile seems to work fine, but using AIO/Nginx + MooseFS/FuseFS causes Nginx
to hang.
Error message: kernel: pid 60903 (nginx) is attemp
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=246886
--- Comment #52 from Alan Somers ---
(In reply to jSML4ThWwBID69YC from comment #51)
Those are definitely unrelated. Open separate PRs for them if you want help.
--
You are receiving this mail because:
You are the assignee for the bug.
_
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=246886
--- Comment #53 from jsml4thwwbid6...@protonmail.com ---
(In reply to Alan Somers from comment #52)
Will do. Thanks.
--
You are receiving this mail because:
You are the assignee for the bug.
___
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=246886
--- Comment #54 from Gleb Smirnoff ---
Then that's a crazy mix of subsystems involved!
Here goes description of how nginx combines aio and sendfile. When sendfile(2)
returns EBUSY, nginx would do aio_read(2) of 1 byte out of the file, and
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=246886
--- Comment #55 from Alan Somers ---
(In reply to Gleb Smirnoff from comment #54)
It's not likely that aio_read makes a difference, since he is seeing the
warning about "use unsafe AIO requests". That warning means that aio_read
would've r
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=246886
--- Comment #56 from Gleb Smirnoff ---
If aio is disabled in nginx, it would not set SF_NODISKIO and thus sendfile
would wait on busy pages.
--
You are receiving this mail because:
You are the assignee for the bug.
___
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=249461
Ed Maste changed:
What|Removed |Added
CC||ema...@freebsd.org
--- Comment #1 from
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=246886
--- Comment #57 from jsml4thwwbid6...@protonmail.com ---
(In reply to Alan Somers from comment #55)
I've tested three options in the nginx.conf.
sendfile on;
This works as expected.
aio on;
This causes content not to load. Nginx keeps
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=246886
--- Comment #58 from Alan Somers ---
(In reply to jSML4ThWwBID69YC from comment #57)
Keep using this bug to discuss NGinx hangs. Open separate bugs for anything
else. Can you easily reproduce the hang with MooseFS? If so, please describe
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=249461
--- Comment #2 from Moritz Schmitt ---
Yes, this is the case. In fact thj ran into this problem during yesterday's bug
squash. He suggested I send the above patch in for review, which I did:
https://reviews.freebsd.org/D26483
By the w
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=246886
--- Comment #59 from Hiroshi Nishida ---
Let me also try with vfs.aio.enable_unsafe=1
I'm doing make world stuff but it's gonna take over an hour because of a slow
hardware (Core i3-8109U).
--
You are receiving this mail because:
You are
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=246886
--- Comment #60 from Hiroshi Nishida ---
Nginx still stalls with vfs.aio.enable_unsafe=1.
--
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org m
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=229745
Nicolas Richeton changed:
What|Removed |Added
CC||nicolas.riche...@gmail.com
---
30 matches
Mail list logo
