LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Andrew Morton <akpm@osdl.org>
To: tmp <skrald@amossen.dk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Kernel OOPS
Date: Sun, 16 May 2004 16:27:16 -0700	[thread overview]
Message-ID: <20040516162716.34f3d94a.akpm@osdl.org> (raw)
In-Reply-To: <1084709330.743.8.camel@debian>

tmp <skrald@amossen.dk> wrote:
>
> I get the attached oops message in syslog on my 2.6.6 kernel. I have
>  also attached the ksymoops output.
> 
>  When the oops has occured, I cannot open any shell (including a login
>  shell).
> 
> 
> 
> [oops1.txt  text/plain (2452 bytes)]
>  May 16 13:29:34 debian kernel: Unable to handle kernel paging request at virtual address 1841b518
>  May 16 13:29:34 debian kernel:  printing eip:
>  May 16 13:29:34 debian kernel: c016c02e
>  May 16 13:29:34 debian kernel: *pde = 00000000
>  May 16 13:29:34 debian kernel: Oops: 0000 [#1]
>  May 16 13:29:34 debian kernel: CPU:    0
>  May 16 13:29:34 debian kernel: EIP:    0060:[proc_get_inode+110/272]    Not tainted
>  May 16 13:29:34 debian kernel: EFLAGS: 00010202   (2.6.6) 
>  May 16 13:29:34 debian kernel: EIP is at proc_get_inode+0x6e/0x110
>  May 16 13:29:34 debian kernel: eax: 00000000   ebx: df107850   ecx: 0114df68   edx: 36013bf9
>  May 16 13:29:34 debian kernel: esi: dffec810   edi: dffdee00   ebp: 00000007   esp: d5037e30
>  May 16 13:29:34 debian kernel: ds: 007b   es: 007b   ss: 0068
>  May 16 13:29:35 debian kernel: Process emacs (pid: 743, threadinfo=d5036000 task=d3ec8030)
>  May 16 13:29:35 debian kernel: Stack: df107850 f0000000 df7f19c0 e0820ead dffec810 c5bef353 dffec863 c016e8e3 
>  May 16 13:29:35 debian kernel:        dffdee00 f0000000 dffec810 ffffffea 00000000 dffdddd0 d5037f70 c5bef2d0 
>  May 16 13:29:35 debian kernel:        c5bef2d0 c016c1d1 dffdddd0 c5bef2d0 d5037f70 fffffff4 dffdde38 dffdddd0 
>  May 16 13:29:35 debian kernel: Call Trace:
>  May 16 13:29:35 debian kernel:  [pg0+541367981/1069707264] unix_stream_sendmsg+0x24d/0x3a0 [unix]
>  May 16 13:29:35 debian kernel:  [proc_lookup+179/192] proc_lookup+0xb3/0xc0
>  May 16 13:29:35 debian kernel:  [proc_root_lookup+49/128] proc_root_lookup+0x31/0x80
>  May 16 13:29:35 debian kernel:  [real_lookup+203/240] real_lookup+0xcb/0xf0
>  May 16 13:29:35 debian kernel:  [do_lookup+150/176] do_lookup+0x96/0xb0
>  May 16 13:29:35 debian kernel:  [link_path_walk+1052/2048] link_path_walk+0x41c/0x800
>  May 16 13:29:35 debian kernel:  [path_lookup+105/272] path_lookup+0x69/0x110
>  May 16 13:29:35 debian kernel:  [open_namei+131/1024] open_namei+0x83/0x400
>  May 16 13:29:35 debian kernel:  [__pollwait+0/208] __pollwait+0x0/0xd0
>  May 16 13:29:35 debian kernel:  [filp_open+62/112] filp_open+0x3e/0x70

It's a bit strange that no registers have a value vaguely like
0x1841b518, but at a guess I'd say that you have a bad ->owner
pointer in a /proc inode.

What modules are you using, and had any modules been rmmod'ed prior
to the crash?

  reply	other threads:[~2004-05-16 23:27 UTC|newest]

Thread overview: 61+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-16 12:08 tmp
2004-05-16 23:27 ` Andrew Morton [this message]
2004-05-17  0:33   ` tmp
  -- strict thread matches above, loose matches on Subject: below --
2008-07-23 12:52 kernel oops Andrei Popa
2008-07-23 17:11 ` Vegard Nossum
2008-08-18 16:33   ` Vegard Nossum
2008-08-18 16:39     ` Greg KH
     [not found] <e8eb01770803120245x7690e6a9te8ad04296aa3fc4d@mail.gmail.com>
2008-03-12  9:49 ` Zbynek Drlik
2008-03-12 10:33   ` Al Viro
2008-03-12 13:12     ` Zbynek Drlik
2008-02-05 12:57 Andrej Hocevar
2008-02-06 17:55 ` Len Brown
2006-09-12 10:21 Kernel Oops Marcin Prączko
2006-09-13  3:43 ` Andrew Morton
2005-10-15  1:03 Marc Perkel
2005-10-15  1:21 ` Randy.Dunlap
2005-10-15  1:43   ` Marc Perkel
2005-10-15  1:52     ` Randy.Dunlap
2005-01-03 21:10 Kernel oops Marat BN
2005-01-05 10:13 ` Andrew Morton
2004-06-11  7:27 tmp
2004-05-24 20:19 tmp
2004-03-09 22:13 Philipp Baer
2004-03-09 23:11 ` Andrew Morton
2004-03-12  7:46   ` Philipp Baer
2004-02-08 11:05 Kernel Oops Mathieu LESNIAK
2004-02-08 16:35 ` Greg KH
2004-02-09  7:06   ` Mathieu LESNIAK
2003-11-28 23:15 Kernel oops Ville Jutvik
2003-11-28  5:45 Anderson Levi
2003-08-09 12:39 kernel oops Jean-Yves LENHOF
2003-08-09 20:37 ` Jean-Yves LENHOF
2003-08-09  9:28 Jean-Yves LENHOF
2003-07-18 19:44 Kernel OOPS Robert Scussel
2003-07-18 21:31 ` Alan Cox
2003-07-07 12:53 kernel oops Anders Karlsson
2003-07-07 13:14 ` Alan Cox
2003-07-07 13:32   ` Anders Karlsson
2003-07-07 13:37     ` Alan Cox
2003-07-07 13:56       ` Anders Karlsson
2003-07-08  9:39         ` Marcelo Tosatti
     [not found] ` <200307072009.50677.bernd-schubert@web.de>
2003-07-08  5:13   ` Anders Karlsson
2003-05-31  1:32 Nadeem Riaz
2003-03-26 15:52 Steve Terrell
2003-02-03  1:18 Kernel Oops Daniel Espinoza
2003-02-03  3:23 ` vishwas
2002-08-09  5:25 sanket rathi
2002-06-23 19:39 Dirk Schmidt
2002-06-10  8:46 kernel oops Robert Litwiniec
2002-02-26 18:26 Suporte RedeBonja
2002-02-27 13:35 ` Erik Mouw
2001-11-13 13:23 Kernel oops Anthony
2001-11-14  6:02 ` Thiago Rondon
2001-10-08 12:59 kernel oops Terry Kendal
2001-09-27  9:49 kewl
2001-06-01 15:13 Kernel oops David Harris
2001-06-01 15:12 David Harris
2001-04-19 18:32 kernel oops Ronald Bultje
2001-04-19 19:04 ` Alan Cox
2001-04-19 19:08   ` Ronald Bultje
2001-02-19 14:44 Kernel Oops Alberto Bertogli

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=20040516162716.34f3d94a.akpm@osdl.org \
    --to=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=skrald@amossen.dk \
    --subject='Re: Kernel OOPS' \
    /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

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).