From: Zbigniew Luszpinski <zbiggy@go2.pl>
To: "Justin P. mattock" <justinmattock@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.32 help needed with reverting APIC patches.
Date: Tue, 23 Mar 2010 00:18:15 +0100 [thread overview]
Message-ID: <201003230018.15750.zbiggy@go2.pl> (raw)
In-Reply-To: <4BA716E5.2060800@gmail.com>
> 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
next prev parent reply other threads:[~2010-03-22 23:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-22 0:23 Zbigniew Luszpinski
2010-03-22 7:06 ` Justin P. mattock
2010-03-22 23:18 ` Zbigniew Luszpinski [this message]
2010-03-22 23:25 ` Justin P. Mattock
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=201003230018.15750.zbiggy@go2.pl \
--to=zbiggy@go2.pl \
--cc=justinmattock@gmail.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®