Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Mon, 3 Mar 2003 10:53:19 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Mon, 3 Mar 2003 10:53:19 -0500 Received: from rzserv1.gsi.de ([140.181.96.11]:10201 "EHLO rzserv1.gsi.de") by vger.kernel.org with ESMTP id ; Mon, 3 Mar 2003 10:53:14 -0500 Message-ID: <3E637CDC.3030409@GSI.de> Date: Mon, 03 Mar 2003 17:03:40 +0100 From: ChristopherHuhn Organization: GSI User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2.1) Gecko/20021213 Debian/1.2.1-2.bunk X-Accept-Language: de-de, en-us, fr-fr MIME-Version: 1.0 To: root@chaos.analogic.com CC: linux-kernel@vger.kernel.org, linux-smp , support-gsi@credativ.de Subject: Re: Kernel Bug at spinlock.h ?! References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2690 Lines: 68 Hi, I'm sorry I didn't know about ksymoops as I'm not experienced with kernel bugs yet. Richard B. Johnson wrote: >The "Re: Kernel Bug at spinlock.h ?!" is an eye-catcher because this >inline code cannot have any bugs or you wouldn't even have booted. > I think this is the code, that produced the BUG message: static inline void spin_unlock(spinlock_t *lock) { char oldval = 1; #if SPINLOCK_DEBUG if (lock->magic != SPINLOCK_MAGIC) BUG(); ... The oops occured after an uptime of about 50 hours. I just discovered the following messages in the syslog, right before that oops (I never found any kernel oops logs in the syslog until now ...): Feb 27 20:51:37 lxb039 kernel: Unable to handle kernel NULL pointer dereference at virtual address 00000000 Feb 27 20:51:37 lxb039 kernel: printing eip: Feb 27 20:51:37 lxb039 kernel: 00000000 Feb 27 20:51:37 lxb039 kernel: *pde = 00000000 Feb 27 20:51:37 lxb039 kernel: Oops: 0000 Feb 27 20:51:37 lxb039 kernel: CPU: 3 Feb 27 20:51:37 lxb039 kernel: EIP: 0010:[msr_exit+0/24] Not tainted Feb 27 20:51:37 lxb039 kernel: EFLAGS: 00010246 Feb 27 20:51:37 lxb039 kernel: eax: fffffffe ebx: f1857cb0 ecx: 00000002 edx: 00000008 Feb 27 20:51:37 lxb039 kernel: esi: fffffff5 edi: f1857cb0 ebp: f1857c90 esp: f1857c84 Feb 27 20:51:37 lxb039 kernel: ds: 0018 es: 0018 ss: 0018 Feb 27 20:51:37 lxb039 kernel: Process sh (pid: 29359, stackpage=f1857000) Feb 27 20:51:37 lxb039 kernel: Stack: f1857cb0 f1857ca8 00000000 f1857d38 c02a8ff1 f1857cb0 f1857d58 f1856000 Feb 27 20:51:37 lxb039 kernel: 00000001 fffffefd ffffffff 00000000 00000000 00000000 00000000 00000000 Feb 27 20:51:37 lxb039 kernel: 00000000 00000000 fffffffe 00000000 00000003 f1857da8 f1857d9c 00000000 Feb 27 20:51:38 lxb039 kernel: Call Trace: [rpc_call_sync+121/164] [rpc_run_timer+0/240] [nfs3_rpc_wrapper+54/124] [nfs3_proc_lookup +194/340] [nfs_lookup+122/204] Feb 27 20:51:38 lxb039 kernel: [dput+27/464] [link_path_walk+2940/3200] [in_group_p+32/40] [vfs_permission+121/248] [d_alloc+25/476] [real_lookup+169/360] Feb 27 20:51:38 lxb039 kernel: [link_path_walk+2425/3200] [path_walk+29/36] [path_lookup+30/44] [__user_walk+45/72] [sys_stat64+26/11 2] [sys_close+115/140] Feb 27 20:51:38 lxb039 kernel: [system_call+51/56] Feb 27 20:51:38 lxb039 kernel: Feb 27 20:51:38 lxb039 kernel: Code: Bad EIP value. Looks like a NFS problem, huh? - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/