https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=202680
Kevin Bowling changed:
What|Removed |Added
Resolution|--- |Not Enough Information
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=202680
Eitan Adler changed:
What|Removed |Added
Status|In Progress |Open
--- Comment #29 from Eitan Adle
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=202680
--- Comment #28 from Dmitry Afanasiev ---
Bug still exists on stable/10 r309900 - 3 times got ssh disconnections, and got
2 errors for dumb TCP data transfer per ~3Tb of transmitted data.
To check on current I should switch some services f
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=202680
--- Comment #27 from Kevin Bowling ---
It's possible things were fixed in past versions, but r311849 in -CURRENT has a
large cleanup and optimization of the FreeBSD part of the driver.
--
You are receiving this mail because:
You are the a
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=202680
--- Comment #26 from Dmitry Afanasiev ---
(In reply to Kevin Bowling from comment #25)
I started to recheck this problem on stable/10 r306961, and currently have no
problems.
I need more time to more tests, but may be problem is already sol
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=202680
Kevin Bowling changed:
What|Removed |Added
CC||kbowl...@freebsd.org
--- Comment #
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=202680
--- Comment #24 from Yaniv Kunda ---
(In reply to Dmitry Afanasiev from comment #23)
I don't even have PF loaded... :-(
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=202680
--- Comment #23 from Dmitry Afanasiev ---
(In reply to Yaniv Kunda from comment #22)
Yaniv, is PF(4) used on your system with em interfaces?
I tested another Sun X4200 with em(4) interfaces and I have *NO* problem with
data corruption!
On
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=202680
--- Comment #22 from Yaniv Kunda ---
(In reply to Sean Bruno from comment #21)
I've set the value to -1 (in loader.conf), rebooted, and verified the new value
using sysctl.
In contrast to Dmitry, the problem happens for me even right after
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=202680
--- Comment #21 from Sean Bruno ---
Can you folks try setting the processing limits to -1? I'm curious if what
you're seeing is a symptom of conflicting processing during interrupt context
and deferred handling to the taskqueue threads.
c
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=202680
--- Comment #20 from Yaniv Kunda ---
(In reply to Yaniv Kunda from comment #19)
Also tried after running ifconfig em0 -tso (verified that it removed TSO4 from
em0's options) but with the same result - a big file copy resulted in a quiet
er
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=202680
--- Comment #19 from Yaniv Kunda ---
(In reply to Sean Bruno from comment #16)
I'm using commodity desktop PC hardware, installed with NAS4Free on a USB
stick.
Attached outputs of pciconf -lv and dmesg -a
I'd like to help find the root cau
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=202680
--- Comment #17 from Yaniv Kunda ---
Created attachment 162976
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=162976&action=edit
output of pciconf -lv
--
You are receiving this mail because:
You are the assignee for the bug.
__
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=202680
--- Comment #18 from Yaniv Kunda ---
Created attachment 162977
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=162977&action=edit
output of dmesg -a
--
You are receiving this mail because:
You are the assignee for the bug.
_
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=202680
--- Comment #16 from Sean Bruno ---
(In reply to Yaniv Kunda from comment #15)
What type of hardware are you using? Can you dump a full pciconf -lv and dmesg
into this ticket?
--
You are receiving this mail because:
You are the assignee
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=202680
Yaniv Kunda changed:
What|Removed |Added
CC||ya...@kundas.net
--- Comment #15 fro
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=202680
--- Comment #14 from Dmitry Afanasiev ---
I tried to use freebsd-current from nightly snapshot:
FreeBSD sunrise0 11.0-CURRENT FreeBSD 11.0-CURRENT #0 r289044: Thu Oct 8
21:21:40 UTC 2015 r...@releng2.nyi.freebsd.org:/usr/obj/usr/src/sy
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=202680
--- Comment #13 from Dmitry Afanasiev ---
(In reply to Dmitry Afanasiev from comment #12)
sys/dev/e1000 tree from head is not compatible with stable/10 :(
--
You are receiving this mail because:
You are the assignee for the bug.
_
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=202680
--- Comment #12 from Dmitry Afanasiev ---
(In reply to Sean Bruno from comment #11)
sys/dev/e1000 in head have many differences from stable/10.
For example different lem's driver version:
< char lem_driver_version[] = "1.0.6";
---
> char le
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=202680
--- Comment #11 from Sean Bruno ---
(In reply to Dmitry Afanasiev from comment #10)
Can you see if this change in head helps with your issue.
https://svnweb.freebsd.org/base?view=revision&revision=287330
--
You are receiving this mail be
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=202680
--- Comment #10 from Dmitry Afanasiev ---
Also I installed into buggy system with fbsd10.2 old Sun's gigabit ethernet
adapter with cas(4) driver and reconfigured lagg to use only this adapter.
I transferred huge files several times with sys
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=202680
--- Comment #9 from Sean Bruno ---
(In reply to Sean Bruno from comment #8)
wait ... never mind. This is a lem(4) device not a em(4) device so those
patches are not applicable. I'll think more.
--
You are receiving this mail because:
Yo
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=202680
--- Comment #8 from Sean Bruno ---
Can you try to apply three changesets from head and see if the condition still
exists?
https://svnweb.freebsd.org/base?view=revision&revision=286831
https://svnweb.freebsd.org/base?view=revision&revision=
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=202680
--- Comment #7 from Dmitry Afanasiev ---
(In reply to Sean Bruno from comment #4)
"pciconf -lvbc" output and dmesg.boot from "boot -v" attached.
I'm not sure that the problem is similar to PR196980, because I have no
"Allocation of PCI res
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=202680
--- Comment #6 from Dmitry Afanasiev ---
Created attachment 160605
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=160605&action=edit
boot -v output
--
You are receiving this mail because:
You are the assignee for the bug.
_
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=202680
--- Comment #5 from Dmitry Afanasiev ---
Created attachment 160604
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=160604&action=edit
pciconf -lvbc output
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=202680
Mark Linimon changed:
What|Removed |Added
Assignee|freebsd-b...@freebsd.org|freebsd-net@FreeBSD.org
--
You are
27 matches
Mail list logo
