- To: outages-list@eskimo.com
- Subject: Eskinews Linux 2.2.1
- From: Robert Dinse <nanook@eskimo.com>
- Date: Sat, 30 Jan 1999 16:51:50 -0800 (PST)
- Resent-Date: Sat, 30 Jan 1999 16:51:53 -0800
- Resent-From: outages-list@eskimo.com
- Resent-Message-ID: <"XwMED.0.QA4.eawis"@mx1>
- Resent-Sender: outages-list-request@eskimo.com
- Prev by Date: Eskinews - Booted Linux 2.2.1
- Next by Date: UUCP Problems
- Prev by thread: UUCP Problems
- Next by thread: Eskinews - Booted Linux 2.2.1
- Index(es):
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Eskinews Linux 2.2.1
Unfortunately, 2.2.1 crashed and burned today with scrolling read_lock at
(hex address) CPU x (where CPU x alternated between 0 and 1). Nothing short of
power cycling would interrupt this scrolling message, and as a consequence
eskinews is now doing fsck's on all the partitions which takes anywhere from 45
minutes to an hour and a half depending on how much stuff is trashed.
Apparently the SMP code in 2.2.x isn't there yet.