Bug#470070: marked as done (linux-image-2.6.24-1-amd64: Flaky file system problems in the last 3 days or so)

To: maximilian attems <max@stro.at>
Subject: Bug#470070: marked as done (linux-image-2.6.24-1-amd64: Flaky file system problems in the last 3 days or so)
From: owner@bugs.debian.org (Debian Bug Tracking System)
Date: Wed, 21 May 2008 11:00:10 +0000
Message-id: <[🔎] handler.470070.D470070.121136732827308.ackdone@bugs.debian.org>
References: <20080521103138.GK27599@baikonur.stro.at> <20080308234209.10209.47957.reportbug@faerun.comcast.net>

Your message dated Wed, 21 May 2008 12:31:38 +0200
with message-id <20080521103138.GK27599@baikonur.stro.at>
and subject line Re: Bug#470070: linux-image-2.6.24-1-amd64: Flaky file system problems in the last 3 days or so
has caused the Debian Bug report #470070,
regarding linux-image-2.6.24-1-amd64: Flaky file system problems in the last 3 days or so
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
470070: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=470070
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems

--- Begin Message ---

To: Debian Bug Tracking System <submit@bugs.debian.org>
Subject: linux-image-2.6.24-1-amd64: Flaky file system problems in the last 3 days or so
From: Tom Epperly <tomepperly@comcast.net>
Date: Sat, 08 Mar 2008 15:42:09 -0800
Message-id: <20080308234209.10209.47957.reportbug@faerun.comcast.net>

Package: linux-image-2.6.24-1-amd64
Version: 2.6.24-4
Severity: normal

The last 2 or 3 days I've gotten JFS filesystem corruption within
minutes of logging in via gdm, and I had to reboot. Various processes have
just spontaneously died. Most of the crashes don't have anything in
the log, but here is some backtrace information:

