oops when calling sync(2)

Shane Wegner (shane@cm.nu)
Sun, 30 May 1999 19:08:25 -0700


--1yeeQ81UyVL57Vl7
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable

Hi all,

I am hoping someone here will be able to fix this as I am not a kernel
hacker. After an uptime of around 12 days, Linux kernel 2.2.9 started
oopsing whenever sync was ran. an strace on sync determined sync(2)
returns unfinished and sync itself then segfaults. A reboot fixed the
problem but I have experienced it with early 2.2 kernels as well. System
info:
Linux 2.2.9 compiled with gcc 2.7.2.3 runing glibc 2.1.1 Four ide devices
are installed, hda is a maxtor 8.4g hd, hdb is a quantum fireball 6.4g hd,
hdc is an hp 8110 CD writer and hdd is a MATSHITA CR-581, ATAPI CDROM
drive.

Below is what klogd spat out in /var/log/kern.log. It looks a bit more
comprehensive than what came up on the console as I believe it's using
System.map. I had it log 3 seperate sync calls.

May 30 18:47:03 continuum kernel: Unable to handle kernel NULL pointer dere=
ference at virtual address 00000024=20
May 30 18:47:03 continuum kernel: current->tss.cr3 =3D 07c66000, %cr3 =3D 0=
7c66000=20
May 30 18:47:03 continuum kernel: *pde =3D 00000000=20
May 30 18:47:03 continuum kernel: Oops: 0000=20
May 30 18:47:03 continuum kernel: CPU: 0=20
May 30 18:47:03 continuum kernel: EIP: 0010:[write_dquot+18/200]=20
May 30 18:47:03 continuum kernel: EFLAGS: 00010296=20
May 30 18:47:03 continuum kernel: eax: c5ff0004 ebx: c5ff3a40 ecx: 0000=
0000 edx: 00000000=20
May 30 18:47:03 continuum kernel: esi: c5ff39e0 edi: 0804ffff ebp: bfff=
0000 esp: c1e8bf70=20
May 30 18:47:03 continuum kernel: ds: 0018 es: 0018 ss: 0018=20
May 30 18:47:03 continuum kernel: Process sync (pid: 13683, process nr: 234=
, stackpage=3Dc1e8b000)=20
May 30 18:47:03 continuum kernel: Stack: 0804ffff bfff0000 0000f4c0 0000000=
0 c01327fa c5ff3a40 00000000 00000001 =20
May 30 18:47:03 continuum kernel: 08048740 bffffbb8 c012482a 0000000=
0 ffffffff 00000000 00000000 00000000 =20
May 30 18:47:03 continuum kernel: 00000000 c1e8a000 c012483f 0000000=
0 c010889c bffffbd4 400fafcd 0804a0d0 =20
May 30 18:47:03 continuum kernel: Call Trace: [sync_dquots+82/116] [fsync_d=
ev+34/48] [sys_sync+7/16] [system_call+52/56] =20
May 30 18:47:03 continuum kernel: Code: 8b 74 91 24 f6 43 2c 01 74 09 53 e8=
52 ff ff ff 83 c4 04 80 =20
May 30 18:47:06 continuum kernel: Unable to handle kernel NULL pointer dere=
ference at virtual address 00000024=20
May 30 18:47:06 continuum kernel: current->tss.cr3 =3D 07c66000, %cr3 =3D 0=
7c66000=20
May 30 18:47:06 continuum kernel: *pde =3D 00000000=20
May 30 18:47:06 continuum kernel: Oops: 0000=20
May 30 18:47:06 continuum kernel: CPU: 0=20
May 30 18:47:06 continuum kernel: EIP: 0010:[write_dquot+18/200]=20
May 30 18:47:06 continuum kernel: EFLAGS: 00010296=20
May 30 18:47:06 continuum kernel: eax: c0000004 ebx: c5ff3a40 ecx: 0000=
0000 edx: 00000000=20
May 30 18:47:06 continuum kernel: esi: c5ff39e0 edi: 0804ffff ebp: bfff=
0000 esp: c1e8bf70=20
May 30 18:47:06 continuum kernel: ds: 0018 es: 0018 ss: 0018=20
May 30 18:47:06 continuum kernel: Process sync (pid: 13684, process nr: 234=
, stackpage=3Dc1e8b000)=20
May 30 18:47:06 continuum kernel: Stack: 0804ffff bfff0000 c442e8a0 c6cb787=
0 c01327fa c5ff3a40 00000000 00000001 =20
May 30 18:47:06 continuum kernel: 08048740 bffffbb8 c012482a 0000000=
0 ffffffff 00000000 00000000 00000000 =20
May 30 18:47:06 continuum kernel: 00000000 c1e8a000 c012483f 0000000=
0 c010889c bffffbd4 400fafcd 0804a0d0 =20
May 30 18:47:06 continuum kernel: Call Trace: [sync_dquots+82/116] [fsync_d=
ev+34/48] [sys_sync+7/16] [system_call+52/56] =20
May 30 18:47:06 continuum kernel: Code: 8b 74 91 24 f6 43 2c 01 74 09 53 e8=
52 ff ff ff 83 c4 04 80 =20
May 30 18:47:09 continuum kernel: Unable to handle kernel NULL pointer dere=
ference at virtual address 00000024=20
May 30 18:47:09 continuum kernel: current->tss.cr3 =3D 0517a000, %cr3 =3D 0=
517a000=20
May 30 18:47:09 continuum kernel: *pde =3D 00000000=20
May 30 18:47:09 continuum kernel: Oops: 0000=20
May 30 18:47:09 continuum kernel: CPU: 0=20
May 30 18:47:09 continuum kernel: EIP: 0010:[write_dquot+18/200]=20
May 30 18:47:09 continuum kernel: EFLAGS: 00010296=20
May 30 18:47:09 continuum kernel: eax: c0000004 ebx: c5ff3a40 ecx: 0000=
0000 edx: 00000000=20
May 30 18:47:09 continuum kernel: esi: c5ff39e0 edi: 0804ffff ebp: bfff=
0000 esp: c23f7f70=20
May 30 18:47:09 continuum kernel: ds: 0018 es: 0018 ss: 0018=20
May 30 18:47:09 continuum kernel: Process sync (pid: 13686, process nr: 69,=
stackpage=3Dc23f7000)=20
May 30 18:47:09 continuum kernel: Stack: 0804ffff bfff0000 c0847780 c7ac244=
0 c01327fa c5ff3a40 00000000 00000001 =20
May 30 18:47:09 continuum kernel: 08048740 bffffbb8 c012482a 0000000=
0 ffffffff 00000000 00000000 00000000 =20
May 30 18:47:09 continuum kernel: 00000000 c23f6000 c012483f 0000000=
0 c0108910 bffffbd4 400fafcd 0804a0d0 =20
May 30 18:47:09 continuum kernel: Call Trace: [sync_dquots+82/116] [fsync_d=
ev+34/48] [sys_sync+7/16] [tracesys+24/35] =20
May 30 18:47:09 continuum kernel: Code: 8b 74 91 24 f6 43 2c 01 74 09 53 e8=
52 ff ff ff 83 c4 04 80 =20

