___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
On Tue, 26 May 2020 at 17:01, Matthew Macy wrote:
>
> >
> > I can go setup my second PC this week (I have PTO!) and go see if I
> > have any PCIe igb hardware here. I /think/ I do but it's fibre.
>
> The RSS compile time option used to be disabled in part because of
> this. The drivers had working
Konstantin Belousov wrote:
>On Fri, May 22, 2020 at 11:46:26PM +, Rick Macklem wrote:
>> Konstantin Belousov wrote:
>> >On Wed, May 20, 2020 at 11:58:50PM -0700, Ryan Libby wrote:
>> >> On Wed, May 20, 2020 at 6:04 PM Rick Macklem wrote:
>> >> >
>> >> > Hi,
>> >> >
>> >> > Since I hadn't upgra
>
> I can go setup my second PC this week (I have PTO!) and go see if I
> have any PCIe igb hardware here. I /think/ I do but it's fibre.
The RSS compile time option used to be disabled in part because of
this. The drivers had working RSS that relied on packet receipt before
setting flowid.
-M
___
reply to all this time:
On Tue, 26 May 2020 at 02:03, Hans Petter Selasky wrote:
>
> Hi,
>
> I just found a bug where outgoing TCP connections over igb0 doesn't work
> because likely the software computed hash is wrong, so the incoming
> packets get dropped because they are received on the wrong
On 2020-05-25 16:40, marco wrote:
> On Mon, May 25, 2020 at 08:13:16PM +, you (marco) sent the following to
> [freebsd-current] :
>>
>> I took 3 pictures of the system dropping to the debugger for r360723.
>> 1st 2 pictures are right before the panic and the final the panic screen
>> itself.
>
On 5/26/20 11:55 AM, Konstantin Belousov wrote:
> On Tue, May 26, 2020 at 06:22:13PM +0300, Andriy Gapon wrote:
>> On 25/05/2020 11:37, Andriy Gapon wrote:
>>> Also, there is another issue related to atrtc.
>>> When I have both drivers attached, and also when I have only atrtc attached
>>> (efi.rt.
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
On Tue, May 26, 2020 at 06:22:13PM +0300, Andriy Gapon wrote:
> On 25/05/2020 11:37, Andriy Gapon wrote:
> > Also, there is another issue related to atrtc.
> > When I have both drivers attached, and also when I have only atrtc attached
> > (efi.rt.disabled=1), system clock jumps 10 minutes forward
On 26/05/2020 12:03, Hans Petter Selasky wrote:
> Hi,
>
> I just found a bug where outgoing TCP connections over igb0 doesn't work
> because
> likely the software computed hash is wrong, so the incoming packets get
> dropped
> because they are received on the wrong queue.
>
> It is the manageme
On 25/05/2020 11:37, Andriy Gapon wrote:
> Also, there is another issue related to atrtc.
> When I have both drivers attached, and also when I have only atrtc attached
> (efi.rt.disabled=1), system clock jumps 10 minutes forward after each suspend
> /
> resume cycle (S0 -> S3 -> S0). That does no
On Mon, 2020-05-25 at 11:37 +0300, Andriy Gapon wrote:
> I see that on my laptop both efirtc and atrtc get attached.
> The latter is via an ACPI attachment:
> efirtc0:
> efirtc0: registered as a time-of-day clock, resolution 1.00s
> atrtc0: port 0x70-0x71 on acpi0
> atrtc0: registered as a ti
Hi,
I just found a bug where outgoing TCP connections over igb0 doesn't work
because likely the software computed hash is wrong, so the incoming
packets get dropped because they are received on the wrong queue.
It is the management port, so I'm just using this hack for now:
dev.igb.0.iflib.o
13 matches
Mail list logo
