public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Sid Boyce <sboyce@blueyonder.co.uk>
To: linux-kernel@vger.kernel.org
Subject: RE: [BUG]: Hard lockups continue with linux-2.6.15-rc1-rc7
Date: Mon, 26 Dec 2005 21:28:03 +0000	[thread overview]
Message-ID: <43B06063.8030909@blueyonder.co.uk> (raw)

Tarkan Erimer wrote:
 > Hi all,
 >
 > 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.
 >
 > PS: These problems never occured in 2.6.14.xx and downwards.
 >
 > Regards.

Don't rule out hardware. This SuSE 10.0 x86 box worked without problems 
on kernels up to 2.6.15-rc6-git2, but I experienced strange apparent 
filesystem corruptions/compile failures running normally and hard 
lockups when running mythtv with 2.6.15-rc6-git6 and 2.6.15-rc7, while 
on the Mandriva 2006 x86 box and the SuSE x86_64 there were no problems. 
Until I found the suspect SDRAM, on some occasions I had to run 
reiserfsck before 2.6.15-rc6-git2 would boot again correctly after 
trying rc6-git6 or -rc7. Finally I got a corruption again with 
2.6.15-rc7, replaced the SDRAM stick with the one taken out previously, 
booted up on 2.6.15-rc7 with no problems. I had run memtest some days 
earlier, but only for a couple of hours. (current uptime 1 day 1.04hrs).
Regards
Sid.
-- 
Sid Boyce ... Hamradio License G3VBV, Licensed Private Pilot
Retired IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support 
Specialist, Cricket Coach
Microsoft Windows Free Zone - Linux used for all Computing Tasks

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

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-26 21:28 Sid Boyce [this message]
2005-12-29  0:06 ` [BUG]: Hard lockups continue with linux-2.6.15-rc1-rc7 Tarkan Erimer
2005-12-29  0:29   ` Sid Boyce
  -- strict thread matches above, loose matches on Subject: below --
2005-12-26 11:57 Tarkan Erimer
2005-12-26 12:48 ` Pekka Enberg

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=43B06063.8030909@blueyonder.co.uk \
    --to=sboyce@blueyonder.co.uk \
    --cc=linux-kernel@vger.kernel.org \
    /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