linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Warshall <warshall@99main.com>
To: viro@zeniv.linux.org.uk
Cc: linux-fsdevel@vger.kernel.org
Subject: procfs in linux 3.7.1: OOPS in do_task_stat in fs/proc/array.c
Date: Wed, 2 Jan 2013 13:03:10 -0500	[thread overview]
Message-ID: <20130102130310.2da3e7ab@practicealgebra.net> (raw)

[-- Attachment #1: Type: text/plain, Size: 1545 bytes --]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi-

   Feel free to forward this report to anyone who is actually in charge
   of procfs (I couldn't find a maintainer listed).

   After a recent software upgrade, my machine has become prone to
   oopses, such as the one attached. It can run for hours or a day
   without them, but once they start they keep happening and a hard
   reboot is required. The one attached was the first in a series (I'm
   following the Sherlock Holmes principle that the first one is the
   most useful for debugging what's wrong). They all seem to involve
   the same kernel code being called from potentially different
   userspace programs. Usually the system becomes unusable before
   anything can be properly written to /var/log/sys.log; I was lucky
   this last time, thus enabling me to send this (I hope useful) report.

   Please let me know if there's other info you need about my setup to
   debug this.

                       Thanks,

                       Andrew Warshall
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.13 (GNU/Linux)

iQEcBAEBAgAGBQJQ5HZeAAoJEESPRWh79T7t38kH/2XrEY//SyrxRHi6wEwjvpw7
lvLHW+b+7gqLvhXNIMIIOvZH3emZfnzokVxMS1+/CvYxELNSJhWD9VAYfqpQK1Zz
C+KRhUrDw9CY7zGgjlHLr6sequncW/XEndFZcE4BoehtQ2/LskjtPrXj/d+nQ4Vm
T9Dt/zCYN6Ok6mAuoNIxy4IZ6F2T2dcUdyY3dZUxXL++5YwSq4rmoAgFzklNTWdJ
gquXWVm9VfK7MFAwFnz5tIb9/dQfIJs/3BtTpFoIn172tUr+ravaQkr58iLaDtnw
JyrOzU1UOA4ngze0wgOKRB8dipfBsjp6TkLlDi7D10hKz1Dmk6VAFiVnPW4veqc=
=SAiB
-----END PGP SIGNATURE-----

[-- Attachment #2: oops.log --]
[-- Type: application/octet-stream, Size: 2942 bytes --]

Jan  2 11:50:40 warshall kernel: BUG: unable to handle kernel paging request at 07202704
Jan  2 11:50:40 warshall kernel: IP: [<c10aef19>] do_task_stat+0x84/0xa44
Jan  2 11:50:40 warshall kernel: *pde = 00000000
Jan  2 11:50:40 warshall kernel: Oops: 0000 [#1]
Jan  2 11:50:40 warshall kernel: Pid: 2481, comm: conky Not tainted 3.7.1 #2 To Be Filled By O.E.M. To Be Filled By O.E.M./A76ML-K 30
Jan  2 11:50:40 warshall kernel: EIP: 0060:[<c10aef19>] EFLAGS: 00010202 CPU: 0
Jan  2 11:50:40 warshall kernel: EIP is at do_task_stat+0x84/0xa44
Jan  2 11:50:40 warshall kernel: EAX: 07200720 EBX: f5f28000 ECX: f1448580 EDX: f5cd3a80
Jan  2 11:50:40 warshall kernel: ESI: f5f28000 EDI: f5ddb8c0 EBP: f5cd3a80 ESP: f5fcde54
Jan  2 11:50:40 warshall kernel:  DS: 007b ES: 007b FS: 0000 GS: 00e0 SS: 0068
Jan  2 11:50:40 warshall kernel: CR0: 80050033 CR2: 07202704 CR3: 35d88000 CR4: 000007d0
Jan  2 11:50:40 warshall kernel: DR0: 00000000 DR1: 00000000 DR2: 00000000 DR3: 00000000
Jan  2 11:50:40 warshall kernel: DR6: ffff0ff0 DR7: 00000400
Jan  2 11:50:40 warshall kernel: Process conky (pid: 2481, ti=f5fcc000 task=f5d16d80 task.ti=f5fcc000)
Jan  2 11:50:40 warshall kernel: Stack:
Jan  2 11:50:40 warshall kernel:  f5e9001b 00000004 c10801f6 f5fcdf04 c1080dc7 f5fcde7c f17cac80 00000000
Jan  2 11:50:40 warshall kernel:  00000001 c147f568 f089c300 f5c4fa90 f0890000 00000024 f5dcf580 f6285158
Jan  2 11:50:40 warshall kernel:  f5c4fa90 f089c300 002e3000 f5fcdf04 00000000 f5d16d80 c1082cdf f5fcdf84
Jan  2 11:50:40 warshall kernel: Call Trace:
Jan  2 11:50:40 warshall kernel:  [<c10801f6>] ? __inode_permission+0x21/0x37
Jan  2 11:50:40 warshall kernel:  [<c1080dc7>] ? link_path_walk+0x3c/0x64c
Jan  2 11:50:40 warshall kernel:  [<c1082cdf>] ? path_openat+0x2f9/0x36b
Jan  2 11:50:40 warshall kernel:  [<c11003d8>] ? copy_to_user+0x2b/0x48
Jan  2 11:50:40 warshall kernel:  [<c107cd3b>] ? cp_new_stat64+0x10b/0x11b
Jan  2 11:50:40 warshall kernel:  [<c10aff8e>] ? proc_tgid_stat+0x18/0x1d
Jan  2 11:50:40 warshall kernel:  [<c10abd33>] ? proc_single_show+0x39/0x5d
Jan  2 11:50:40 warshall kernel:  [<c108da8b>] ? seq_read+0x162/0x31c
Jan  2 11:50:40 warshall kernel:  [<c107d384>] ? sys_fstat64+0x1d/0x21
Jan  2 11:50:40 warshall kernel:  [<c108d929>] ? seq_open+0x72/0x72
Jan  2 11:50:40 warshall kernel:  [<c107a27b>] ? vfs_read+0x7f/0xfd
Jan  2 11:50:40 warshall kernel:  [<c107a4f1>] ? sys_read+0x3f/0x6a
Jan  2 11:50:40 warshall kernel:  [<c133df41>] ? sysenter_do_call+0x12/0x22
Jan  2 11:50:40 warshall kernel: Code: 0f b6 d0 88 44 24 72 89 f0 89 54 24 20 e8 49 db f6 ff 85 c0 89 c5 74 2b e8 11 c5 ff ff 83 7c 24 20 00 89 44 24 48 74 35 8b 46 04 <8b> 88 e4 1f 00 00 05 f8 1f 00 00 8b 40 f8 89 4c 24 34 89 44 24
Jan  2 11:50:40 warshall kernel: EIP: [<c10aef19>] do_task_stat+0x84/0xa44 SS:ESP 0068:f5fcde54
Jan  2 11:50:40 warshall kernel: CR2: 0000000007202704
Jan  2 11:50:40 warshall kernel: ---[ end trace 04775951fde67708 ]---

                 reply	other threads:[~2013-01-02 18:40 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20130102130310.2da3e7ab@practicealgebra.net \
    --to=warshall@99main.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=viro@zeniv.linux.org.uk \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).