From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755283Ab1GVTpJ (ORCPT ); Fri, 22 Jul 2011 15:45:09 -0400 Received: from mail.candelatech.com ([208.74.158.172]:40738 "EHLO ns3.lanforge.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755134Ab1GVTpH (ORCPT ); Fri, 22 Jul 2011 15:45:07 -0400 Message-ID: <4E29D326.7070403@candelatech.com> Date: Fri, 22 Jul 2011 12:44:38 -0700 From: Ben Greear Organization: Candela Technologies User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.9) Gecko/20100430 Fedora/3.0.4-2.fc11 Thunderbird/3.0.4 MIME-Version: 1.0 To: Linus Torvalds CC: David , Linux Kernel Mailing List , netdev@vger.kernel.org Subject: Re: Linux 3.0 release References: <4E29CB5B.4040408@unsolicited.net> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 07/22/2011 12:21 PM, Linus Torvalds wrote: > On Fri, Jul 22, 2011 at 12:11 PM, David wrote: >> >> I'm getting the following warning at boot from 3.0, everything seems to be fine otherwise though. >> >> Jul 22 19:40:02 server kernel: [ 15.526629] ------------[ cut here ]------------ >> Jul 22 19:40:02 server kernel: [ 15.526635] WARNING: at kernel/timer.c:1011 del_timer_sync+0x4e/0x50() > > Hmm. That looks like a real bug: you shouldn't do a "del_timer_sync()" > from an interrupt. It probably works, but it sounds like a really bad > idea. > >> Jul 22 19:40:02 server kernel: [ 15.526677] [] del_timer_sync+0x4e/0x50 >> Jul 22 19:40:02 server kernel: [ 15.526679] [] linkwatch_schedule_work+0x84/0xa0 >> Jul 22 19:40:02 server kernel: [ 15.526681] [] linkwatch_fire_event+0x7c/0x100 >> Jul 22 19:40:02 server kernel: [ 15.526684] [] netif_carrier_on+0x2d/0x40 >> Jul 22 19:40:02 server kernel: [ 15.526689] [] __rtl8169_check_link_status+0x4b/0xc0 [r8169] >> Jul 22 19:40:02 server kernel: [ 15.526693] [] rtl8169_interrupt+0x166/0x3a0 [r8169] >> Jul 22 19:40:02 server kernel: [ 15.526696] [] handle_irq_event_percpu+0x55/0x1f0 >> Jul 22 19:40:02 server kernel: [ 15.526698] [] handle_irq_event+0x31/0x50 > > I'm not seeing a lot of changes in any of these areas, though. I > wonder what made it start happen. This has been around since at least 2.6.38. I haven't tested recently on my rtl8169 system, but I don't recall seeing any attempts to fix it... http://permalink.gmane.org/gmane.linux.network/193565 http://lists.openwall.net/netdev/2011/05/04/183 Thanks, Ben -- Ben Greear Candela Technologies Inc http://www.candelatech.com