From: Jay Cliburn <jacliburn@bellsouth.net>
To: Arjan van de Ven <arjan@infradead.org>
Cc: linux-kernel@vger.kernel.org, torvalds@linux-foundation.org,
netdev@vger.kernel.org, tglx@tglx.de, mingo@elte.hu,
linux-acpi@vger.kernel.org, linux-scsi@vger.kernel.org
Subject: Re: Warning/Oops report of the week of September 16th, 2008
Date: Tue, 16 Sep 2008 19:40:47 -0500 [thread overview]
Message-ID: <20080916194047.0d23eb92@osprey.hogchain.net> (raw)
In-Reply-To: <20080916092206.6342c498@infradead.org>
On Tue, 16 Sep 2008 09:22:06 -0700
Arjan van de Ven <arjan@infradead.org> wrote:
> Not yet fixed issues
> ====================
>
> Rank 1: dev_watchdog (warning)
> Reported 263 times (495 total reports)
> Network card timeout; this error is currently not specific
> enough, a patch is pending to get this reported per driver, with some
> luck this gets merged soon. This warning was last seen in version
> 2.6.27-rc6, and first seen in 2.6.26-rc3. More info:
> http://www.kerneloops.org/searchweek.php?search=dev_watchdog
Some of these are undoubtedly from the atl1 driver, and many of those
from that driver are probably from me personally as I've poked around
trying to isolate the cause. I sent a patch yesterday to Alexey
Dobriyan (who's also been experiencing it) that seems to quash the
warnings, so hopefully we're near resolution. On my own development
system I recently turned off kerneloops, so at least *my* contribution
to the list will diminish. :)
Jay
prev parent reply other threads:[~2008-09-17 0:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-16 16:22 Warning/Oops report of the week of September 16th, 2008 Arjan van de Ven
2008-09-17 0:40 ` Jay Cliburn [this message]
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=20080916194047.0d23eb92@osprey.hogchain.net \
--to=jacliburn@bellsouth.net \
--cc=arjan@infradead.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=netdev@vger.kernel.org \
--cc=tglx@tglx.de \
--cc=torvalds@linux-foundation.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox