Ubuntu
linux-source-2.6.15 package

kernel-image-2.4.26-1-686: oops under unknown circumstances (cron task?)

Bug #7168 reported by Debian Bug Importer
6
Affects Status Importance Assigned to Milestone
linux-source-2.6.15 (Debian)
Fix Released
Unknown
linux-source-2.6.15 (Ubuntu)
Invalid
High
Unassigned

Bug Description

Automatically imported from Debian bug report #255175 http://bugs.debian.org/255175

See original description

CVE References

Revision history for this message
In , Javier Fernández-Sanguino (jfs) wrote : kernel-image-2.4.26-1-686: system crash due to kernel bug

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.
Since I don't really know what causes it I'm at a loss in order to
reproduce it.

Thanks

Javier

Revision history for this message
Debian Bug Importer (debzilla) wrote :

Automatically imported from Debian bug report #255175 http://bugs.debian.org/255175

Revision history for this message
Debian Bug Importer (debzilla) wrote :
Download full text (20.1 KiB)

Message-ID: <email address hidden>
Date: Sat, 19 Jun 2004 12:31:03 +0200
From: Javier =?iso-8859-15?Q?Fern=E1ndez-Sanguino_Pe=F1a?= <email address hidden>
To: <email address hidden>
Subject: kernel-image-2.4.26-1-686: oops under unknown circumstances (cron task?)

--xgyAXRrhYN0wYx8y
Content-Type: multipart/mixed; boundary="7AUc2qLy4jB3hD7Z"
Content-Disposition: inline

--7AUc2qLy4jB3hD7Z
Content-Type: text/plain; charset=iso-8859-15
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

Package: kernel-image-2.4.26-1-686
Version: 2.4.26-2
Priority: normal

I really don't know what caused this (the computer in which this was found=
=20
is turned on 24h a day and I didn't see the oops, I just found it=20
unresponsive at that time). Digging in the logs (today, now that I had=20
time) I found this at 06:56 two days ago I found this:

-------------------------------------------------------------------
Jun 18 06:46:38 xxxx -- MARK --
Jun 18 06:56:46 xxxx kernel: printing eip:
Jun 18 06:56:46 xxxx kernel: c0153c3d
Jun 18 06:56:46 xxxx kernel: Oops: 0002
Jun 18 06:56:46 xxxx kernel: CPU: 0
Jun 18 06:56:46 xxxx kernel: EIP: 0010:[d_alloc+77/368] Not tainted
Jun 18 06:56:46 xxxx kernel: EFLAGS: 00010217
Jun 18 06:56:46 xxxx kernel: eax: 0000000e ebx: 2f7795a0 ecx: 00000003 =
 =20
edx: 2f7795fc
Jun 18 06:56:46 xxxx kernel: esi: ce4e0000 edi: 2f7795fc ebp: cfa48620 =
 =20
esp: cd9fdeec
Jun 18 06:56:46 xxxx kernel: ds: 0018 es: 0018 ss: 0018
Jun 18 06:56:46 xxxx kernel: Process find (pid: 31710, stackpage=3Dcd9fd000)
Jun 18 06:56:46 xxxx kernel: Stack: c1487f84 000001f0 0000000e fffffff4=20
cef9986c cef99800 cfa48620 c014a657
Jun 18 06:56:46 xxxx kernel: cfa48620 cd9fdf40 00000000 ce4e000e=20
00000000 cd9fdf98 c014ad38 cfa48620
Jun 18 06:56:46 xxxx kernel: cd9fdf40 00000000 00000008 cef99800=20
00000000 ce4e0000 0000000e a6a94a0b
Jun 18 06:56:46 xxxx kernel: Call Trace: [real_lookup+183/240]=20
[link_path_walk+1400/1680] [path_lookup+57/64] [__user_walk+73/96]=20
[sys_lstat64+31/144]
Jun 18 06:56:46 xxxx kernel: [system_call+51/56]
Jun 18 06:56:46 xxxx kernel:
Jun 18 06:56:46 xxxx kernel: Code: f3 a5 a8 02 74 02 66 a5 a8 01 74 01 a4=
=20
8b 4c 24 24 85 ed 8b
Jun 18 06:56:46 xxxx kernel: <1>Unable to handle kernel paging request at=
=20
virtual address 2f7795fc
Jun 18 06:56:46 xxxx kernel: printing eip:
Jun 18 06:56:46 xxxx kernel: c0153c3d
Jun 18 06:56:46 xxxx kernel: Oops: 0002
Jun 18 06:56:46 xxxx kernel: CPU: 0
Jun 18 06:56:46 xxxx kernel: EIP: 0010:[d_alloc+77/368] Not tainted
Jun 18 06:56:46 xxxx kernel: EFLAGS: 00010213
Jun 18 06:56:46 xxxx kernel: eax: 00000007 ebx: 2f7795a0 ecx: 00000001 =
 =20
edx: 2f7795fc
-------------------------------------------------------------------

Followed by 5 other oops (ksymoops of all of them attached). Since the last
symoops named process 'cron' it seems that it might be related to it. I had
to manually reset the system after this oops at that time.

If there's anything I can do to try to catch this and reproduce it,=20
please let me know.

Regards

Javier

--7AUc2qLy4jB3hD7Z
Content-Type: text/plain; charset=iso-8859-15
Cont...

Revision history for this message
Debian Bug Importer (debzilla) wrote :
Download full text (23.6 KiB)

Message-ID: <email address hidden>
Date: Mon, 26 Jul 2004 20:57:19 +0200
From: Javier =?iso-8859-1?Q?Fern=E1ndez-Sanguino_Pe=F1a?= <email address hidden>
To: <email address hidden>
Cc: <email address hidden>
Subject: kernel-image-2.4.26-1-686: system crash due to kernel bug

--dc+cDN39EJAMEtIO
Content-Type: multipart/mixed; boundary="n8g4imXOkfNTN/H1"
Content-Disposition: inline

