Re: 2.6.32 help needed with reverting APIC patches.

[Zbigniew Luszpinski]

> best would be todo a bisect. but if your for sure these
> are the commits, then you probably wont need too.
> 
> if your doing git revert xxxx
> and the commit reverts for you then your good,
> but if there's too much happening(big merge), then
> a git rebase probably is the best bet(but could be wrong).
> 
> hope this helps.
> 
> Justin P. Mattock
> 

Yeah I imagine reverting patches from kernel 2.6.32.10 up to 2.6.20 and seeing all these conflicts in git.
I have just done this in different way: downloaded official 2.6.32.10 and manually reinserted the removed code.
I resolved IRQ_DELAYED_DISABLE irq.h conflict by moving it to higher bitfield position.
The patched kernel booted OK but these reverts did not resolve the OHCI hangs in APIC mode.
The final verdict is: idea #1 was false.
Now I focus on #2 and #3 ideas.

Call for action:
1. If you have any idea why ohci hangs in APIC mode let me know.
2. If you have Nvidia MCP78S mainboard with AMD CPU please send me ACPI dump:
acpidump > dump.bin
bzip2 -9v dump.bin
This will be good APIC code comparison to check the #3 idea.
Do not mess the ML with attachments - send me the file(s) PM.

On my mainboard almost all onboard devices are sitting on INT A according to ACPI code.
Only USB 2.0 EHCI controller sits on INT B alone.

have a nice day,
Zbigniew Luszpinski
--
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/