Mar  7 07:20:37 faerun kernel: Bad page state in process 'jfsCommit'
Mar  7 07:20:37 faerun kernel: page:ffff81003f3d37e0 flags:0x010000000000080d mapping:ffff81003c078de8 mapcount:0 count:0
Mar  7 07:20:37 faerun kernel: Trying to fix it up, but a reboot is needed
Mar  7 07:20:37 faerun kernel: Backtrace:
Mar  7 07:20:37 faerun kernel: Pid: 1262, comm: jfsCommit Tainted: P        2.6.24-1-amd64 #1
Mar  7 07:20:37 faerun kernel: 
Mar  7 07:20:37 faerun kernel: Call Trace:
Mar  7 07:20:37 faerun kernel:  [<ffffffff80275147>] bad_page+0x63/0x8d
Mar  7 07:20:37 faerun kernel:  [<ffffffff8027575b>] free_hot_cold_page+0x8c/0x13d
Mar  7 07:20:37 faerun kernel:  [<ffffffff88132a19>] :jfs:txUnlock+0xc8/0x215
Mar  7 07:20:37 faerun kernel:  [<ffffffff881354d2>] :jfs:jfs_lazycommit+0xf8/0x22b
Mar  7 07:20:37 faerun kernel:  [<ffffffff8022ee06>] default_wake_function+0x0/0xe
Mar  7 07:20:37 faerun kernel:  [<ffffffff881353da>] :jfs:jfs_lazycommit+0x0/0x22b
Mar  7 07:20:37 faerun kernel:  [<ffffffff80247ed3>] kthread+0x47/0x74
Mar  7 07:20:37 faerun kernel:  [<ffffffff8020cc48>] child_rip+0xa/0x12
Mar  7 07:20:37 faerun kernel:  [<ffffffff80247e8c>] kthread+0x0/0x74
Mar  7 07:20:37 faerun kernel:  [<ffffffff8020cc3e>] child_rip+0x0/0x12
Mar  7 07:20:37 faerun kernel: 
Mar  7 07:20:37 faerun kernel: ------------[ cut here ]------------
Mar  7 07:20:37 faerun kernel: kernel BUG at mm/filemap.c:553!
Mar  7 07:20:37 faerun kernel: invalid opcode: 0000 [1] SMP 
Mar  7 07:20:37 faerun kernel: CPU 1 
Mar  7 07:20:37 faerun kernel: Modules linked in: snd_rtctimer binfmt_misc nvidia(P) nfsd lockd nfs_acl auth_rpcgss sunrpc exportfs ppdev ac battery cpufreq_userspace cpufreq_stats cpufreq_powersave ipv6 fuse dm_crypt dm_snapshot dm_mirror dm_mod cpufreq_conservative cpufreq_ondemand powernow_k8 freq_table it87 hwmon_vid eeprom loop snd_intel8x0 snd_ac97_codec ac97_bus snd_pcm_oss snd_pcm snd_mixer_oss snd_seq_dummy snd_mpu401 snd_seq_oss snd_mpu401_uart snd_seq_midi snd_seq_midi_event snd_seq snd_rawmidi snd_timer snd_seq_device parport_pc parport k8temp snd soundcore pcspkr snd_page_alloc button i2c_nforce2 i2c_core evdev jfs sd_mod ide_cd cdrom generic usbhid hid sata_nv amd74xx ide_core floppy forcedeth ata_generic libata scsi_mod ohci_hcd ehci_hcd thermal processor fan
Mar  7 07:20:37 faerun kernel: Pid: 1262, comm: jfsCommit Tainted: P    B   2.6.24-1-amd64 #1
Mar  7 07:20:37 faerun kernel: RIP: 0010:[<ffffffff80271523>]  [<ffffffff80271523>] unlock_page+0xf/0x26
Mar  7 07:20:37 faerun kernel: RSP: 0018:ffff81003c8b5e50  EFLAGS: 00010246
Mar  7 07:20:37 faerun kernel: RAX: 0000000000000000 RBX: ffff81003f3d37e0 RCX: 0000000000000000
Mar  7 07:20:37 faerun kernel: RDX: ffff81003f3d37e0 RSI: 0000000000000000 RDI: ffff81003f3d37e0
Mar  7 07:20:37 faerun kernel: RBP: ffffc200106a5f00 R08: ffffffff805c6cc0 R09: ffffffff8043a700
Mar  7 07:20:37 faerun kernel: R10: 0000000000000008 R11: ffffffff8049384d R12: ffffc2001054ce80
Mar  7 07:20:37 faerun kernel: R13: ffff8100379afc00 R14: 0000000016e016e0 R15: ffff8100379afd10
Mar  7 07:20:37 faerun kernel: FS:  00002ab16d96c2d0(0000) GS:ffff81003edfdac0(0000) knlGS:0000000000000000
Mar  7 07:20:37 faerun kernel: CS:  0010 DS: 0018 ES: 0018 CR0: 000000008005003b
Mar  7 07:20:37 faerun kernel: CR2: 000000000619c350 CR3: 00000000098fd000 CR4: 00000000000006e0
Mar  7 07:20:37 faerun kernel: DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
Mar  7 07:20:37 faerun kernel: DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
Mar  7 07:20:37 faerun kernel: Process jfsCommit (pid: 1262, threadinfo ffff81003c8b4000, task ffff81003d2df000)
Mar  7 07:20:37 faerun kernel: Stack:  ffff810007423830 ffffffff8812fd97 ffff81000000b700 0000000000000282
Mar  7 07:20:37 faerun kernel:  0000000000000286 ffff810007423830 ffffc200106a5f00 ffffc2001054ce80
Mar  7 07:20:37 faerun kernel:  ffff810007423830 ffffffff88132a9a 0000ffff80576f00 ffffc2001054ce80
Mar  7 07:20:37 faerun kernel: Call Trace:
Mar  7 07:20:37 faerun kernel:  [<ffffffff8812fd97>] :jfs:put_metapage+0xef/0xfd
Mar  7 07:20:37 faerun kernel:  [<ffffffff88132a9a>] :jfs:txUnlock+0x149/0x215
Mar  7 07:20:37 faerun kernel:  [<ffffffff881354d2>] :jfs:jfs_lazycommit+0xf8/0x22b
Mar  7 07:20:37 faerun kernel:  [<ffffffff8022ee06>] default_wake_function+0x0/0xe
Mar  7 07:20:37 faerun kernel:  [<ffffffff881353da>] :jfs:jfs_lazycommit+0x0/0x22b
Mar  7 07:20:37 faerun kernel:  [<ffffffff80247ed3>] kthread+0x47/0x74
Mar  7 07:20:37 faerun kernel:  [<ffffffff8020cc48>] child_rip+0xa/0x12
Mar  7 07:20:37 faerun kernel:  [<ffffffff80247e8c>] kthread+0x0/0x74
Mar  7 07:20:37 faerun kernel:  [<ffffffff8020cc3e>] child_rip+0x0/0x12
Mar  7 07:20:37 faerun kernel: 
Mar  7 07:20:37 faerun kernel: 
Mar  7 07:20:37 faerun kernel: Code: 0f 0b eb fe e8 14 f7 ff ff 48 89 de 48 89 c7 31 d2 5b e9 69 
Mar  7 07:20:37 faerun kernel: RIP  [<ffffffff80271523>] unlock_page+0xf/0x26
Mar  7 07:20:37 faerun kernel:  RSP <ffff81003c8b5e50>
Mar  7 07:20:37 faerun kernel: ---[ end trace 65d0cebcd237f23e ]---
Mar  7 07:20:37 faerun kernel: Bad page state in process 'syslogd'
Mar  7 07:20:37 faerun kernel: page:ffff81003f3d37e0 flags:0x010000000000000c mapping:0000000000000000 mapcount:0 count:1
Mar  7 07:20:37 faerun kernel: Trying to fix it up, but a reboot is needed
Mar  7 07:20:37 faerun kernel: Backtrace:
Mar  7 07:20:37 faerun kernel: Pid: 2879, comm: syslogd Tainted: P    B D 2.6.24-1-amd64 #1
Mar  7 07:20:37 faerun kernel: 
Mar  7 07:20:37 faerun kernel: Call Trace:
Mar  7 07:20:37 faerun kernel:  [<ffffffff80275147>] bad_page+0x63/0x8d
Mar  7 07:20:37 faerun kernel:  [<ffffffff802766f7>] get_page_from_freelist+0x3fc/0x5e6
Mar  7 07:20:37 faerun kernel:  [<ffffffff80276ab1>] __alloc_pages+0x66/0x309
Mar  7 07:20:37 faerun kernel:  [<ffffffff80413e71>] schedule_timeout+0x1e/0xad
Mar  7 07:20:37 faerun kernel:  [<ffffffff8024816f>] remove_wait_queue+0x12/0x45
Mar  7 07:20:37 faerun kernel:  [<ffffffff802718c6>] __grab_cache_page+0x33/0x6f
Mar  7 07:20:37 faerun kernel:  [<ffffffff802b8e4a>] nobh_write_begin+0x73/0x3b2
Mar  7 07:20:37 faerun kernel:  [<ffffffff8811c4a7>] :jfs:jfs_get_block+0x0/0x233
Mar  7 07:20:37 faerun kernel:  [<ffffffff8811c040>] :jfs:jfs_write_begin+0x1b/0x20
Mar  7 07:20:37 faerun kernel:  [<ffffffff8811c4a7>] :jfs:jfs_get_block+0x0/0x233
Mar  7 07:20:37 faerun kernel:  [<ffffffff802724e8>] generic_file_buffered_write+0x150/0x652
Mar  7 07:20:37 faerun kernel:  [<ffffffff80239dac>] current_fs_time+0x1e/0x24
Mar  7 07:20:37 faerun kernel:  [<ffffffff88136c84>] :jfs:jfs_getxattr+0xd/0x12
Mar  7 07:20:37 faerun kernel:  [<ffffffff80272d29>] __generic_file_aio_write_nolock+0x33f/0x3a9
Mar  7 07:20:37 faerun kernel:  [<ffffffff803a10d6>] sock_recvmsg+0xf0/0x10f
Mar  7 07:20:37 faerun kernel:  [<ffffffff80272df4>] generic_file_aio_write+0x61/0xc1
Mar  7 07:20:37 faerun kernel:  [<ffffffff80272d93>] generic_file_aio_write+0x0/0xc1
Mar  7 07:20:37 faerun kernel:  [<ffffffff80297b58>] do_sync_readv_writev+0xc0/0x107
Mar  7 07:20:37 faerun kernel:  [<ffffffff80247ff2>] autoremove_wake_function+0x0/0x2e
Mar  7 07:20:37 faerun kernel:  [<ffffffff802a02fc>] getname+0x14c/0x1b3
Mar  7 07:20:37 faerun kernel:  [<ffffffff8030e48d>] _atomic_dec_and_lock+0x39/0x58
Mar  7 07:20:37 faerun kernel:  [<ffffffff802979ed>] rw_copy_check_uvector+0x6c/0xdc
Mar  7 07:20:37 faerun kernel:  [<ffffffff80298239>] do_readv_writev+0xcf/0x1a6
Mar  7 07:20:37 faerun kernel:  [<ffffffff8029b0ad>] sys_newstat+0x28/0x31
Mar  7 07:20:37 faerun kernel:  [<ffffffff8029879e>] sys_writev+0x45/0x93
Mar  7 07:20:37 faerun kernel:  [<ffffffff8020be2e>] system_call+0x7e/0x83
Mar  7 07:20:37 faerun kernel: 
Mar  8 09:45:00 faerun kernel: klogd 1.5.0#2, log source = /proc/kmsg started.
Mar  8 09:45:00 faerun kernel: Initializing cgroup subsys cpuset
Mar  8 09:45:00 faerun kernel: Linux version 2.6.24-1-amd64 (Debian 2.6.24-4) (waldi@debian.org) (gcc version 4.1.3 20080114 (prerelease) (Debian 4.1.2-19)) #1 SMP Mon Feb 11 13:47:43 UTC 2008
Mar  8 09:45:00 faerun kernel: Command line: root=/dev/sda1 ro 
Mar  8 09:45:00 faerun kernel: BIOS-provided physical RAM map:

