public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andreas Schmidt <andy@space.wh1.tu-dresden.de>
To: linux-kernel@vger.kernel.org
Subject: Re: Frequent system freezes after kernel bug
Date: Wed, 16 Jun 2004 09:23:44 +0200	[thread overview]
Message-ID: <20040616072344.GC28402@rocket> (raw)
In-Reply-To: <20040612183742.GE1733@rocket> (from andy@space.wh1.tu-dresden.de on Sat, Jun 12, 2004 at 20:37:42 +0200)

On 2004.06.12 20:37, Andreas Schmidt wrote:
> Hi,
> 
> in the last few days I have experienced frequent system freezes
> apparently related to kernel bugs on one box here. Unfortunately,
> that's just the same system serving as router and local fileserver  
> for
I have removed the tainted fcdsl-module and tried to crash the machine  
by generating a steady harddisk activity. Writing to a partition with  
EXT2 resulted in two non-fatal bugs in buffer.c after several hours:

19:09:32
kernel:  kernel BUG at buffer.c:575!
kernel: invalid operand: 0000
kernel: CPU:    0
kernel: EIP:    0010:[__insert_into_lru_list+28/112]    Not tainted
kernel: EFLAGS: 00010206
kernel: eax: 00000000   ebx: 00000002   ecx: d2e980c0   edx: c02ad6cc
kernel: esi: d2e980c0   edi: d2e980c0   ebp: 00000001   esp: c4677ebc
kernel: ds: 0018   es: 0018   ss: 0018
kernel: Process cp (pid: 4081, stackpage=c4677000)
kernel: Stack: 00000002 c0135a36 d2e980c0 00000002 d2e980c0 00001000  
c0135a4a d2e980c0
kernel:        c0136443 d2e980c0 00001000 dc1bc0c0 06261000 00000000  
00001000 00000000
kernel:        c0136ab4 dc1bc0c0 c130e514 00000000 00001000 c130e514  
bffff404 d1c7b000
kernel: Call Trace:    [__refile_buffer+86/96] [refile_buffer+10/16]  
[__block_commit_write+131/208] [generic_commit_write+52/96]  
[do_generic_file_write+654/976]
kernel:   [generic_file_write+259/288] [sys_write+150/240] [system_call 
+51/56]
kernel:
kernel: Code: 0f 0b 3f 02 e5 57 21 c0 83 3a 00 75 05 89 0a 89 49 24 8b  
02

04:47:01
kernel:  kernel BUG at buffer.c:575!
kernel: invalid operand: 0000
kernel: CPU:    0
kernel: EIP:
0010:[__insert_into_lru_list+28/112]    Not tainted
kernel: EFLAGS: 00010206
kernel: eax: 00000000   ebx: 00000002   ecx: d07e80c0   edx: c02ad6cc
kernel: esi: d07e80c0   edi: d07e80c0   ebp: 00000001   esp: c2d85ebc
kernel: ds: 0018   es: 0018   ss: 0018
kernel: Process cp (pid: 760, stackpage=c2d85000)
kernel: Stack: 00000002 c0135a36 d07e80c0 00000002 d07e80c0 00001000  
c0135a4a d07e80c0
kernel:        c0136443 d07e80c0 00001000 cee62ac0 0c7b4000 00000000  
00001000 00000000
kernel:        c0136ab4 cee62ac0 c14be3d4 00000000 00001000 c14be3d4  
bffff3d4 db98b000
kernel: Call Trace:    [__refile_buffer+86/96] [refile_buffer+10/16]  
[__block_commit_write+131/208] [generic_commit_write+52/96]  
[do_generic_file_write+654/976]
kernel:   [generic_file_write+259/288] [sys_write+150/240] [system_call 
+51/56]
kernel:
kernel: Code: 0f 0b 3f 02 e5 57 21 c0 83 3a 00 75 05 89 0a 89 49 24 8b  
02


Thereafter, I tried to continuously writing to an EXT3 partition, which  
after just about half an hour resulted in bugs in buffer.c and   
transaction.c. This time, the system froze again. "init 6" stopped  
after sending the KILL signal because the processes with IDs "ca" and   
"1" to "6" were hanging. Here's the output:

