public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Christophe Dupre <duprec@bloodwolf.org>
To: linux-kernel@vger.kernel.org
Subject: Kernel bug
Date: Sun, 19 Jan 2003 13:01:13 -0500	[thread overview]
Message-ID: <3E2AE7E9.1080804@bloodwolf.org> (raw)

Running Red Hat 7.2 with Red Hat's kernel 2.4.18-19.7.x, I  get this 
error whenever there's a lot of disk activity (such as a backup):

kernel BUG at inode.c:565!
invalid operand: 0000
esp cyclades ip_conntrack_ftp eepro10 3c59x ipt_REHECT iptable_nat 
ip_conntrack
iptable_filter ip_tables st ext3 jbd aic7xxx sd_mod scsi_mod
CPI: 0
EIP: 0010:[<c014c689>]   Not tainted
EFLAGS: 00010206

EIP is at clear_inode [kernel] 0x19 (2.4.19-19.7.x)
eax: cb841060   ebx: cb841040   ecx: cb841040   edx: 00000800
esi: c170ffa8   edi: c170e000   ebp: 0000d6a9   esp: c170ff70
ds: 0018  es: 0018  ss: 0018
Process kswapd (pid: 5, stackpage=c170f000)
Cal Trace: [<c014c797>] dispose_list [kernel] 0x47 (0xc170ff7c))
[<c014c790>] dispose_list [kernel] 0x50 (0xc170ff84))
[<c014ca53>] prune_icache [kernel] 0x123 (0xc170ff98))
[<c014ca90>] shrink_icache_memory [kernel] 0x20 (0xc170ffc0))
[<c0131c9d>] kswapd [kernel] 0x30d (0xc170ffc8))
[<c0105000>] stext [kernel] 0x0 (0xc170ffe8))
[<c0107146>] kernel_thread [kernel] 0x26 (0xc170fff0))
[<c0131990>] kswapd [kernel] 0x0 (0xc170fff8))

Code: 0f 0b 35 02 3d e0 22 c0 8b 83 0c 01 00 00 a9 10 00 00 00 75

The tape backup is SCSI connected to an Adaptec 29160. The disk is IDE. 
The filesystem is ext2fs.

Help would be appreciated.


             reply	other threads:[~2003-01-19 17:51 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-19 18:01 Christophe Dupre [this message]
     [not found] <200907311139.55095.christoph.thielecke@gmx.de>
2009-07-31 16:01 ` kernel bug Linus Torvalds
2009-07-31 16:26   ` Eric Paris
  -- strict thread matches above, loose matches on Subject: below --
2008-09-10 20:35 Todor Gyumyushev
2008-09-11  3:21 ` Aaron Straus
2008-04-13 16:06 monte
2008-04-13 18:20 ` Jesper Juhl
2008-04-13 18:33 ` Alan Cox
2008-03-29  9:05 Olver Eduardo Ramos
2008-03-30  1:06 ` Rafael J. Wysocki
2007-09-19 21:43 Kernel bug Branislav Bozgai
2007-09-24 15:33 ` Mel Gorman
2007-08-19 18:33 kernel bug Costas Sismanis
2006-12-22 11:59 Kernel BUG Rudy Zijlstra
2006-12-22 13:42 ` Peter Zijlstra
2005-11-26  1:23 Kernel bug Vympel
2005-11-27 12:51 ` Hugh Dickins
2005-11-03 18:10 Kernel BUG Mark Fortescue
2005-11-03 18:59 ` Trond Myklebust
2005-11-03 23:15   ` Mark Fortescue
2005-11-04 10:08   ` Mark Fortescue
2003-03-26 23:57 Perez-Gonzalez, Inaky
2003-03-27 14:23 ` Hugh Dickins
2003-03-26 13:13 kasper_k_jensen
2003-01-25 22:56 Kernel bug Massimiliano C. - Uf0On|in3
2003-01-07  9:17 kernel BUG Sönke Ruempler
2002-12-07 10:09 Kernel BUG Henrik Steffen
2002-12-08  1:47 ` Alan Cox
2002-11-27 11:31 kernel bug sanket rathi
2002-11-27 10:45 sanket rathi
2002-11-27  9:50 sanket rathi
2002-11-27 10:10 ` Arjan van de Ven
2002-06-28 19:54 kernel BUG Eric Weiss
2002-06-28 19:26 ew
2002-06-27 19:23 Chaoyang Deng
2002-06-28  5:58 ` Austin Gonyou
2002-06-28 14:00   ` Mike Black
2002-05-21 14:01 kernel bug Chen Hao
2001-11-25 18:03 Kernel Bug gonzalo.ab
2001-11-25 23:59 ` Adam Schrotenboer
2001-03-06 19:55 kernel bug ernte23

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=3E2AE7E9.1080804@bloodwolf.org \
    --to=duprec@bloodwolf.org \
    --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