[lkml]   [2005]   [Jan]   [5]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: dmesg: PCI interrupts are no longer routed automatically.........
On Wed, 5 Jan 2005, David Vrabel wrote:

> linux-os wrote:
>> For instance, Level interrupts from PLX chips on the PCI bus
>> can (read do) generate interrupts when some of the BARS are
>> being configured. Once you get an unhandled interrupt, you
>> are dead because there's nothing to reset the line.
> Why not unconditionally clear all interrupts after configuring the chip?
> David Vrabel

You can't configure the chip until the BARS are set up for
access. You _must_ know what the interrupt line is, before
you touch any registers so that any "waiting" interrupt
gets handled, i.e., cleared. Otherwise, the code that
inspects the PCI bus, looking for a device to claim, finds
the device, then (in order to make its IRQ correct) enables
it ... BAM that's all she wrote. No messages, no nothing,
a halted machine because the IRQ line is permanently TRUE
with no code in place to reset it.

The temporary work-around is....
save_irq = pdev->irq;
pci_disable_device(pdev); // Turn back off.

request_irq(save_irq,...) // Put ISR in place

pci_write_config_byte(pdev, PCI_CACHE_LINE_SIZE, 0x08);
pci_write_config_byte(pdev, PCI_LATENCY_TIMER, 0x40);
pci_set_dma_mask(pdev, 0x00000000ffffffffULL);
pci_set_drvdata(pdev, NULL);
pci_set_power_state(pdev, 0);
pci_write_config_dword(pdev, PCI_COMMAND, PCI_CONFIG);

.... configure chip-specific stuff, clear interrupts, etc.

Now, the temporary work-around is a MACRO called ROUTE_IRQ().
If the guy who changed the PCI API adds a seperate callable
procedure to do this routing without actually enabling the
chip, I will substitute.

This work-round is a new Linux-2.6.10 bug-hack. It was never
required before

Dick Johnson
Penguin : Linux version 2.6.10 on an i686 machine (5537.79 BogoMips).
Notice : All mail here is now cached for review by Dictator Bush.
98.36% of all statistics are fiction.
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2005-03-22 14:09    [W:0.056 / U:1.752 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site