From: Andries Brouwer <aebr@win.tue.nl>
To: linux-os@analogic.com
Cc: Linux kernel <linux-kernel@vger.kernel.org>
Subject: Re: Joe User DOS kills Linux-2.6.10
Date: Thu, 3 Feb 2005 01:33:34 +0100 [thread overview]
Message-ID: <20050203003334.GA5680@pclin040.win.tue.nl> (raw)
In-Reply-To: <Pine.LNX.4.61.0502021314340.5410@chaos.analogic.com>
On Wed, Feb 02, 2005 at 01:23:43PM -0500, linux-os wrote:
>
> When I compile and run the following program:
>
> #include <stdio.h>
> int main(int x, char **y)
> {
> pause();
> }
> ... as:
>
> ./xxx `yes`
>
> ... the following occurs after about 30 seconds (your mileage
> may vary):
>
> Additional sense: Peripheral device write fault
> end_request: I/O error, dev sdb, sector 34605780
> SCSI error : <0 0 1 0> return code = 0x8000002
> Info fld=0x2100101, Deferred sdb: sense key Medium Error
> Additional sense: Peripheral device write fault
> end_request: I/O error, dev sdb, sector 34603748
> SCSI error : <0 0 1 0> return code = 0x8000002
> Info fld=0x2100103, Deferred sdb: sense key Medium Error
When I run "sleep `yes`" under bash, all of swap space is filled,
and then bash says "realloc error ..." and exits.
No kernel problem, no bad bash problem.
If you do not run vm overcommit mode 2 then probably your bash
will be killed by the OOM killer, and if you are unlucky some
other stuff might be killed as well.
Concerning the SCSI errors, looks like you might have disk problems.
Bad blocks in your swap space. Recheck the disk.
Andries
next prev parent reply other threads:[~2005-02-03 0:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-02 18:23 linux-os
2005-02-02 18:35 ` linux-os
2005-02-02 18:44 ` Andreas Schwab
2005-02-02 18:49 ` Rik van Riel
2005-02-03 0:33 ` Andries Brouwer [this message]
2005-02-03 12:28 ` linux-os
2005-02-03 14:29 ` Andries Brouwer
2005-02-03 14:37 ` linux-os
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=20050203003334.GA5680@pclin040.win.tue.nl \
--to=aebr@win.tue.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-os@analogic.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®