--n8g4imXOkfNTN/H1
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

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.=
=20
Since I don't really know what causes it I'm at a loss in order to=20
reproduce it.

Thanks

Javier

--n8g4imXOkfNTN/H1
Content-Type: application/octet-stream
Content-Disposition: attachment; filename="ksymoops.gz"
Content-Transfer-Encoding: base64

H4sICDVTBUEAA2tzeW1vb3BzAO1b+2/kthH+ff8KFmjQu65tiRT18jkGmiANDih6QS/XoggO
Al+yFWtXW0lrr/PXd/jQc3fPPjd3SRMLya1EDj8OyZn5hhJ909yvqmrTIHJGz1JUrVERJZF5
ItEpPoWHM4TebNqiWjdo2yi5QPo6/Sd6IVXOtmX70pXcIG9TV8K7Achmr7Z0tatKbku1X18h
ryx4V+2NFfD2hFfI41XVem/vm1atzlZsczpuMJJf/IvV62J9dY7+XW2RLCRaVy1qVVmilUJ3
16pWqK1QXqwlAr15VaJinVf1iukRw9Bfo7uiLBesabbQoL1m0PpaobK6QiAjrmEo+vlG1WtV
IgYw3QiNLAP8ervWKizq4uq6hf7vjNjrP4EOMKGmudMXVW6iGa9uFQI9OqVq1VTl1ui0eJ2b
NmJb12rdjrr2QL7rXVZmpEbHTuMTdA+TINgaXal2sapANyYAhrUKVdt2s20RvzeTA+qilRqP
7FbVDfRuVJ9M2wJm/6Tr9gTZ1VetgLm76Yzr9Bqp3aZkxdrOlhvmWb886AXUA3RW8R+VaJuX
58jefcAqrGJe3nhq1wbmn7PKzJkVR7oEXbMGiWu2vlKwwMVa6Ilg8ufp90cu9f/TXqHg03Uq
60IvhFdIpf8/laqFdlMFhvLPo8dGFN5twRIidrvdVJW++DPOSNHcHJgPKP18s7GRgvhkt8vW
6m6qy7jm882JAE/fnxNd+ul0WKvW266Lnfln2rkuOdax767FG4gb58jcfv3du3Md9v3FN6+/
s3c+9s...

Revision history for this message
In , Michelle Konzack (linux4michelle) wrote : Re: Bug#255175: kernel-image-2.4.26-1-686: system crash due to kernel bug

Hello Javier,

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

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

It works very well...

Maybe you have a problem with your Hardware ?

Greetings
Michelle

Am 2004-07-26 20:57:19, schrieb Javier Fernández-Sanguino Peña:
>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.
>Since I don't really know what causes it I'm at a loss in order to
>reproduce it.
>
>Thanks
>
>Javier

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

Revision history for this message
In , Javier Fernández-Sanguino (jfs) wrote :

On Tue, Jul 27, 2004 at 12:38:05AM +0200, Michelle Konzack wrote:
> Hello Javier,
 (...)

Hi there,

> Maybe you have a problem with your Hardware ?

Can't tell, I'm not enough of a kernel hacker to be able to debug kernel
oops and determine were the fault is. In any case, this system has been
running with other kernels just fine since it was re-installed (march last
year). There has been no hardware change since then. In any case, even on
faulty hardware, I wouldn't expect the kernel to spit out 'kernel BUG' oops
messages at me.

I have been running 2.4.25-1-686 (version 2.4.25-3) and 2.4.22-1-686
through several months without any issues. Kernel logs in this system go
back to february this year, previously I was running
kernel-image-2.4.21-{4,5}-686, versions 2.4.21-{4,5} and
kernel-image-2.4.20-3-686, version 2.4.20-10. I started seeing these oops
(and crashes) after I installed 2.4.26-1-686 (4th of july this year). My
bets are on the kernel, but probably somebody with more knowledge can prove
me otherwise.

Regards

Javi

Revision history for this message
Debian Bug Importer (debzilla) wrote :
Download full text (3.3 KiB)

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)

iD8DBQFBBYf...

Read more...

Revision history for this message
Debian Bug Importer (debzilla) wrote :

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

--sdtB3X0nJg68CQEu
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Tue, Jul 27, 2004 at 12:38:05AM +0200, Michelle Konzack wrote:
> Hello Javier,=20
 (...)

Hi there,

> Maybe you have a problem with your Hardware ?

Can't tell, I'm not enough of a kernel hacker to be able to debug kernel
oops and determine were the fault is. In any case, this system has been
running with other kernels just fine since it was re-installed (march last
year). There has been no hardware change since then. In any case, even on
faulty hardware, I wouldn't expect the kernel to spit out 'kernel BUG' oops
messages at me.

I have been running 2.4.25-1-686 (version 2.4.25-3) and 2.4.22-1-686
through several months without any issues. Kernel logs in this system go
back to february this year, previously I was running
kernel-image-2.4.21-{4,5}-686, versions 2.4.21-{4,5} and
kernel-image-2.4.20-3-686, version 2.4.20-10. I started seeing these oops
(and crashes) after I installed 2.4.26-1-686 (4th of july this year). My
bets are on the kernel, but probably somebody with more knowledge can prove
me otherwise.

Regards

Javi

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

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

iD8DBQFBBZwhi4sehJTrj0oRAhyQAJ90x/ZimHaMRdobWZEg3UACagdrMQCeNQTV
pM1exUhElsXqHMsDXiYSGCU=
=b9/T
-----END PGP SIGNATURE-----

--sdtB3X0nJg68CQEu--

Revision history for this message
In , Simon Horman (horms) wrote :

On Mon, Jul 26, 2004 at 08:57:19PM +0200, Javier wrote:
> 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.
> Since I don't really know what causes it I'm at a loss in order to
> reproduce it.

Hi Javier,

thanks for the feed back. Do you have a reliable way to reproduce this.
What hardware (CPU) are you running this on?

