From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Mon, 23 Sep 2002 17:47:37 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Mon, 23 Sep 2002 17:47:37 -0400 Received: from e3.ny.us.ibm.com ([32.97.182.103]:31893 "EHLO e3.ny.us.ibm.com") by vger.kernel.org with ESMTP id ; Mon, 23 Sep 2002 17:47:35 -0400 Subject: Bug in last night's bk test From: Paul Larson To: lkml , akpm@digeo.com, lse-tech@lists.sourceforge.net Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Ximian Evolution 1.0.5 Date: 23 Sep 2002 16:36:41 -0500 Message-Id: <1032817002.24372.138.camel@plars.austin.ibm.com> Mime-Version: 1.0 Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org The automated nightly testing turned up a bug on one of the test machines last night. The system that had the problem was running ltp and was a 2-way PII-550, 2GB ram, ext2. Here is the ksymoops dump: ksymoops 2.4.5 on i686 2.4.18. Options used -V (default) -K (specified) -L (specified) -O (specified) -m System.map (specified) kernel BUG at ll_rw_blk.c:1802! invalid operand: 0000 CPU: 0 EIP: 0060:[] Not tainted Using defaults from ksymoops -t elf32-i386 -a i386 EFLAGS: 00010202 eax: 00000080 ebx: f7e3a418 ecx: f7dc8f60 edx: 000000a0 esi: f71f3960 edi: 000000a0 ebp: 00008cd8 esp: ef18bbf0 ds: 0068 es: 0068 ss: 0068 Stack: 00000000 00000000 00000000 0000000c c02159fd f71f3960 ef18bc4c c015b4b1 00000000 f71f3960 ef18bc4c c015b683 ef18bc4c 0809d000 ef18bc4c c015bd52 ef18bc4c 00000fff f7295a54 00000000 f71db900 ef18bc4c 00014000 f71f3960 Call Trace: [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] Code: 0f 0b 0a 07 ac a1 36 c0 8d b4 26 00 00 00 00 3b 49 44 74 0b >>EIP; c0215971 <===== >>ebx; f7e3a418 >>ecx; f7dc8f60 >>esi; f71f3960 >>ebp; 00008cd8 Before first symbol >>esp; ef18bbf0 Trace; c02159fd Trace; c015b4b1 Trace; c015b683 Trace; c015bd52 Trace; c017decc Trace; c0266b05 Trace; c02674a3 Trace; c0265c78 Trace; c0248d20 Trace; c0263a16 Trace; c024889c Trace; c01157f6 Trace; c0214ba0 Trace; c012d689 Trace; c015be13 Trace; c017decc Trace; c017df2e Trace; c017decc Trace; c015be4f Trace; c012e0dd <__generic_file_aio_read+f1/1a4> Trace; c012f502 Trace; c012f54e Trace; c013f95a Trace; c012e1c0 Trace; c012c4c9 Trace; c012123b Trace; c013efb0 Trace; c013f2af Trace; c013faa6 Trace; c0107073 Code; c0215971 00000000 <_EIP>: Code; c0215971 <===== 0: 0f 0b ud2a <===== Code; c0215973 2: 0a 07 or (%edi),%al Code; c0215975 4: ac lods %ds:(%esi),%al Code; c0215976 5: a1 36 c0 8d b4 mov 0xb48dc036,%eax Code; c021597b a: 26 00 00 add %al,%es:(%eax) Code; c021597e d: 00 00 add %al,(%eax) Code; c0215980 f: 3b 49 44 cmp 0x44(%ecx),%ecx Code; c0215983 12: 74 0b je 1f <_EIP+0x1f> c0215990 It didn't hang the machine, or crash it. Just showed up in the logs. This error did not show up in the previous night's test. Please let me know if any other information would be helpful. Thanks, Paul Larson