On Thu, 3 Feb 2005, Andries Brouwer wrote:
On Thu, Feb 03, 2005 at 07:28:50AM -0500, linux-os wrote:
I ran badblocks (all night). There were none. It's a SCSI disk
and it requires chunks of DMA RAM for each write. The machine
just croaks when it gets low on RAM and tries to write to
SCSI swap
On Thu, Feb 03, 2005 at 07:28:50AM -0500, linux-os wrote:
> I ran badblocks (all night). There were none. It's a SCSI disk
> and it requires chunks of DMA RAM for each write. The machine
> just croaks when it gets low on RAM and tries to write to
> SCSI swap which requires RAM.
In some other
On Thu, 3 Feb 2005, Andries Brouwer wrote:
On Wed, Feb 02, 2005 at 01:23:43PM -0500, linux-os wrote:
When I compile and run the following program:
#include
int main(int x, char **y)
{
pause();
}
... as:
./xxx `yes`
... the following occurs after about 30 seconds (your mileage
may vary):
On Thu, 3 Feb 2005, Andries Brouwer wrote:
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
On Thu, Feb 03, 2005 at 07:28:50AM -0500, linux-os wrote:
I ran badblocks (all night). There were none. It's a SCSI disk
and it requires chunks of DMA RAM for each write. The machine
just croaks when it gets low on RAM and tries to write to
SCSI swap which requires RAM.
In some other post
On Thu, 3 Feb 2005, Andries Brouwer wrote:
On Thu, Feb 03, 2005 at 07:28:50AM -0500, linux-os wrote:
I ran badblocks (all night). There were none. It's a SCSI disk
and it requires chunks of DMA RAM for each write. The machine
just croaks when it gets low on RAM and tries to write to
SCSI swap
On Wed, Feb 02, 2005 at 01:23:43PM -0500, linux-os wrote:
>
> When I compile and run the following program:
>
> #include
> int main(int x, char **y)
> {
> pause();
> }
> ... as:
>
> ./xxx `yes`
>
> ... the following occurs after about 30 seconds (your mileage
> may vary):
>
> Additional
On Wed, 2 Feb 2005, linux-os wrote:
When I compile and run the following program:
./xxx `yes`
It looks like the program itself doesn't matter, since it's
bash that's eating up memory like crazy, until the point where
it is OOM killed.
PID USER PR NI VIRT RES SHR S %CPU %MEMTIME+
linux-os <[EMAIL PROTECTED]> writes:
> When I compile and run the following program:
>
> #include
> int main(int x, char **y)
> {
> pause();
> }
> ... as:
>
> ./xxx `yes`
This is roughly equivalent to this:
#include
int main(void) { while (1) malloc(1); }
Andreas.
--
Andreas Schwab,
Additional information:
My swap-file is also on /dev/sdb2. It appears as though swap
is being written beyond the end of the SCSI device and the
device doesn't like it. Also on a subsequent re-boot the
signature in the swap file had been destroyed so that swapon
didn't like it. I needed to use
When I compile and run the following program:
#include
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
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
Additional information:
My swap-file is also on /dev/sdb2. It appears as though swap
is being written beyond the end of the SCSI device and the
device doesn't like it. Also on a subsequent re-boot the
signature in the swap file had been destroyed so that swapon
didn't like it. I needed to use
On Wed, 2 Feb 2005, linux-os wrote:
When I compile and run the following program:
./xxx `yes`
It looks like the program itself doesn't matter, since it's
bash that's eating up memory like crazy, until the point where
it is OOM killed.
PID USER PR NI VIRT RES SHR S %CPU %MEMTIME+
linux-os [EMAIL PROTECTED] writes:
When I compile and run the following program:
#include stdio.h
int main(int x, char **y)
{
pause();
}
... as:
./xxx `yes`
This is roughly equivalent to this:
#include stdlib.h
int main(void) { while (1) malloc(1); }
Andreas.
--
Andreas Schwab,
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:
16 matches
Mail list logo
