All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ben Duncan <ben@versaccounting.com>
To: linux-kernel@vger.kernel.org
Subject: Re: 2.6.18 Nasty Lockup
Date: Tue, 26 Sep 2006 10:41:26 -0500	[thread overview]
Message-ID: <45194A26.4060403@versaccounting.com> (raw)
In-Reply-To: <20060926123640.GA7826@tigers.local>

have gotten recently that as well. One time happen to have top running when
that happened again.

Top showed PDFLUSH consuming 100%CPU and 100% memeory

Do not know if this well help anyone, but thought I would share.

My lspci for the record:

00:00.0 Host bridge: nVidia Corporation nForce2 AGP (different version?) (rev c1)
00:00.1 RAM memory: nVidia Corporation nForce2 Memory Controller 1 (rev c1)
00:00.2 RAM memory: nVidia Corporation nForce2 Memory Controller 4 (rev c1)
00:00.3 RAM memory: nVidia Corporation nForce2 Memory Controller 3 (rev c1)
00:00.4 RAM memory: nVidia Corporation nForce2 Memory Controller 2 (rev c1)
00:00.5 RAM memory: nVidia Corporation nForce2 Memory Controller 5 (rev c1)
00:01.0 ISA bridge: nVidia Corporation nForce2 ISA Bridge (rev a3)
00:01.1 SMBus: nVidia Corporation nForce2 SMBus (MCP) (rev a2)
00:02.0 USB Controller: nVidia Corporation nForce2 USB Controller (rev a3)
00:02.1 USB Controller: nVidia Corporation nForce2 USB Controller (rev a3)
00:02.2 USB Controller: nVidia Corporation nForce2 USB Controller (rev a3)
00:04.0 Ethernet controller: nVidia Corporation nForce2 Ethernet Controller (rev a1)
00:06.0 Multimedia audio controller: nVidia Corporation nForce2 AC97 Audio Controler (MCP) 
(rev a1)
00:08.0 PCI bridge: nVidia Corporation nForce2 External PCI Bridge (rev a3)
00:09.0 IDE interface: nVidia Corporation nForce2 IDE (rev a2)
00:1e.0 PCI bridge: nVidia Corporation nForce2 AGP (rev c1)
01:09.0 Mass storage controller: Silicon Image, Inc. SiI 3112 [SATALink/SATARaid] Serial ATA 
Controller (rev 02)
02:00.0 VGA compatible controller: nVidia Corporation NV18 [GeForce4 MX 440 AGP 8x] (rev a2)


Greg Schafer wrote:
> Hi
> 
> This is a _hard_ lockup. No oops, no magic sysrq, no nuthin, just a
> completely dead machine with only option the reset button. Usually happens
> within a couple of minutes of desktop use but is 100% reproducible. Problem
> is still there in a fresh checkout of current Linus git tree (post 2.6.18).
> 
<SNIP>
-- 
Ben Duncan   - Business Network Solutions, Inc. 336 Elton Road  Jackson MS, 39212
"Never attribute to malice, that which can be adequately explained by stupidity"
        - Hanlon's Razor


  parent reply	other threads:[~2006-09-26 15:51 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-26 12:36 2.6.18 Nasty Lockup Greg Schafer
2006-09-26 13:56 ` Michael Obster
2006-09-26 15:41 ` Ben Duncan [this message]
2006-09-26 18:18 ` john stultz
2006-09-26 20:15 ` john stultz
2006-09-26 22:02   ` Greg Schafer
2006-09-26 22:58     ` john stultz
2006-09-26 21:15 ` S.Çağlar Onur
2006-09-26 22:50   ` john stultz
2006-09-27  9:45     ` S.Çağlar Onur
2006-09-27 19:14       ` john stultz
2006-09-27 20:55         ` Andi Kleen
2006-09-27 21:06           ` S.Çağlar Onur
2006-09-28 11:39         ` S.Çağlar Onur
2006-09-29  8:49           ` S.Çağlar Onur
2006-10-06 22:57             ` john stultz
2006-10-07 15:48               ` S.Çağlar Onur

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=45194A26.4060403@versaccounting.com \
    --to=ben@versaccounting.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.