mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jean Tourrilhes <jt@bougret.hpl.hp.com>
To: Linux kernel mailing list <linux-kernel@vger.rutgers.edu>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>
Subject: Re: My computer doesn't like 2.3.X [2.3.99-pre6 still flaky]
Date: Thu, 27 Apr 2000 09:25:52 -0700	[thread overview]
Message-ID: <20000427092552.B19008@bougret.hpl.hp.com> (raw)
In-Reply-To: <20000426125056.A12819@bougret.hpl.hp.com>; from jt on Wed, Apr 26, 2000 at 12:50:56PM -0700

On Wed, Apr 26, 2000 at 12:50:56PM -0700, Jean Tourrilhes wrote:
>
> 	2d) If I do some kernel compilation, big ftp or other stuff, I
> can also crash the box without effort. Oops look the same.

	Full of hopes, I did upgrade to the latest kernel
(2.3.99-pre6). The kernel seems sligthly better, but it is still
ridiculously easy to crash.

	Let say that I have a directory with a few kernel tarballs (in
tar.gz form), or probably anything else big (few dozen MB). One kernel
is not enough, but 2 will do nicely. Add a few more kernels if you
have more RAM or just to make sure...
	If I do :
--------
ftp 127.0.0.1
cd kernels
prompt
mget *
--------
	I get :
--------------------------------
stack segment: 0000
CPU:    0
EIP:    0010:[kmem_cache_grow+811/1036]
EFLAGS: 00010296
eax: 00000073   ebx: c00edfe0   ecx: 00000000   edx: 0000001d
esi: c11279e0   edi: c00ed060   ebp: ffffffff   esp: c3155de8
ds: 0018   es: 0018   ss: 0018
Process wu-ftpd (pid: 201, stackpage=c3155000)
Stack: c11279e8 c11279e0 00000003 00000282 c00ed158 c11279e8 c00ed060 0000001d 
       00000000 00000202 00000001 00000003 00000060 c0125f8b c11279e0 00000003 
       c0225f00 00000000 c0225f00 00000400 c012cecd c11279e0 00000003 c0225f00 
Call Trace: [kmem_cache_alloc+375/456] [get_unused_buffer_head+57/184] [create_buffers+32/784] [create_empty_buffers+24/112] [block_read_full_page+92/532] [add_to_page_cache_unique+205/316] [ext2_readpage+15/20] 
       [ext2_get_block+0/1164] [generic_file_readahead+522/728] [do_generic_file_read+644/1244] [generic_file_read+99/128] [file_read_actor+0/136] [sys_read+192/224] [system_call+52/56] [startup_32+43/309] 
Code: 89 45 00 8b 6d 00 83 6c 24 1c 01 0f 83 04 ff ff ff c7 45 00 
--------------------------------

	That's all...

	Jean

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/

           reply	other threads:[~2000-04-27 16:31 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <20000426125056.A12819@bougret.hpl.hp.com>]

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=20000427092552.B19008@bougret.hpl.hp.com \
    --to=jt@bougret.hpl.hp.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=jt@hpl.hp.com \
    --cc=linux-kernel@vger.rutgers.edu \
    /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®