Am Dienstag 27 November 2007 schrieb ming lei:
> It seems oom happenes when VM(page frame reclaim) try to reclaim much
> more memory by writing back dirty pages, but there is not enough ram
> for usb disk related driver to finish the writeback operation. (usb
> disk related driver: scsi_mod, usb
When you untar, which filesystem do you untar too?
I've untarred it to Ext3, Ext2, and Reiser filesystems. I've been fighting
with this for a while.
I did manage to get it to happen again doing a recursive chmod after
untarring the kernel (I stopped the untar a few times to let the system
catch
Hi,
I have some similar problems on a completely unrelated system, but i
still wonder.
When you untar, which filesystem do you untar too?
--
Ian Kumlien -- http://pomac.netswarm.net
signature.asc
Description: This is a digitally signed message part
It seems oom happenes when VM(page frame reclaim) try to reclaim much
more memory by writing back dirty pages, but there is not enough ram
for usb disk related driver to finish the writeback operation. (usb
disk related driver: scsi_mod, usb mass storage, usbcore and uhci or
ehci )
You can try
Josh Goldsmith wrote:
David: The exact command this time was a "tar jxf
linux-2.6.23.tar.bz2" as part of an emerge (gentoo). Gnu tar version
1.18 but has happened with prior versions too. I replicated it after
my post by manually untarring it on the command line and can almost
always replic
EMAIL PROTECTED]>
To: "Josh Goldsmith" <[EMAIL PROTECTED]>
Cc:
Sent: Monday, November 26, 2007 4:57 AM
Subject: Re: Small System Paging Problem - OOM-killer goes nuts
Josh Goldsmith wrote:
The problem comes when I try to untar a large file (in this case
linux-2.6.23.tar.bz2)
On Sun 2007-11-25 22:28:03, Josh Goldsmith wrote:
> Thanks for the response Mikael.
>
> Is your 486 running a IDE disk on a normal interface or
> via USB? I wonder if the NSLU2 only having I/O via USB
> might be significant. Also, this is a 2.6 kernel and
I'd suspect USB is significant here.
Josh Goldsmith wrote:
The problem comes when I try to untar a large file (in this case
linux-2.6.23.tar.bz2). Regardless if I kill off every other process,
eventually the oom-killer will appear and kill either the tar or the
shell.
What's the actual command you are executing?
-
To unsubscrib
On Sun, 25 Nov 2007 22:28:03 -0700, Josh Goldsmith wrote:
> Is your 486 running a IDE disk on a normal interface or via USB? I wonder
> if the NSLU2 only having I/O via USB might be significant.
My 486 has neither PCI nor USB, the disk is attached to a
plain ancient IDE port.
> Also, this is a
about 2.6.7.
Thanks!
-Josh
- Original Message -
From: "Mikael Pettersson" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>;
Sent: Sunday, November 25, 2007 3:55 PM
Subject: Re: Small System Paging Problem - OOM-killer goes nuts
I'm no VM tuning expert, but I
On Sun, 25 Nov 2007 15:02:15 -0700, Josh Goldsmith wrote:
> I have a Linksys NSLU2 running 2.6.21 (I can replicate the problem on
> 2.6.23 but it isn't fully supported on SlugOS). It is a armv5teb device
> with 32MB of RAM, 400+ MB swap on its 160GB USB2 root disk. The machine is
> used as a
Hi,
I have a Linksys NSLU2 running 2.6.21 (I can replicate the problem on
2.6.23 but it isn't fully supported on SlugOS). It is a armv5teb device
with 32MB of RAM, 400+ MB swap on its 160GB USB2 root disk. The machine is
used as a fileserver and to build packages for other ARM devices. It
12 matches
Mail list logo
