From: Mikael Bouillot <xaajimri@corbac.com>
To: linux-kernel@vger.kernel.org
Cc: Carl-Daniel Hailfinger <c-d.hailfinger.kernel.2004@gmx.net>
Subject: Re: Forcedeth driver bug
Date: Wed, 23 Jun 2004 17:02:39 +0000 [thread overview]
Message-ID: <20040623170239.GA12050@mail.nute.net> (raw)
In-Reply-To: <40D9A857.5040901@gmx.net>
> forcedeth_gigabit_try19.txt is the most recent one.
OK, I've tried forcedeth_gigabit_try19 and I still get the same
problem. The only difference is a "bad: scheduling while atomic!" in the
syslog, but I still get stuck packets.
I've also tried reverting to the older XT-PIC and again, no
improvement.
I'll now try to work my way through debugging the problem myself. I've
got limited experience with kernel hacking, but I'll learn along the way
:-) If anyone has got any new information or suggestion, I would like to
hear about it.
Mikael
--
Hi! I'm a .signature virus! Copy me into your ~/.signature to help me spread!
next prev parent reply other threads:[~2004-06-23 17:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-23 14:29 Forcedeth driver bug Mikael Bouillot
2004-06-23 14:46 ` Martin Zwickel
2004-06-23 16:04 ` Mikael Bouillot
2004-06-23 14:56 ` Kalin KOZHUHAROV
2004-06-23 15:57 ` Carl-Daniel Hailfinger
2004-06-23 16:14 ` Mikael Bouillot
2004-06-23 17:02 ` Mikael Bouillot [this message]
2004-07-24 12:37 ` Carl-Daniel Hailfinger
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=20040623170239.GA12050@mail.nute.net \
--to=xaajimri@corbac.com \
--cc=c-d.hailfinger.kernel.2004@gmx.net \
--cc=linux-kernel@vger.kernel.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