[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20080831171836.GA20894@electric-eye.fr.zoreil.com>
Date: Sun, 31 Aug 2008 19:18:36 +0200
From: Francois Romieu <romieu@...zoreil.com>
To: David Witbrodt <dawitbro@...global.net>
Cc: Yinghai Lu <yhlu.kernel@...il.com>, Ingo Molnar <mingo@...e.hu>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Thomas Gleixner <tglx@...utronix.de>,
"H. Peter Anvin" <hpa@...or.com>,
Andrew Morton <akpm@...ux-foundation.org>,
Jesse Barnes <jbarnes@...tuousgeek.org>,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH] x86: split e820 reserved entries record to late v2
David Witbrodt <dawitbro@...global.net> :
[...]
> ===== SETTERM OUTPUT =====
> Clocksource tsc unstable (delta = -98677795 ns)
> NETDEV WATCHDOG: eth0 (r8169): transmit timed out
> ------------[ cut here ]------------
> WARNING: at net/sched/sch_generic.c:221 dev_watchdog+0x21e/0x250()
> Modules linked in: ipv6 cpufreq_userspace pcspkr 8250_pnp 8250 serial_core evdev
> Pid: 0, comm: swapper Not tainted 2.6.27-rc4.080829.yh-patches-tip #1
> Call Trace:
[...]
> [<ffffffff8020a8d6>] cpu_idle+0x56/0xa0
> ---[ end trace 28095e4c2b529c2a ]---
> r8169: eth0: link up
> ===== END SETTERM OUTPUT =====
>
> Other than this strangeness, everything seems OK with your patches. This
> looks like some random networking annoyance to me, not really related to
> the regression patches, but I'll let better minds be the judge of that.
Could you enable CONFIG_PRINTK_TIME ?
Even if the networking driver manages to negotiate the link, this is
the kind of message which upsets people (myself included :o) ).
--
Ueimor
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists