This message generated a parse failure. Raw output follows here. Please use 'back' to navigate. From devnull@lkml.org Wed May 22 04:26:06 2024 Received: from nic2.funet.fi (nic2.funet.fi [128.214.248.46]) by herbie.ucs.indiana.edu (8.9.3/8.9.3) with ESMTP id LAA05713 for ; Wed, 20 Oct 1999 11:00:39 -0500 (EST) Received: from vger.rutgers.edu ([128.6.190.2]:9894 "EHLO vger.rutgers.edu") by nic2.funet.fi with ESMTP id ; Wed, 20 Oct 1999 19:00:01 +0300 Received: by vger.rutgers.edu via listexpand id ; Wed, 20 Oct 1999 11:57:23 -0400 Received: by vger.rutgers.edu id ; Wed, 20 Oct 1999 11:56:58 -0400 Received: from home.desertinternet.com ([208.246.162.10]:1927 "EHLO home.desertinternet.com") by vger.rutgers.edu with ESMTP id convert rfc822-to-8bit; Wed, 20 Oct 1999 11:54:41 -0400 Received: (from soren@localhost) by home.desertinternet.com (8.9.3/8.9.3) id IAA27650 for linux-kernel@vger.rutgers.edu; Wed, 20 Oct 1999 08:54:09 -0700 Date: Wed, 20 Oct 1999 08:54:09 -0700 From: "Leiden, Soren" To: linux-kernel Subject: Re: 2.3.22: Crash with "kernel BUG at sched.c:573!" Message-Id: <19991020085409.A27582@desertinternet.com> Mail-Followup-To: linux-kernel References: <380DE1C9.3A3A84BA@a2zis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8BIT X-Mailer: Mutt 0.95.5i In-Reply-To: <380DE1C9.3A3A84BA@a2zis.com> Sender: owner-linux-kernel@vger.rutgers.edu Precedence: bulk X-Loop: majordomo@vger.rutgers.edu X-Orcpt: rfc822;linux-kernel-outgoing-dig Remi, This's a known problem with 2.3.22. Applying things @ ftp://ftp.us.kernel.org/pub/linux/kernel/people/andrea/patches/v2.3/2.3.22/ will solve your problem. Remi Turk [remi@a2zis.com] wrote: > Hi folks, > while playing with 2.3.22 my system crashed. > it doesn't boot normally, (silent hardlock, no oops etc) > so I booted with init=/bin/sh > it works, but: > When I mounted /proc, started en terminated top it crashed > with a "Unable to handle kernel paging request at bfff3ebd" > with EIP bfffff24 and "Aiee, killing interrupt handler. > Sadly I wasn't able to write it down. After some testing > I couldn't reproduce it anymore, but I got another problem. > After doing the following, I got an oops and a hardlock (SysRQ didn't > work anymore): > (boot with init=/bin/sh) > $ mount /proc > $ ps > $ ps > $ ps > $ some_command (I tried `ls', `ps', `cat' and `file') -- Soren - 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/