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

This is a discussion on Bug#470070: linux-image-2.6.24-1-amd64: Flaky file system problems in the last 3 days or so - Debian ; 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 ...

+ Reply to Thread
Results 1 to 4 of 4

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

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

    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: [] bad_page+0x63/0x8d
    Mar 7 07:20:37 faerun kernel: [] free_hot_cold_page+0x8c/0x13d
    Mar 7 07:20:37 faerun kernel: [] :jfs:txUnlock+0xc8/0x215
    Mar 7 07:20:37 faerun kernel: [] :jfs:jfs_lazycommit+0xf8/0x22b
    Mar 7 07:20:37 faerun kernel: [] default_wake_function+0x0/0xe
    Mar 7 07:20:37 faerun kernel: [] :jfs:jfs_lazycommit+0x0/0x22b
    Mar 7 07:20:37 faerun kernel: [] kthread+0x47/0x74
    Mar 7 07:20:37 faerun kernel: [] child_rip+0xa/0x12
    Mar 7 07:20:37 faerun kernel: [] kthread+0x0/0x74
    Mar 7 07:20:37 faerun kernel: [] 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:[] [] 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: [] :jfsut_metapage+0xef/0xfd
    Mar 7 07:20:37 faerun kernel: [] :jfs:txUnlock+0x149/0x215
    Mar 7 07:20:37 faerun kernel: [] :jfs:jfs_lazycommit+0xf8/0x22b
    Mar 7 07:20:37 faerun kernel: [] default_wake_function+0x0/0xe
    Mar 7 07:20:37 faerun kernel: [] :jfs:jfs_lazycommit+0x0/0x22b
    Mar 7 07:20:37 faerun kernel: [] kthread+0x47/0x74
    Mar 7 07:20:37 faerun kernel: [] child_rip+0xa/0x12
    Mar 7 07:20:37 faerun kernel: [] kthread+0x0/0x74
    Mar 7 07:20:37 faerun kernel: [] 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 [] unlock_page+0xf/0x26
    Mar 7 07:20:37 faerun kernel: RSP
    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: [] bad_page+0x63/0x8d
    Mar 7 07:20:37 faerun kernel: [] get_page_from_freelist+0x3fc/0x5e6
    Mar 7 07:20:37 faerun kernel: [] __alloc_pages+0x66/0x309
    Mar 7 07:20:37 faerun kernel: [] schedule_timeout+0x1e/0xad
    Mar 7 07:20:37 faerun kernel: [] remove_wait_queue+0x12/0x45
    Mar 7 07:20:37 faerun kernel: [] __grab_cache_page+0x33/0x6f
    Mar 7 07:20:37 faerun kernel: [] nobh_write_begin+0x73/0x3b2
    Mar 7 07:20:37 faerun kernel: [] :jfs:jfs_get_block+0x0/0x233
    Mar 7 07:20:37 faerun kernel: [] :jfs:jfs_write_begin+0x1b/0x20
    Mar 7 07:20:37 faerun kernel: [] :jfs:jfs_get_block+0x0/0x233
    Mar 7 07:20:37 faerun kernel: [] generic_file_buffered_write+0x150/0x652
    Mar 7 07:20:37 faerun kernel: [] current_fs_time+0x1e/0x24
    Mar 7 07:20:37 faerun kernel: [] :jfs:jfs_getxattr+0xd/0x12
    Mar 7 07:20:37 faerun kernel: [] __generic_file_aio_write_nolock+0x33f/0x3a9
    Mar 7 07:20:37 faerun kernel: [] sock_recvmsg+0xf0/0x10f
    Mar 7 07:20:37 faerun kernel: [] generic_file_aio_write+0x61/0xc1
    Mar 7 07:20:37 faerun kernel: [] generic_file_aio_write+0x0/0xc1
    Mar 7 07:20:37 faerun kernel: [] do_sync_readv_writev+0xc0/0x107
    Mar 7 07:20:37 faerun kernel: [] autoremove_wake_function+0x0/0x2e
    Mar 7 07:20:37 faerun kernel: [] getname+0x14c/0x1b3
    Mar 7 07:20:37 faerun kernel: [] _atomic_dec_and_lock+0x39/0x58
    Mar 7 07:20:37 faerun kernel: [] rw_copy_check_uvector+0x6c/0xdc
    Mar 7 07:20:37 faerun kernel: [] do_readv_writev+0xcf/0x1a6
    Mar 7 07:20:37 faerun kernel: [] sys_newstat+0x28/0x31
    Mar 7 07:20:37 faerun kernel: [] sys_writev+0x45/0x93
    Mar 7 07:20:37 faerun kernel: [] 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



    --
    To UNSUBSCRIBE, email to debian-bugs-dist-REQUEST@lists.debian.org
    with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

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

    tags 470070 moreinfo
    thanks

    On Sat, Mar 08, 2008 at 03:42:09PM -0800, Tom Epperly wrote:
    > 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:


    Your kernel is tainted with some proprietary module. You have to
    reproduce without and provide several other informations
    - complete log and
    - loaded modules.

    Bastian

    --
    The sight of death frightens them [Earthers].
    -- Kras the Klingon, "Friday's Child", stardate 3497.2



    --
    To UNSUBSCRIBE, email to debian-bugs-dist-REQUEST@lists.debian.org
    with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

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

    On Sat, 08 Mar 2008, Tom Epperly wrote:

    > I believe the only tainted module is nvidia. I realize that tainted is
    > tainted, but in the past, some kernel people have been willing to work on
    > issues that included a kernel tainted with just nvidia.


    "just" is a funny expression with module that is much bigger then
    the kernel itself. either you run a free os or you don't.

    can you reproduce without nvidia and with 2.6.25 from unstable?


    thanks

    --
    maks




    --
    To UNSUBSCRIBE, email to debian-bugs-dist-REQUEST@lists.debian.org
    with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

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


    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


+ Reply to Thread