fs/fs-writeback oopses in kernel 2.6.33.4-95.fc13.i686.PAE
Hello,
I upgrade from kernel 2.6.33.3 to 2.6.33.4 (2.6.33.4-95.fc13.i686.PAE, Fedora 13 distro) and now I see several these messages every day in /var/log/messages:
May 24 14:01:32 ns kernel: ------------[ cut here ]------------ May 24 14:01:32 ns kernel: WARNING: at fs/fs-writeback.c:597 writeback_inodes_wb+0x202/0x30e() May 24 14:01:32 ns kernel: Hardware name: GA-MA785GMT-UD2H May 24 14:01:32 ns kernel: Modules linked in: nfs fscache bluetooth rfkill inet_diag nfsd lockd nfs_acl auth_rpcgss exportfs a
utofs4 it87 hwmon_vid sunrpc cpufreq_ondemand powernow_k8 ppp_synctty ppp_async crc_ccitt ppp_generic slhc nf_conntrack_ftp ip t_LOG xt_limit xt_recent ipt_MASQUERADE ipt_REDIRECT iptable_nat nf_nat xt_TCPMSS xt_helper xt_MARK xt_DSCP iptable_mangle kvm _amd kvm uinput snd_hda_codec_atihdmi snd_hda_codec_realtek snd_hda_intel snd_hda_codec snd_hwdep snd_seq ppdev snd_seq_device
parport_pc snd_pcm snd_timer i2c_piix4 r8169 parport snd soundcoresnd_page_alloc e100 mii k10temp microcode raid1 ata_generi
c pata_acpi firewire_ohci firewire_core crc_itu_t pata_atiixp radeon ttm drm_kms_helper drm i2c_algo_bit i2c_core [last unload
ed: scsi_wait_scan]
May 24 14:01:32 ns kernel: Pid: 30516, comm: flush-9:3 Tainted: G W 2.6.33.4-95.fc13.i686.PAE #1 May 24 14:01:32 ns kernel: Call Trace: May 24 14:01:32 ns kernel: [<c043d629>] warn_slowpath_common+0x65/0x7c May 24 14:01:32 ns kernel: [<c04e6dd9>] ? writeback_inodes_wb+0x202/0x30e May 24 14:01:32 ns kernel: [<c043d64d>] warn_slowpath_null+0xd/0x10 May 24 14:01:32 ns kernel: [<c04e6dd9>] writeback_inodes_wb+0x202/0x30e May 24 14:01:32 ns kernel: [<c04e6fe8>] wb_writeback+0x103/0x162 May 24 14:01:32 ns kernel: [<c0482e6d>] ? call_rcu+0x8/0xa May 24 14:01:32 ns kernel: [<c04e70c4>] ? wb_clear_pending+0x6a/0x6f May 24 14:01:32 ns kernel: [<c04e712e>] wb_do_writeback+0x65/0x128 May 24 14:01:32 ns kernel: [<c04e7219>] bdi_writeback_task+0x28/0x84 May 24 14:01:32 ns kernel: [<c04b0aed>] ? bdi_start_fn+0x0/0xa3 May 24 14:01:32 ns kernel: [<c04b0b42>] bdi_start_fn+0x55/0xa3 May 24 14:01:32 ns kernel: [<c04b0aed>] ? bdi_start_fn+0x0/0xa3 May 24 14:01:32 ns kernel: [<c045271f>] kthread+0x5f/0x64 May 24 14:01:32 ns kernel: [<c04526c0>] ? kthread+0x0/0x64 May 24 14:01:32 ns kernel: [<c0408dfe>] kernel_thread_helper+0x6/0x10 May 24 14:01:32 ns kernel: ---[ end trace 8bd04b585937393a ]---
HW is Gigabyte GA-MA785GMT-UD2H MB, AMD Athlon II X2 240e CPU, 2x2GB DDR3 1066 nonECC RAM, 2x ST31500341AS 1.5TB SATA II HDD in SW RAID1 (md). lspi:
00:00.0 Host bridge: Advanced Micro Devices [AMD] RS780 Host Bridge Alternate
00:01.0 PCI bridge: Advanced Micro Devices [AMD] RS780 PCI to PCI bridge (int gfx)
00:04.0 PCI bridge: Advanced Micro Devices [AMD] RS780 PCI to PCI bridge (PCIE port 0)
00:0a.0 PCI bridge: Advanced Micro Devices [AMD] RS780 PCI to PCI bridge (PCIE port 5)
00:11.0 SATA controller: ATI Technologies Inc SB700/SB800 SATA Controller [AHCI mode]
00:12.0 USB Controller: ATI Technologies Inc SB700/SB800 USB OHCI0 Controller
00:12.1 USB Controller: ATI Technologies Inc SB700 USB OHCI1 Controller
00:12.2 USB Controller: ATI Technologies Inc SB700/SB800 USB EHCI Controller
00:13.0 USB Controller: ATI Technologies Inc SB700/SB800 USB OHCI0 Controller
00:13.1 USB Controller: ATI Technologies Inc SB700 USB OHCI1 Controller
00:13.2 USB Controller: ATI Technologies Inc SB700/SB800 USB EHCI Controller
00:14.0 SMBus: ATI Technologies Inc SBx00 SMBus Controller (rev 3c)
00:14.1 IDE interface: ATI Technologies Inc SB700/SB800 IDE Controller
00:14.2 Audio device: ATI Technologies Inc SBx00 Azalia (Intel HDA)
00:14.3 ISA bridge: ATI Technologies Inc SB700/SB800 LPC host controller
00:14.4 PCI bridge: ATI Technologies Inc SBx00 PCI to PCI Bridge
00:14.5 USB Controller: ATI Technologies Inc SB700/SB800 USB OHCI2 Controller
00:18.0 Host bridge: Advanced Micro Devices [AMD] K10 [Opteron, Athlon64, Sempron] HyperTransport Configuration
00:18.1 Host bridge: Advanced Micro Devices [AMD] K10 [Opteron, Athlon64, Sempron] Address Map
00:18.2 Host bridge: Advanced Micro Devices [AMD] K10 [Opteron, Athlon64, Sempron] DRAM Controller
00:18.3 Host bridge: Advanced Micro Devices [AMD] K10 [Opteron, Athlon64, Sempron] Miscellaneous Control
00:18.4 Host bridge: Advanced Micro Devices [AMD] K10 [Opteron, Athlon64, Sempron] Link Control
01:05.0 VGA compatible controller: ATI Technologies Inc RS880 [Radeon HD 4200]
01:05.1 Audio device: ATI Technologies Inc RS880 Audio Device [Radeon HD 4200]
02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 01) 03:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 02) 04:06.0 Ethernet controller: Intel Corporation 82557/8/9/0/1 Ethernet Pro 100 (rev 08)
04:07.0 Serial controller: 3Com Corp, Modem Division 56K FaxModem Model 5610 (rev 01)
04:0e.0 FireWire (IEEE 1394): Texas Instruments TSB43AB23 IEEE-1394a-2000 Controller (PHY/Link)
It is not fatal error, system still continue work, but I not know, when it can be any dangerous for my disk data. Can anyone give any advice about this?
Thanks in advance, Franta Hanzlik
Quoted 8 lines · On Mon, 24 May 2010 14:37:32 +0200 Frantisek Hanzlik <[email protected]> wrote:
Hello,
I upgrade from kernel 2.6.33.3 to 2.6.33.4 (2.6.33.4-95.fc13.i686.PAE, Fedora 13 distro) and now I see several these messages every day in/var/log/messages:May 24 14:01:32 ns kernel: ------------[ cut here ]------------ May 24 14:01:32 ns kernel: WARNING: at fs/fs-writeback.c:597writeback_inodes_wb+0x202/0x30e()
I don't see anything which would generate this warning in 2.6.33.4's fs/fs-writeback.c:597. RH must have mucked with it.
Quoted 7 lines · Andrew Morton
Quoted 5 lines · On Mon, 24 May 2010 14:37:32 +0200 Frantisek Hanzlik <[email protected]> wrote:
Hello,
I upgrade from kernel 2.6.33.3 to 2.6.33.4 (2.6.33.4-95.fc13.i686.PAE, Fedora 13 distro) and now I see several these messages every day in/var/log/messages:
Quoted 6 lines
Quoted 3 lines
May 24 14:01:32 ns kernel: ------------[ cut here ]------------ May 24 14:01:32 ns kernel: WARNING: at fs/fs-writeback.c:597writeback_inodes_wb+0x202/0x30e()
I don't see anything which would generate this warning in 2.6.33.4's
fs/fs-writeback.c:597. RH must have mucked with it.
Already fixed in mainstream by
commit 7c8a3554c683f512dbcee26faedb42e4c05f12fa
Author: Jens Axboe <[email protected]> Date: Tue May 18 14:29:29 2010 +0200
Quoted 6 lines
--
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/
Quoted 6 lines
Quoted 2 lines
I don't see anything which would generate this warning in 2.6.33.4's
fs/fs-writeback.c:597. RH must have mucked with it.Already fixed in mainstream by
commit7c8a3554c683f512dbcee26faedb42e4c05f12fa
Author: Jens Axboe <[email protected]>
Date: Tue May 18 14:29:29 2010 +0200
Do you send it to stable ? I am hitting the same bug and count is high on kerneloops (http://www.kerneloops.org/searchweek.php?search=writeback_inodes_wb)
Bastien
Quoted 10 lines · On Thu, 10 Jun 2010 11:06:17 +0200 Bastien ROUCARIES…
Quoted 6 lines
Quoted 2 lines
I don't see anything which would generate this warning in 2.6.33.4's
fs/fs-writeback.c:597.__RHmust have mucked with it.Already fixed in mainstream by
commit7c8a3554c683f512dbcee26faedb42e4c05f12fa
Author: Jens Axboe <[email protected]>
Date: __ Tue May 18 14:29:29 2010 +0200Do you send it to stable ? I am hitting the same bug and count is high on kerneloops (http://www.kerneloops.org/searchweek.php?search=writeback_inodes_wb)
The commit didn't have a cc:stable in the changelog so no, it probably wasn't backported.
But that commit was later reverted anyway. Hopefully when the real fix gets merged, it will be backported.
Quoted 10 lines · Andrew Morton
Quoted 3 lines
Do you send it to stable ? I am hitting the same bug and count is high on kerneloops (http://www.kerneloops.org/searchweek.php?search=writeback_inodes_wb)
The commit didn't have a cc:stable in the changelog so no, it probably wasn't backported.
But that commit was later reverted anyway. Hopefully when the real fix gets merged, it will be backported.
Yes, we backported it when it hit mainline, and have since pulled them until the real fix is sorted out.
thanks, Kyle.
Quoted 14 lines · Andrew Morton
Quoted 10 lines · On Thu, 10 Jun 2010 11:06:17 +0200 Bastien ROUCARIES…
Quoted 6 lines
Quoted 2 lines
I don't see anything which would generate this warning in 2.6.33.4's
fs/fs-writeback.c:597.__RHmust have mucked with it.Already fixed in mainstream by
commit7c8a3554c683f512dbcee26faedb42e4c05f12fa
Author: Jens Axboe <[email protected]>
Date: __ Tue May 18 14:29:29 2010 +0200Do you send it to stable ? I am hitting the same bug and count is high on kerneloops (http://www.kerneloops.org/searchweek.php?search=writeback_inodes_wb)
Quoted 5 lines
The commit didn't have a cc:stable in the changelog so no, it probably wasn't backported.
But that commit was later reverted anyway. Hopefully when the real fix gets merged, it will be backported.
Thank Andrew. I am hitting this warning at each boot, without anything fancy on my machine
(I am hitting it just after mounting the root partition, i suppose reiserfs user_xattr, acl help but I was expecting that automatic testing could catch this kind of bug)
Regards
Bastien
Quoted 16 lines · Bastien ROUCARIES
Quoted 14 lines · Andrew Morton
Quoted 10 lines · On Thu, 10 Jun 2010 11:06:17 +0200 Bastien ROUCARIES…
Quoted 6 lines
Quoted 2 lines
I don't see anything which would generate this warning in 2.6.33.4's
fs/fs-writeback.c:597.__RHmust have mucked with it.Already fixed in mainstream by
commit7c8a3554c683f512dbcee26faedb42e4c05f12fa
Author: Jens Axboe <[email protected]>
Date: __ Tue May 18 14:29:29 2010 +0200Do you send it to stable ? I am hitting the same bug and count is high on kerneloops (http://www.kerneloops.org/searchweek.php?search=writeback_inodes_wb)
Quoted 6 lines
Quoted 5 lines
The commit didn't have a cc:stable in the changelog so no, it probably wasn't backported.
But that commit was later reverted anyway. Hopefully when the real fix gets merged, it will be backported.
Any news of this bug ?
Regard
Bastien
Quoted 18 lines · On Thu, 1 Jul 2010 09:54:07 +0200 Bastien ROUCARIES…
Quoted 16 lines · Bastien ROUCARIES
Quoted 14 lines · Andrew Morton
Quoted 10 lines · On Thu, 10 Jun 2010 11:06:17 +0200 Bastien ROUCARIES…
Quoted 6 lines
Quoted 2 lines
I don't see anything which would generate this warning in 2.6.33.4's
fs/fs-writeback.c:597.__RHmust have mucked with it.Already fixed in mainstream by
commit7c8a3554c683f512dbcee26faedb42e4c05f12fa
Author: Jens Axboe <[email protected]>
Date: __ Tue May 18 14:29:29 2010 +0200Do you send it to stable ? I am hitting the same bug and count is high on kerneloops (http://www.kerneloops.org/searchweek.php?search=writeback_inodes_wb)
Quoted 9 lines
Quoted 6 lines
Quoted 5 lines
The commit didn't have a cc:stable in the changelog so no, it probably wasn't backported.
But that commit was later reverted anyway.
__Hopefullywhen the real fix gets merged, it will be backported.Any news of this bug ?
There have been various dramas in the writeback code recently. Christoph has been working on it.
Christoph, is this oops known about, and are those patches expected to fix it?
Thanks.
Quoted 5 lines · Andrew Morton
There have been various dramas in the writeback code recently. Christoph has been working on it.
Christoph, is this oops known about, and are those patches expected to fix it?
I have no idea what oops you mean. But the writeback code is very different now compared to 2.6.33, and with the latest fixes in Jens' tree there are no known issues left. (know to me anyway)
Quoted 8 lines · On Wed, 7 Jul 2010 23:02:09 +0200 Christoph Hellwig <[email protected]> wrote:
Quoted 5 lines · Andrew Morton
There have been various dramas in the writeback code recently. Christoph has been working on it.
Christoph, is this oops known about, and are those patches expected to fix it?
I have no idea what oops you mean.
http://lmgtfy.com/?q=fs%2Ffs-writeback+oopses+in+kernel+2.6.33.4-95.fc13.i686.PAE
Quoted 3 lines
But the writeback code is very
different now compared to 2.6.33, and with the latest fixes in Jens' tree there are no known issues left. (know to me anyway)
Well the issue is that 2.6.33.x goes oops and we'd like to fix that. if it's fixed in current mainline then which patch did it?
Quoted 4 lines · Andrew Morton
Quoted 2 lines
I have no idea what oops you mean.
http://lmgtfy.com/?q=fs%2Ffs-writeback+oopses+in+kernel+2.6.33.4-95.fc13.i686.PAE
Not particularly useful. Line numbers and function have changed completely since .33. Given that 2.6.33-stable is at the end of line I really can't be bothered to go back, figure out what the hell was going on back then and backport things. In fact we'd probably end up backporting all writeback changes since then anyway, as the changes to sort out the per-sb syncs were very large and interdependent.