From: "Matt Heaton" Subject: Kernel bug problem. Date: Mon, 6 Oct 2003 23:13:57 -0600 Sender: nfs-admin@lists.sourceforge.net Message-ID: <04c801c38c91$d020c160$6401a8c0@Matt> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_04C5_01C38C5F.850A6AA0" Return-path: Received: from sc8-sf-mx1-b.sourceforge.net ([10.3.1.11] helo=sc8-sf-mx1.sourceforge.net) by sc8-sf-list1.sourceforge.net with esmtp (Cipher TLSv1:DES-CBC3-SHA:168) (Exim 3.31-VA-mm2 #1 (Debian)) id 1A6kAb-00073u-00 for ; Mon, 06 Oct 2003 22:14:01 -0700 Received: from [216.190.237.135] (helo=cvs.0catch.com) by sc8-sf-mx1.sourceforge.net with esmtp (TLSv1:AES256-SHA:256) (Exim 4.22) id 1A6kAZ-0004BR-N9 for nfs@lists.sourceforge.net; Mon, 06 Oct 2003 22:13:59 -0700 Received: from Matt (12-255-25-93.client.attbi.com [12.255.25.93]) by cvs.0catch.com (8.12.8/8.12.8) with SMTP id h975DxFt019854 for ; Mon, 6 Oct 2003 23:13:59 -0600 To: Errors-To: nfs-admin@lists.sourceforge.net List-Help: List-Post: List-Subscribe: , List-Id: Discussion of NFS under Linux development, interoperability, and testing. List-Unsubscribe: , List-Archive: This is a multi-part message in MIME format. ------=_NextPart_000_04C5_01C38C5F.850A6AA0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Howdy all, I am running Redhat 8.0 with a customer 2.4.20 kernel, with a = 3ware 7500-8 controller formatted using the XFS Filesystem. My Raid array (Raid 1+0) (8 Drives total) is 720 Gigs. =20 I keep getting the following kernel bug. Oct 4 06:29:18 catchusers2 kernel: kernel BUG at ll_rw_blk.c:1192! Oct 4 06:29:18 catchusers2 kernel: invalid operand: 0000 Oct 4 06:29:18 catchusers2 kernel: CPU: 0 Oct 4 06:29:18 catchusers2 kernel: EIP: 0010:[] Not = tainted Oct 4 06:29:18 catchusers2 kernel: EFLAGS: 00010206 Oct 4 06:29:18 catchusers2 kernel: eax: 00000410 ebx: 00000008 ecx: = d9ec12a0 edx: d9ec12a0 Oct 4 06:29:18 catchusers2 kernel: esi: 00000001 edi: d9ec12a0 ebp: = c2229360 esp: f7bfdefc Oct 4 06:29:18 catchusers2 kernel: ds: 0018 es: 0018 ss: 0018 Oct 4 06:29:18 catchusers2 kernel: Process kswapd (pid: 4, = stackpage=3Df7bfd000) Oct 4 06:29:18 catchusers2 kernel: Stack: d9ec12a0 00000001 d9ec12a0 = 00000001 c0145a10 00000001 d9ec12a0 d9ec12a0=20 Oct 4 06:29:18 catchusers2 kernel: c2229360 d9ec12a0 c0145b60 = d9ec12a0 00000000 c2229360 0000968e c03af668=20 Oct 4 06:29:18 catchusers2 kernel: c0137c71 c2229360 000001d0 = f7bfc000 00000200 000001d0 00000015 00000020=20 Oct 4 06:29:18 catchusers2 kernel: Call Trace: [] = [] [] [] [] Oct 4 06:29:18 catchusers2 kernel: [] [] = [] [] [] [] Oct 4 06:29:18 catchusers2 kernel:=20 Oct 4 06:29:18 catchusers2 kernel: Code: 0f 0b a8 04 99 ff 36 c0 b8 03 = 00 00 00 f0 0f ab 42 18 b8 08 I am wondering if this is NFS related? I only have about 50 gigs free = on the raid array now. Whenever I get down to about 25 gigs I get this kernel bug? It is killing me. If I keep it above 50 gigs free = then this NEVER happens? Any ideas? I would be VERY grateful. Thanks, Matt ------=_NextPart_000_04C5_01C38C5F.850A6AA0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
Howdy all, I am running Redhat 8.0 with = a customer=20 2.4.20 kernel, with a 3ware 7500-8 controller formatted using the XFS=20 Filesystem.
My Raid array (Raid 1+0) (8 Drives = total) is 720=20 Gigs. 
 
I keep getting the following kernel=20 bug.
 
Oct  4 06:29:18 catchusers2 = kernel: kernel BUG=20 at ll_rw_blk.c:1192!
Oct  4 06:29:18 catchusers2 kernel: invalid = operand: 0000
Oct  4 06:29:18 catchusers2 kernel: = CPU:   =20 0
Oct  4 06:29:18 catchusers2 kernel: EIP:   =20 0010:[<c024b027>]    Not tainted
Oct  4 = 06:29:18=20 catchusers2 kernel: EFLAGS: 00010206
Oct  4 06:29:18 catchusers2 = kernel:=20 eax: 00000410   ebx: 00000008   ecx: = d9ec12a0  =20 edx: d9ec12a0
Oct  4 06:29:18 catchusers2 kernel: esi:=20 00000001   edi: d9ec12a0   ebp: c2229360   = esp:=20 f7bfdefc
Oct  4 06:29:18 catchusers2 kernel: ds: = 0018   es:=20 0018   ss: 0018
Oct  4 06:29:18 catchusers2 kernel: = Process=20 kswapd (pid: 4, stackpage=3Df7bfd000)
Oct  4 06:29:18 = catchusers2 kernel:=20 Stack: d9ec12a0 00000001 d9ec12a0 00000001 c0145a10 00000001 d9ec12a0 = d9ec12a0=20
Oct  4 06:29:18 catchusers2=20 kernel:        c2229360 d9ec12a0 = c0145b60=20 d9ec12a0 00000000 c2229360 0000968e c03af668
Oct  4 06:29:18=20 catchusers2 kernel:        c0137c71 = c2229360=20 000001d0 f7bfc000 00000200 000001d0 00000015 00000020
Oct  4 = 06:29:18=20 catchusers2 kernel: Call Trace:    [<c0145a10>]=20 [<c0145b60>] [<c0137c71>] [<c0137eb3>]=20 [<c0137f26>]
Oct  4 06:29:18 catchusers2 = kernel:  =20 [<c013803c>] [<c01380b8>] [<c01381ed>] = [<c0105000>]=20 [<c010747e>] [<c0138150>]
Oct  4 06:29:18 = catchusers2=20 kernel:
Oct  4 06:29:18 catchusers2 kernel: Code: 0f 0b a8 04 = 99 ff 36=20 c0 b8 03 00 00 00 f0 0f ab 42 18 b8 08
 
 
I am wondering if this is NFS = related?  I=20 only have about 50 gigs free on the raid array now.  Whenever I get = down to=20 about 25 gigs I get
this kernel bug?   It is = killing=20 me.  If I keep it above 50 gigs free then this NEVER happens?  = Any=20 ideas?  I would be VERY grateful.
 
Thanks,
Matt
 
------=_NextPart_000_04C5_01C38C5F.850A6AA0-- ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ NFS maillist - NFS@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nfs