Muli Ben-Yehuda <[email protected]> writes:
> My x366 no longer boots with 2.6.19-rc1. The boot either hangs in
> uhci_hcd_init or dies with 'do_IRQ: cannot handle IRQ -1". Bisection
> says this one is bad:
Ok. So at least the second case is because some irq is being delivered
to a cpu that was not expecting it.
The hang case is weird because the kernel does not get told about
the irqs on your second ioapic.
When it gets the 'do_IRQ: cannot handle IRQ -1' how long
has the system been in user space? (It doesn't look like
init got started but that is hard to tell, shutting off irqbalanced
for testing purposes would be interesting)
Seeing the failure case is really weird because this early in boot
everything should be routed to cpu 0.
What happens if you boot with max_cpus=1?
The change the patch introduced was that we are now always
pointing irqs towards individual cpus, and not accepting an irq
if it comes into the wrong cpu.
The only hypothesis I have so far is that there may be an issue
with the x366 chipset ioapics that this patch reveals.
I would suspect a wider issue but in several months of testing
this is the first bug report I have seen.
If simple tests don't reveal what is going on then we will
have to instrument up that BUG and print out the per
cpu vector to irq tables, the cpu number, and the vector
the unexpected irq came in on.
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]
