netdev - Re: No traffic with Marvell switch and latest linux-next

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <f3a6797d-2b0c-384e-47e0-c1f9811294d1@gmail.com>
Date:   Sun, 17 Feb 2019 16:55:38 +0100
From:   Heiner Kallweit <hkallweit1@...il.com>
To:     Andrew Lunn <andrew@...n.ch>
Cc:     Florian Fainelli <f.fainelli@...il.com>,
        Russell King - ARM Linux <linux@...linux.org.uk>,
        "netdev@...r.kernel.org" <netdev@...r.kernel.org>
Subject: Re: No traffic with Marvell switch and latest linux-next

On 17.02.2019 16:51, Andrew Lunn wrote:
>> 36:    2030566   mscm-ir  79 Edge      400d1000.ethernet
>>  38:    1010437  gpio-vf610   2 Level     400d1000.ethernet-1:00
>>  42:          0  mv88e6xxx-g1   3 Edge      mv88e6xxx-g1-atu-prob
>>  44:          0  mv88e6xxx-g1   5 Edge      mv88e6xxx-g1-vtu-prob
>>  46:    1010435  mv88e6xxx-g1   7 Edge      mv88e6xxx-g2
>>  49:          0  mv88e6xxx-g2   1 Edge      mv88e6xxx-1:01
>>  53:          0  mv88e6xxx-g2   5 Edge      mv88e6xxx-1:05
>>  54:          0  mv88e6xxx-g2   6 Edge      mv88e6xxx-1:06
>>  56:     100000  mv88e6xxx-g2   8 Edge      mv88e6xxx-1:08
>>  63:          0  mv88e6xxx-g2  15 Edge      mv88e6xxx-watchdog
> 
> The PHY for Port 8 is not clearing its interrupt. In fact, it is not
> even saying to the kernel it had an interrupt. After 100,000 interrupts
> which nobody claimed, the kernel just disables it. So this looks like
> your fix:
> 
> -       if (!phy_is_started(phydev))
> -               return IRQ_NONE;
> 
> I think this went into net first. So it takes a little while to make
> it into net-next. Maybe you don't have it yet?
> 
I have it. And the root cause seems to be another one as Russell
mentioned he has a fix for the trace.

>      Andrew
> 
Heiner