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

version graph

Package: linux-image-2.6.24-1-amd64; Maintainer for linux-image-2.6.24-1-amd64 is (unknown);

Reported by: Tom Epperly <tomepperly@comcast.net>

Date: Sat, 8 Mar 2008 23:45:05 UTC

Severity: normal

Tags: moreinfo

Found in version linux-2.6/2.6.24-4

Fixed in version 2.6.25-1

Done: maximilian attems <max@stro.at>

Bug is archived. No further changes may be made.

Toggle useless messages

View this report as an mbox folder, status mbox, maintainer mbox


Report forwarded to debian-bugs-dist@lists.debian.org, Debian Kernel Team <debian-kernel@lists.debian.org>:
Bug#470070; Package linux-image-2.6.24-1-amd64. Full text and rfc822 format available.

Acknowledgement sent to Tom Epperly <tomepperly@comcast.net>:
New Bug report received and forwarded. Copy sent to Debian Kernel Team <debian-kernel@lists.debian.org>. Full text and rfc822 format available.

Message #5 received at submit@bugs.debian.org (full text, mbox):

From: Tom Epperly <tomepperly@comcast.net>
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
Date: Sat, 08 Mar 2008 15:42:09 -0800
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




Information forwarded to debian-bugs-dist@lists.debian.org, Debian Kernel Team <debian-kernel@lists.debian.org>:
Bug#470070; Package linux-image-2.6.24-1-amd64. Full text and rfc822 format available.

Acknowledgement sent to Bastian Blank <waldi@debian.org>:
Extra info received and forwarded to list. Copy sent to Debian Kernel Team <debian-kernel@lists.debian.org>. Full text and rfc822 format available.

Message #10 received at 470070@bugs.debian.org (full text, mbox):

From: Bastian Blank <waldi@debian.org>
To: Tom Epperly <tomepperly@comcast.net>, 470070@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
Date: Sun, 9 Mar 2008 11:20:18 +0100
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




Tags added: moreinfo Request was from Bastian Blank <waldi@debian.org> to control@bugs.debian.org. (Sun, 09 Mar 2008 10:21:10 GMT) Full text and rfc822 format available.

Information forwarded to debian-bugs-dist@lists.debian.org, Debian Kernel Team <debian-kernel@lists.debian.org>:
Bug#470070; Package linux-image-2.6.24-1-amd64. Full text and rfc822 format available.

Acknowledgement sent to "Tom Epperly" <tepperly@gmail.com>:
Extra info received and forwarded to list. Copy sent to Debian Kernel Team <debian-kernel@lists.debian.org>. Full text and rfc822 format available.

Message #17 received at 470070@bugs.debian.org (full text, mbox):

From: "Tom Epperly" <tepperly@gmail.com>
To: 470070@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
Date: Sun, 9 Mar 2008 09:05:39 -0700
[Message part 1 (text/plain, inline)]
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.

Here is the list of modules loaded from
Linux faerun 2.6.22-3-amd64 #1 SMP Sun Nov 4 18:18:09 UTC 2007 x86_64
GNU/Linux
I am worried about booting 2.6.24-1-amd64 again because of the potential for
serious filesystem corruption.

