public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Justin P. Mattock" <justinmattock@gmail.com>
To: Zbigniew Luszpinski <zbiggy@go2.pl>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.32 help needed with reverting APIC patches.
Date: Mon, 22 Mar 2010 16:25:23 -0700	[thread overview]
Message-ID: <4BA7FC63.6000503@gmail.com> (raw)
In-Reply-To: <201003230018.15750.zbiggy@go2.pl>

On 03/22/2010 04:18 PM, Zbigniew Luszpinski wrote:
>> 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
>


for number one, the only thing off the top of my
head would possibly be load time i.g. if ehci_hcd loads
after ohci is loaded there could be a conflict or vice/versa
with something else.

for number two, I don't have an AMD processor here only and intel
(iMac)

Justin P. Mattock

      reply	other threads:[~2010-03-22 23:25 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-22  0:23 2.6.32 help needed with reverting APIC patches Zbigniew Luszpinski
2010-03-22  7:06 ` Justin P. mattock
2010-03-22 23:18   ` Zbigniew Luszpinski
2010-03-22 23:25     ` Justin P. Mattock [this message]

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=4BA7FC63.6000503@gmail.com \
    --to=justinmattock@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=zbiggy@go2.pl \
    /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