Re: regression caused by: genirq: do not leave interupts enabled onfree_irq

[Daniel Barkalow]

On Fri, 11 Apr 2008, Yinghai Lu wrote:

> On Fri, Apr 11, 2008 at 12:30 AM, Eric W. Biederman
> <ebiederm@xxxxxxxxxxxx> wrote:
> >
> >
> >  On Fri, 2008-04-11 at 00:17 -0700, Yinghai Lu wrote:
> >  > On Fri, Apr 11, 2008 at 12:14 AM, Yinghai Lu <yhlu.kernel@xxxxxxxxx> wrote:
> >  > >  RHEL 5.1 kexec RHEL 5.1 : works
> >  > >  RHEL 5.1 kexec linus kernel: works
> >  > >  linus (after -rc2) kexec linus tree: works:
> >  > >  linus  (after -rc2) kexec RHEL 5.1 : forcedeth will not come up
> >  > >  linus ( before -rc2 include rc2) kexec RHEL 5.1 works
> >  > >
> >  > the forcedeth can not get IP address...
> >
> >  Sounds like you are not getting any interrupts when you receive a
> >  packet.  (i.e. The interrupt line is staying disabled).
> >
> >  Is MSI an option here?  I'm wondering if we disable the MSI and
> >  something is not enabling it.
> 
> mcp55 is using msi for forcedeth
> 
> MSI.. will look at the driver in RHEL 5.1
> 
> it seems that another server with ck804 works because it is using ioapic.

When turning on MSI for forcedeth, we do the INTx disable thing (and it's 
actually necessary for at least some forcedeth-driven hardware); if we're 
not disabling MSI (and making INTx undisabled), the old kernel may not 
undisable INTx but expect to have legacy interrupts delivered.

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