I've backed off to 2.6.22-3-amd64, and the flakiness has gone away.

-- Package-specific info:

-- System Information:
Debian Release: lenny/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.22-3-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages linux-image-2.6.24-1-amd64 depends on:
ii  debconf [debconf-2.0]        1.5.19      Debian configuration management sy
ii  initramfs-tools [linux-initr 0.91e       tools for generating an initramfs
ii  module-init-tools            3.3-pre11-4 tools for managing Linux kernel mo

linux-image-2.6.24-1-amd64 recommends no packages.

-- debconf information:
  linux-image-2.6.24-1-amd64/preinst/abort-overwrite-2.6.24-1-amd64:
  linux-image-2.6.24-1-amd64/postinst/old-dir-initrd-link-2.6.24-1-amd64: true
  linux-image-2.6.24-1-amd64/preinst/failed-to-move-modules-2.6.24-1-amd64:
  linux-image-2.6.24-1-amd64/postinst/bootloader-test-error-2.6.24-1-amd64:
  linux-image-2.6.24-1-amd64/postinst/create-kimage-link-2.6.24-1-amd64: true
  linux-image-2.6.24-1-amd64/postinst/depmod-error-initrd-2.6.24-1-amd64: false
  linux-image-2.6.24-1-amd64/preinst/overwriting-modules-2.6.24-1-amd64: true
  linux-image-2.6.24-1-amd64/postinst/bootloader-error-2.6.24-1-amd64:
  linux-image-2.6.24-1-amd64/postinst/old-initrd-link-2.6.24-1-amd64: true
  linux-image-2.6.24-1-amd64/postinst/kimage-is-a-directory:
  linux-image-2.6.24-1-amd64/preinst/bootloader-initrd-2.6.24-1-amd64: true
  linux-image-2.6.24-1-amd64/preinst/initrd-2.6.24-1-amd64:
  linux-image-2.6.24-1-amd64/prerm/removing-running-kernel-2.6.24-1-amd64: true
  linux-image-2.6.24-1-amd64/postinst/depmod-error-2.6.24-1-amd64: false
  shared/kernel-image/really-run-bootloader: true
  linux-image-2.6.24-1-amd64/preinst/lilo-initrd-2.6.24-1-amd64: true
  linux-image-2.6.24-1-amd64/postinst/old-system-map-link-2.6.24-1-amd64: true
  linux-image-2.6.24-1-amd64/preinst/lilo-has-ramdisk:
  linux-image-2.6.24-1-amd64/preinst/abort-install-2.6.24-1-amd64:
  linux-image-2.6.24-1-amd64/prerm/would-invalidate-boot-loader-2.6.24-1-amd64: true
  linux-image-2.6.24-1-amd64/preinst/elilo-initrd-2.6.24-1-amd64: true

--- End Message ---

--- Begin Message ---

To: 470070-done@bugs.debian.org

Subject: Re: Bug#470070: linux-image-2.6.24-1-amd64: Flaky file system problems in the last 3 days or so

From: maximilian attems <max@stro.at>

Date: Wed, 21 May 2008 12:31:38 +0200

Message-id: <20080521103138.GK27599@baikonur.stro.at>

In-reply-to: <4833768F.4060904@gmail.com>

References: <20080308234209.10209.47957.reportbug@faerun.comcast.net> <[🔎] 20080520161901.GV13383@stro.at> <4833768F.4060904@gmail.com>
Version: 2.6.25-1

On Tue, May 20, 2008 at 06:10:39PM -0700, Tom Epperly wrote:
>   
> The current kernel from unstable works without problems for me.
> 
> Thanks,
> 
> Tom

ok cool closing.

thanks for feedback.

-- 
maks
--- End Message ---

Reply to:

Prev by Date: Bug#482153: linux-image-2.6-686: Driver b43 fails to recover from hibernate
Next by Date: Bug#482164: firmware-qlogic: new firmware available
Previous by thread: Bug#401035: another workaround: use lvm
Next by thread: Bug#398948: .
Index(es):
- Date
- Thread