On 2/28/2022 2:51 PM, Navdeep Parhar wrote:
On 2/28/22 11:48 AM, mike tancsa wrote:
On 2/28/2022 2:43 PM, Navdeep Parhar wrote:
On 2/28/22 11:36 AM, mike tancsa wrote:
Hi Navdeep,
I updated a pair of releng13 boxes today as I saw there are
new drivers/firmware. However, the firmware see
On 2/28/22 11:48 AM, mike tancsa wrote:
On 2/28/2022 2:43 PM, Navdeep Parhar wrote:
On 2/28/22 11:36 AM, mike tancsa wrote:
Hi Navdeep,
I updated a pair of releng13 boxes today as I saw there are new
drivers/firmware. However, the firmware seems to fail on both in
different ways
t5nex
On 2/28/2022 2:43 PM, Navdeep Parhar wrote:
On 2/28/22 11:36 AM, mike tancsa wrote:
Hi Navdeep,
I updated a pair of releng13 boxes today as I saw there are new
drivers/firmware. However, the firmware seems to fail on both in
different ways
t5nex0: mem
0x9130-0x9137,0x9000
On 2/28/22 11:36 AM, mike tancsa wrote:
Hi Navdeep,
I updated a pair of releng13 boxes today as I saw there are new
drivers/firmware. However, the firmware seems to fail on both in
different ways
t5nex0: mem
0x9130-0x9137,0x9000-0x90ff,0x91984000-0x91985fff irq 17
at
Hi Navdeep,
I updated a pair of releng13 boxes today as I saw there are new
drivers/firmware. However, the firmware seems to fail on both in
different ways
t5nex0: mem
0x9130-0x9137,0x9000-0x90ff,0x91984000-0x91985fff irq 17
at device 0.4 on pci2
t5nex0: failed to load
On 2022-Feb-26, at 17:10, Mark Millard wrote:
> On 2022-Jan-15, at 07:55, Mark Johnston wrote:
>
>> On Fri, Jan 14, 2022 at 09:38:56PM -0800, Mark Millard wrote:
>>> Thanks. This will allow me to remove part of my personal additions
>>> in this area --and my having to explain the misnomer wh
