mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Jesper Juhl" <jesper.juhl@gmail.com>
To: "Metathronius Galabant" <m.galabant@googlemail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: user-space command "ipcs" seems broken on 2.6.18.1
Date: Mon, 30 Oct 2006 18:36:09 +0100	[thread overview]
Message-ID: <9a8748490610300936m38b54afei1e77f1c88ceccec4@mail.gmail.com> (raw)
In-Reply-To: <9a8748490610300933t793e0aaew1016f03410f2f96@mail.gmail.com>

On 30/10/06, Jesper Juhl <jesper.juhl@gmail.com> wrote:
> On 30/10/06, Metathronius Galabant <m.galabant@googlemail.com> wrote:
> > > Can you identify the latest kernel where it works OK?
> >
> > I can't reproduce that behaviour on another SMP machine with the same
> > kernel-config for 2.6.18.1 (only storage and network device drivers
> > differ).
> > The affected one is a production machine I can't use to test, and
> > furthermore the only one I've got of that series.
> >
> Ok, can you then at least tell us what the latest kernel you have used
> that was OK was?
> Just to try and narrow things down a bit.
>
> > Has to wait until the weekend. Any remote clue so I know where to look?
>
> Well, with a simple good/bad test case like you have, the obvious
> thing to do would be to find a resonably new kernel that's good and
> one that's bad and then do a git bisection search to find the exact
> commit that broke things for you. Short of that, narrowing it down to
> a released version, a -rc or -git snapshot is also good.
>
> You could also start browsing through changelogs looking for changes
> to IPC and then try revert patches that look likely. But  git bisect
> is probably a lot easier.
>
Ohh and btw, testing the latest -rc (and/or -git snapshot) kernel is
also useful, to see if the bug has already been fixed in what is to
become 2.6.19 eventually.

-- 
Jesper Juhl <jesper.juhl@gmail.com>
Don't top-post  http://www.catb.org/~esr/jargon/html/T/top-post.html
Plain text mails only, please      http://www.expita.com/nomime.html

      reply	other threads:[~2006-10-30 17:36 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-30 12:14 Metathronius Galabant
2006-10-30 12:32 ` Jesper Juhl
     [not found]   ` <1b270aae0610300437u1529b5ddo5a365a06f16611c@mail.gmail.com>
2006-10-30 13:15     ` Metathronius Galabant
2006-10-30 17:33       ` Jesper Juhl
2006-10-30 17:36         ` Jesper Juhl [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=9a8748490610300936m38b54afei1e77f1c88ceccec4@mail.gmail.com \
    --to=jesper.juhl@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=m.galabant@googlemail.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

all inboxes | Powered by JetHome®