From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1759340AbYDUDQm (ORCPT ); Sun, 20 Apr 2008 23:16:42 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1754542AbYDUDQ3 (ORCPT ); Sun, 20 Apr 2008 23:16:29 -0400 Received: from rv-out-0708.google.com ([209.85.198.240]:17120 "EHLO rv-out-0506.google.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1754414AbYDUDQ2 (ORCPT ); Sun, 20 Apr 2008 23:16:28 -0400 DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth; b=BAoCaKcDxjG4/5oYun2LETzHXB3IgIcavjmJfnFlpo9MEKZXxbMy9M+L8p1kcIoquI4xtl1hZCRzmd1xP4mJi8mpBRhVVwGXYsfeFZiFoy9D1Cy3z0JlH6iJ2BYroK16hNtMCqH4bMCNwtrGd9wf+RCnb901EL7ReAZJW66YKC8= Message-ID: <76366b180804202016l19ac362cyb814781449f81e9a@mail.gmail.com> Date: Sun, 20 Apr 2008 23:16:28 -0400 From: "Andrew Paprocki" To: LKML Subject: Re: kernel BUG at /usr/src/linux-2.6.25/kernel/workqueue.c:224! (r8169?) Cc: shuchen@realtek.com.tw, "Francois Romieu" , netdev@vger.kernel.org In-Reply-To: <76366b180804201548g309ae6cci286ed6552f3cb71e@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <76366b180804201548g309ae6cci286ed6552f3cb71e@mail.gmail.com> X-Google-Sender-Auth: 42a9d21e2eb0c850 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org I just received a similar bug on workqueue.c:223 while I was not doing anything with the card. These bugs seem to have increased with frequency when running under 2.6.25. It used to take me some time to cause a problem to appear under 2.6.24, but under 2.6.25 they appear very readily. I was actually not touching the machine at all when this appeared on the console: r8169: eth0: link up r8169: eth0: link up r8169: eth0: link up r8169: eth0: link up r8169: eth0: link up r8169: eth0: link up r8169: eth0: link up r8169: eth0: link up ------------[ cut here ]------------ kernel BUG at /usr/src/linux-2.6.25/kernel/workqueue.c:223! invalid opcode: 0000 [#1] Pid: 4, comm: events/0 Not tainted (2.6.25 #2) EIP: 0060:[] EFLAGS: 00010286 CPU: 0 EIP is at queue_delayed_work_on+0x1c/0x7b EAX: 00000000 EBX: cf0ae9f0 ECX: cf0ae9e0 EDX: 00000000 ESI: cf002840 EDI: ffffffff EBP: cf0ae360 ESP: cf037ea4 DS: 007b ES: 007b FS: 0000 GS: 0000 SS: 0068 Process events/0 (pid: 4, ti=cf036000 task=cf02e590 task.ti=cf036000) Stack: cf0b7400 cf0ae000 cf0ae360 c02234cb 00000004 c037a1a5 d002e03e 00000050 00000014 d002e000 d002e03e d002e000 cf1d6000 cf0f8400 c2b00157 cf1c9c80 00000080 00000001 0000000a c0230811 c0537ae0 0000000a 00000000 0000000a Call Trace: [] queue_delayed_work+0x16/0x18 [] rtl8169_interrupt+0x1bb/0x2ef [] handle_IRQ_event+0x1a/0x3f [] handle_level_irq+0x7a/0x8a [] do_IRQ+0x4b/0x60 [] common_interrupt+0x23/0x28 [] elevator_init+0x5a/0xcd [] kfree+0x6a/0x6e [] __kfree_skb+0x8/0x61 [] rtl8169_rx_clear+0x1f/0x48 [] rtl8169_close+0x13/0x67 [] rtl8169_reinit_task+0x25/0x64 [] rtl8169_reinit_task+0x0/0x64 [] run_workqueue+0x63/0xca [] worker_thread+0x0/0xb7 [] worker_thread+0xac/0xb7 [] autoremove_wake_function+0x0/0x2b [] worker_thread+0x0/0xb7 [] kthread+0x36/0x5b [] kthread+0x0/0x5b [] kernel_thread_helper+0x7/0x10 ======================= Code: 8d 50 10 e9 46 ff ff ff 31 d2 e9 3f ff ff ff 57 89 c7 56 89 d6 53 8d 59 1 EIP: [] queue_delayed_work_on+0x1c/0x7b SS:ESP 0068:cf037ea4 Kernel panic - not syncing: Fatal exception in interrupt On Sun, Apr 20, 2008 at 6:48 PM, Andrew Paprocki wrote: > I received this while testing the network card on a AMD Geode LX800 board. > (cat /dev/zero | nc remote-host remote-port) The machine config is attached. > > ------------[ cut here ]------------ > kernel BUG at /usr/src/linux-2.6.25/kernel/workqueue.c:224! > invalid opcode: 0000 [#1] > > Pid: 719, comm: nc Not tainted (2.6.25 #2) > EIP: 0060:[] EFLAGS: 00010283 CPU: 0 > EIP is at queue_delayed_work_on+0x28/0x7b > EAX: cf0ae9e4 EBX: cf0ae9f0 ECX: cf0ae9e0 EDX: 00000000 > ESI: cf002840 EDI: ffffffff EBP: cf0ae360 ESP: cc07fd08 > DS: 007b ES: 007b FS: 0000 GS: 0033 SS: 0068 > Process nc (pid: 719, ti=cc07e000 task=ce7b73f0 task.ti=cc07e000) > Stack: cf059400 cf0ae000 cf0ae360 c02234cb 00000004 c037a1a5 d002e03e 00000050 > 00000014 d002e000 d002e03e d002e000 cf0cc000 cf0f8400 c2b00157 cf1c9c80 > 00000080 00000001 0000000a c0230811 c0537ae0 0000000a 00000000 0000000a > Call Trace: > [] queue_delayed_work+0x16/0x18 > [] rtl8169_interrupt+0x1bb/0x2ef > [] handle_IRQ_event+0x1a/0x3f > [] handle_level_irq+0x7a/0x8a > [] do_IRQ+0x4b/0x60 > [] common_interrupt+0x23/0x28 > [] tcp_recvmsg+0x475/0x6cc > [] tcp_rcv_established+0x42/0x611 > [] tcp_v4_do_rcv+0x1f/0x13f > [] release_sock+0x30/0x6c > [] tcp_sendmsg+0x896/0x96e > [] __wake_up_common+0x2d/0x52 > [] sock_aio_write+0xb2/0xbb > [] do_sync_write+0xbd/0x104 > [] autoremove_wake_function+0x0/0x2b > [] ktime_get_ts+0x11/0x3a > [] ktime_get+0xf/0x2b > [] hrtick_start_fair+0xb3/0xec > [] vfs_write+0x94/0xfc > [] sys_write+0x3c/0x63 > [] syscall_call+0x7/0xb > ======================= > Code: ff ff ff 57 89 c7 56 89 d6 53 8d 59 10 0f ba 29 00 19 c0 31 d2 85 c0 75 5 > EIP: [] queue_delayed_work_on+0x28/0x7b SS:ESP 0068:cc07fd08 > Kernel panic - not syncing: Fatal exception in interrupt >