kernel:  kernel BUG at buffer.c:575!
kernel: invalid operand: 0000
kernel: CPU:    0
kernel: EIP:    0010:[__insert_into_lru_list+28/112]    Not tainted
kernel: EFLAGS: 00010206
kernel: eax: 00000000   ebx: 00000002   ecx: d07b80c0   edx: c02ad6cc
kernel: esi: d07b80c0   edi: d07b80c0   ebp: 00000001   esp: c6195e6c
kernel: ds: 0018   es: 0018   ss: 0018
kernel: Process cp (pid: 3627, stackpage=c6195000)
kernel: Stack: 00000002 c0135a36 d07b80c0 00000002 d07b80c0 00001000  
c0135a4a d07b80c0
kernel:        c0136443 d07b80c0 00001000 c648bc80 07df7000 00000000  
00001000 00000000
kernel:        c0136ab4 c648bc80 c105c770 00000000 00001000 c105c770  
bffff3e4 c648bc80
kernel: Call Trace:    [__refile_buffer+86/96] [refile_buffer+10/16]  
[__block_commit_write+131/208] [generic_commit_write+52/96]  
[ext3_commit_write+305/448]
kernel:   [do_generic_file_write+654/976] [generic_file_write+259/288]  
[ext3_file_write+35/192] [sys_write+150/240] [system_call+51/56]
kernel:
kernel: Code: 0f 0b 3f 02 e5 57 21 c0 83 3a 00 75 05 89 0a 89 49 24 8b  
02
kernel:  <0>Assertion failure in journal_start() at transaction.c:251:  
"handle->h_transaction->t_journal == journal"
kernel: kernel BUG at transaction.c:251!
kernel: invalid operand: 0000
kernel: CPU:    0
kernel: EIP:    0010:[journal_start+74/192]   Not tainted
kernel: EFLAGS: 00010282
kernel: eax: 0000006c   ebx: d3ea6600   ecx: df37e000   edx: 00000001
kernel: esi: dfe49800   edi: c6194000   ebp: 00000040   esp: c6195c10
kernel: ds: 0018   es: 0018   ss: 0018
kernel: Process cp (pid: 3627, stackpage=c6195000)
kernel: Stack: c021b240 c021b46c c021b220 000000fb c021b440 d3ea6600  
dfae0c00 c419d6c0
kernel:        c015ea38 dfe49800 00000002 c419d6c0 dfae0c00 00000001  
c014642e c419d6c0
kernel:        c419d6c0 c419d72c d163cec0 c0128c93 c419d6c0 00000001  
c419d6c0 c419d72c
kernel: Call Trace:    [ext3_dirty_inode+88/256] [__mark_inode_dirty 
+46/144] [do_generic_file_write+211/976] [ide_start_request+382/432]  
[generic_file_write+259/288]
kernel:   [ext3_file_write+35/192] [do_acct_process+571/592]  
[acct_process+25/39] [do_exit+105/592] [do_invalid_op+0/160] [die 
+86/96]
kernel:   [do_invalid_op+140/160] [__insert_into_lru_list+28/112]  
[ext3_get_block_handle+426/640] [ext3_get_block_handle+242/640]  
[error_code+52/60] [__insert_into_lru_list+28/112]
kernel:   [__refile_buffer+86/96] [refile_buffer+10/16]  
[__block_commit_write+131/208] [generic_commit_write+52/96]  
[ext3_commit_write+305/448] [do_generic_file_write+654/976]
kernel:   [generic_file_write+259/288] [ext3_file_write+35/192]  
[sys_write+150/240] [system_call+51/56]
kernel:
kernel: Code: 0f 0b fb 00 20 b2 21 c0 83 c4 14 ff 43 08 89 d8 eb 59 8d  
74

Best regards,

Andreas

      parent reply	other threads:[~2004-06-16  7:24 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-12 18:37 Frequent system freezes after kernel bug Andreas Schmidt
2004-06-12 20:20 ` Chris Wedgwood
2004-06-12 21:49   ` Andreas Schmidt
2004-06-13  0:10     ` Christian Kujau
2004-06-13 17:51       ` Andreas Schmidt
2004-06-13 22:14         ` Christian Kujau
2004-06-14  3:51           ` Andreas Schmidt
2004-06-16  7:23 ` Andreas Schmidt [this message]

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=20040616072344.GC28402@rocket \
    --to=andy@space.wh1.tu-dresden.de \
    --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