I am wondering if what you are seeing relates to the clear_fpu() bug,
also known as CAN-2004-0554, which effects signal handling. It was
fixed in 2.4.26-3 (kernel-source and kernel-image-2.4.26-1-*) and
the fix is also present in 2.4.26-4.

http://www.ultramonkey.org/bugs/cve/CAN-2004-0554.shtml
http://marc.theaimsgroup.com/?l=linux-kernel&m=108704809114434&w=2

--
Horms

Revision history for this message
Debian Bug Importer (debzilla) wrote :

Message-ID: <email address hidden>
Date: Tue, 27 Jul 2004 10:46:09 +0900
From: Horms <email address hidden>
To: <email address hidden>
Cc: <email address hidden>, <email address hidden>
Subject: Re: Bug#255175: kernel-image-2.4.26-1-686: system crash due to kernel bug

On Mon, Jul 26, 2004 at 08:57:19PM +0200, Javier wrote:
> 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.
> Since I don't really know what causes it I'm at a loss in order to
> reproduce it.

Hi Javier,

thanks for the feed back. Do you have a reliable way to reproduce this.
What hardware (CPU) are you running this on?

I am wondering if what you are seeing relates to the clear_fpu() bug,
also known as CAN-2004-0554, which effects signal handling. It was
fixed in 2.4.26-3 (kernel-source and kernel-image-2.4.26-1-*) and
the fix is also present in 2.4.26-4.

http://www.ultramonkey.org/bugs/cve/CAN-2004-0554.shtml
http://marc.theaimsgroup.com/?l=linux-kernel&m=108704809114434&w=2

--
Horms

Revision history for this message
In , Javier Fernández-Sanguino (jfs) wrote :

On Tue, Jul 27, 2004 at 10:46:09AM +0900, Horms wrote:
> Hi Javier,
>
> thanks for the feed back. Do you have a reliable way to reproduce this.

Unfortunately no, it just happens from time to time.

> What hardware (CPU) are you running this on?

Pentium III 500Mhz (yes, I know it sucks)

> I am wondering if what you are seeing relates to the clear_fpu() bug,
> also known as CAN-2004-0554, which effects signal handling. It was
> fixed in 2.4.26-3 (kernel-source and kernel-image-2.4.26-1-*) and
> the fix is also present in 2.4.26-4.

I am running now (installed yesterday) kernel-image-2.4.26-1-686, 2.4.26-4,
I will send info to the bug if it reproduces and will tag the bug
accordingly (since 2.4.26-4 is in sid, but 2.4.26-2 in sarge).

Regards

Javier

Revision history for this message
In , Horms (horms-verge) wrote :

On Tue, Jul 27, 2004 at 08:18:54AM +0200, Javier Fern??wrote:
> On Tue, Jul 27, 2004 at 10:46:09AM +0900, Horms wrote:
> > Hi Javier,
> >
> > thanks for the feed back. Do you have a reliable way to reproduce this.
>
> Unfortunately no, it just happens from time to time.
>
> > What hardware (CPU) are you running this on?
>
> Pentium III 500Mhz (yes, I know it sucks)
>
> > I am wondering if what you are seeing relates to the clear_fpu() bug,
> > also known as CAN-2004-0554, which effects signal handling. It was
> > fixed in 2.4.26-3 (kernel-source and kernel-image-2.4.26-1-*) and
> > the fix is also present in 2.4.26-4.
>
> I am running now (installed yesterday) kernel-image-2.4.26-1-686, 2.4.26-4,
> I will send info to the bug if it reproduces and will tag the bug
> accordingly (since 2.4.26-4 is in sid, but 2.4.26-2 in sarge).

Hopefully 2.4.26-4 will make it into sarge shortly.
Please let me know how you go with this bug.

--
Horms

Revision history for this message
Debian Bug Importer (debzilla) wrote :

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

--7AUc2qLy4jB3hD7Z
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Tue, Jul 27, 2004 at 10:46:09AM +0900, Horms wrote:
> Hi Javier,
>=20
> thanks for the feed back. Do you have a reliable way to reproduce this.

Unfortunately no, it just happens from time to time.

> What hardware (CPU) are you running this on?

Pentium III 500Mhz (yes, I know it sucks)

> I am wondering if what you are seeing relates to the clear_fpu() bug,
> also known as CAN-2004-0554, which effects signal handling. It was
> fixed in 2.4.26-3 (kernel-source and kernel-image-2.4.26-1-*) and
> the fix is also present in 2.4.26-4.

I am running now (installed yesterday) kernel-image-2.4.26-1-686, 2.4.26-4,=
=20
I will send info to the bug if it reproduces and will tag the bug=20
accordingly (since 2.4.26-4 is in sid, but 2.4.26-2 in sarge).

Regards

Javier

--7AUc2qLy4jB3hD7Z
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
Content-Disposition: inline

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

iD8DBQFBBfPNi4sehJTrj0oRAjxtAKCP0UBVzqcneUGEOMWC3eW7ZZRl2gCfaALA
AAuNOPtNr3XqUEPutrO22I8=
=3zJC
-----END PGP SIGNATURE-----

--7AUc2qLy4jB3hD7Z--

Revision history for this message
Debian Bug Importer (debzilla) wrote :

Message-ID: <email address hidden>
Date: Tue, 27 Jul 2004 16:04:13 +0900
From: Horms <email address hidden>
To: <email address hidden>
Cc: <email address hidden>
Subject: Re: Bug#255175: kernel-image-2.4.26-1-686: system crash due to kernel bug

