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] [day] [month] [year] [list]
Date:	Mon, 04 Jun 2007 08:31:05 -0600
From:	Robert Hancock <hancockr@...w.ca>
To:	Thomas Voegtle <tv@...96.de>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: hisax isdn card (Sedlbauer Speed Fax+) does not get an interrupt

Thomas Voegtle wrote:
> Thx for your answer. Unfortunately, it didn't help us yet in finding a fix 
> for the problem.
> 
> The first IRQs are received after the call to pci_enable_device, but 
> before the IRQ handler itself is registered (register_irq). The IRQs seem 
> to be triggered by the write operations to the card registers 
> (byteout()/outb() calls around lines 676ff in sedlbauer.c); the IRQ 
> handler is registered much later, though. The dump above suggests that the 
> kernel relays the interrupts to the USB handler (on the same IRQ) instead 
> - which obviously is wrong.
> 
> In short:
> * pci_enable_device
> * writing to card registers -> triggering interrupts
>   (handler not yet installed -> error)
> * register interrupt -> fails, as it already was disabled due to the 
>   errors
> 
> Again: thx for your comments. Do you have any further ideas/advice on how 
> to get the driver running?

Presumably whatever writes the driver is doing there are enabling the 
card to generate interrupts - in this case the IRQ handler needs to be 
registered before this point, and not after..

-- 
Robert Hancock      Saskatoon, SK, Canada
To email, remove "nospam" from hancockr@...pamshaw.ca
Home Page: http://www.roberthancock.com/

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