mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Pekka Enberg <penberg@cs.helsinki.fi>
To: Tarkan Erimer <tarkane@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [BUG]: Hard lockups continue with linux-2.6.15-rc1-rc7
Date: Mon, 26 Dec 2005 14:48:05 +0200	[thread overview]
Message-ID: <84144f020512260448w119fa376uea3bf985c35a70a6@mail.gmail.com> (raw)
In-Reply-To: <9611fa230512260357gcb3a163tae35f7e69f1ee7df@mail.gmail.com>

Hi Tarkan,

On 12/26/05, Tarkan Erimer <tarkane@gmail.com> wrote:
> I'm having hard lockups with all the RCs of linux-2.6.15. I,
> previously, mentioned this with the subject "[BUG]: Software compiling
> occasionlly hangs under 2.6.15-rc1/rc2 and 2.6.15-rc1-mm2" in the
> list. I investigated a bit at found these interesting things.
>
> -- Always reproducable. To reproduce:
>     - in console 1, issueing "updatedb"
>     - in console 2, issueing "find / -name "blahblah" -print
>     - in console 3, issueing "emerge -uDp world" (BTW, I'm using Gentoo.)
>     - in console 4, X started.
>     - a few minutes later, system completely freezes. No Alt+SysRq+t
> works. (Normally, it does)
>
> When the system freezes, there is nothing in logs. But hardly, I
> captured an  Alt+SysRq+t. A few seconds (15-20 seconds) before hang. I
> attached this  Alt+SysRq+t and lsmod output. Hope this helps to solve
> this.

You can use git bisect to narrow down the changeset that introduced
the bug. Please refer to the following URL for details:
http://www.kernel.org/pub/software/scm/git/docs/howto/isolate-bugs-with-bisect.txt

                        Pekka

  reply	other threads:[~2005-12-26 12:48 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-26 11:57 Tarkan Erimer
2005-12-26 12:48 ` Pekka Enberg [this message]
     [not found]   ` <9611fa230512281558m339739a6v709b963c9c8933b3@mail.gmail.com>
2005-12-29  0:08     ` Fwd: " Tarkan Erimer
2005-12-26 21:28 Sid Boyce
2005-12-29  0:06 ` Tarkan Erimer
2005-12-29  0:29   ` Sid Boyce

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=84144f020512260448w119fa376uea3bf985c35a70a6@mail.gmail.com \
    --to=penberg@cs.helsinki.fi \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tarkane@gmail.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®