On Tue, Jul 27, 2004 at 08:18:54AM +0200, Javier Fern??wrote:
> On Tue, Jul 27, 2004 at 10:46:09AM +0900, Horms wrote:
> > Hi Javier,
> >
> > thanks for the feed back. Do you have a reliable way to reproduce this.
>
> Unfortunately no, it just happens from time to time.
>
> > What hardware (CPU) are you running this on?
>
> Pentium III 500Mhz (yes, I know it sucks)
>
> > I am wondering if what you are seeing relates to the clear_fpu() bug,
> > also known as CAN-2004-0554, which effects signal handling. It was
> > fixed in 2.4.26-3 (kernel-source and kernel-image-2.4.26-1-*) and
> > the fix is also present in 2.4.26-4.
>
> I am running now (installed yesterday) kernel-image-2.4.26-1-686, 2.4.26-4,
> I will send info to the bug if it reproduces and will tag the bug
> accordingly (since 2.4.26-4 is in sid, but 2.4.26-2 in sarge).

Hopefully 2.4.26-4 will make it into sarge shortly.
Please let me know how you go with this bug.

--
Horms

Revision history for this message
In , Javier Fernández-Sanguino (jfs) wrote :

> Hopefully 2.4.26-4 will make it into sarge shortly.
> Please let me know how you go with this bug.

Still hasn't reproduced (crossing fingers). Isn't the debug information
sufficient to determine which part of the kernel might be broken?

Javier

Revision history for this message
In , Horms (horms-verge) wrote :

On Tue, Jul 27, 2004 at 03:01:45PM +0200, Javier wrote:
>
> > Hopefully 2.4.26-4 will make it into sarge shortly.
> > Please let me know how you go with this bug.
>
> Still hasn't reproduced (crossing fingers). Isn't the debug information
> sufficient to determine which part of the kernel might be broken?

Perhaps, though the kernel is a complex beast and if the bug
can't reliably be reproduced it hard to know exactly where
the problem lies.

I noticed in your trace that signal handling functions featured,
notably in the first oops in the trace you sent yesterday. This
makes me syspect CAN-2004-0554. Certainly that seems to be
the only relevant change since 2.4.26-2.

--
Horms

Revision history for this message
Debian Bug Importer (debzilla) wrote :

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

--UlVJffcvxoiEqYs2
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

> Hopefully 2.4.26-4 will make it into sarge shortly.
> Please let me know how you go with this bug.

Still hasn't reproduced (crossing fingers). Isn't the debug information=20
sufficient to determine which part of the kernel might be broken?

Javier

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

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

iD8DBQFBBlI4i4sehJTrj0oRAqLdAKDJkoj3pqRlKeJ9mbez6u+KoIeFpQCgnnws
fvJ6SGXMvWdC/+0xs66bfFg=
=Nvd0
-----END PGP SIGNATURE-----

--UlVJffcvxoiEqYs2--

Revision history for this message
Debian Bug Importer (debzilla) wrote :

Message-ID: <email address hidden>
Date: Tue, 27 Jul 2004 22:11:40 +0900
From: Horms <email address hidden>
To: <email address hidden>
Cc: <email address hidden>
Subject: Re: Bug#255175: kernel-image-2.4.26-1-686: system crash due to kernel bug

On Tue, Jul 27, 2004 at 03:01:45PM +0200, Javier wrote:
>
> > Hopefully 2.4.26-4 will make it into sarge shortly.
> > Please let me know how you go with this bug.
>
> Still hasn't reproduced (crossing fingers). Isn't the debug information
> sufficient to determine which part of the kernel might be broken?

Perhaps, though the kernel is a complex beast and if the bug
can't reliably be reproduced it hard to know exactly where
the problem lies.

I noticed in your trace that signal handling functions featured,
notably in the first oops in the trace you sent yesterday. This
makes me syspect CAN-2004-0554. Certainly that seems to be
the only relevant change since 2.4.26-2.

--
Horms

Revision history for this message
In , Javier Fernández-Sanguino (jfs) wrote :

> Hopefully 2.4.26-4 will make it into sarge shortly.
> Please let me know how you go with this bug.

It has reproduced again, with 2.4.26-4, a kernel oops is attached. Do you
want me to run ksymoops?

Regards

Javier

Revision history for this message
Debian Bug Importer (debzilla) wrote :
Download full text (4.0 KiB)

Message-ID: <email address hidden>
Date: Wed, 28 Jul 2004 01:33:47 +0200
From: Javier =?iso-8859-1?Q?Fern=E1ndez-Sanguino_Pe=F1a?= <email address hidden>
To: Horms <email address hidden>
Cc: <email address hidden>
Subject: Re: Bug#255175: kernel-image-2.4.26-1-686: system crash due to kernel bug

--WfZ7S8PLGjBY9Voh
Content-Type: multipart/mixed; boundary="eAbsdosE1cNLO4uF"
Content-Disposition: inline

--eAbsdosE1cNLO4uF
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

> Hopefully 2.4.26-4 will make it into sarge shortly.
> Please let me know how you go with this bug.

It has reproduced again, with 2.4.26-4, a kernel oops is attached. Do you=
=20
want me to run ksymoops?

Regards

Javier

--eAbsdosE1cNLO4uF
Content-Type: text/plain; charset=us-ascii
Content-Disposition: attachment; filename=oops
Content-Transfer-Encoding: quoted-printable

