mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@osdl.org>
To: Martin Bligh <mbligh@google.com>
Cc: linux-kernel@vger.kernel.org, apw@shadowen.org, greg@kroah.com
Subject: Re: Problems with 2.6.15-mm1 and mm2.
Date: Mon, 9 Jan 2006 16:46:53 -0800	[thread overview]
Message-ID: <20060109164653.23b2676e.akpm@osdl.org> (raw)
In-Reply-To: <43C2FA2E.2040704@google.com>

Martin Bligh <mbligh@google.com> wrote:
>
> >>from the NUMA-Q. http://test.kernel.org/19793/debug/console.log
>  >>
>  > 
>  > 
>  > Yes, I asked Greg about that - we don't know what's causing it yet.  I have
>  > a bad feeling that this bug will go into Linus's tree if we don't fix it
>  > quick.
>  > 
>  > I had problems with gregkh-pci-x86-pci-domain-support-the-meat.patch.  It
>  > might be worth reverting that.
> 
>  Andy figured out what caused it.
> 
>  >>on -mm2 I get the x86_64 seems to lock up (NFI why ... looking at it), 
>  >>the NUMA-Q and x440 panic (very similar to the above).
>  >>
>  >>I think Andy figured out what was causing those panics. Can we drop 
>  >>those patches until they're fixed?
>  >>
>  > 
>  > 
>  > I'm not aware of any buggy x86_64 patches in -mm2 :(
>  > 
>  > I guess you don't have the time to sit down and do a bisection search. 
>  > It'd take a solid few hours...
> 
>  It's more that I don't have direct access to the machines in question
>  any more. The x86_64 one might just be a machine issue ... trying to 
>  confirm that still ... but the PCI one was real.
> 
>  M.
> 
>  Below is cut & pasted, so not applyable, and maybe it shouldn't be 
>  applied. But ... it worked before whatever is in -mm ... so my personal 
>  feeling is that if we don't have a fix for whatever is currently in -mm, 
>  it should get dropped until we do ? Going backwards = bad.
> 
>  Perhaps I'm in a time loop, and just confused. but I don't think so ?

This isn't at all clear, sorry.

Does the patch you sent fix things in 2.6.15-mm2?  On NUMAQ and on x86_64? 
Does it fix a bug which was introduced in a patch which in in 2.6.15-mm2? 
If so, which one?

etc ;)

  reply	other threads:[~2006-01-10  0:47 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-09 17:59 Martin Bligh
2006-01-09 23:41 ` Andrew Morton
2006-01-10  0:05   ` Martin Bligh
2006-01-10  0:46     ` Andrew Morton [this message]
2006-01-10  0:50       ` Martin Bligh
2006-01-10 14:52         ` Andy Whitcroft

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=20060109164653.23b2676e.akpm@osdl.org \
    --to=akpm@osdl.org \
    --cc=apw@shadowen.org \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mbligh@google.com \
    /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

Powered by JetHome