general protection fault: 0000 [1] SMP

--Boundary-02=_TRd3DCPUIy8HbDB
Content-Type: text/plain;
charset="iso-8859-15"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

Dear list,

has somebody seen something like that before?

=2D-----------------snip----------------------
Jan 28 00:27:54 svdbslx002 kernel: general protection fault: 0000 [1] SMP
Jan 28 00:27:54 svdbslx002 kernel: CPU 1
Jan 28 00:27:54 svdbslx002 kernel: Pid: 14706, comm: ps Tainted: P U =20
(2.6.5-7.201-smp SLES9_SP2_BRANCH-20050825
0620450000)
Jan 28 00:27:54 svdbslx002 kernel: RIP: 0010:[]=20
{get_user_pages+267}
Jan 28 00:27:54 svdbslx002 kernel: RSP: 0018:00000101d2e8dd58 EFLAGS:=20
00010202
Jan 28 00:27:54 svdbslx002 kernel: RAX: 00009cd0f0009ff8 RBX: 00000000ffffe=
000=20
RCX: 0000010000000000
Jan 28 00:27:54 svdbslx002 kernel: RDX: 00009bd0f0009ff8 RSI: 000ffffffffff=
000=20
RDI: ffffffff803d4f80
Jan 28 00:27:54 svdbslx002 kernel: RBP: 00000101d8d6cc00 R08: 0000000000000=
000=20
R09: 0000000000000001
Jan 28 00:27:54 svdbslx002 kernel: R10: 0000000000000001 R11: 0000000000000=
246=20
R12: 0000000000000000
Jan 28 00:27:54 svdbslx002 kernel: R13: 0000000000000000 R14: 000001017b916=
3e0=20
R15: 0000000000000001
Jan 28 00:27:54 svdbslx002 kernel: FS: 00000000417ff960(0000)=20
GS:ffffffff80562f00(0000) knlGS:00000000557d56a0
Jan 28 00:27:54 svdbslx002 kernel: CS: 0010 DS: 0000 ES: 0000 CR0:=20
000000008005003b
Jan 28 00:27:54 svdbslx002 kernel: CR2: 0000007fbfffbc90 CR3: 000000017ff54=
000=20
CR4: 00000000000006e0
Jan 28 00:27:54 svdbslx002 kernel: Process ps (pid: 14706, threadinfo=20
00000101d2e8c000, task 000001015fecf330)
Jan 28 00:27:54 svdbslx002 kernel: Stack: 00000101e9e263a0 ffffffff8019c54b=
=20
00000101d2e8de98 0000000000000000
Jan 28 00:27:54 svdbslx002 kernel: 000fffffeff80106 0000000000000106=
=20
00000010d2e8dde8 00000000ffffe000
Jan 28 00:27:54 svdbslx002 kernel: 0000000000000001 00000101d2e8de18
Jan 28 00:27:54 svdbslx002 kernel: Call=20
Trace:{real_lookup+123} {access_process
_vm+179}
Jan 28 00:27:54 svdbslx002 kernel: =20
{proc_pid_cmdline+146} {proc_info_rea
d+111}
Jan 28 00:27:54 svdbslx002 kernel: {vfs_read+244}=
=20
{sys_read+157}
Jan 28 00:27:54 svdbslx002 kernel: {sys_open+231}=
=20
{system_call+124}
Jan 28 00:27:54 svdbslx002 kernel:
Jan 28 00:27:54 svdbslx002 kernel:
Jan 28 00:27:54 svdbslx002 kernel: Code: 48 8b 00 48 c1 eb 09 81 e3 f8 0f 0=
0=20
00 48 21 f0 48 01 d8 48
Jan 28 00:27:54 svdbslx002 kernel: RIP {get_user_pages+26=
7}=20
RSP <00000101d2e8dd58>
=2D-----------------snip----------------------

