From: Chase Venters <chase.venters@clientec.com>
To: Kalin KOZHUHAROV <kalin@thinrope.net>
Cc: linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org
Subject: Re: OOM Killer killing whole system
Date: Sun, 22 Jan 2006 21:28:50 -0600 [thread overview]
Message-ID: <200601222129.12882.chase.venters@clientec.com> (raw)
In-Reply-To: <dr1gl8$tec$1@sea.gmane.org>
On Sunday 22 January 2006 20:56, Kalin KOZHUHAROV wrote:
> I have two of these boards and one of them is constantly hanging, just
> simply dead. With 2.6.15 it reports failed I/O (SATA here) and mounts
> reiserfs root RO. sky2 works for me, but I had another hang, so sk98lin
> might not be the culprit.
Really? I had serious problems with mine hanging in earlier kernel revisions.
I haven't seen a hang yet on 2.6.15, but that may be because I've not made it
to a longer uptime because of the scsi leak.
When I hang I get complaints about DMA timeouts / weird ATA port statuses as
the last messages on my serial console. After that, not even SysRQ works.
Cheers,
Chase
next prev parent reply other threads:[~2006-01-23 3:28 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-15 15:05 OOM Killer killing whole system Anton Titov
2006-01-20 12:11 ` Andrew Morton
2006-01-20 20:04 ` Chase Venters
2006-01-20 21:48 ` Anton Titov
2006-01-20 22:50 ` Andrew Morton
2006-01-21 0:09 ` Anton Titov
2006-01-21 0:19 ` Chase Venters
2006-01-21 0:50 ` Andrew Morton
2006-01-21 1:17 ` James Bottomley
2006-01-21 3:29 ` Anton Titov
2006-01-21 3:44 ` Andrew Morton
2006-01-25 22:20 ` Matthias Urlichs
2006-01-21 3:45 ` Anton Titov
2006-01-21 3:53 ` Chase Venters
2006-01-21 4:21 ` Anton Titov
2006-01-21 4:35 ` Chase Venters
2006-01-23 2:56 ` Kalin KOZHUHAROV
2006-01-23 3:28 ` Chase Venters [this message]
2006-01-23 8:39 ` Jens Axboe
2006-01-23 8:41 ` Arjan van de Ven
2006-01-23 9:10 ` Chase Venters
-- strict thread matches above, loose matches on Subject: below --
2006-01-23 12:55 Nicolas Mailhot
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=200601222129.12882.chase.venters@clientec.com \
--to=chase.venters@clientec.com \
--cc=kalin@thinrope.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@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.