All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Alex Villací­s Lasso" <a_villacis@palosanto.com>
To: netdev@vger.kernel.org, Francois Romieu <romieu@fr.zoreil.com>
Subject: Re: Fwd: Re: WARNING: at net/sched/sch_generic.c:256 dev_watchdog+0x277/0x280()
Date: Fri, 04 May 2012 09:57:13 -0500	[thread overview]
Message-ID: <4FA3EE49.7070805@palosanto.com> (raw)
In-Reply-To: <4FA2A6A4.1030308@ceibo.fiec.espol.edu.ec>

(Resending to netdev@vger.kernel.org since previous attempt was rejected as spam)

El 03/05/12 10:39, Alex Villací­s Lasso escribió:
> Alex Villací­s Lasso<avillaci@fiec.espol.edu.ec>  :
> [...]
> >  I am currently away from the target computer. How should I check for this? lspci?
>
> lspci can not tell much. Use 'dmesg | grep XID' instead.
[alex@karlalex linux-git]$ dmesg | grep -i xid
[   10.647557] r8169 0000:02:00.0: eth0: RTL8168b/8111b at 0xffffc90000352000, 00:22:68:44:17:2f, XID 98500000 IRQ 43
> A complete dmesg would be welcome.
>
> It could help to know a few things :
> - does the problem qualify as a regression since some kernel version ?
>    If so which one ?
I have only seen these messages since 3.4-rc1. Vanilla kernels up to 3.3, and stock Fedora 16 kernels (kernel-3.3.2-6.fc16.x86_64) did not display this problem. However, I cannot confirm that the latest stock kernel is free from the message, since I prefer 
to run the latest RC kernel on my home machine.
> - can it be reproduced with a kernel that has not been vbox tainted ?
I will check this. However, since the message only appears after an hour of so of moderate bittorrent traffic, it might take a while to confirm.
> - does networking recover ?
It does recover, after a few seconds.
>
> Thanks.
>
> -- 
> Ueimor
>

  parent reply	other threads:[~2012-05-04 14:57 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-21 17:21 WARNING: at net/sched/sch_generic.c:256 dev_watchdog+0x277/0x280() Alex Villací­s Lasso
2012-05-02 19:20 ` Alex Villací­s Lasso
2012-05-02 22:52   ` Francois Romieu
2012-05-02 23:28     ` Alex Villací­s Lasso
2012-05-03  6:47       ` Francois Romieu
     [not found]         ` <4FA2A6A4.1030308@ceibo.fiec.espol.edu.ec>
2012-05-04 14:57           ` Alex Villací­s Lasso [this message]
2012-05-05 21:44             ` Fwd: " Alex Villacís Lasso
2012-05-05 23:01               ` Francois Romieu
2012-05-24 15:26                 ` Alex Villací­s Lasso
2012-05-26 10:11                   ` Francois Romieu
2012-05-29  3:31                     ` Alex Villacís Lasso
     [not found]     ` <4FA1C34C.6080909@fiec.espol.edu.ec>
2012-05-03  0:44       ` Alex Villací­s Lasso
2012-05-02 19:26 ` Alex Villací­s Lasso

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4FA3EE49.7070805@palosanto.com \
    --to=a_villacis@palosanto.com \
    --cc=netdev@vger.kernel.org \
    --cc=romieu@fr.zoreil.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.