--=20
Shane Wegner: shane@cm.nu
Sysadmin, Continuum Systems: http://www.cm.nu Tel: (604) 930-0520
Personal website: http://www.cm.nu/~shane Fax: (604) 930-0529
PGP: keyid: 2048/F5C2BD91 ICQ UIN: 120000
Fingerprint: 8C 48 B9 D8 53 BB D8 EF
76 BB DB A2 1C 0D 1D 87

--1yeeQ81UyVL57Vl7
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v0.9.7 (GNU/Linux)
Comment: Shane Wegner <shane@cm.nu>

iQEVAwUBN1HvFXernFT1wr2RAQFe0Af/S1mr6SATaaJcG76v2B66zKfHnLFl5te1
M/kTgJSRh7Y7rDzkZVHv3IGypxhyt9KdOn0L9IuRedyc1OLq5LsCEcFO/3nhcRtu
xQlpULNySWqzLugg39OXWkTErdLGVByG2gNQgwhjyqPz0PwzZqSXLYy3tL3aWbKP
JHjW20Z+zYWw5eAC4Ny+eb5ibuJANm5j9DHWSvThCPdSP9J4v0PgeICPtlqLUwVz
sW7OBp1z+e/MY4IK0eqDwVQUAJG/HbIWs/ebUfqXQMvanIhi2u23h7r7iO76ChDu
Kq1jtE/p+da92zQzU48gOVwWKUJKQYfLONJ04MYnTdUb9Tjf1541Kw==
=DX7f
-----END PGP SIGNATURE-----

--1yeeQ81UyVL57Vl7--

-
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/