public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Jochen Heuer <jogi-kernel@planetzork.ping.de>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: linux-kernel@vger.kernel.org, Ingo Molnar <mingo@elte.hu>,
	nathans@sgi.com, xfs@oss.sgi.com
Subject: Re: BUG: soft lockup detected on CPU#1!
Date: Mon, 17 Jul 2006 16:48:31 +0200	[thread overview]
Message-ID: <20060717144831.GA28284@planetzork.ping.de> (raw)
In-Reply-To: <1153146608.1218.9.camel@localhost.localdomain>

On Mon, Jul 17, 2006 at 10:30:08AM -0400, Steven Rostedt wrote:
> 
> Jochen, you didn't say whether or not the 2.6.18-rc2 locked up. I'm
> assuming it did. But did it?

Hi Steven,

no, it did not lock up yet but I did not do any "serious" webbrowsing
with 2.6.18-rc2 so far.

Best regards,

   Jochen

       reply	other threads:[~2006-07-17 15:53 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20060717125216.GA15481@planetzork.ping.de>
     [not found] ` <1153146608.1218.9.camel@localhost.localdomain>
2006-07-17 14:48   ` Jochen Heuer [this message]
2006-07-21 22:53     ` BUG: soft lockup detected on CPU#1! Jochen Heuer
2006-07-21 22:58   ` Jochen Heuer
2009-02-11  7:16 raksac
2009-02-11  9:21 ` Justin Piszcz
2009-02-11 23:33   ` raksac
2009-02-11 23:36     ` Justin Piszcz
2009-02-12  9:22       ` raksac
2009-02-12 21:55         ` Dave Chinner
2009-02-12 21:59           ` raksac
2009-02-12 22:10             ` Eric Sandeen
2009-02-12 22:16               ` raksac
2009-02-13  4:56                 ` Eric Sandeen
2009-02-19  8:04                   ` raksac
2009-02-13  9:32                 ` Michael Monnerie
2009-02-11 23:34   ` raksac
2009-02-12 21:49 ` Dave Chinner
2009-02-12 21:55   ` raksac
  -- strict thread matches above, loose matches on Subject: below --
2009-02-11  7:57 Rakesh

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=20060717144831.GA28284@planetzork.ping.de \
    --to=jogi-kernel@planetzork.ping.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=nathans@sgi.com \
    --cc=rostedt@goodmis.org \
    --cc=xfs@oss.sgi.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