On Fri, Jun 2, 2017 at 3:31 AM, Daniel Kim wrote:
> On Fri, May 12, 2017 at 6:12 PM, Daniel Kim wrote:
>> I believe I do have IOMMU enabled. At least the dmesg output seems to
>> imply that I do:
>> [1.141948] iommu: Adding device :00:02.0 to group 0
>> [1.142033] iommu: Adding device
On Fri, May 12, 2017 at 6:12 PM, Daniel Kim wrote:
> I believe I do have IOMMU enabled. At least the dmesg output seems to
> imply that I do:
> [1.141948] iommu: Adding device :00:02.0 to group 0
> [1.142033] iommu: Adding device :00:10.0 to group 1
> [1.142074] iommu: Adding d
I believe I do have IOMMU enabled. At least the dmesg output seems to
imply that I do:
[1.141948] iommu: Adding device :00:02.0 to group 0
[1.142033] iommu: Adding device :00:10.0 to group 1
[1.142074] iommu: Adding device :00:10.1 to group 1
[1.142119] iommu: Adding dev
On Fri, May 12, 2017 at 12:10 PM, Daniel Kim wrote:
> [ 4898.361530] tg3 :04:00.0 enp4s0: 0: Host status block
> [0001:0021:(:0486:):(:002c)]
> [ 4898.361535] tg3 :04:00.0 enp4s0: 0: NAPI info
> [0021:0021:(0135:002c:01ff)::(0568:::)]
As you ca
I disabled TSO after a reboot and the TX timeout still occurred. I
have the clipped dmesg log with the first timeout below. I can post
the entire dmesg log if you need it.
[ 4895.554334] [ cut here ]
[ 4895.554395] WARNING: CPU: 1 PID: 0 at
/home/kernel/COD/linux/net/sched
On Fri, May 12, 2017 at 9:39 AM, Siva Reddy Kallam
wrote:
> On Thu, May 11, 2017 at 8:55 PM, Daniel Kim wrote:
>> Summary:
>> Broadcom BCM5762 Ethernet tg3 times out with stack trace
>>
>> Description:
>> The ethernet device will disconnect with dmesg reporting a stack trace
>> and a time out (vi
On Thu, May 11, 2017 at 8:55 PM, Daniel Kim wrote:
> Summary:
> Broadcom BCM5762 Ethernet tg3 times out with stack trace
>
> Description:
> The ethernet device will disconnect with dmesg reporting a stack trace
> and a time out (visible in DMesg Output below). The ethernet device
> will periodical
Summary:
Broadcom BCM5762 Ethernet tg3 times out with stack trace
Description:
The ethernet device will disconnect with dmesg reporting a stack trace
and a time out (visible in DMesg Output below). The ethernet device
will periodically reconnect and disconnect and the driver will output
a lot of h