From: Jerry Geis <geisj@pagestation.com>
To: Tarkan Erimer <tarkan@netone.net.tr>
Cc: Arjan van de Ven <arjan@infradead.org>, linux-kernel@vger.kernel.org
Subject: Re: Kernel BUG in 2.6.23.9
Date: Mon, 10 Dec 2007 10:42:19 -0500 [thread overview]
Message-ID: <475D5E5B.6000506@pagestation.com> (raw)
In-Reply-To: <475D5D53.8070906@netone.net.tr>
Tarkan Erimer wrote:
> Arjan van de Ven wrote:
>> well... try to get the oops message out; for many causes of crash
>> that's a good way to find out what happened...
>> (not always, but it allows us to find patterns if nothing else)
>>
>>
> Unfortunately, I couldn't get the oops message. Because when this
> behavior happens, the machine hardly freezes and the SysRq
> combinations do not work. Also, I checked the logs
> (message,syslog,kern.log etc.) to see something suspicious.
> Unfortunately, there was none. Just one thing I noticed when
> investigating on the logs: the kernel is doing its regular jobs. Like
> cron etc. So, the kernel is not really dieing. Next time, I will try
> to ssh to my machine to check what's going on, when this behavior
> occurred.
>
I agree, the kernel is not completely dead. I could ping my box but
nothing else.
This was the /var/log/messages I had:
Dec 8 22:23:57 devcentos5x64 kernel: Assertion failure in journal_dirty_data() at fs/jbd/transaction.c:983: "jh->b_transaction == journal->j_committing_transaction"
Dec 8 22:23:57 devcentos5x64 kernel: ------------[ cut here ]------------
Dec 8 22:23:57 devcentos5x64 kernel: kernel BUG at fs/jbd/transaction.c:983!
Dec 8 22:23:57 devcentos5x64 kernel: invalid opcode: 0000 [1] SMP
Dec 8 22:23:57 devcentos5x64 kernel: CPU 1
Dec 8 22:23:57 devcentos5x64 kernel: Modules linked in: zttranscode nfsd exportfs lockd nfs_acl auth_rpcgss autofs4 hidp rfcomm l2cap bluetooth sunrpc wcusb wctdm wcfxo wcte11xp wct1xxp wcte12xp wct4xxp tor2 nf_conntrack_netbios_ns ipt_REJECT nf_conntrack_ipv4 xt_state nf_conntrack nfnetlink iptable_filter ip_tables ip6t_REJECT xt_tcpudp ip6table_filter ip6_tables x_tables cpufreq_ondemand dm_mirror dm_multipath dm_mod video output sbs battery ac ipv6 lp shpchp snd_hda_intel snd_seq_dummy snd_seq_oss snd_seq_midi_event snd_seq snd_seq_device snd_pcm_oss snd_mixer_oss snd_pcm nvidia(P) snd_timer wctdm24xxp snd zaptel soundcore sr_mod forcedeth sg parport_pc snd_page_alloc crc_ccitt serio_raw cdrom parport i2c_nforce2 usb_storage i2c_core button sata_nv libata sd_mod scsi_mod raid1 ext3 jbd ehci_hcd ohci_hcd uhci_hcd
Dec 8 22:23:57 devcentos5x64 kernel: Pid: 5028, comm: rsync Tainted: P 2.6.23.9 #1
Dec 8 22:23:57 devcentos5x64 kernel: RIP: 0010:[<ffffffff88034a3b>] [<ffffffff88034a3b>] :jbd:journal_dirty_data+0xad/0x1ed
Dec 8 22:23:57 devcentos5x64 kernel: RSP: 0018:ffff810095edd7e8 EFLAGS: 00010292
Dec 8 22:23:57 devcentos5x64 kernel: RAX: 0000000000000083 RBX: ffff81008e1f50c8 RCX: ffffffff81344c28
Dec 8 22:23:57 devcentos5x64 kernel: RDX: 0000000100000000 RSI: 0000000000000096 RDI: ffffffff81344c20
Dec 8 22:23:57 devcentos5x64 kernel: RBP: ffff81009b42fdf4 R08: ffffffff81344c28 R09: 00000002ffffffff
Dec 8 22:23:57 devcentos5x64 kernel: R10: 0000000000000046 R11: ffffffff813b8000 R12: ffff8100c082b348
Dec 8 22:23:58 devcentos5x64 kernel: R13: ffff81010ce3cc00 R14: 0000000000000000 R15: 0000000000000000
Dec 8 22:23:58 devcentos5x64 kernel: FS: 00002ae6d4b2b560(0000) GS:ffff81011fa9a6c0(0000) knlGS:00000000f7f009a0
Dec 8 22:23:58 devcentos5x64 kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b
Dec 8 22:23:58 devcentos5x64 kernel: CR2: 00002aea6b0d30a8 CR3: 00000000959f0000 CR4: 00000000000006e0
Dec 8 22:23:58 devcentos5x64 kernel: DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
Dec 8 22:23:58 devcentos5x64 kernel: DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
Dec 8 22:23:58 devcentos5x64 kernel: Process rsync (pid: 5028, threadinfo ffff810095edc000, task ffff8100ccc78000)
Dec 8 22:23:58 devcentos5x64 kernel: Stack: 0000000000001000 ffff8100c082b348 ffff81008e1f50c8 ffff81008e1f50c8
Dec 8 22:23:58 devcentos5x64 kernel: ffff81008e1f50c8 ffffffff8804ff8f 0000000000001000 0000000000001000
Dec 8 22:23:58 devcentos5x64 kernel: 0000000000001000 ffffffff8804f437 ffffffff8804ffb4 0000000000001000
Dec 8 22:23:58 devcentos5x64 kernel: Call Trace:
Dec 8 22:23:58 devcentos5x64 kernel: [<ffffffff8804ff8f>] :ext3:ext3_journal_dirty_data+0xf/0x34
Dec 8 22:23:58 devcentos5x64 kernel: [<ffffffff8804f437>] :ext3:walk_page_buffers+0x65/0x8b
Dec 8 22:23:58 devcentos5x64 kernel: [<ffffffff8804ffb4>] :ext3:journal_dirty_data_fn+0x0/0xe
Dec 8 22:23:58 devcentos5x64 kernel: [<ffffffff880521da>] :ext3:ext3_ordered_writepage+0x108/0x18c
Dec 8 22:23:58 devcentos5x64 kernel: [<ffffffff8106bf9a>] __writepage+0xa/0x23
Dec 8 22:23:58 devcentos5x64 kernel: [<ffffffff8106c4b8>] write_cache_pages+0x17b/0x2aa
Dec 8 22:23:58 devcentos5x64 kernel: [<ffffffff8106bf90>] __writepage+0x0/0x23
Dec 8 22:23:58 devcentos5x64 kernel: [<ffffffff8106c62a>] do_writepages+0x27/0x2d
Dec 8 22:23:58 devcentos5x64 kernel: [<ffffffff810a8749>] __writeback_single_inode+0x1ba/0x332
Dec 8 22:23:58 devcentos5x64 kernel: [<ffffffff8805b7ea>] :ext3:__ext3_journal_dirty_metadata+0x1e/0x46
Dec 8 22:23:58 devcentos5x64 kernel: [<ffffffff810a8c00>] sync_sb_inodes+0x1a3/0x261
Dec 8 22:23:58 devcentos5x64 kernel: [<ffffffff810a9030>] writeback_inodes+0x82/0xd8
Dec 8 22:23:58 devcentos5x64 kernel: [<ffffffff8106c869>] balance_dirty_pages_ratelimited_nr+0x114/0x1f4
Dec 8 22:23:58 devcentos5x64 kernel: [<ffffffff81068168>] generic_file_buffered_write+0x62d/0x751
Dec 8 22:23:58 devcentos5x64 kernel: [<ffffffff810685c8>] __generic_file_aio_write_nolock+0x33c/0x3a6
Dec 8 22:23:58 devcentos5x64 kernel: [<ffffffff811ec26b>] sock_aio_read+0x10c/0x124
Dec 8 22:23:58 devcentos5x64 kernel: [<ffffffff81068693>] generic_file_aio_write+0x61/0xc1
Dec 8 22:23:58 devcentos5x64 kernel: [<ffffffff8804e1ae>] :ext3:ext3_file_write+0x16/0x94
Dec 8 22:23:58 devcentos5x64 kernel: [<ffffffff8108d950>] do_sync_write+0xc9/0x10c
Dec 8 22:23:58 devcentos5x64 kernel: [<ffffffff8104912d>] autoremove_wake_function+0x0/0x2e
Dec 8 22:23:58 devcentos5x64 kernel: [<ffffffff8108e118>] vfs_write+0xce/0x157
Dec 8 22:23:58 devcentos5x64 kernel: [<ffffffff8108e676>] sys_write+0x45/0x6e
Dec 8 22:23:58 devcentos5x64 kernel: [<ffffffff8100bdfc>] tracesys+0xdc/0xe1
Dec 8 22:23:58 devcentos5x64 kernel:
Dec 8 22:23:58 devcentos5x64 kernel:
Dec 8 22:23:58 devcentos5x64 kernel: Code: 0f 0b eb fe 8b 45 0c 83 f8 01 76 09 83 f8 08 0f 85 eb 00 00
Dec 8 22:23:58 devcentos5x64 kernel: RIP [<ffffffff88034a3b>] :jbd:journal_dirty_data+0xad/0x1ed
Dec 8 22:23:58 devcentos5x64 kernel: RSP <ffff810095edd7e8>
prev parent reply other threads:[~2007-12-10 15:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-09 19:49 Kernel BUG in 2.6.23.9 Jerry Geis
2007-12-09 21:44 ` Arjan van de Ven
2007-12-10 9:14 ` Tarkan Erimer
2007-12-10 11:40 ` Jerry Geis
2007-12-10 12:02 ` Tarkan Erimer
2007-12-10 14:45 ` Arjan van de Ven
2007-12-10 15:37 ` Tarkan Erimer
2007-12-10 15:42 ` Jerry Geis [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=475D5E5B.6000506@pagestation.com \
--to=geisj@pagestation.com \
--cc=arjan@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tarkan@netone.net.tr \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.