Re: Kernel BUG in 2.6.23.9
Arjan van de Ven wrote: On Sun, 09 Dec 2007 14:49:16 -0500 Jerry Geis <[EMAIL PROTECTED]> wrote: I am using centos 5.1, 2.6.23.9 kernel. Machine works great all day. Then sometime through the night the kernel dies, the trace is below. is this when a 3D screensaver is active? Probably worth running without the proprietary nvidia driver it also tends to get more people to pay attention :) In addition to this suspicion; you're the first one to report this oops since at least a year as shown in http://www.kerneloops.org/guilty.php?guilty=journal_dirty_data=2.6.23-release=1540096=1572863 so it might well be something weird on your side (like the binary driver or some heat problem created by having a 3D screensaver) Hi, For a while, I have the same behavior. I tested under 2.6.23.9, 2.6.24-rc3 and rc4. So all of these kernels have the same issue. Also, I don't use any proprietary driver. My video card is Intel-945 and I use the "intel" driver. I use 3D screensavers as well. These kernels die after some long idles like 1 or 2 days after. My distribution is Kubuntu 7.10 and with Kubuntu kernel this behavior did not happened. So, how to track this interesting problem ? Any ideas welcomed :-) Cheers, Tarkan Erimer -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Kernel BUG in 2.6.23.9
Arjan van de Ven wrote: On Sun, 09 Dec 2007 14:49:16 -0500 Jerry Geis [EMAIL PROTECTED] wrote: I am using centos 5.1, 2.6.23.9 kernel. Machine works great all day. Then sometime through the night the kernel dies, the trace is below. is this when a 3D screensaver is active? Probably worth running without the proprietary nvidia driver it also tends to get more people to pay attention :) In addition to this suspicion; you're the first one to report this oops since at least a year as shown in http://www.kerneloops.org/guilty.php?guilty=journal_dirty_dataversion=2.6.23-releasestart=1540096end=1572863 so it might well be something weird on your side (like the binary driver or some heat problem created by having a 3D screensaver) Hi, For a while, I have the same behavior. I tested under 2.6.23.9, 2.6.24-rc3 and rc4. So all of these kernels have the same issue. Also, I don't use any proprietary driver. My video card is Intel-945 and I use the intel driver. I use 3D screensavers as well. These kernels die after some long idles like 1 or 2 days after. My distribution is Kubuntu 7.10 and with Kubuntu kernel this behavior did not happened. So, how to track this interesting problem ? Any ideas welcomed :-) Cheers, Tarkan Erimer -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Kernel BUG in 2.6.23.9
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: [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:[] [] :jbd:journal_dirty_data+0xad/0x1ed Dec 8 22:23:57 devcentos5x64 kernel: RSP: 0018:810095edd7e8 EFLAGS: 00010292 Dec 8 22:23:57 devcentos5x64 kernel: RAX: 0083 RBX: 81008e1f50c8 RCX: 81344c28 Dec 8 22:23:57 devcentos5x64 kernel: RDX: 0001 RSI: 0096 RDI: 81344c20 Dec 8 22:23:57 devcentos5x64 kernel: RBP: 81009b42fdf4 R08: 81344c28 R09: 0002 Dec 8 22:23:57 devcentos5x64 kernel: R10: 0046 R11: 813b8000 R12: 8100c082b348 Dec 8 22:23:58 devcentos5x64 kernel: R13: 81010ce3cc00 R14: R15: Dec 8 22:23:58 devcentos5x64 kernel: FS: 2ae6d4b2b560() GS:81011fa9a6c0() knlGS:f7f009a0 Dec 8 22:23:58 devcentos5x64 kernel: CS: 0010 DS: ES: CR0: 8005003b Dec 8 22:23:58 devcentos5x64 kernel: CR2: 2aea6b0d30a8 CR3: 959f CR4: 06e0 Dec 8 22:23:58 devcentos5x64 kernel: DR0: DR1: DR2: Dec 8 22:23:58 devcentos5x64 kernel: DR3: DR6: 0ff0 DR7: 0400 Dec 8 22:23:58 devcentos5x64 kernel: Process rsync (pid: 5028, threadinfo 810095edc000, task 8100ccc78000) Dec 8 22:23:58 devcentos5x64 kernel: Stack: 1000 8100c082b348 81008e1f50c8 81008e1f50c8 Dec 8 22:23:58 devcentos5x64 kernel: 81008e1f50c8 8804ff8f 1000 1000 Dec 8 22:23:58 devcentos5x64 kernel: 1000 8804f437 8804ffb4 1000 Dec 8 22:23:58 devcentos5x64 kernel: Call Trace: Dec 8 22:23:58 devcentos5x64 kernel: [] :ext3:ext3_journal_dirty_data+0xf/0x34 Dec 8 22:23:58 devcentos5x64 kernel: [] :ext3:walk_page_buffers+0x65/0x8b Dec 8 22:23:58 devcentos5x64 kernel: [] :ext3:journal_dirty_data_fn+0x0/0xe Dec 8 22:23:58 devcentos5x64 kernel: [] :ext3:ext3_ordered_writepage+0x108/0x18c Dec 8 22:23:58 devcentos5x64 kernel: [] __writepage+0xa/0x23 Dec 8 22:23:58 devcentos5x64 kernel: [] write_cache_pages+0x17b/0x2aa Dec 8 22:23:58 devcentos5x64 kernel: [] __writepage+0x0/0x23 Dec 8 22:23:58 devcentos5x64 kernel: [] do_writepages+0x27/0x2d Dec 8 22:23:58 devcentos5x64 kernel: [] __writeback_single_inode+0x1ba/0x332 Dec 8 22:23:58 devcentos5x64 kernel: [] :ext3:__ext3_journal_dirty_metadata+0x1e/0x46 Dec 8 22:23:58 devcentos5x64 kernel: [] sync_sb_inodes+0x1a3/0x261 Dec 8 22:23:58 devcentos5x64 kernel: [] writeback_inodes+0x82/0xd8 Dec 8 22:23:58 devcentos5x64 kernel: [] balance_dirty_pages_ratelimited_nr+0x114/0x1f4 Dec 8 22:23:58 devcentos5x64 kernel: []
Re: Kernel BUG in 2.6.23.9
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. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Kernel BUG in 2.6.23.9
On Mon, 10 Dec 2007 11:14:47 +0200 Tarkan Erimer <[EMAIL PROTECTED]> wrote: > Hi, > > For a while, I have the same behavior. I tested under 2.6.23.9, > 2.6.24-rc3 and rc4. So all of these kernels have the same issue. > Also, I don't use any proprietary driver. My video card is Intel-945 > and I use the "intel" driver. I use 3D screensavers as well. These > kernels die after some long idles like 1 or 2 days after. My > distribution is Kubuntu 7.10 and with Kubuntu kernel this behavior > did not happened. So, how to track this interesting problem ? Any > ideas welcomed :-) > 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) -- If you want to reach me at my work email, use [EMAIL PROTECTED] For development, discussion and tips for power savings, visit http://www.lesswatts.org -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Kernel BUG in 2.6.23.9
Arjan van de Ven wrote: On Sun, 09 Dec 2007 14:49:16 -0500 Jerry Geis <[EMAIL PROTECTED]> wrote: I am using centos 5.1, 2.6.23.9 kernel. Machine works great all day. Then sometime through the night the kernel dies, the trace is below. is this when a 3D screensaver is active? Probably worth running without the proprietary nvidia driver it also tends to get more people to pay attention :) In addition to this suspicion; you're the first one to report this oops since at least a year as shown in http://www.kerneloops.org/guilty.php?guilty=journal_dirty_data=2.6.23-release=1540096=1572863 so it might well be something weird on your side (like the binary driver or some heat problem created by having a 3D screensaver) Hi, For a while, I have the same behavior. I tested under 2.6.23.9, 2.6.24-rc3 and rc4. So all of these kernels have the same issue. Also, I don't use any proprietary driver. My video card is Intel-945 and I use the "intel" driver. I use 3D screensavers as well. These kernels die after some long idles like 1 or 2 days after. My distribution is Kubuntu 7.10 and with Kubuntu kernel this behavior did not happened. So, how to track this interesting problem ? Any ideas welcomed :-) Cheers, Tarkan Erimer -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Kernel BUG in 2.6.23.9
Tarkan Erimer wrote: Arjan van de Ven wrote: On Sun, 09 Dec 2007 14:49:16 -0500 Jerry Geis <[EMAIL PROTECTED]> wrote: I am using centos 5.1, 2.6.23.9 kernel. Machine works great all day. Then sometime through the night the kernel dies, the trace is below. is this when a 3D screensaver is active? Probably worth running without the proprietary nvidia driver it also tends to get more people to pay attention :) In addition to this suspicion; you're the first one to report this oops since at least a year as shown in http://www.kerneloops.org/guilty.php?guilty=journal_dirty_data=2.6.23-release=1540096=1572863 so it might well be something weird on your side (like the binary driver or some heat problem created by having a 3D screensaver) Hi, For a while, I have the same behavior. I tested under 2.6.23.9, 2.6.24-rc3 and rc4. So all of these kernels have the same issue. Also, I don't use any proprietary driver. My video card is Intel-945 and I use the "intel" driver. I use 3D screensavers as well. These kernels die after some long idles like 1 or 2 days after. My distribution is Kubuntu 7.10 and with Kubuntu kernel this behavior did not happened. So, how to track this interesting problem ? Any ideas welcomed :-) Cheers, Tarkan Erimer I am not running a 3D screen saver. I was just using blank screen. However, I did turn off the screen saver and last night my machine did not crash. I am still using the NVIDIA driver. All I changed was the screen saver. Any ideas on that? Jerry -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Kernel BUG in 2.6.23.9
Tarkan Erimer wrote: Arjan van de Ven wrote: On Sun, 09 Dec 2007 14:49:16 -0500 Jerry Geis [EMAIL PROTECTED] wrote: I am using centos 5.1, 2.6.23.9 kernel. Machine works great all day. Then sometime through the night the kernel dies, the trace is below. is this when a 3D screensaver is active? Probably worth running without the proprietary nvidia driver it also tends to get more people to pay attention :) In addition to this suspicion; you're the first one to report this oops since at least a year as shown in http://www.kerneloops.org/guilty.php?guilty=journal_dirty_dataversion=2.6.23-releasestart=1540096end=1572863 so it might well be something weird on your side (like the binary driver or some heat problem created by having a 3D screensaver) Hi, For a while, I have the same behavior. I tested under 2.6.23.9, 2.6.24-rc3 and rc4. So all of these kernels have the same issue. Also, I don't use any proprietary driver. My video card is Intel-945 and I use the intel driver. I use 3D screensavers as well. These kernels die after some long idles like 1 or 2 days after. My distribution is Kubuntu 7.10 and with Kubuntu kernel this behavior did not happened. So, how to track this interesting problem ? Any ideas welcomed :-) Cheers, Tarkan Erimer I am not running a 3D screen saver. I was just using blank screen. However, I did turn off the screen saver and last night my machine did not crash. I am still using the NVIDIA driver. All I changed was the screen saver. Any ideas on that? Jerry -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Kernel BUG in 2.6.23.9
Arjan van de Ven wrote: On Sun, 09 Dec 2007 14:49:16 -0500 Jerry Geis [EMAIL PROTECTED] wrote: I am using centos 5.1, 2.6.23.9 kernel. Machine works great all day. Then sometime through the night the kernel dies, the trace is below. is this when a 3D screensaver is active? Probably worth running without the proprietary nvidia driver it also tends to get more people to pay attention :) In addition to this suspicion; you're the first one to report this oops since at least a year as shown in http://www.kerneloops.org/guilty.php?guilty=journal_dirty_dataversion=2.6.23-releasestart=1540096end=1572863 so it might well be something weird on your side (like the binary driver or some heat problem created by having a 3D screensaver) Hi, For a while, I have the same behavior. I tested under 2.6.23.9, 2.6.24-rc3 and rc4. So all of these kernels have the same issue. Also, I don't use any proprietary driver. My video card is Intel-945 and I use the intel driver. I use 3D screensavers as well. These kernels die after some long idles like 1 or 2 days after. My distribution is Kubuntu 7.10 and with Kubuntu kernel this behavior did not happened. So, how to track this interesting problem ? Any ideas welcomed :-) Cheers, Tarkan Erimer -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Kernel BUG in 2.6.23.9
On Mon, 10 Dec 2007 11:14:47 +0200 Tarkan Erimer [EMAIL PROTECTED] wrote: Hi, For a while, I have the same behavior. I tested under 2.6.23.9, 2.6.24-rc3 and rc4. So all of these kernels have the same issue. Also, I don't use any proprietary driver. My video card is Intel-945 and I use the intel driver. I use 3D screensavers as well. These kernels die after some long idles like 1 or 2 days after. My distribution is Kubuntu 7.10 and with Kubuntu kernel this behavior did not happened. So, how to track this interesting problem ? Any ideas welcomed :-) 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) -- If you want to reach me at my work email, use [EMAIL PROTECTED] For development, discussion and tips for power savings, visit http://www.lesswatts.org -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Kernel BUG in 2.6.23.9
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. -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Kernel BUG in 2.6.23.9
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: [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:[88034a3b] [88034a3b] :jbd:journal_dirty_data+0xad/0x1ed Dec 8 22:23:57 devcentos5x64 kernel: RSP: 0018:810095edd7e8 EFLAGS: 00010292 Dec 8 22:23:57 devcentos5x64 kernel: RAX: 0083 RBX: 81008e1f50c8 RCX: 81344c28 Dec 8 22:23:57 devcentos5x64 kernel: RDX: 0001 RSI: 0096 RDI: 81344c20 Dec 8 22:23:57 devcentos5x64 kernel: RBP: 81009b42fdf4 R08: 81344c28 R09: 0002 Dec 8 22:23:57 devcentos5x64 kernel: R10: 0046 R11: 813b8000 R12: 8100c082b348 Dec 8 22:23:58 devcentos5x64 kernel: R13: 81010ce3cc00 R14: R15: Dec 8 22:23:58 devcentos5x64 kernel: FS: 2ae6d4b2b560() GS:81011fa9a6c0() knlGS:f7f009a0 Dec 8 22:23:58 devcentos5x64 kernel: CS: 0010 DS: ES: CR0: 8005003b Dec 8 22:23:58 devcentos5x64 kernel: CR2: 2aea6b0d30a8 CR3: 959f CR4: 06e0 Dec 8 22:23:58 devcentos5x64 kernel: DR0: DR1: DR2: Dec 8 22:23:58 devcentos5x64 kernel: DR3: DR6: 0ff0 DR7: 0400 Dec 8 22:23:58 devcentos5x64 kernel: Process rsync (pid: 5028, threadinfo 810095edc000, task 8100ccc78000) Dec 8 22:23:58 devcentos5x64 kernel: Stack: 1000 8100c082b348 81008e1f50c8 81008e1f50c8 Dec 8 22:23:58 devcentos5x64 kernel: 81008e1f50c8 8804ff8f 1000 1000 Dec 8 22:23:58 devcentos5x64 kernel: 1000 8804f437 8804ffb4 1000 Dec 8 22:23:58 devcentos5x64 kernel: Call Trace: Dec 8 22:23:58 devcentos5x64 kernel: [8804ff8f] :ext3:ext3_journal_dirty_data+0xf/0x34 Dec 8 22:23:58 devcentos5x64 kernel: [8804f437] :ext3:walk_page_buffers+0x65/0x8b Dec 8 22:23:58 devcentos5x64 kernel: [8804ffb4] :ext3:journal_dirty_data_fn+0x0/0xe Dec 8 22:23:58 devcentos5x64 kernel: [880521da] :ext3:ext3_ordered_writepage+0x108/0x18c Dec 8 22:23:58 devcentos5x64 kernel: [8106bf9a] __writepage+0xa/0x23 Dec 8 22:23:58 devcentos5x64 kernel: [8106c4b8] write_cache_pages+0x17b/0x2aa Dec 8 22:23:58 devcentos5x64 kernel: [8106bf90] __writepage+0x0/0x23 Dec 8 22:23:58 devcentos5x64 kernel: [8106c62a] do_writepages+0x27/0x2d Dec 8 22:23:58 devcentos5x64 kernel: [810a8749] __writeback_single_inode+0x1ba/0x332 Dec 8 22:23:58 devcentos5x64 kernel: [8805b7ea] :ext3:__ext3_journal_dirty_metadata+0x1e/0x46 Dec 8 22:23:58 devcentos5x64 kernel: [810a8c00] sync_sb_inodes+0x1a3/0x261 Dec 8 22:23:58
Re: Kernel BUG in 2.6.23.9
On Sun, 09 Dec 2007 14:49:16 -0500 Jerry Geis <[EMAIL PROTECTED]> wrote: > I am using centos 5.1, 2.6.23.9 kernel. Machine works great all day. > Then sometime through the night the kernel dies, the trace is below. is this when a 3D screensaver is active? Probably worth running without the proprietary nvidia driver it also tends to get more people to pay attention :) In addition to this suspicion; you're the first one to report this oops since at least a year as shown in http://www.kerneloops.org/guilty.php?guilty=journal_dirty_data=2.6.23-release=1540096=1572863 so it might well be something weird on your side (like the binary driver or some heat problem created by having a 3D screensaver) -- If you want to reach me at my work email, use [EMAIL PROTECTED] For development, discussion and tips for power savings, visit http://www.lesswatts.org -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Kernel BUG in 2.6.23.9
I am using centos 5.1, 2.6.23.9 kernel. Machine works great all day. Then sometime through the night the kernel dies, the trace is below. My machine is an AMD 6400+ X2, seagate 500G SATA, Nvidia 7100, 4 GIG RAM. --- Linux version 2.6.23.9 ([EMAIL PROTECTED]) (gcc version 4.1.2 20070626 (Red Hat 4.1.2-14)) #1 SMP Mon Dec 3 10:20:13 EST 2007 If some fields are empty or look unusual you may have an old version. Compare to the current minimal requirements in Documentation/Changes. Linux devcentos5x64.msgnet.com 2.6.23.9 #1 SMP Mon Dec 3 10:20:13 EST 2007 x86_64 x86_64 x86_64 GNU/Linux Gnu C 4.1.2 Gnu make 3.81 binutils 2.17.50.0.6-5.el5 util-linux 2.13-pre7 mount 2.13-pre7 module-init-tools 3.3-pre2 e2fsprogs 1.39 pcmciautils014 quota-tools3.13. PPP2.4.4 isdn4k-utils 3.9 Linux C Library2.5 Dynamic linker (ldd) 2.5 Procps 3.2.7 Net-tools 1.60 Kbd1.12 oprofile 0.9.2 Sh-utils 5.97 udev 095 wireless-tools 28 Modules Loaded 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 snd_timer snd soundcore snd_page_alloc nvidia sr_mod wctdm24xxp i2c_nforce2 i2c_core cdrom zaptel crc_ccitt forcedeth usb_storage button sg parport_pc parport serio_raw sata_nv libata sd_mod scsi_mod raid1 ext3 jbd ehci_hcd ohci_hcd uhci_hcd [EMAIL PROTECTED] linux-2.6.23.9]# 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: [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:[] [] :jbd:journal_dirty_data+0xad/0x1ed Dec 8 22:23:57 devcentos5x64 kernel: RSP: 0018:810095edd7e8 EFLAGS: 00010292 Dec 8 22:23:57 devcentos5x64 kernel: RAX: 0083 RBX: 81008e1f50c8 RCX: 81344c28 Dec 8 22:23:57 devcentos5x64 kernel: RDX: 0001 RSI: 0096 RDI: 81344c20 Dec 8 22:23:57 devcentos5x64 kernel: RBP: 81009b42fdf4 R08: 81344c28 R09: 0002 Dec 8 22:23:57 devcentos5x64 kernel: R10: 0046 R11: 813b8000 R12: 8100c082b348 Dec 8 22:23:58 devcentos5x64 kernel: R13: 81010ce3cc00 R14: R15: Dec 8 22:23:58 devcentos5x64 kernel: FS: 2ae6d4b2b560() GS:81011fa9a6c0() knlGS:f7f009a0 Dec 8 22:23:58 devcentos5x64 kernel: CS: 0010 DS: ES: CR0: 8005003b Dec 8 22:23:58 devcentos5x64 kernel: CR2: 2aea6b0d30a8 CR3: 959f CR4: 06e0 Dec 8 22:23:58 devcentos5x64 kernel: DR0: DR1: DR2: Dec 8 22:23:58 devcentos5x64 kernel: DR3: DR6: 0ff0 DR7: 0400 Dec 8 22:23:58 devcentos5x64 kernel: Process rsync (pid: 5028, threadinfo 810095edc000, task 8100ccc78000) Dec 8 22:23:58 devcentos5x64 kernel: Stack: 1000 8100c082b348 81008e1f50c8 81008e1f50c8 Dec 8 22:23:58 devcentos5x64 kernel: 81008e1f50c8 8804ff8f 1000 1000 Dec 8 22:23:58 devcentos5x64
Kernel BUG in 2.6.23.9
I am using centos 5.1, 2.6.23.9 kernel. Machine works great all day. Then sometime through the night the kernel dies, the trace is below. My machine is an AMD 6400+ X2, seagate 500G SATA, Nvidia 7100, 4 GIG RAM. --- Linux version 2.6.23.9 ([EMAIL PROTECTED]) (gcc version 4.1.2 20070626 (Red Hat 4.1.2-14)) #1 SMP Mon Dec 3 10:20:13 EST 2007 If some fields are empty or look unusual you may have an old version. Compare to the current minimal requirements in Documentation/Changes. Linux devcentos5x64.msgnet.com 2.6.23.9 #1 SMP Mon Dec 3 10:20:13 EST 2007 x86_64 x86_64 x86_64 GNU/Linux Gnu C 4.1.2 Gnu make 3.81 binutils 2.17.50.0.6-5.el5 util-linux 2.13-pre7 mount 2.13-pre7 module-init-tools 3.3-pre2 e2fsprogs 1.39 pcmciautils014 quota-tools3.13. PPP2.4.4 isdn4k-utils 3.9 Linux C Library2.5 Dynamic linker (ldd) 2.5 Procps 3.2.7 Net-tools 1.60 Kbd1.12 oprofile 0.9.2 Sh-utils 5.97 udev 095 wireless-tools 28 Modules Loaded 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 snd_timer snd soundcore snd_page_alloc nvidia sr_mod wctdm24xxp i2c_nforce2 i2c_core cdrom zaptel crc_ccitt forcedeth usb_storage button sg parport_pc parport serio_raw sata_nv libata sd_mod scsi_mod raid1 ext3 jbd ehci_hcd ohci_hcd uhci_hcd [EMAIL PROTECTED] linux-2.6.23.9]# 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: [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:[88034a3b] [88034a3b] :jbd:journal_dirty_data+0xad/0x1ed Dec 8 22:23:57 devcentos5x64 kernel: RSP: 0018:810095edd7e8 EFLAGS: 00010292 Dec 8 22:23:57 devcentos5x64 kernel: RAX: 0083 RBX: 81008e1f50c8 RCX: 81344c28 Dec 8 22:23:57 devcentos5x64 kernel: RDX: 0001 RSI: 0096 RDI: 81344c20 Dec 8 22:23:57 devcentos5x64 kernel: RBP: 81009b42fdf4 R08: 81344c28 R09: 0002 Dec 8 22:23:57 devcentos5x64 kernel: R10: 0046 R11: 813b8000 R12: 8100c082b348 Dec 8 22:23:58 devcentos5x64 kernel: R13: 81010ce3cc00 R14: R15: Dec 8 22:23:58 devcentos5x64 kernel: FS: 2ae6d4b2b560() GS:81011fa9a6c0() knlGS:f7f009a0 Dec 8 22:23:58 devcentos5x64 kernel: CS: 0010 DS: ES: CR0: 8005003b Dec 8 22:23:58 devcentos5x64 kernel: CR2: 2aea6b0d30a8 CR3: 959f CR4: 06e0 Dec 8 22:23:58 devcentos5x64 kernel: DR0: DR1: DR2: Dec 8 22:23:58 devcentos5x64 kernel: DR3: DR6: 0ff0 DR7: 0400 Dec 8 22:23:58 devcentos5x64 kernel: Process rsync (pid: 5028, threadinfo 810095edc000, task 8100ccc78000) Dec 8 22:23:58 devcentos5x64 kernel: Stack: 1000 8100c082b348 81008e1f50c8 81008e1f50c8 Dec 8 22:23:58 devcentos5x64 kernel: 81008e1f50c8 8804ff8f 1000 1000 Dec 8
Re: Kernel BUG in 2.6.23.9
On Sun, 09 Dec 2007 14:49:16 -0500 Jerry Geis [EMAIL PROTECTED] wrote: I am using centos 5.1, 2.6.23.9 kernel. Machine works great all day. Then sometime through the night the kernel dies, the trace is below. is this when a 3D screensaver is active? Probably worth running without the proprietary nvidia driver it also tends to get more people to pay attention :) In addition to this suspicion; you're the first one to report this oops since at least a year as shown in http://www.kerneloops.org/guilty.php?guilty=journal_dirty_dataversion=2.6.23-releasestart=1540096end=1572863 so it might well be something weird on your side (like the binary driver or some heat problem created by having a 3D screensaver) -- If you want to reach me at my work email, use [EMAIL PROTECTED] For development, discussion and tips for power savings, visit http://www.lesswatts.org -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
