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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <alpine.DEB.2.21.2106242013340.37803@angie.orcam.me.uk>
Date:   Thu, 24 Jun 2021 20:25:40 +0200 (CEST)
From:   "Maciej W. Rozycki" <macro@...am.me.uk>
To:     Nikolai Zhubr <zhubr.2@...il.com>
cc:     Arnd Bergmann <arnd@...nel.org>,
        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.

Hi Nikolai,

> Meanwhile I've captured a similar log from another (and actually this one is
> my main concern because it can not be replaced easily):
> 
> https://pastebin.com/NVfRcMww
> 
> Something is clearly different here, 8259A.pl reports all irqs are edge no
> matter what. BIOS setup only offers some strange "PCI IDE IRQ mode"
> (Edge/Level) and apparently it has no effect anyway.

 Such an option was common in BIOS configuration of the time, due to odd 
arrangements with early PCI ATA interfaces, such as being equipped with an 
ISA stub board with a connecting cable to route IRQ14/15 from an ISA slot.

 Anyway, this the ALi M1489/M1487 chipset and no datasheet is easily 
available (perhaps Nvidia, which bought the chipset part of ALi back in 
2006, has a copy, but I wouldn't bet on it).  A product brief is available 
that says the chipset supports PCI steering, but we can only guess how it 
works.

 Please try the debug patch I sent with the previous message and maybe 
it'll dump the PIRQ router, which may or may not help.  Choosing the 
CONFIG_PCI_GOBIOS option may also reveal something along with said patch.

  Maciej