faerun:/home/tepperly# cat /proc/modules
snd_rtctimer 8416 1 - Live 0xffffffff88c16000
binfmt_misc 17164 1 - Live 0xffffffff88c10000
nvidia 8898756 24 - Live 0xffffffff88392000 (P)
nfsd 260392 13 - Live 0xffffffff88351000
exportfs 10368 1 nfsd, Live 0xffffffff8834d000
lockd 72752 2 nfsd, Live 0xffffffff8833a000
nfs_acl 8064 1 nfsd, Live 0xffffffff88300000
sunrpc 186632 9 nfsd,lockd,nfs_acl, Live 0xffffffff8830b000
ppdev 13704 2 - Live 0xffffffff88306000
button 13472 0 - Live 0xffffffff882fb000
ac 10376 0 - Live 0xffffffff882f7000
battery 15496 0 - Live 0xffffffff882f2000
cpufreq_userspace 9472 0 - Live 0xffffffff882ee000
cpufreq_stats 10400 0 - Live 0xffffffff882ea000
cpufreq_powersave 6272 0 - Live 0xffffffff882e7000
ipv6 296840 28 - Live 0xffffffff8829d000
fuse 50608 1 - Live 0xffffffff8828f000
dm_crypt 18192 0 - Live 0xffffffff88289000
dm_snapshot 21704 0 - Live 0xffffffff88282000
dm_mirror 26240 0 - Live 0xffffffff8827a000
dm_mod 64112 3 dm_crypt,dm_snapshot,dm_mirror, Live 0xffffffff88269000
cpufreq_conservative 12424 0 - Live 0xffffffff88264000
cpufreq_ondemand 13328 1 - Live 0xffffffff8825f000
powernow_k8 18464 1 - Live 0xffffffff88259000
freq_table 9600 3 cpufreq_stats,cpufreq_ondemand,powernow_k8, Live
0xffffffff88255000
it87 27408 0 - Live 0xffffffff8824d000
hwmon_vid 7296 1 it87, Live 0xffffffff8824a000
i2c_isa 9344 1 it87, Live 0xffffffff88246000
eeprom 12432 0 - Live 0xffffffff88241000
loop 23044 0 - Live 0xffffffff8823a000
snd_mpu401 13864 0 - Live 0xffffffff88235000
snd_mpu401_uart 13440 1 snd_mpu401, Live 0xffffffff88230000
snd_intel8x0 41000 1 - Live 0xffffffff88224000
snd_ac97_codec 117464 1 snd_intel8x0, Live 0xffffffff88206000
ac97_bus 7168 1 snd_ac97_codec, Live 0xffffffff88203000
snd_pcm_oss 48288 0 - Live 0xffffffff881f6000
snd_pcm 89992 3 snd_intel8x0,snd_ac97_codec,snd_pcm_oss, Live
0xffffffff881df000
snd_mixer_oss 21376 1 snd_pcm_oss, Live 0xffffffff881d8000
snd_seq_dummy 8452 0 - Live 0xffffffff881d4000
snd_seq_oss 36736 0 - Live 0xffffffff881ca000
snd_seq_midi 13504 0 - Live 0xffffffff881c5000
snd_seq_midi_event 12416 2 snd_seq_oss,snd_seq_midi, Live 0xffffffff881c0000
snd_seq 58752 7 snd_seq_dummy,snd_seq_oss,snd_seq_midi,snd_seq_midi_event,
Live 0xffffffff881b0000
snd_rawmidi 30624 2 snd_mpu401_uart,snd_seq_midi, Live 0xffffffff881a7000
snd_timer 28424 3 snd_rtctimer,snd_pcm,snd_seq, Live 0xffffffff8819f000
snd_seq_device 12820 5
snd_seq_dummy,snd_seq_oss,snd_seq_midi,snd_seq,snd_rawmidi, Live
0xffffffff8819a000
snd 65896 15
snd_mpu401,snd_mpu401_uart,snd_intel8x0,snd_ac97_codec,snd_pcm_oss,snd_pcm,snd_mixer_oss,snd_seq_oss,snd_seq,snd_rawmidi,snd_timer,snd_seq_device,
Live 0xffffffff88188000
parport_pc 42664 1 - Live 0xffffffff8817c000
psmouse 45468 0 - Live 0xffffffff8816f000
pcspkr 7680 0 - Live 0xffffffff8816c000
soundcore 13088 1 snd, Live 0xffffffff88167000
snd_page_alloc 15376 2 snd_intel8x0,snd_pcm, Live 0xffffffff88162000
parport 44428 2 ppdev,parport_pc, Live 0xffffffff88156000
serio_raw 11780 0 - Live 0xffffffff88152000
k8temp 10496 0 - Live 0xffffffff8814e000
i2c_nforce2 10624 0 - Live 0xffffffff8814a000
i2c_core 31488 5 nvidia,it87,i2c_isa,eeprom,i2c_nforce2, Live
0xffffffff88141000
tsdev 13312 0 - Live 0xffffffff8813c000
evdev 15232 3 - Live 0xffffffff88137000
jfs 168016 5 - Live 0xffffffff8810c000
sd_mod 33280 7 - Live 0xffffffff88102000
ide_cd 44832 0 - Live 0xffffffff880f6000
cdrom 39848 1 ide_cd, Live 0xffffffff880eb000
generic 10372 0 [permanent], Live 0xffffffff880e7000
usbhid 32704 0 - Live 0xffffffff880de000
hid 31360 1 usbhid, Live 0xffffffff880d5000
sata_nv 25860 6 - Live 0xffffffff880cd000
amd74xx 19888 0 [permanent], Live 0xffffffff880c7000
ide_core 147728 3 ide_cd,generic,amd74xx, Live 0xffffffff880a1000
floppy 67560 0 - Live 0xffffffff8808f000
forcedeth 52872 0 - Live 0xffffffff8807f000
ata_generic 13188 0 - Live 0xffffffff88078000
libata 132528 2 sata_nv,ata_generic, Live 0xffffffff88056000
scsi_mod 164536 2 sd_mod,libata, Live 0xffffffff8802c000
ehci_hcd 37900 0 - Live 0xffffffff8801f000
ohci_hcd 25860 0 - Live 0xffffffff88015000
thermal 19600 0 - Live 0xffffffff8800f000
processor 39912 2 powernow_k8,thermal, Live 0xffffffff88004000
fan 9992 0 - Live 0xffffffff88000000

I am attaching the complete log from boot to reboot.

Tom
[Message part 2 (text/html, inline)]
[kern.log (text/x-log, attachment)]

Information forwarded to debian-bugs-dist@lists.debian.org, Debian Kernel Team <debian-kernel@lists.debian.org>:
Bug#470070; Package linux-image-2.6.24-1-amd64. Full text and rfc822 format available.

Acknowledgement sent to maximilian attems <max@stro.at>:
Extra info received and forwarded to list. Copy sent to Debian Kernel Team <debian-kernel@lists.debian.org>. Full text and rfc822 format available.

Message #22 received at 470070@bugs.debian.org (full text, mbox):

From: maximilian attems <max@stro.at>
To: Tom Epperly <tomepperly@comcast.net>, 470070@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
Date: Tue, 20 May 2008 18:19:01 +0200
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





Reply sent to maximilian attems <max@stro.at>:
You have taken responsibility. Full text and rfc822 format available.

Notification sent to Tom Epperly <tomepperly@comcast.net>:
Bug acknowledged by developer. Full text and rfc822 format available.

Message #27 received at 470070-done@bugs.debian.org (full text, mbox):

From: maximilian attems <max@stro.at>
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
Date: Wed, 21 May 2008 12:31:38 +0200
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




Bug archived. Request was from Debbugs Internal Request <owner@bugs.debian.org> to internal_control@bugs.debian.org. (Mon, 11 Aug 2008 09:25:31 GMT) Full text and rfc822 format available.

Send a report that this bug log contains spam.


Debian bug tracking system administrator <owner@bugs.debian.org>. Last modified: Thu Apr 17 04:24:06 2014; Machine Name: beach.debian.org

Debian Bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.