Re: 2.6.19-rc1 genirq causes either boot hang or "do_IRQ: cannot handle IRQ -1"

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Muli Ben-Yehuda <[email protected]> writes:

> On Fri, Oct 06, 2006 at 05:42:40PM -0600, Eric W. Biederman wrote:
>
>> If I read your bootlog right. You have logical cpus, but only two
>> sockets, and I think only two cores.  The other two logical cpus
>> being hyperthreaded.
>
> Yes, 2 sockets each of which is HT. Here's a /proc/cpuinfo from a
> distro kernel:

Ok.  From looking at an individual case the ioapic is programmed
correctly and I don't see a reason the local apic would be programmed
incorrectly.  However logical delivery mode and lowest priority
delivery mode are enabled.  So we are asking the interrupt delivery
subsystem to choose a cpu to deliver the interrupt to and then are not
giving the cpu any choice.  So we may be confusing things. 

Can you try CONFIG_CPU_HOTPLUG?  That will force genapic to be set
to genapic_physflat instead of genapic_flat.

I am hoping that by running the apics in a different delivery mode
that explicitly says just deliver this interrupt to this cpu we
will avoid the problem you are seeing.

If genapic_physflat works we will have to decide what to do about
genapic_flat.

Thanks,

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

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]
  Powered by Linux