In the web, I found several *shrug*s and vague hints on a nmi watchdog issu=
e.=20
But I have not seen a real solution anywhere. Can YOU tell me more?
=2D-=20
Mit freundlichen Grüßen

i.A. Martin Klier
PC-Benutzerunterstützung / Linux-Server
IT Asset Management

A.T.U - Auto-Teile-Unger
Dr.-Kilian-Straße 11
92637 Weiden

Telefon: (0961) 306-5663
Telefax: (0961) 306-5982

Internet: www.atu.de

Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte
Informationen. Wenn Sie nicht der richtige Adressat sind oder diese E-Mail
irrtümlich erhalten haben, informieren Sie bitte sofort den Absender und
vernichten Sie diese Mail. Das unerlaubte Kopieren sowie die unbefugte
Weitergabe dieser Mail ist nicht gestattet.

--Boundary-02=_TRd3DCPUIy8HbDB
Content-Type: application/pgp-signature
Content-Description: signature

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

iD8DBQBD3dRTVKZfihvnEcQRAsM7AJsHDcN4IKBL8BTvAFhy2hPR7K8gIACg zCUO
zsuizjP5ee3DQBWrtxidAAo=
=NDiO
-----END PGP SIGNATURE-----

--Boundary-02=_TRd3DCPUIy8HbDB--
-
To unsubscribe from this list: send the line "unsubscribe linux-admin" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html

Re: general protection fault: 0000 [1] SMP

--nextPart2245466.SCZL5vySHx
Content-Type: text/plain;
charset="iso-8859-15"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

Hi there,

> Jan 28 00:27:54 svdbslx002 kernel: general protection fault: 0000 [1] SMP
> Jan 28 00:27:54 svdbslx002 kernel: CPU 1
> Jan 28 00:27:54 svdbslx002 kernel: Pid: 14706, comm: ps Tainted: P U
> (2.6.5-7.201-smp SLES9_SP2_BRANCH-20050825
> 0620450000)

I have found the culprit (Novell support helped a lot):
The 2.6.5-7.201 kernel for x86_64 suffered from a racing condition via which
32-bit systemcalls could cause Oopses. As far as I understood occured the=20
problem in memory allocation for 32bit code.

Maybe you want to read=20
http://www.x86-64.org/lists/discuss/msg05795.html
or
http://groups.google.de/group/fa.linux.kernel/browse_thread/ thread/d3d72f30=
1833e6e2/948440747db94d2b?lnk=3Dst&q=3Dkernel%3A+general+pro tection+fault%3=
A+0000+%5B1%5D+SMP&rnum=3D1&hl=3Dde#948440747db94d2b

It will help to upgrade to the 2.6.5-7.244 kernel, available as part of SP3=
or=20
as
the separate patch-10731, "Recommended update for Linux kernel", =20
http://support.novell.com/cgi-bin/search/searchtid.cgi?/psdb /309c95cc337c1c=
860f8b7fd1ef14067a.html

Have care, maybe you will have to re-think your raw device rights managemen=
t=20
after patching to -7.244. Dunno why, but it's fact that since the upgrade t=
he=20
raw binary messes up the given file permissions/ownership/group each time y=
ou=20
(re)map a raw device.

Regards,
=2D-=20
Mit freundlichen Grüßen

i.A. Martin Klier
Serveradministration / Datenbanken

A.T.U - Auto-Teile-Unger
Dr.-Kilian-Straße 11
92637 Weiden

--nextPart2245466.SCZL5vySHx
Content-Type: application/pgp-signature

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

iD8DBQBD9c60VKZfihvnEcQRAlw6AJ9m1qaSRI+8urWqLGcOrR1EiJZLUwCf XIOD
HXTiOCluubeumNXwkU1b7gU=
=jzVq
-----END PGP SIGNATURE-----

--nextPart2245466.SCZL5vySHx--
-
To unsubscribe from this list: send the line "unsubscribe linux-admin" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html