From: "Nick Warne" <nick@ukfsn.org>
To: OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>,
linux-kernel@vger.kernel.org
Subject: Re: 2.6.3 - 8139too timeout debug info
Date: Sun, 29 Feb 2004 11:09:15 -0000 [thread overview]
Message-ID: <4041C85B.30333.2D21C847@localhost> (raw)
In-Reply-To: <87llmmtihe.fsf@devron.myhome.or.jp>
> > Umm.. Looks like chip registers is normal, but TX/RX interrupt doesn't
> > happen. (BTW, there isn't rtl8139_open on debuginfo.txt. Was it already
> > scrolled?)
> >
> > The following patch (incremental patch) is some part reverts to
> > 2.6.2. Is behavior changed?
>
> Oops, wrong patches. Please try these.
OK, I applied patch01 first - same problems. Then I applied patch02
_over_ patch01. Still same results.
I am not sure if you meant me to apply over the first debug patch you
sent? Here, I just applied to standard 2.6.3 > 8139too.c file with
RTL8139_NDEBUG 1 set.
With these patched dmesg gets flooded - and I have real trouble
trying to do anything on the box with the timeout issues.
http://www.linicks.net/8139too_debug/patch01_02_info.txt
Thanks,
Nick
--
"When you're chewing on life's gristle,
Don't grumble, Give a whistle..."
next prev parent reply other threads:[~2004-02-29 11:09 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-27 17:31 2.6.3 - 8139too timeout debug info Nick Warne
2004-02-27 17:40 ` Matt H.
2004-02-27 17:50 ` Nick Warne
2004-02-28 17:41 ` OGAWA Hirofumi
2004-02-28 18:47 ` Nick Warne
2004-02-29 7:58 ` OGAWA Hirofumi
2004-02-29 8:09 ` OGAWA Hirofumi
2004-02-29 11:09 ` Nick Warne [this message]
[not found] <4041BAA6.28283.2CEC419B@localhost>
[not found] ` <87fzcut9ua.fsf@devron.myhome.or.jp>
2004-02-29 11:57 ` Nick Warne
2004-02-29 12:38 ` OGAWA Hirofumi
2004-02-29 13:05 ` Nick Warne
2004-02-29 18:28 ` OGAWA Hirofumi
2004-03-01 18:29 ` Nick Warne
2004-03-22 21:17 ` Jeff Garzik
2004-03-22 22:51 ` OGAWA Hirofumi
2004-03-31 19:42 ` Christian Gut
2004-04-01 3:56 ` OGAWA Hirofumi
2004-04-04 17:02 ` OGAWA Hirofumi
-- strict thread matches above, loose matches on Subject: below --
2004-03-23 21:07 Nick Warne
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=4041C85B.30333.2D21C847@localhost \
--to=nick@ukfsn.org \
--cc=hirofumi@mail.parknet.co.jp \
--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 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.