Jul 28 01:29:49 silicio kernel: kernel BUG at page_alloc.c:221!
Jul 28 01:29:49 silicio kernel: invalid operand: 0000
Jul 28 01:29:49 silicio kernel: CPU: 0
Jul 28 01:29:49 silicio kernel: EIP: 0010:[rmqueue+135/576] Not taint=
ed
Jul 28 01:29:49 silicio kernel: EFLAGS: 00010006
Jul 28 01:29:49 silicio kernel: eax: 00000000 ebx: c100a100 ecx: 000000=
00 edx: 0000035a
Jul 28 01:29:49 silicio kernel: esi: c0266ab8 edi: 00000000 ebp: c0266a=
80 esp: c9d25e5c
Jul 28 01:29:49 silicio kernel: ds: 0018 es: 0018 ss: 0018
Jul 28 01:29:49 silicio kernel: Process rsync (pid: 18482, stackpage=3Dc9d2=
5000)
Jul 28 01:29:49 silicio kernel: Stack: 00000000 00000020 d448e1ac 00000296 =
00000000 c0266a80 c0266a80 c0266d10=20
Jul 28 01:29:49 silicio kernel: 00000001 c0266a80 c0137f5b 3e0d34d6 =
c01ed7a0 d448e040 000004b0 c9d25f64=20
Jul 28 01:29:49 silicio kernel: c0266b58 c0266d08 00000000 000001f0 =
c9d24000 00000000 cb86cc40 c9d25f3c=20
Jul 28 01:29:49 silicio kernel: Call Trace: [__alloc_pages+107/640] [tcp=
_recvmsg+976/2272] [__get_free_pages+28/32] [__pollwait+124/192] [tcp_poll+=
55/400]
Jul 28 01:29:49 silicio kernel: [sock_poll+44/64] [do_select+532/544] [sy=
s_select+825/1248] [net_tx_action+67/192] [system_call+51/56]
Jul 28 01:29:49 silicio kernel:=20
Jul 28 01:29:49 silicio kernel: Code: 0f 0b dd 00 6a 17 24 c0 8b 53 04 89 d=
d 8b 03 89 50 04 89 02=20
Jul 28 01:29:49 silicio kernel: kernel BUG at page_alloc.c:152!
Jul 28 01:29:49 silicio kernel: invalid operand: 0000
Jul 28 01:29:49 silicio kernel: CPU: 0
Jul 28 01:29:49 silicio kernel: EIP: 0010:[__free_pages_ok+448/688] N=
ot tainted
Jul 28 01:29:49 silicio kernel: EFLAGS: 00010006
Jul 28 01:29:49 silicio kernel: eax: 00000000 ebx: c102e7c0 ecx: 000000=
00 edx: 00000f7e
Jul 28 01:29:49 silicio kernel: esi: 00000f7f edi: 00000000 ebp: c0266a=
b8 esp: c3269ee0
Jul 28 01:29:49 silicio kernel: ds: 0018 es: 0018 ss: 0018
Jul 28 01:29:49 silicio kernel: Process rsync (pid: 9613, stackpage=3Dc3269=
000)
Jul 28 01:29:49 silicio kernel: Stack: c0266b30 c1000020 c102e7f0 c0266a80 =
c1000020 00000203 ffffffff 000007bf=20
Jul 28 01:29:49 silicio kernel: 0017f000 d5aec5fc 00400000 00000180 =
c012d38a c102e7f0 cd294a20...

Read more...

Revision history for this message
In , Horms (horms-verge) wrote :

severity 255175 important

On Wed, Jul 28, 2004 at 01:33:47AM +0200, Javier wrote:
> > Hopefully 2.4.26-4 will make it into sarge shortly.
> > Please let me know how you go with this bug.
>
> It has reproduced again, with 2.4.26-4, a kernel oops is attached. Do you
> want me to run ksymoops?

I am not sure that would really help.
Are you sure that it couldn't be a hardware problem.
It seems to be rather intermittend and do not have any
other reports of similar failures.

Pending a way to reliably reproduce the problem,
or at least some confirmation that it manifests on
different hardware I have changed the severity to important.

Thanks

--
Horms

Revision history for this message
Debian Bug Importer (debzilla) wrote :

Message-ID: <email address hidden>
Date: Thu, 29 Jul 2004 11:07:35 +0900
From: Horms <email address hidden>
To: Javier <email address hidden>
Cc: <email address hidden>, <email address hidden>
Subject: Re: Bug#255175: kernel-image-2.4.26-1-686: system crash due to kernel bug

severity 255175 important

On Wed, Jul 28, 2004 at 01:33:47AM +0200, Javier wrote:
> > Hopefully 2.4.26-4 will make it into sarge shortly.
> > Please let me know how you go with this bug.
>
> It has reproduced again, with 2.4.26-4, a kernel oops is attached. Do you
> want me to run ksymoops?

I am not sure that would really help.
Are you sure that it couldn't be a hardware problem.
It seems to be rather intermittend and do not have any
other reports of similar failures.

Pending a way to reliably reproduce the problem,
or at least some confirmation that it manifests on
different hardware I have changed the severity to important.

Thanks

--
Horms

Revision history for this message
Matt Zimmerman (mdz) wrote :

Sounds like flaky hardware

Revision history for this message
In , Javier Fernández-Sanguino (jfs) wrote :

> I am not sure that would really help.
> Are you sure that it couldn't be a hardware problem.

I don't see any hardware problems in the log before the kernel oopses. If
there were, if there are hardware issues, then it's the kernel fault that
nothing gets reported.

The only think I can think of is that there might be some (unreported by
the kernel) hard drive problems which doesn't get reported by the kernel
and when it tries to use the swap space it cannot read/write to it and this
generates the oopses. Isnt' there a tool to test the swapspace? (besides
'mkswap -c')

The one thing I'm surprised about is that the oopses vary somewhat in their
messages:

 kernel BUG at mmap.c:1172!
 kernel BUG at page_alloc.c:152!
 kernel BUG at page_alloc.c:221!

Digging the code of the first one I find it in mm/mmap.c exit_mmap():
        /* This is just debugging */
        if (mm->map_count)
                BUG();

And the page_alloc ones code are:

