Comment 7 for bug 7168

Message-ID: <email address hidden>
Date: Tue, 27 Jul 2004 00:38:05 +0200
From: Michelle Konzack <email address hidden>
To: Javier =?iso-8859-1?Q?Fern=E1ndez-Sanguino_Pe=F1a?= <email address hidden>,
 <email address hidden>
Subject: Re: Bug#255175: kernel-image-2.4.26-1-686: system crash due to kernel bug

--mI5TpPl/qDRoXxBg
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

Hello Javier,=20

I run some Intel pentium II with 233, 333 and 450 MHz with=20
2.4.26-1 and now 2.4.26-2. All two are working very well.=20

I have downloaded the new sources 2.4.26-4 and compiled it for a=20
FileServer (nfs, samba, netatalk, courier, proftpd, apache) and=20
the server has a very high load, because I compile via network.=20

It works very well...

Maybe you have a problem with your Hardware ?

Greetings
Michelle

Am 2004-07-26 20:57:19, schrieb Javier Fern=E1ndez-Sanguino Pe=F1a:
>severity 255175 critical
>thanks
>
>I upgraded some time ago the kernel-image to kernel-image-2.4.26-1-686,
>version 2.4.26-2 (in testing at the moment) and these oops appear
>frequently (I would even say that with a higher frequency that with
>previous version 2.4.26-1, but I have not investigated in depth). My system
>still crashes from time to time (it will not stay up for more than a week).
>It usually will start first spouting some 'Unable to handle kernel paging
>request at virtual address' oopses but it will keep running, however, at
>some point, and after some time (see attached syslog) it will start to send
>oops: 'kernel BUG at page_alloc.c:221!' (sometimes page_alloc.c:113)
>whenever a process is spawned, rendering the system unusable. In this
>situation only a hard reboot can make it recover.
>
>I'm consequently raising this bug's priority, because this kernel image
>makes the system quite unstable. I don't know if this affects version
>2.4.26-4 (in sid at the moment) too, it's not easy to reproduce, but I will
>install that kernel version and see what happens.
>
>Attached is a capture of the different oops I've encountered at different
>points before the system crash, these were copy&pasted directly from the
>screen. Also attached are the kernel oops that syslog recorded (as you can
>see, not all of them are included). Also, in case it's useful, I'm
>providing the output of ksymoops using this oops file. Most of the tasks
>associated with the oops are usually cron tasks and the system has plenty
>of swap space.
>
>If there is anything I can do to provide additional info, feel free to ask=
=2E=20
>Since I don't really know what causes it I'm at a loss in order to=20
>reproduce it.
>
>Thanks
>
>Javier

--=20
Linux-User #280138 with the Linux Counter, http://counter.li.org/=20
Michelle Konzack Apt. 917 ICQ #328449886
                   50, rue de Soultz MSM LinuxMichi
0033/3/88452356 67100 Strasbourg/France IRC #Debian (irc.icq.com)

--mI5TpPl/qDRoXxBg
Content-Type: application/pgp-signature; name="signature.pgp"
Content-Description: Digital signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFBBYfMC0FPBMSS+BIRArPmAKCfnhOiFB5RAdlH/yy5iISO9OXXHgCfXnDI
C40o5XwItXNBWNCh+WWlcuI=
=XetJ
-----END PGP SIGNATURE-----

--mI5TpPl/qDRoXxBg--