On Fri, 05 May 2006 19:42:27 +0100
Daniel Drake <[EMAIL PROTECTED]> wrote:

> Stephen Hemminger wrote:
> > What is happening is that if there is a misconfiguration and irq routing
> > is messed up (ie edge trigged). The driver will degenerate to polling every 
> > 100ms.
> > If your system is this misconfigured, then ACPI or the BIOS needs to be 
> > fixed
> > and the driver really only needs to work well enough to get the bug report 
> > out ;-)
> 
> Ok, thanks for the explanation.
> 
> Can you give any hints as to how we can classify this misconfiguration? 
> Barry's system has a level triggered IRQ assigned to sky2, and that IRQ 
> is not shared:
> 
> http://bugs.gentoo.org/show_bug.cgi?id=132056#c3
> 
> I'm just looking for something I can take to the ACPI developers, other 
> than "its broken because Stephen said so" ;)

Try running idle_timeout=0 module parameter.  In that case there will be no
polling timer.  If it just hangs, then the problem is missed interrupt.

You could use this to see if you are getting irq's

--- sky2.orig/drivers/net/sky2.c
+++ sky2/drivers/net/sky2.c
@@ -2125,6 +2125,9 @@ static int sky2_poll(struct net_device *
        int work_done = 0;
        u32 status = sky2_read32(hw, B0_Y2_SP_EISR);
 
+       if (netif_msg_intr((struct sky2_port *) netdev_priv(dev0)))
+               printk(KERN_DEBUG PFX "poll status %#x\n", status);
+
        if (status & Y2_IS_HW_ERR)
                sky2_hw_intr(hw);
 
@@ -2183,6 +2186,9 @@ static irqreturn_t sky2_intr(int irq, vo
        if (status == 0 || status == ~0)
                return IRQ_NONE;
 
+       if (netif_msg_intr((struct sky2_port *) netdev_priv(dev0)))
+               printk(KERN_DEBUG PFX "irq status %#x\n", status);
+
        prefetch(&hw->st_le[hw->st_idx]);
        if (likely(__netif_rx_schedule_prep(dev0)))
                __netif_rx_schedule(dev0);
-
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to