https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=204453
Mark Linimon changed:
What|Removed |Added
Assignee|freebsd-b...@freebsd.org|freebsd-net@FreeBSD.org
--
You are
On 11/10/15 3:13 PM, Adrian Chadd wrote:
hiya,
there's a PR with a patch:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=204438
https://github.com/sparrc/freebsd/commit/157f90c55d1d54d33f41c6f7517de1a9c5f5e229
Does anyone know why setting the limits isn't as simple as this patch?
Does a
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=204438
Hiren Panchasara changed:
What|Removed |Added
CC||gleb...@freebsd.org,
hiya,
there's a PR with a patch:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=204438
https://github.com/sparrc/freebsd/commit/157f90c55d1d54d33f41c6f7517de1a9c5f5e229
Does anyone know why setting the limits isn't as simple as this patch?
Does anyone mind if I just commit this?
-adrian
_
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=204437
Mark Linimon changed:
What|Removed |Added
Assignee|freebsd-b...@freebsd.org|freebsd-net@FreeBSD.org
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=204438
NGie Cooper changed:
What|Removed |Added
Assignee|freebsd-b...@freebsd.org|freebsd-net@FreeBSD.org
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
Intel are currently finishing up a freebsd version of the firmware
update tool. Expect it in a month or two.
(I am, because I have fortville hardware I can't use atm. :( )
-a
On 10 November 2015 at 09:10, Steven Hartland wrote:
> The driver in head is outputting a warning to /var/log/messages
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.
_
On 2015-11-10, at 18:10, Steven Hartland wrote:
>
> Having spent 30mins searching for the FreeBSD utility to perform said update
> I'm hitting a dead end so looking for advice on where to find this?
No idea. I ended up booting into Linux to flash.
> While searching for this I found that the la
The driver in head is outputting a warning to /var/log/messages:
ixl0: The driver for the device detected an older version of the NVM
image than expected.
Please update the NVM image.
Having spent 30mins searching for the FreeBSD utility to perform said
update I'm hitting a dead end so looking
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=200221
Kubilay Kocak changed:
What|Removed |Added
CC||freebsd-net@FreeBSD.org,
15 matches
Mail list logo
