From: Tarkan Erimer <tarkane@gmail.com>
To: linux-kernel@vger.kernel.org
Cc: Pekka Enberg <penberg@cs.helsinki.fi>
Subject: Fwd: [BUG]: Hard lockups continue with linux-2.6.15-rc1-rc7
Date: Thu, 29 Dec 2005 00:08:05 +0000 [thread overview]
Message-ID: <9611fa230512281608g45aace26hd84d68cf1668a807@mail.gmail.com> (raw)
In-Reply-To: <9611fa230512281558m339739a6v709b963c9c8933b3@mail.gmail.com>
Hi Pekka,
Thanks for the reply. I will try out that and let know the results.
Regards,
On 12/26/05, Pekka Enberg <penberg@cs.helsinki.fi> wrote:
> 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
>
prev parent reply other threads:[~2005-12-29 0:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-26 11:57 Tarkan Erimer
2005-12-26 12:48 ` Pekka Enberg
[not found] ` <9611fa230512281558m339739a6v709b963c9c8933b3@mail.gmail.com>
2005-12-29 0:08 ` Tarkan Erimer [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=9611fa230512281608g45aace26hd84d68cf1668a807@mail.gmail.com \
--to=tarkane@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=penberg@cs.helsinki.fi \
/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®