netdev - RE: lan78xx: WARNING: irq 79 handler enabled interrupts

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: <BN6PR1101MB21304C3686D65E78E59110FDE78C0@BN6PR1101MB2130.namprd11.prod.outlook.com>
Date:   Wed, 2 Jan 2019 21:42:25 +0000
From:   <Woojung.Huh@...rochip.com>
To:     <stefan.wahren@...e.com>
CC:     <eric@...olt.net>, <UNGLinuxDriver@...rochip.com>,
        <marc.zyngier@....com>, <netdev@...r.kernel.org>,
        <linux-arm-kernel@...ts.infradead.org>
Subject: RE: lan78xx: WARNING: irq 79 handler enabled interrupts

Hi Stefan,

Thanks for information and creating a ticket.

Did quick check on a PC machine with 4.20 rc. However, not seeing same warning.
Look need time to repro and get details on same build & target you are using.

Regards,
Woojung

> -----Original Message-----
> From: Stefan Wahren <stefan.wahren@...e.com>
> Sent: Tuesday, January 1, 2019 4:32 PM
> To: Woojung Huh - C21699 <Woojung.Huh@...rochip.com>
> Cc: eric@...olt.net; UNGLinuxDriver <UNGLinuxDriver@...rochip.com>; marc.zyngier@....com;
> netdev@...r.kernel.org; linux-arm-kernel@...ts.infradead.org
> Subject: RE: lan78xx: WARNING: irq 79 handler enabled interrupts
> 
> Hi Woojung,
> 
> > Woojung.Huh@...rochip.com hat am 30. Dezember 2018 um 04:25 geschrieben:
> >
> >
> > HI Marc & Stephen,
> >
> > Most of engineers are out until New Year's Day.
> 
> thanks. I didn't expect a reply that fast.
> 
> >
> > LAN78xx driver uses irq_domain for phy interrupt, but smsc95xx uses polling.
> > Need to check flow again, you can try that comment out "lan78xx_setup_irq_domain" to
> > make dev->domain_data.phyirq = 0 which forces PHY polling.
> 
> I tested your suggestion with multi_v7_defconfig (32 bit) and arm64/defconfig.
> The warning disappeared and Ethernet is still working.
> 
> Only the old issue that we can't receive until a first packet has been send out reappear. But this should
> be manageable.
> 
> >
> > Can you share if this is filed on RPI forum?
> 
> I didn't submit this to the raspberrypi.org forum / github. They mostly care about the next LTS release
> 4.19 and not really about arm64.
> 
> But an Arch Linux user (aarch64 using Mainline kernel) already discovered this issue:
> https://archlinuxarm.org/forum/viewtopic.php?f=65&t=13302
> 
> > Also, it would be appreciated if you can create a ticket on Microchip site at
> > https://www.microchip.com/technical-support/hot-topics
> 
> Done
> 
> Best regards
> Stefan
> 
> >
> > Best Regards,
> > Woojung
> >