public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Manivannan Shanmugam <manivannan@newbreak.com>
To: linux-kernel@vger.kernel.org
Subject: Bug report
Date: 03 Mar 2004 16:17:18 +0530	[thread overview]
Message-ID: <1078310837.3192.3.camel@linux0014> (raw)

Hi.

Please find here the bug report and inform us what this is and how can
we avoid this in future. We are facing difficulties with this.

Thanks.
S.Manivannan



_________________________________________________________________________________

kernel BUG at filemap.c:892!
invalid operand: 0000
nfs lockd sunrpc autofs 8139too mii ext3 jbd
CPU:    1
EIP:    0010:[unlock_page+70/112]    Not tainted
EIP:    0010:[<c0130506>]    Not tainted
EFLAGS: 00010246

EIP is at unlock_page [kernel] 0x46 (2.4.20-13.7smp)
eax: c1bbe278   ebx: c030bca0   ecx: 0000001c   edx: 00000000
esi: c1dffd54   edi: 00000000   ebp: f7402f80   esp: f76f3ef0
 ds: 0018   es: 0018   ss: 0018
Process rpciod (pid: 969, stackpage=f76f3000)
Stack: 00001000 c1bbe278 f88ec7ae f76f2000 f7402f80 f75a0380 00000046
00000000
       f759c000 f759c050 f75a7a0c 00000000 f75a0380 f88f2300 f88f2332
f736ba88
       f75a0430 d7a19774 f75a0380 f736ba74 00000001 f75a0380 f75a0424
f75a0380
Call Trace:   [<f88ec7ae>] nfs_readpage_result [nfs] 0x20e (0xf76f3ef8))
[<f88f2300>] nfs3_xdr_readres [nfs] 0x0 (0xf76f3f24))
[<f88f2332>] nfs3_xdr_readres [nfs] 0x32 (0xf76f3f28))
[<f88f2300>] nfs3_xdr_readres [nfs] 0x0 (0xf76f3f50))
[<f88bff73>] call_decode [sunrpc] 0x133 (0xf76f3f58))
[<f88c357d>] __rpc_execute [sunrpc] 0x27d (0xf76f3f78))
[do_softirq+107/208] do_softirq [kernel] 0x6b (0xf76f3f90))
[<c012107b>] do_softirq [kernel] 0x6b (0xf76f3f90))
[<f88c3742>] __rpc_schedule [sunrpc] 0xd2 (0xf76f3fb4))
[<f88c4069>] rpciod [sunrpc] 0xe9 (0xf76f3fc8))
[<f88d2128>] rpciod_killer [sunrpc] 0x0 (0xf76f3fcc))
[arch_kernel_thread+38/48] arch_kernel_thread [kernel] 0x26
(0xf76f3ff0))
[<c0107266>] arch_kernel_thread [kernel] 0x26 (0xf76f3ff0))
[<f88d2128>] rpciod_killer [sunrpc] 0x0 (0xf76f3ff4))
[<f88c3f80>] rpciod [sunrpc] 0x0 (0xf76f3ff8))


Code: 0f 0b 7c 03 50 53 25 c0 8d 46 04 39 46 04 74 10 5b 89 f0 31
	
_________________________________________________________________________________


             reply	other threads:[~2004-03-03 10:44 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-03 10:47 Manivannan Shanmugam [this message]
  -- strict thread matches above, loose matches on Subject: below --
2012-08-20 22:31 Bug report mr.shroom
2012-08-20 22:43 ` Randy Dunlap
2012-08-20 23:16   ` Alan Cox
2012-08-21  9:37 ` Borislav Petkov
2011-10-28 15:55 Hendrik Knackstedt
2011-07-19 17:34 Bug Report Charles Opondo
2011-07-20 15:38 ` Bjorn Helgaas
2008-11-03 18:30 bug report Todor Gyumyushev
2008-09-25 14:08 Todor Gyumyushev
2008-09-24  9:41 Todor Gyumyushev
2008-09-24 16:38 ` Simon Holm Thøgersen
2008-09-24 17:55   ` Todor Gyumyushev
2008-09-24 18:25     ` Simon Holm Thøgersen
2008-09-29  1:36       ` Tejun Heo
2008-09-29  8:30         ` Todor Gyumyushev
2008-09-30 11:47           ` Tejun Heo
2008-06-06 19:59 Zsiros Attila
2008-06-07  1:44 ` Oliver Pinter
2008-06-07  1:45   ` Oliver Pinter
2008-06-07  5:56   ` Andrew Morton
2008-06-07  8:47     ` Ilpo Järvinen
2008-06-07 12:50       ` Oliver Pinter
2008-06-07 15:09         ` Phil Oester
2008-06-07 18:53           ` Oliver Pinter
2008-06-08 11:56             ` Zsiros Attila
2008-06-09 17:04               ` Oliver Pinter
2006-07-09  2:04 BUG report Antonio Mignolli
2006-07-12 10:56 ` Markus Rechberger
2004-12-25 13:00 Bug report Ioannis Fikouras
2002-10-04 15:01 bug report Sander Kamphuis
2002-10-04 15:32 ` Paulo Andre'
2002-10-04 15:35 ` Adrian Bunk
2002-04-24  9:15 Pan,Gaoyong
2002-03-04 16:04 Vitaly Fertman
2001-11-27 15:04 Bug (?) report Matteo Sasso
2001-11-27 15:51 ` Tommy Reynolds
2001-11-10 19:01 Bug Report Logoth Dragon
2001-11-10 19:08 ` Alan Cox
2001-08-02  9:38 Bug report Daniel Glozman
2001-03-22 20:58 Craig Cummings
2001-03-22 21:43 ` Tim Walberg
2001-02-01 22:09 Anders S. Buch
2001-02-03  1:44 ` Jens Axboe

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=1078310837.3192.3.camel@linux0014 \
    --to=manivannan@newbreak.com \
    --cc=linux-kernel@vger.kernel.org \
    /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