netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Francois Romieu <romieu@fr.zoreil.com>
To: Martin Michlmayr <tbm@cyrius.com>
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: de2104x: interrupts before interrupt handler is registered
Date: Wed, 8 Mar 2006 01:15:56 +0100	[thread overview]
Message-ID: <20060308001556.GA9362@electric-eye.fr.zoreil.com> (raw)
In-Reply-To: <20060307051152.GA1244@deprecation.cyrius.com>

Martin Michlmayr <tbm@cyrius.com> :
[...]
> It seems to help.  It's hard to say for sure because I don't have a
> foolproof way to reproduce this panic.  It _usually_ occurs after
> copying a few hundred MB but there's no clear trigger.  I've now copied
> a few GB around using a kernel with your patch and it hasn't crashed.

netdev watchdog events appear in the dmesg of the patched driver.
The driver survived it. So I'd say that the patch does its job.

OTOH, if you ever saw the unpatched driver survive this event, yell now.

-- 
Ueimor

  parent reply	other threads:[~2006-03-08  0:15 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-05 18:07 de2104x: interrupts before interrupt handler is registered Martin Michlmayr
2006-03-05 18:59 ` Francois Romieu
2006-03-06 14:35   ` Martin Michlmayr
2006-03-06 19:17     ` Martin Michlmayr
2006-03-06 19:48       ` Francois Romieu
2006-03-06 19:59         ` Martin Michlmayr
2006-03-06 20:23           ` Francois Romieu
2006-03-06 20:29             ` Martin Michlmayr
2006-03-06 20:54           ` Francois Romieu
2006-03-07  5:16             ` Martin Michlmayr
2006-03-06 21:17       ` Francois Romieu
2006-03-07  5:11         ` Martin Michlmayr
2006-03-07 14:57           ` Martin Michlmayr
2006-03-08  0:15           ` Francois Romieu [this message]
2006-03-08  3:22             ` Martin Michlmayr
2006-03-07 15:16       ` Martin Michlmayr
2006-03-06 13:02 ` linux-os (Dick Johnson)

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=20060308001556.GA9362@electric-eye.fr.zoreil.com \
    --to=romieu@fr.zoreil.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=tbm@cyrius.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).