All of lore.kernel.org
 help / color / mirror / Atom feed
From: George Garvey <tmwg-linuxknl@inxservices.com>
To: linux-kernel@vger.kernel.org
Subject: Re: Linux 2.4.13-ac4
Date: Mon, 29 Oct 2001 20:09:47 -0800	[thread overview]
Message-ID: <20011029200947.C14203@inxservices.com> (raw)
In-Reply-To: <20011028204003.A1640@lightning.swansea.linux.org.uk>
In-Reply-To: <20011028204003.A1640@lightning.swansea.linux.org.uk>; from laughing@shared-source.org on Sun, Oct 28, 2001 at 08:40:03PM +0000

   Just recently installed a dlink dge550t in P3 Asus CUV4X-E. Still has
vortex board installed, but not connected to LAN. Connected to 10/100
switch still.
   After switching to 2.4.13-ac4, short time after boot start getting
transmit timeout. No log, because that goes to another system on LAN.
Will reproduce if exact message is desired.
   Rebooted 2.4.13-ac4. Got timeout again shortly after.
   Rebooted back to 2.4.12-ac3. No problems for rest of day. Running
RML's preempt patch on both kernels: that's the only difference from ac
(except for nVidia driver module).
   Willing to get better information if this is worth pursuing.

  parent reply	other threads:[~2001-10-30  4:09 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-28 20:40 Linux 2.4.13-ac4 Alan Cox
2001-10-29  7:47 ` Vojtech Pavlik
2001-10-29 10:56   ` Alan Cox
2001-10-29 16:38     ` Vojtech Pavlik
2001-10-29 17:14       ` Henning P. Schmiedehausen
2001-10-29 17:28         ` Maciej W. Rozycki
2001-10-29 17:48     ` Vojtech Pavlik
2001-10-29 16:07 ` Maciej W. Rozycki
2001-10-29 16:19   ` Alan Cox
2001-10-29 20:03   ` Vojtech Pavlik
2001-10-30 11:23     ` Maciej W. Rozycki
2001-10-30  4:09 ` George Garvey [this message]
2001-10-30  4:24   ` Mike Fedyk
     [not found] <E15yFhL-0003ED-00@the-village.bc.nu>
2001-10-29 17:11 ` Maciej W. Rozycki

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=20011029200947.C14203@inxservices.com \
    --to=tmwg-linuxknl@inxservices.com \
    --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.