linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: William Lee Irwin III <wli@holomorphy.com>
To: Steven Pratt <slpratt@austin.ibm.com>
Cc: linux-kernel@vger.kernel.org, Andrew Morton <akpm@digeo.com>
Subject: Re: 2.6.0-test7-mm1
Date: Thu, 16 Oct 2003 07:58:59 -0700	[thread overview]
Message-ID: <20031016145859.GD723@holomorphy.com> (raw)
In-Reply-To: <3F8EAEB5.5040102@austin.ibm.com>

On Thu, Oct 16, 2003 at 09:44:05AM -0500, Steven Pratt wrote:
> On reboot after heavy IO loads (tiobench) I keep getting the following 
> oops. Happens right after the "turning off swap" message. Root FS is 
> ext3, but the oops has happened while testing ext2 and ext3 with 
> tiobench(xfs, jfs and rieser still to come).
> kernel BUG at include/linux/list.h:148!
> invalid operand: 0000 [#1]
> SMP
> CPU:    2
> EIP:    0060:[<c01756f7>]    Not tainted VLI
> EFLAGS: 00010213
> EIP is at __iget+0x67/0x80

Could you try with the invalidate_inodes-speedup.patch backed out?


-- wli

  parent reply	other threads:[~2003-10-16 14:56 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-16 14:44 2.6.0-test7-mm1 Steven Pratt
2003-10-16 14:58 ` 2.6.0-test7-mm1 Andrew Morton
2003-10-16 23:13   ` 2.6.0-test7-mm1 Steven Pratt
2003-10-17  7:23   ` 2.6.0-test7-mm1 Kirill Korotaev
2003-10-16 14:58 ` William Lee Irwin III [this message]
2003-10-19 14:16 ` 2.6.0-test7-mm1 Alexander Hoogerhuis
     [not found] <20031016083124.45a171a5.akpm@osdl.org>
2003-10-17  7:03 ` 2.6.0-test7-mm1 Bradley Chapman
2003-10-17  7:25   ` 2.6.0-test7-mm1 Andrew Morton
2003-10-17  9:15     ` 2.6.0-test7-mm1 Russell King
  -- strict thread matches above, loose matches on Subject: below --
2003-10-15 12:17 2.6.0-test7-mm1 Jan Killius
2003-10-15 10:11 2.6.0-test7-mm1 Bradley Chapman
2003-10-15 10:22 ` 2.6.0-test7-mm1 Andrew Morton
2003-10-15 12:34   ` 2.6.0-test7-mm1 Bradley Chapman
2003-10-15 12:46     ` 2.6.0-test7-mm1 Tim Schmielau
2003-10-15 12:53       ` 2.6.0-test7-mm1 Bradley Chapman
2003-10-15 17:28     ` 2.6.0-test7-mm1 Andrew Morton
2003-10-15 17:40       ` 2.6.0-test7-mm1 Ben Collins
2003-10-15 17:53         ` 2.6.0-test7-mm1 Andrew Morton
2003-10-16  2:25           ` 2.6.0-test7-mm1 Ben Collins
2003-10-16 14:04             ` 2.6.0-test7-mm1 Anton Blanchard
2003-10-18 12:39             ` 2.6.0-test7-mm1 Kristian Høgsberg
2003-10-18 13:27               ` 2.6.0-test7-mm1 Ben Collins
2003-10-15 21:14   ` 2.6.0-test7-mm1 Alexander Hoogerhuis
2003-10-15 21:44     ` 2.6.0-test7-mm1 Andrew Morton
2003-10-15  8:36 2.6.0-test7-mm1 Andrew Morton
2003-10-15 15:20 ` 2.6.0-test7-mm1 Luiz Capitulino
2003-10-15 15:42 ` 2.6.0-test7-mm1 Luiz Capitulino
2003-10-15 16:55   ` 2.6.0-test7-mm1 William Lee Irwin III
2003-10-15 21:40     ` 2.6.0-test7-mm1 William Lee Irwin III
2003-10-16 15:11       ` 2.6.0-test7-mm1 Luiz Capitulino
2003-10-17  8:58     ` 2.6.0-test7-mm1 Kirill Korotaev
2003-10-17  9:10       ` 2.6.0-test7-mm1 William Lee Irwin III
2003-10-17 12:02       ` 2.6.0-test7-mm1 Luiz Capitulino
2003-10-18 17:43 ` 2.6.0-test7-mm1 Thomas Schlichter
2003-10-18 17:50   ` 2.6.0-test7-mm1 Andrew Morton

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=20031016145859.GD723@holomorphy.com \
    --to=wli@holomorphy.com \
    --cc=akpm@digeo.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=slpratt@austin.ibm.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;
as well as URLs for NNTP newsgroup(s).