netdev - Re: Realtek 8139 problem on 486.

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 for Android: free password hash cracker in your pocket

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

Message-ID: <60DF62DA.6030508@gmail.com>
Date:   Fri, 02 Jul 2021 22:02:50 +0300
From:   Nikolai Zhubr <zhubr.2@...il.com>
To:     Arnd Bergmann <arnd@...nel.org>
CC:     "Maciej W. Rozycki" <macro@...am.me.uk>,
        Thomas Gleixner <tglx@...utronix.de>,
        Heiner Kallweit <hkallweit1@...il.com>,
        netdev <netdev@...r.kernel.org>,
        the arch/x86 maintainers <x86@...nel.org>,
        Ingo Molnar <mingo@...hat.com>, Borislav Petkov <bp@...en8.de>,
        "H. Peter Anvin" <hpa@...or.com>
Subject: Re: Realtek 8139 problem on 486.

24.06.2021 11:28, Arnd Bergmann:
> Right, I forgot you saw that one WARN_ON trigger. If you enable KALLSYMS
> and BUGVERBOSE, it should become obvious what that one is about.

Here is new log with a better backtrace:

https://pastebin.com/DP3dSE4w

The respective diff against regular 8139too.c is here:

https://pastebin.com/v8kA7ZmX

(Basically the same as you proposed initially, just slight difference 
might be as a remainder of my various previous testing)


Thank you,

Regards,
Nikolai