linux-kernel - 4.4.3 issue: Hisax driver no longer loading

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-next>] [day] [month] [year] [list]

Message-ID: <56D6FBF9.2090805@xs4all.nl>
Date:	Wed, 2 Mar 2016 15:43:05 +0100
From:	Udo van den Heuvel <udovdh@...all.nl>
To:	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: 4.4.3 issue: Hisax driver no longer loading

Hello,

On 3.18.11 the card was functioning OK.
On 4.4.3 I get:

   1.894086] HiSax: Card 1 Protocol EDSS1 Id=HiSax (0)
[    1.894198] HiSax: W6692 driver Rev. 1.18.2.4
[    1.894364] Found: Dynalink/AsusCom IS64PH, I/O base: 0xd000, irq: 6
[    1.894490] HiSax: IS64PH config irq:6 I/O:d000
[    1.894611] W6692: Winbond W6692 version (0): W6692 V00
[    1.894865] W6692 ISTA=0x0
[    1.894967] W6692 IMASK=0xFF
[    1.895070] W6692 D_EXIR=0x0
[    1.895173] W6692 D_EXIM=0xFF
[    1.895277] W6692 D_RSTA=0xA0
[    1.895384] Winbond 6692: IRQ 6 count 0
[    1.897842] input: AT Translated Set 2 keyboard as
/devices/platform/i8042/serio0/input/input3
[    1.932040] Winbond 6692: IRQ 6 count 0
[    1.932149] Winbond 6692: IRQ(6) getting no interrupts during init 1
[    1.984031] Winbond 6692: IRQ 6 count 0
[    1.984139] Winbond 6692: IRQ(6) getting no interrupts during init 2
[    2.034988] ata1.00: ATA-8: Hitachi HDS721050CLA360, JP2OA50E, max
UDMA/133
[    2.035111] ata1.00: 976773168 sectors, multi 16: LBA48 NCQ (depth 0/32)
[    2.048185] Winbond 6692: IRQ 6 count 0
[    2.048292] Winbond 6692: IRQ(6) getting no interrupts during init 3
[    2.048592] HiSax: Card Winbond 6692 not installed !

I reserved some IRQs in the BIOS of the box but different IRQ does not
solve the issue.
Cold boot doesn't help either.

Any workarounds?


Kind regards,
Udo