mm/page_alloc.c:
     84 static void FASTCALL(__free_pages_ok (struct page *page, unsigned int or der));
     85 static void __free_pages_ok (struct page *page, unsigned int order)
     86 {
(...)
    149 buddy1 = base + (page_idx ^ -mask);
    150 buddy2 = base + page_idx;
    151 if (BAD_RANGE(zone,buddy1))
    152 BUG();
    153 if (BAD_RANGE(zone,buddy2))
    154 BUG();
(...)
    203 static struct page * rmqueue(zone_t *zone, unsigned int order)
    204 {
(...)
    219 page = list_entry(curr, struct page, list);
    220 if (BAD_RANGE(zone,page))
    221 BUG();

I don't have an in depth knowledge of the kernel, but I don't believe that
hardware issues can make the above code generate those BUG(). It looks to
me that somehow, the kernel is not handling its swap definitions properly.

Can you figure up a way in which I could reproduce these errors and maybe
trace the kernel to see what's going on?

> It seems to be rather intermittend and do not have any
> other reports of similar failures.

The "intermittency" might be related to the fact that it's a problem in the
cleanup of swap pages, when swap is not used, the problem does not show
up. For what it's worth, in my system:

$ free
             total used free shared buffers cached
Mem: 386156 381800 4356 0 15712 258080
-/+ buffers/cache: 108008 278148
Swap: 979956 1088 978868

So swap is not usually used. The oops seem to appear when cron jobs make
intensive use of the system and the swap usage goes up and down.

> Pending a way to reliably reproduce the problem,
> or at least some confirmation that it manifests on
> different hardware I have changed the severity to important.

I understand this but I would appreciate some indication on how to debug
this issue myself if necessary and trace what the kernel is hitting
against.

Regards

Javier

Revision history for this message
Debian Bug Importer (debzilla) wrote :
Download full text (3.8 KiB)

Message-ID: <email address hidden>
Date: Thu, 29 Jul 2004 09:20:29 +0200
From: Javier =?iso-8859-1?Q?Fern=E1ndez-Sanguino_Pe=F1a?= <email address hidden>
To: Horms <email address hidden>
Cc: <email address hidden>
Subject: Re: Bug#255175: kernel-image-2.4.26-1-686: system crash due to kernel bug

--gKMricLos+KVdGMg
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

> I am not sure that would really help.
> Are you sure that it couldn't be a hardware problem.

I don't see any hardware problems in the log before the kernel oopses. If
there were, if there are hardware issues, then it's the kernel fault that
nothing gets reported.=20

The only think I can think of is that there might be some (unreported by
the kernel) hard drive problems which doesn't get reported by the kernel
and when it tries to use the swap space it cannot read/write to it and this
generates the oopses. Isnt' there a tool to test the swapspace? (besides=20
'mkswap -c')

The one thing I'm surprised about is that the oopses vary somewhat in their=
=20
messages:

 kernel BUG at mmap.c:1172!
 kernel BUG at page_alloc.c:152!
 kernel BUG at page_alloc.c:221!

Digging the code of the first one I find it in mm/mmap.c exit_mmap():
        /* This is just debugging */
        if (mm->map_count)
                BUG();

And the page_alloc ones code are:

mm/page_alloc.c:
     84 static void FASTCALL(__free_pages_ok (struct page *page, unsigned i=
nt or der));
     85 static void __free_pages_ok (struct page *page, unsigned int order)
     86 {
(...)
    149 buddy1 =3D base + (page_idx ^ -mask);
    150 buddy2 =3D base + page_idx;
    151 if (BAD_RANGE(zone,buddy1))
    152 BUG();
    153 if (BAD_RANGE(zone,buddy2))
    154 BUG();
(...)
    203 static struct page * rmqueue(zone_t *zone, unsigned int order)
    204 {
(...)
    219 page =3D list_entry(curr, struct page, list=
);
    220 if (BAD_RANGE(zone,page))
    221 BUG();

I don't have an in depth knowledge of the kernel, but I don't believe that
hardware issues can make the above code generate those BUG(). It looks to
me that somehow, the kernel is not handling its swap definitions properly.

Can you figure up a way in which I could reproduce these errors and maybe=
=20
trace the kernel to see what's going on?

> It seems to be rather intermittend and do not have any
> other reports of similar failures.

The "intermittency" might be related to the fact that it's a problem in the=
=20
cleanup of swap pages, when swap is not used, the problem does not show=20
up. For what it's worth, in my system:

$ free
             total used free shared buffers cached
Mem: 386156 381800 4356 0 15712 258080
-/+ buffers/cache: 108008 278148
Swap: 979956 1088 978868

So swap is not usually used. The oops seem to appear when cron jobs make=20
intensive use of the system and the swap usage goes up and down.
...

Read more...

Revision history for this message
In , Matt Zimmerman (mdz) wrote :

On Thu, Jul 29, 2004 at 09:20:29AM +0200, Javier Fernández-Sanguino Peña wrote:

> > I am not sure that would really help.
> > Are you sure that it couldn't be a hardware problem.
>
> I don't see any hardware problems in the log before the kernel oopses. If
> there were, if there are hardware issues, then it's the kernel fault that
> nothing gets reported.

He's talking about the kind of hardware problems that cause the kernel to
crash (such as unreliable RAM). Unless you are using error-correcting
memory (and sometimes, even if you are), the kernel can't automatically
detect and report this condition.

> The one thing I'm surprised about is that the oopses vary somewhat in their
> messages:

This is symptomatic of a hardware-induced failure.

--
 - mdz

Revision history for this message
In , Javier Fernández-Sanguino (jfs) wrote :

On Thu, Jul 29, 2004 at 08:52:37AM -0700, Matt Zimmerman wrote:
> He's talking about the kind of hardware problems that cause the kernel to
> crash (such as unreliable RAM). Unless you are using error-correcting
> memory (and sometimes, even if you are), the kernel can't automatically
> detect and report this condition.

Yes, I imagined this after googling for the BUG messages. In order to
discard RAM issues I've been running memtest for a while, without any
errors. I'll plug in a bootable cd and see if memtest fails.
If I find any hardware issues I'll report it here.

Regards

Javier

Revision history for this message
Debian Bug Importer (debzilla) wrote :

Message-ID: <email address hidden>
Date: Thu, 29 Jul 2004 08:52:37 -0700
From: Matt Zimmerman <email address hidden>
To: Javier =?iso-8859-1?Q?Fern=E1ndez-Sanguino_Pe=F1a?= <email address hidden>,
 <email address hidden>
Cc: Horms <email address hidden>
Subject: Re: Bug#255175: kernel-image-2.4.26-1-686: system crash due to kernel bug

On Thu, Jul 29, 2004 at 09:20:29AM +0200, Javier Fern�ez-Sanguino Pe�rote:

> > I am not sure that would really help.
> > Are you sure that it couldn't be a hardware problem.
>
> I don't see any hardware problems in the log before the kernel oopses. If
> there were, if there are hardware issues, then it's the kernel fault that
> nothing gets reported.

He's talking about the kind of hardware problems that cause the kernel to
crash (such as unreliable RAM). Unless you are using error-correcting
memory (and sometimes, even if you are), the kernel can't automatically
detect and report this condition.

> The one thing I'm surprised about is that the oopses vary somewhat in their
> messages:

This is symptomatic of a hardware-induced failure.

--
 - mdz

Revision history for this message
Debian Bug Importer (debzilla) wrote :

Message-ID: <email address hidden>
Date: Thu, 29 Jul 2004 18:04:03 +0200
From: Javier =?iso-8859-1?Q?Fern=E1ndez-Sanguino_Pe=F1a?= <email address hidden>
To: Matt Zimmerman <email address hidden>
Cc: <email address hidden>, Horms <email address hidden>
Subject: Re: Bug#255175: kernel-image-2.4.26-1-686: system crash due to kernel bug

On Thu, Jul 29, 2004 at 08:52:37AM -0700, Matt Zimmerman wrote:
> He's talking about the kind of hardware problems that cause the kernel to
> crash (such as unreliable RAM). Unless you are using error-correcting
> memory (and sometimes, even if you are), the kernel can't automatically
> detect and report this condition.

Yes, I imagined this after googling for the BUG messages. In order to
discard RAM issues I've been running memtest for a while, without any
errors. I'll plug in a bootable cd and see if memtest fails.
If I find any hardware issues I'll report it here.

Regards

Javier

Revision history for this message
In , Bozhan (edmon) wrote : kernel-image-2.4.26-1-686: after overload maybe?
Download full text (4.6 KiB)

Package: kernel-image-2.4.26-1-686
Version: 2.4.26-4
Followup-For: Bug #255175

here is what happens after cron(checksecurity, faubackup):
Aug 22 07:37:57 carredas kernel: Unable to handle kernel paging request
at virtual address e77dd630
Aug 22 07:37:57 carredas kernel: printing eip:
Aug 22 07:37:57 carredas kernel: c015385f
Aug 22 07:37:57 carredas kernel: *pde = 00000000
Aug 22 07:37:57 carredas kernel: Oops: 0002
Aug 22 07:37:57 carredas kernel: CPU: 0
Aug 22 07:37:57 carredas kernel: EIP: 0010:[prune_dcache+191/336]
Tainted: P
Aug 22 07:37:57 carredas kernel: EFLAGS: 00010282
Aug 22 07:37:57 carredas kernel: eax: df43ee90 ebx: df43ee78 ecx:
e77dd630 edx: c77dd630
Aug 22 07:37:57 carredas kernel: esi: df43ee60 edi: c77dd620 ebp:
00003da3 esp: dfa77f18
Aug 22 07:37:57 carredas kernel: ds: 0018 es: 0018 ss: 0018
Aug 22 07:37:57 carredas kernel: Process kswapd (pid: 4,
stackpage=dfa77000)
Aug 22 07:37:57 carredas kernel: Stack: d724d8c0 df43e560 00000018
c1504530 c0266b58 0000340f c0153bd4 00007787
Aug 22 07:37:57 carredas kernel: c0136956 00000006 000001d0
ffffffff 000001d0 00000018 0000001f 000001d0
Aug 22 07:37:57 carredas kernel: c0266b58 c0266b58 c0136d3d
dfa77f84 000001d0 0000003c 00000020 c0136dc2
Aug 22 07:37:57 carredas kernel: Call Trace:
[shrink_dcache_memory+36/64] [shrink_cache+358/944]
[shrink_caches+61/96] [try_to_free_pages_zone+98/256]
[kswapd_balance_pgdat+102/176]
Aug 22 07:37:57 carredas kernel: [kswapd_balance+40/64]
[kswapd+152/192] [kswapd+0/192] [rest_init+0/64]
[arch_kernel_thread+46/64] [kswapd+0/192]
Aug 22 07:37:57 carredas kernel:
Aug 22 07:37:57 carredas kernel: Code: 89 11 89 40 04 89 43 18 8b 46 4c
85 c0 74 07 8b 50 14 85 d2

and kswapd die defunc

machine still works but produces mesages like this when using dselect
for example:
Aug 21 12:13:28 carredas kernel: Unable to handle kernel paging request
at virtual address ebaff2f0
Aug 21 12:13:28 carredas kernel: printing eip:
Aug 21 12:13:28 carredas kernel: c015381e
Aug 21 12:13:28 carredas kernel: *pde = 00000000
Aug 21 12:13:28 carredas kernel: Oops: 0002
Aug 21 12:13:28 carredas kernel: CPU: 0
Aug 21 12:13:28 carredas kernel: EIP: 0010:[prune_dcache+126/336]
Tainted: P
Aug 21 12:13:28 carredas kernel: EFLAGS: 00010246
Aug 21 12:13:28 carredas kernel: eax: d042b7b0 ebx: d042b7b8 ecx:
ebaff2f0 edx: dfb56fc8
Aug 21 12:13:28 carredas kernel: esi: d042b7a0 edi: c9230280 ebp:
00006dbf esp: d34e1d60
Aug 21 12:13:28 carredas kernel: ds: 0018 es: 0018 ss: 0018
Aug 21 12:13:28 carredas kernel: Process apt-get (pid: 21264,
stackpage=d34e1000)
Aug 21 12:13:28 carredas kernel: Stack: ccd15cc0 d042b720 00000005
c1513ce0 c0266b58 00002746 c0153bd4 0000af2e
Aug 21 12:13:28 carredas kernel: c0136956 00000006 000001d2
ffffffff 000001d2 00000005 00000011 000001d2
Aug 21 12:13:28 carredas kernel: c0266b58 c0266b58 c0136d3d
d34e1dcc 000001d2 0000003c 00000020 c0136dc2
Aug 21 12:13:28 carredas kernel: Call Trace:
[shrink_dcache_memory+36/64] [shrink_cache+358/944]
[shrink_caches+61/96] [try_to_free_pages_zone+98/256]
[balance_classzone+66/480]
Aug 21 12:13:28 carredas kernel: [__alloc_pages+376/640]
[d...

Read more...

Revision history for this message
Debian Bug Importer (debzilla) wrote :
Download full text (4.8 KiB)

Message-Id: <email address hidden>
Date: Sun, 22 Aug 2004 15:04:19 +0300
From: Bozhan Boiadzhiev <email address hidden>
To: Debian Bug Tracking System <email address hidden>
Subject: kernel-image-2.4.26-1-686: after overload maybe?

Package: kernel-image-2.4.26-1-686
Version: 2.4.26-4
Followup-For: Bug #255175

here is what happens after cron(checksecurity, faubackup):
Aug 22 07:37:57 carredas kernel: Unable to handle kernel paging request
at virtual address e77dd630
Aug 22 07:37:57 carredas kernel: printing eip:
Aug 22 07:37:57 carredas kernel: c015385f
Aug 22 07:37:57 carredas kernel: *pde = 00000000
Aug 22 07:37:57 carredas kernel: Oops: 0002
Aug 22 07:37:57 carredas kernel: CPU: 0
Aug 22 07:37:57 carredas kernel: EIP: 0010:[prune_dcache+191/336]
Tainted: P
Aug 22 07:37:57 carredas kernel: EFLAGS: 00010282
Aug 22 07:37:57 carredas kernel: eax: df43ee90 ebx: df43ee78 ecx:
e77dd630 edx: c77dd630
Aug 22 07:37:57 carredas kernel: esi: df43ee60 edi: c77dd620 ebp:
00003da3 esp: dfa77f18
Aug 22 07:37:57 carredas kernel: ds: 0018 es: 0018 ss: 0018
Aug 22 07:37:57 carredas kernel: Process kswapd (pid: 4,
stackpage=dfa77000)
Aug 22 07:37:57 carredas kernel: Stack: d724d8c0 df43e560 00000018
c1504530 c0266b58 0000340f c0153bd4 00007787
Aug 22 07:37:57 carredas kernel: c0136956 00000006 000001d0
ffffffff 000001d0 00000018 0000001f 000001d0
Aug 22 07:37:57 carredas kernel: c0266b58 c0266b58 c0136d3d
dfa77f84 000001d0 0000003c 00000020 c0136dc2
Aug 22 07:37:57 carredas kernel: Call Trace:
[shrink_dcache_memory+36/64] [shrink_cache+358/944]
[shrink_caches+61/96] [try_to_free_pages_zone+98/256]
[kswapd_balance_pgdat+102/176]
Aug 22 07:37:57 carredas kernel: [kswapd_balance+40/64]
[kswapd+152/192] [kswapd+0/192] [rest_init+0/64]
[arch_kernel_thread+46/64] [kswapd+0/192]
Aug 22 07:37:57 carredas kernel:
Aug 22 07:37:57 carredas kernel: Code: 89 11 89 40 04 89 43 18 8b 46 4c
85 c0 74 07 8b 50 14 85 d2

and kswapd die defunc

machine still works but produces mesages like this when using dselect
for example:
Aug 21 12:13:28 carredas kernel: Unable to handle kernel paging request
at virtual address ebaff2f0
Aug 21 12:13:28 carredas kernel: printing eip:
Aug 21 12:13:28 carredas kernel: c015381e
Aug 21 12:13:28 carredas kernel: *pde = 00000000
Aug 21 12:13:28 carredas kernel: Oops: 0002
Aug 21 12:13:28 carredas kernel: CPU: 0
Aug 21 12:13:28 carredas kernel: EIP: 0010:[prune_dcache+126/336]
Tainted: P
Aug 21 12:13:28 carredas kernel: EFLAGS: 00010246
Aug 21 12:13:28 carredas kernel: eax: d042b7b0 ebx: d042b7b8 ecx:
ebaff2f0 edx: dfb56fc8
Aug 21 12:13:28 carredas kernel: esi: d042b7a0 edi: c9230280 ebp:
00006dbf esp: d34e1d60
Aug 21 12:13:28 carredas kernel: ds: 0018 es: 0018 ss: 0018
Aug 21 12:13:28 carredas kernel: Process apt-get (pid: 21264,
stackpage=d34e1000)
Aug 21 12:13:28 carredas kernel: Stack: ccd15cc0 d042b720 00000005
c1513ce0 c0266b58 00002746 c0153bd4 0000af2e
Aug 21 12:13:28 carredas kernel: c0136956 00000006 000001d2
ffffffff 000001d2 00000005 00000011 000001d2
Aug 21 12:13:28 carredas kernel: c0266b58 c0266b58 c0136d3d
d34e1dcc 000001d2 0000003c 000...

Read more...

Revision history for this message
In , Bozhan (edmon) wrote : buggy memory

ooops this was a problem with buggy memory

Revision history for this message
Debian Bug Importer (debzilla) wrote :

Message-ID: <email address hidden>
Date: Mon, 23 Aug 2004 22:47:30 +0300
From: Bozhan Boiadzhiev <email address hidden>
To: <email address hidden>
Subject: buggy memory

ooops this was a problem with buggy memory

Revision history for this message
Debian Bug Importer (debzilla) wrote :

Message-ID: <email address hidden>
Date: Mon, 23 Aug 2004 21:57:13 +0200
From: Christoph Hellwig <email address hidden>
To: <email address hidden>
Subject: closing

Bug Watch Updater (bug-watch-updater)
Changed in linux-source-2.6.15:
status: Unknown → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.