All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nix <nix@esperi.demon.co.uk>
To: Ketil Froyn <kernel@ketil.froyn.name>
Cc: Linux Kernel Development <linux-kernel@vger.kernel.org>
Subject: Re: Weird time-warping with linux-2.4.20/i586/gcc-2.95.4pre
Date: 25 Feb 2003 08:34:24 +0000	[thread overview]
Message-ID: <87fzqc4v3j.fsf@amaterasu.srvr.nix> (raw)
In-Reply-To: <87of51cgyr.fsf@amaterasu.srvr.nix>

On 25 Feb 2003, nix@esperi.demon.co.uk spake:
> What a wonderful bug. :)

Regardless, heavy network load *does* crash this machine.

It crashed again last night, on the 4th track of a transfer of 26 of
Chopin's Mazurkas over 100Mbit Ethernet (3c905 card, still).

A totally useless

Feb 25 02:06:15 loki kernel: Unable to handle kernel paging request at virtual address 008001c3 
Feb 25 02:06:15 loki last message repeated 2 times

got logged this time. (Full oops? Whyever should I get that?)


My network card had been totally stable until today, and I never had any
problems before upgrading to 2.4.20 (although admittedly 2.4.20 was
problem-free too, for 30 days or so).

I'm really starting to wonder if I should revert to 2.4.19 :( with
unreproducible NFS problems on the UltraSPARC and now this... (FWIW, I
managed to get some *data* out of one of those NFS problems the other
day, when it sucked my mbox-format mailbox in and received garbage in it
place. The alleged `mailbox' looked very much like a Unix directory (one
of the directories on that filesystem, naturally; the fs is ext3)...)

-- 
2003-02-01: the day the STS died.

      reply	other threads:[~2003-02-25  8:51 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-25  0:01 Weird time-warping with linux-2.4.20/i586/gcc-2.95.4pre Nix
2003-02-24 23:23 ` Ketil Froyn
2003-02-25  1:00   ` Nix
2003-02-25  8:34     ` Nix [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=87fzqc4v3j.fsf@amaterasu.srvr.nix \
    --to=nix@esperi.demon.co.uk \
    --cc=kernel@ketil.froyn.name \
    --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.