[Bug 243531] Unstable ena and nvme on AWS

2020-06-08 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=243531 --- Comment #15 from Tomáš Čiernik --- Hello, sorry for my late anwer. It seems it's different issue. % sysctl dev.ena | grep mbuf_alloc_fail dev.ena.0.queue1.rx_ring.mbuf_alloc_fail: 0 dev.ena.0.queue0.rx_ring.mbuf_alloc_fail: 0 Many t

[Bug 243531] Unstable ena and nvme on AWS

2020-06-05 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=243531 --- Comment #14 from Colin Percival --- (In reply to Tomáš Čiernik from comment #13) Hi Tomáš, That definitely looks like the same issue. Does `sysctl dev.ena | grep mbuf_alloc_fail` show nonzero values? (If no, it's not the same issue;

[Bug 243531] Unstable ena and nvme on AWS

2020-06-05 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=243531 Tomáš Čiernik changed: What|Removed |Added CC||to...@ciernik.sk --- Comment #13 f

[Bug 243531] Unstable ena and nvme on AWS

2020-05-12 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=243531 --- Comment #12 from commit-h...@freebsd.org --- A commit references this bug: Author: mw Date: Tue May 12 18:44:42 UTC 2020 New revision: 360985 URL: https://svnweb.freebsd.org/changeset/base/360985 Log: MFC r360777: Optimize ENA Rx ref

[Bug 243531] Unstable ena and nvme on AWS

2020-05-07 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=243531 --- Comment #11 from commit-h...@freebsd.org --- A commit references this bug: Author: mw Date: Thu May 7 11:28:41 UTC 2020 New revision: 360777 URL: https://svnweb.freebsd.org/changeset/base/360777 Log: Optimize ENA Rx refill for low m

[Bug 243531] Unstable ena and nvme on AWS

2020-04-22 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=243531 --- Comment #10 from Colin Percival --- I believe that this patch should fix the underlying problem, which is in the ENA driver: https://reviews.freebsd.org/D24546 If you're able to build a custom kernel, please test that patch and report

[Bug 243531] Unstable ena and nvme on AWS

2020-02-27 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=243531 --- Comment #9 from Leif Pedersen --- My timestamps are in America/Chicago (-0600 now/-0500 summer) -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-virtuali

[Bug 243531] Unstable ena and nvme on AWS

2020-02-27 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=243531 --- Comment #8 from Leif Pedersen --- (In reply to Colin Percival from comment #6) Sorry, I didn't notice your message sooner. :( The instance id of extra1-dev is i-0ce4598513b3acbb2. I attached the log from a verbose boot. -- You are r

[Bug 243531] Unstable ena and nvme on AWS

2020-02-27 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=243531 --- Comment #7 from Leif Pedersen --- Created attachment 212007 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=212007&action=edit syslog from verbose boot on 2020-02-27 -- You are receiving this mail because: You are the assign

[Bug 243531] Unstable ena and nvme on AWS

2020-02-24 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=243531 --- Comment #6 from Colin Percival --- Another request: Can you provide a verbose boot? We're wondering if there's something funky going on with interrupt routing. -- You are receiving this mail because: You are the assignee for the bug.

[Bug 243531] Unstable ena and nvme on AWS

2020-02-21 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=243531 --- Comment #5 from Colin Percival --- Hi Leif, Can you tell me the instance ID from that one? And is that timestamp in UTC? -- You are receiving this mail because: You are the assignee for the bug. _

[Bug 243531] Unstable ena and nvme on AWS

2020-02-21 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=243531 --- Comment #4 from Leif Pedersen --- Created attachment 211806 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=211806&action=edit syslog from crash on 2020-02-21 -- You are receiving this mail because: You are the assignee for

[Bug 243531] Unstable ena and nvme on AWS

2020-02-21 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=243531 --- Comment #3 from Leif Pedersen --- Created attachment 211805 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=211805&action=edit console screenshot of crash on 2020-02-21 -- You are receiving this mail because: You are the ass

[Bug 243531] Unstable ena and nvme on AWS

2020-02-21 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=243531 --- Comment #2 from Leif Pedersen --- I'm at a bit of a loss to come up with anything particularly helpful. A few thoughts, although mostly naive observations and wild speculation - It kind of seems like when one machine has a problem, sev

[Bug 243531] Unstable ena and nvme on AWS

2020-02-10 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=243531 --- Comment #1 from Colin Percival --- I haven't been able to reproduce this yet... any more tips on how to replicate your environment? -- You are receiving this mail because: You are the assignee for the bug.

[Bug 243531] Unstable ena and nvme on AWS

2020-01-25 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=243531 Mark Linimon changed: What|Removed |Added Assignee|b...@freebsd.org|virtualizat...@freebsd.org -- You